• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: How can I fix Device 0 bad blocks / bad magic number error  (Read 1833 times)
laternerdz
Newbie
*

Karma: 0
Posts: 6


View Profile
« on: August 08, 2009, 11:42:53 AM »

Hi, everyone. I recently got my sheevaplug (yesterday) and immediately set to SSH'ing in (which was very easy) and then I wanted to change the U-BOOT to boot from an SD card.

I go through this tutorial: http://plugcomputer.org/plugwiki/index.php/SD_Card_As_Root_File_System

Along the way I notice that the mini USB plug is very easy to knock out and accidentally interrupt the serial connection.

Everything is working, I'm booting from the SD card but my NAND isn't showing in the df test and I can't mount it. This is kind of concerning but I go ahead and commit the changes to uboot because everything else seems to be working.

After I saveenv and reset, I get the NAND: ECC error. I go to the forums and try a number of things. Now I'm here and nothing I do seems to change this:

Code:
Marvell>> boot

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-03-19   9:18:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106696 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
Marvell>> nand bad

Device 0 bad blocks:
  07980000
  119a0000
  124c0000
  124e0000
  12500000
  12520000
  12540000
  12560000
  12580000
  125a0000
  15020000
  16e00000
  17fe0000
  19920000
  1b6a0000
  1d220000
  1ff40000
Marvell>>

Here is my printenv:
Code:
Marvell>> printenv
loads_echo=0
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
ethmtu=1500
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootcmd=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
ethaddr=00:50:43:4c:02:26
run_diag=no
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
baudrate=115200=loads_echo=0 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 console=console=ttyS0,115200 CASset=min
MALLOC_len=1=ethprime=egiga0 bootargs_root=root=/dev/mtdblock2 ro ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 serverip=10.10.0.2
ipaddr=10.10.0.1=cesvcid=ULULULULULULPPULULULULULDA bootargs_end=:::DB88FXX81:eth0:none image_name=uImage
standalone=fsload=0x2000000 uImage
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs=mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 yuk_ethaddr=00:00:00:EE:51:81
netretry=no=rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no ethaddr=00:50:43:01:D1:CA run_diag=no
bootargs=console=ttyS0,115200=mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw
ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none=bootcmd=nand read.e 0x800000 0x100000 0x400000
stdin=serial=stdout=serial stderr=serial mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes
enaICPref=yes=enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=3 disaMvPnp=no enaAutoRecovery=yes

Environment size: 1989/131068 bytes
Marvell>>

I expect I have to factory restore or something and I started to look into that but the CD that came with my Sheeva doesn't work in my Macbook for some reason and the only PC I have around is a Asus EEE. :\

Are there any quick fixes to this? (maybe some hardcore soldering or wire shorting I could do... j/k)
Logged

nikad
Newbie
*

Karma: 0
Posts: 1


View Profile
« Reply #1 on: September 18, 2009, 02:32:18 AM »

I have also had this issue following the same link, not sure if it was through loosing a connection on the USB but that has happened.

One way I did manage to get the SheevaPlug to boot was to boot using the tftp options though that does not seem to be stable either (sometimes I get CRC errors once I have not).

Is it possible to have a set of instructions on resetting the sheeva back to it's original settings? I have set all the boot arguments back and tried to perform a full reset, but these do not seem to work.

Ideally I would like an installer under windows that will do everything to reset the SheevaPlug, but a set of instructions would suffice (what to set the boot args too, how to boot the device and how to restore the images either by tftp or directly with the USB).

Although any help would be appreciated.

BTW I do have a second SheevaPlug but I do not want to use that until I have this one working (unless it is for retrieving images/settings for the original device).

Thank you
Keith
Logged

Catalina
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #2 on: September 18, 2009, 07:29:35 PM »

I haven't had your problem, but I know of a good way to reburn your ROM.  The installer utility (http://www.openplug.org/index.php/us/resources/downloads?func=fileinfo&id=53) will reflash the bootloader (uboot), kernel and filesystem.  I've used it a number of times with good results.  I reflash using a Linux host, but the documentation says the installer works on Windows as well (other users have reported success with a Windows host).  It won't get you back to the original state, as the included files are more recent builds, but they have worked better than the originals for me (the originals had a number of warnings on power up, and they were probably 3-4 times slower to boot).
Logged

Pages: [1]
Print
Jump to: