Not accessible after upgrade to v1.1.0rc12

DOWNLOAD THE LATEST FIRMWARE HERE
User avatar
sirhc
Employee
Employee
 
Posts: 7490
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1643 times
Been thanked: 1336 times

Re: Not accessible after upgrade to v1.1.0rc12

Sat Jan 24, 2015 6:58 pm

One thing you can try is when it starts booting and you start seeing the text below press and hold the default button in with a paper clip.
When you see the lines below in red you can let out and then wait a few minutes as it will re format the read/write flash partition

BusyBox v1.11.2 (2015-01-12 16:20:46 EST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
Segmentation fault
root@OpenWrt:/# cmd
/bin/ash: cmd: not found
root@OpenWrt:/# cat config.php | \
> grep -v "<<<<<<< HEAD" | \
> grep -v "=======" | \
> grep -v "Config::save(\$config, false);" | \
> grep -v ">>>>>>> remotes/origin/1.0.10" > config.php
cat: can't open 'config.php': No such file or directory
root@OpenWrt:/# reboot
root@OpenWrt:/# echo Done+M25PXX : Init device with JEDEC ID 0x202018.
Luton26 board detected (VSC7427 Rev. D).
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version 1_18-Vitesse - built 05:56:33, Jan 31 2014
Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
Free Software Foundation, Inc.
RedBoot is free software, covered by the eCos license, derived from the
GNU General Public License. You are welcome to change it and/or distribute
copies of it under certain conditions. Under the license terms, RedBoot's
source code and full license terms must have been made available to you.
Redboot comes with ABSOLUTELY NO WARRANTY.
Platform: VCore-III (MIPS32 24KEc) LUTON26
RAM: 0x80000000-0x88000000 [0x80021b68-0x87fafffc available]
FLASH: 0x40000000-0x40ffffff, 64 x 0x40000 blocks
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load -d linux
Image loaded from 0x80100000-0x8036422c
RedBoot> go
Linux version 2.6.26.8 (dev@netonixdev) (gcc version 4.1.2) #7 Fri Jan 23 16:21:05 EST 2015
Invalid kernel arglist - use RedBoot "exec" command to boot kernel.
Using predefined kernel options.
CPU revision is: 02019654 (MIPS 24K)
Determined physical RAM map:
User-defined physical RAM map:
memory: 08000000 @ 00000000 (usable)
Zone PFN ranges:
Normal 0 -> 32768
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: console=ttyS0,115200 init=/etc/preinit mem=128M
Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=80000000
Readback ErrCtl register=80000000
Cache parity protection enabled
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 126052k/131072k available (1917k kernel code, 4840k reserved, 417k data, 116k init, 0k highmem)
SLUB: Genslabs=6, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
net_namespace: 640 bytes
NET: Registered protocol family 16
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 246
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x70100000 (irq = 14) is a 16550A
console [ttyS0] enabled
No NAND device found!!!
m25p80 spi0.0: m25p128 (16384 Kbytes)
Mapped SPI read area @0x40000000 len 16777216
Creating 10 MTD partitions on "m25p80":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x00080000 : "config"
0x00080000-0x001c0000 : "linux_recovery"
0x001c0000-0x003c0000 : "rootfs_recovery"
0x003c0000-0x00500000 : "linux"
0x00500000-0x00b00000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
0x00b00000-0x00f40000 : "rootfs_data"
0x00f40000-0x00f80000 : "FIS directory"
0x00f80000-0x00f81000 : "RedBoot config"
0x00fc0000-0x01000000 : "Redundant FIS"
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 116k freed
Please be patient, while OpenWrt loads ...
Algorithmics/MIPS FPU Emulator v1.5
- preinit -
Press CTRL-C for failsafe
Press and HOLD default button now for reset to factory defaults
mounting jffs2
switching to jffs2
mini_fo: using base directory: /
mini_fo: using storage directory: /jffs
- init -
Please press Enter to activate this console. vtss_core: module license '(c) Vitesse Semiconductor Inc.' taints kernel.
switch: 'Luton26' board detected
nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
i2c /dev entries driver
i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19


It should then indicate that the button was pressed and it is defaulting, you will need to wait a few minutes while it does it thing but then you will need to press enter and then past Eric text in. FINGERS CROSSED

Hit ENTER to get to the "Netonix Switch#" prompt, then copy/paste the following commands:

Code: Select all
cmd
cat config.php | \
grep -v "<<<<<<< HEAD" | \
grep -v "=======" | \
grep -v "Config::save(\$config, false);" | \
grep -v ">>>>>>> remotes/origin/1.0.10" > config.php
reboot
echo Done


The switch should then reboot and come up running as usual. Now upgrade to 1.1.0rc13.

After seeing the capture of the text from your switches console boot above in your PM I a sure we can recover this as it is booting fine with all the stuff needed for us to recover this tomorrow. I would give you instructions on the emergency recover but I have never had to use it and I would be like a doctor practicing without a license and could mess up your flash image beyond repair.

We need to make a post on the recovery procedure, it was on mine and Eric list to do it but one of the things we never got around to yet. It involved the line above the red line shown above "Press CTRL-C for failsafe" but please wait to try that with Eric please if my suggestion does not work.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

User avatar
sirhc
Employee
Employee
 
Posts: 7490
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1643 times
Been thanked: 1336 times

Re: Not accessible after upgrade to v1.1.0rc12

Sat Jan 24, 2015 7:18 pm

Another option is watch it when it boots on the console and when the line below in red pops up immediately press Enter because this is just the basic Linux kernel provided by the Vitesse SDK before we start loading our stuff, well most of our stuff we do have some kernel code



mini_fo: using storage directory: /jffs
- init -
Please press Enter to activate this console. vtss_core: module license '(c) Vitesse Semiconductor Inc.' taints kernel.
switch: 'Luton26' board detected
nf_conntrack version 0.5.0 (2048 buckets, 8192 max)

Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

User avatar
Eric Stern
Employee
Employee
 
Posts: 532
Joined: Wed Apr 09, 2014 9:41 pm
Location: Toronto, Ontario
Has thanked: 0 time
Been thanked: 130 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 2:56 pm

overkill wrote:I cannot get to the "Netonix Switch#" prompt. I'm getting "Segmentation fault."


In that case you must already be at the linux command line, so just copy/paste these commands (a slight variation of above):

Code: Select all
cd /www
cat config.php | \
grep -v "<<<<<<< HEAD" | \
grep -v "=======" | \
grep -v "Config::save(\$config, false);" | \
grep -v ">>>>>>> remotes/origin/1.0.10" > config.php
reboot
echo Done


User avatar
overkill
Member
 
Posts: 8
Joined: Sun Dec 14, 2014 11:32 pm
Has thanked: 3 times
Been thanked: 5 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 4:44 pm

That did it!

User avatar
sirhc
Employee
Employee
 
Posts: 7490
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1643 times
Been thanked: 1336 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 7:57 pm

overkill wrote:That did it!


Did you then upgrade to v1.1.0rc13
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

User avatar
overkill
Member
 
Posts: 8
Joined: Sun Dec 14, 2014 11:32 pm
Has thanked: 3 times
Been thanked: 5 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 9:17 pm

Yes; no problems.

User avatar
mhoppes
Associate
Associate
 
Posts: 665
Joined: Thu Apr 10, 2014 9:14 pm
Location: Pennsylvania
Has thanked: 10 times
Been thanked: 125 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 9:41 pm

Just upgraded from 1.0.9 to 1.1.0rc13 and so far things seem to be working well.

Switch booted up and no password problems.

User avatar
sirhc
Employee
Employee
 
Posts: 7490
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1643 times
Been thanked: 1336 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 9:47 pm

mhoppes wrote:Just upgraded from 1.0.9 to 1.1.0rc13 and so far things seem to be working well.

Switch booted up and no password problems.


How many switches do you have in service now Matt?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

User avatar
mhoppes
Associate
Associate
 
Posts: 665
Joined: Thu Apr 10, 2014 9:14 pm
Location: Pennsylvania
Has thanked: 10 times
Been thanked: 125 times

Re: Not accessible after upgrade to v1.1.0rc12

Sun Jan 25, 2015 9:52 pm

Thinking.... 6 or 7 at this point.

User avatar
lligetfa
Associate
Associate
 
Posts: 1191
Joined: Sun Aug 03, 2014 12:12 pm
Location: Fort Frances Ont. Canada
Has thanked: 307 times
Been thanked: 381 times

Re: Not accessible after upgrade to v1.1.0rc12

Mon Jan 26, 2015 9:32 pm

It took me a lot longer but I'm back up and running. I didn't have a serial cable at home so I had to wait for the stores to open today. I had a hard time to track one down... first stop was a waste of time... nothing at all with DB9 male or female, no gender changers, no null modems, not even the ends to solder up my own. Second stop was not looking too good... I walk in the store and find out they laid off all their computer techs but then I got to rummage through some dusty old inventory and got lucky. :hurray:

When I got home, I needed to figure out how to use the serial port on the docking bay of my linux laptop. It is the only device that I have with a serial port. At work I used to use Windows with hyperterm.

I also upgraded the switch to rc13.

PreviousNext
Return to Hardware and software issues

Who is online

Users browsing this forum: Google [Bot] and 31 guests