Earl
bad crc and ro serial console unbrick? January 29, 2014 09:56AM |
U-Boot 1.1.4 Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00691750 Soc: 88F6281 A1 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 128MB DRAM Total size 128MB 16bit width Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:256 MB Flash: 0 kB CPU : Marvell Feroceon (Rev 1) CLOUD ENGINES BOARD (GUESSED): DISCOVERY:0.1 Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME] Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x100000, size 0x300000 Reading data from 0x3ff800 -- 100% complete. 3145728 bytes read: OK ## Booting image at 00800000 ... Image Name: Linux-2.6.32.18-dockstar Created: 2011-02-17 8:10:10 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3236180 Bytes = 3.1 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... Bad Data CRC CE>>
Re: bad crc and ro serial console unbrick? January 29, 2014 10:53AM |
Admin Registered: 13 years ago Posts: 19,106 |
setenv serverip 192.168.0.100 setenv ipaddr 192.168.0.200 tftp 0x800000 uboot.kwb nand erase 0x0 0x80000 nand write.e 0x800000 0x0 0x80000
Earl
Re: bad crc and ro serial console unbrick? January 29, 2014 03:49PM |
Re: bad crc and ro serial console unbrick? January 29, 2014 03:54PM |
Registered: 10 years ago Posts: 10 |
Re: bad crc and ro serial console unbrick? January 29, 2014 06:12PM |
Admin Registered: 13 years ago Posts: 19,106 |
Re: bad crc and ro serial console unbrick? January 29, 2014 07:15PM |
Registered: 10 years ago Posts: 10 |
rescue:~# ifdown eth0 /bin/sh: can't create /sys/class/leds/dockstar:green:health/trigger: nonexistent directory rescue:~# ifup eth0 udhcpc (v1.17.1) started Sending discover... Sending discover... Sending select for 192.168.0.230... Sending select for 192.168.0.230... Sending select for 192.168.0.230... Lease of 192.168.0.230 obtained, lease time 604800 deleting routers route: SIOCDELRT: No such process adding dns 192.168.0.1 /bin/sh: can't create /sys/class/leds/dockstar:green:health/trigger: nonexistent directory rescue:~#
Re: bad crc and ro serial console unbrick? January 29, 2014 07:54PM |
Admin Registered: 13 years ago Posts: 19,106 |
Re: bad crc and ro serial console unbrick? January 29, 2014 10:42PM |
Registered: 10 years ago Posts: 10 |
Re: bad crc and ro serial console unbrick? January 30, 2014 10:04AM |
Registered: 10 years ago Posts: 10 |
Error: unrecognized/unsupported machine ID (r1 = 0x00000d0a). Available machine support: ID (hex) NAME 00000690 Marvell DB-88F6281-BP Development Board 00000691 Marvell RD-88F6192-NAS Development Board 00000692 Marvell RD-88F6281 Reference Board 0000078c Marvell 88F6281 GTW GE Board 00000831 Marvell SheevaPlug Reference Board 00000bb6 Seagate FreeAgent DockStar 00000c11 Seagate Goflex Net 0000085b QNAP TS-119/TS-219 00000915 Marvell OpenRD Base Board Please check your kernel config and/or bootloader.
Re: bad crc and ro serial console unbrick? January 31, 2014 12:50PM |
Admin Registered: 13 years ago Posts: 19,106 |
ls -lR /sys/class/leds
Re: bad crc and ro serial console unbrick? February 01, 2014 07:09PM |
Registered: 10 years ago Posts: 10 |
/sys/class/leds: total 0 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:green:health -> ../../devices/platform/leds-gpio/leds/status:green:health lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:orange:fault -> ../../devices/platform/leds-gpio/leds/status:orange:fault lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:left0 -> ../../devices/platform/leds-gpio/leds/status:white:left0 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:left1 -> ../../devices/platform/leds-gpio/leds/status:white:left1 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:left2 -> ../../devices/platform/leds-gpio/leds/status:white:left2 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:left3 -> ../../devices/platform/leds-gpio/leds/status:white:left3 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:right0 -> ../../devices/platform/leds-gpio/leds/status:white:right0 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:right1 -> ../../devices/platform/leds-gpio/leds/status:white:right1 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:right2 -> ../../devices/platform/leds-gpio/leds/status:white:right2 lrwxrwxrwx 1 root root 0 Feb 1 20:05 status:white:right3 -> ../../devices/platform/leds-gpio/leds/status:white:right3
cd /tmp wget http://jeff.doozan.com/debian/rescue/install_rescue.sh chmod +x install_rescue.sh ./install_rescue.sh
Re: bad crc and ro serial console unbrick? February 02, 2014 03:02AM |
Admin Registered: 13 years ago Posts: 19,106 |
# turn on LED if [ -d /sys/class/leds/status:green:health ]; then echo default-on > /sys/class/leds/status:green:health/trigger if [ -d /sys/class/leds/status:orange:fault ]; then echo none > /sys/class/leds/status:orange:fault/trigger fi fi exit 0To turn off the status LED before shutting down, put these in your /etc/rc0.d/Kxxhalt (xx could be 07, 08,… depending on each system installation) before the halt command. Note that it's prudent to wait about 10 seconds for the HDD to spin down before power off.
log_action_msg "Will now halt" if [ -d /sys/class/leds/status:green:health ]; then echo none > /sys/class/leds/status:green:health/trigger fi halt -d -f $netdown $poweroff $hddown }
cat /etc/udev/rules.d/70-persistent-net.rules | grep SUBSYSTEM cat /lib/udev/rules.d/75-persistent-net-generator.rules | grep -i -C3 'device name whitelist'See this post for a possible solution if it is related to udev rules: http://forum.doozan.com/read.php?2,13053,13070#msg-13070
Re: bad crc and ro serial console unbrick? February 02, 2014 07:34AM |
Registered: 10 years ago Posts: 10 |