General NAS-Central Forums

Welcome to the NAS community
It is currently Tue Oct 17, 2017 6:33 pm

All times are UTC




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: ix2-dl Bad eraseblock
PostPosted: Mon Mar 14, 2016 3:04 am 
Offline

Joined: Mon Mar 14, 2016 2:00 am
Posts: 3
Ok, I need help. I've been trying to recover an ix2-dl that is not cooperating. It's been a bit of a saga, so I won't recap everything here (though I will fill in the details wherever necessary). It lost the ability to connect via ethernet (which killed my ssh access). I purchased a TTL-USB converter and got the serial output up. I found instructions on how to recover the firmware here. The process appeared to succeed. I thought I had my terminal window saving the output, but alas it did not. So I don't have the log for that. On next boot, I was dismayed to see a ton of "bad eraseblock" messages flying by on the screen.

Cutting to the chase... Is there a way to reset the bad block table? From the output (pasted below), it looks like the recovery process fails in the end due to "No space left on device". This makes sense if the entire nand device is reported a bad block after bad block.

I looked through the commands available at the Marvell prompt (i.e., after hitting a key to cancel boot), but didn't see anything that looked helpful. I wouldn't just go poking around in there without understanding what I"m doing anyway. I've spent a lot of time trying to Google this to see who has had the same problem with no luck. I'm starting to feel like whatever happened isn't going to be reversible, but I'm hoping someone here can prove me wrong. Thanks to anyone who can help.

I left off the earlier section of the boot log just for brevity's sake. I can post what's before here, if it will be helpful.
Code:
Warning: Giga 1 is Powered Off

tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
 sda:
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
 unknown partition table
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
mvSFlashInit ERROR: Unknown SPI flash device!
ERROR: sflash_probe - Failed to initialize the SFlash.Using Hamming 1-bit ECC for NAND device
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Bad eraseblock 1 at 0x000000020000
Bad eraseblock 2 at 0x000000040000
Bad eraseblock 3 at 0x000000060000


This goes on... literally every block is marked bad. We pick up near the end:
Code:
Bad eraseblock 8188 at 0x00003ff80000
Bad eraseblock 8189 at 0x00003ffa0000
Bad eraseblock 8190 at 0x00003ffc0000
Bad eraseblock 8191 at 0x00003ffe0000
7 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 7 MTD partitions on "nand_mtd":
0x000000000000-0x000000080000 : "uboot"
 sdb:
sd 0:0:0:0: [sda] Attached SCSI disk
0x0000000a0000-0x0000000c0000 : "env"
0x0000000c0000-0x0000000e0000 : "env2"
0x000000100000-0x000000400000 : "uImage"
0x000000400000-0x000000700000 : "initrd"
0x000000800000-0x000040000000 : "boot"
0x000000000000-0x000040000000 : "flash"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
 sdb1
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sdb] Attached SCSI disk
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
adt7473 0-002e: adt7473 chip found
iBoard_model 2
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 5
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc mv_rtc: setting system clock to 2015-12-15 22:23:22 UTC (1450218202)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
RAMDISK: gzip image found at block 0
usb 1-1: new high speed USB device using ehci_marvell and address 2
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 1:0.
Looking for shell in cmdline: console=ttyS0,115200 root=/dev/ram0 :::DB88FXX81:eth0:none mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000(uImage),0x300000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(fusb 1-1: configuration #1 chosen from 1 choice
lash)
Make nodescsi2 : SCSI emulation for USB Mass Storage devices
 for mtd devices
HDD /dev/sda detected
HDD /dev/sdb detected
FLASH based system detected
Create fw_env.config in /etc
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error : Warning: Bad CRC, using default environment
## Error: "mfgmodel" not defined
M
UBI: attaching mtd5 to ubi0
odel name is ix2UBI: physical eraseblock size:   131072 bytes (128 KiB)
-ng
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 14:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 241:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 604:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 1240:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1562:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 1562:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 1803:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 2044:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 2418:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 2445:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 2980:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 3114:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 3114:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 3248:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 3248:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 3275:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 3810:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 3837:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 3971:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 4878:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 4878:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 5278:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5278:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5678:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5812:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 7438:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 7572:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 7599:0, read 64 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 7599:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 8107:512, read 512 bytes
UBI error: ubi_read_volume_table: the layout volume was not found
ubiattach: error!: cannot attach mtd5
           error 22 (Invalid argument)
mdadm: cannot open /dev/sda1: No such device or address
cat: can't open '/sys/block/sda/sda1/size': No such file or directory
Valid Disk 1 in md0:
Valid Disk 2 in md0:
USB Device node is /dev/sdc1
Checking to see the if the reset button is pressed or not
Checking if there is an attached EMC Imager
scsi 2:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 2
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:0:0: [sdc] 4112384 512-byte logical blocks: (2.10 GB/1.96 GiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Checking for pre-image script... none.
Image tar file found: /usb_drive/emctools/ix2-ng_images/*.tgz
Extract Image tar file.
apps
apps.md5
config
config.md5
initrd
initrd.md5
oem
oem.md5
zImage
zImage.md5
apps is valid
config is valid
initrd is valid
zImage is valid
Found EMC Imager with apps and config image...
Started USB Imaging...
md: md0 stopped.
mdadm: stopped /dev/md0
mdadm: /dev/md0 not identified in config file.
---Mounting volume
UBIFS error (pid 707): ubifs_get_sb: cannot open "ubi0:boot", error -19
mount: mounting ubi0:boot on sysroot/boot failed: No such device
Going to do a full install
umount: cannot umount /sysroot/boot: Invalid argument
---Stop volumes
  Volume group "md0_vg" not found
---Stop raid
md: md0 stopped.
mdadm: stopped /dev/md0
---destroy raid
mdadm: Couldn't open /dev/sda1 for write - not zeroing
mdadm: Unrecognised md component device - /dev/sdb1
---Prepping drive: sda
Error: /dev/sda: unrecognised disk label
Error: /dev/sda: unrecognised disk label
10000+0 records in
10000+0 records out
---Creating partition on /dev/sda

                                                                         
Information: You may need to update /etc/fstab.


                                                                         
Information: You may need to update /etc/fstab.

---Prepping drive: sdb
Error: Partition doesn't exist.
10000+0 records in
10000+0 records out
---Creating partition on /dev/sdb

                                                                         
Information: You may need to update /etc/fstab.


                                                                         
Information: You may need to update /etc/fstab.

---Prepping flash
ubidetach: error!: cannot detach mtd5
           error 19 (No such device)

Skipping bad block at 0x00000000

Skipping bad block at 0x00020000

Skipping bad block at 0x00040000

Skipping bad block at 0x00060000

Skipping bad block at 0x00080000

Skipping bad block at 0x000a0000

Skipping bad block at 0x000c0000

Skipping bad block at 0x000e0000

Skipping bad block at 0x00100000

Skipping bad block at 0x00120000

Skipping bad block at 0x00140000

Skipping bad block at 0x00160000

Skipping bad block at 0x00180000

Skipping bad block at 0x001a0000

Erasing 128 Kibyte @ 1c0000 --  0 % complete.
Skipping bad block at 0x001e0000

Skipping bad block at 0x00200000


And again, this goes on to cover all bad blocks... skipping ahead...
Code:
Skipping bad block at 0x3f780000

Skipping bad block at 0x3f7a0000

Skipping bad block at 0x3f7c0000

Skipping bad block at 0x3f7e0000

UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 3810:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 4105:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 4878:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5278:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5678:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5812:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 7438:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 7599:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 7840:512, read 512 bytes
uncorrectable error :
UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 8107:512, read 512 bytes
UBI error: ubi_read_volume_table: the layout volume was not found
ubiattach: error!: cannot attach mtd5
           error 22 (Invalid argument)
ubimkvol: error!: "/dev/ubi0" is not an UBI device node
---Starting raid
mdadm: /dev/sda1 appears to be part of a raid array:
    level=raid1 devices=2 ctime=Tue Dec 15 21:37:50 2015
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
mdadm: Defaulting to version 1.2 metadata
md: bind<sda1>
raid1: raid set md0 active with 1 out of 2 mirrors
md0: detected capacity change from 0 to 21457928192
mdadm: array /dev/md0 started.
---Creating volumes
 md0: unknown partition table
  WARNING: Forcing physical volume creation on /dev/md0 of volume group "md0_vg"
  Physical volume "/dev/md0" successfully created
  Volume group "md0_vg" successfully created
  Logical volume "BFDlv" created
---Formatting partitions
mke2fs 1.42.5 (29-Jul-2012)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/md0_vg/BFDlv is mounted.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
262144 inodes, 1048576 blocks
52428 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1073741824
32 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables:  0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32     done                           
Writing inode tables:  0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32     done                           
Writing superblocks and filesystem accounting information:  0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32     done

---Mounting volume
UBIFS error (pid 770): ubifs_get_sb: cannot open "ubi0:boot", error -19
mount: mounting ubi0:boot on sysroot/boot failed: No such device
---Copying system image files
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
Copied apps config and oem image
BusyBox v1.9.2 (2013-04-08 13:28:37 EDT) multi-call binary

Usage: cp [OPTION]... SOURCE DEST

Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY

Options:
-aSame as -dpR
-d,-PPreserve links
-H,-LDereference all symlinks (default)
-pPreserve file attributes if possible
-fForce overwrite
-iPrompt before overwrite
-R,-rRecurse directories
-l,-sCreate (sym)links

BusyBox v1.9.2 (2013-04-08 13:28:37 EDT) multi-call binary

Usage: cp [OPTION]... SOURCE DEST

Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY

Options:
-aSame as -dpR
-d,-PPreserve links
-H,-LDereference all symlinks (default)
-pPreserve file attributes if possible
-fForce overwrite
-iPrompt before overwrite
-R,-rRecurse directories
-l,-sCreate (sym)links

umount: cannot umount sysroot/boot: Invalid argument
---Stop volumes
---Stop raid
md: md0 stopped.
md: unbind<sda1>
md: export_rdev(sda1)
md0: detected capacity change from 21457928192 to 0
mdadm: stopped /dev/md0
This MTD table has uImage.
mknod: /dev/mtd3: File exists

Skipping bad block at 0x00000000

Skipping bad block at 0x00020000

Skipping bad block at 0x00040000

Skipping bad block at 0x00060000

Skipping bad block at 0x00080000


Skipping bad block at 0x000a0000

Skipping bad block at 0x000c0000

Skipping bad block at 0x000e0000

Skipping bad block at 0x00100000

Skipping bad block at 0x00120000

Skipping bad block at 0x00140000

Skipping bad block at 0x00160000

Skipping bad block at 0x00180000

Skipping bad block at 0x001a0000

Skipping bad block at 0x001c0000

Skipping bad block at 0x001e0000

Skipping bad block at 0x00200000

Skipping bad block at 0x00220000

Skipping bad block at 0x00240000

Skipping bad block at 0x00260000

Skipping bad block at 0x00280000

Skipping bad block at 0x002a0000

Skipping bad block at 0x002c0000

Skipping bad block at 0x002e0000

Writing data to block 0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 20000
Bad block at 20000, 1 block(s) from 20000 will be skipped
Writing data to block 40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 80000
Bad block at 80000, 1 block(s) from 80000 will be skipped
Writing data to block a0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block c0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block e0000
Bad block at e0000, 1 block(s) from e0000 will be skipped
Writing data to block 100000
Bad block at 100000, 1 block(s) from 100000 will be skipped
Writing data to block 120000
Bad block at 120000, 1 block(s) from 120000 will be skipped
Writing data to block 140000
Bad block at 140000, 1 block(s) from 140000 will be skipped
Writing data to block 160000
Bad block at 160000, 1 block(s) from 160000 will be skipped
Writing data to block 180000
Bad block at 180000, 1 block(s) from 180000 will be skipped
Writing data to block 1a0000
Bad block at 1a0000, 1 block(s) from 1a0000 will be skipped
Writing data to block 1c0000
Bad block at 1c0000, 1 block(s) from 1c0000 will be skipped
Writing data to block 1e0000
Bad block at 1e0000, 1 block(s) from 1e0000 will be skipped
Writing data to block 200000
Bad block at 200000, 1 block(s) from 200000 will be skipped
Writing data to block 220000
Bad block at 220000, 1 block(s) from 220000 will be skipped
Writing data to block 240000
Bad block at 240000, 1 block(s) from 240000 will be skipped
Writing data to block 260000
Bad block at 260000, 1 block(s) from 260000 will be skipped
Writing data to block 280000
Bad block at 280000, 1 block(s) from 280000 will be skipped
Writing data to block 2a0000
Bad block at 2a0000, 1 block(s) from 2a0000 will be skipped
Writing data to block 2c0000
Bad block at 2c0000, 1 block(s) from 2c0000 will be skipped
Writing data to block 2e0000
Bad block at 2e0000, 1 block(s) from 2e0000 will be skipped
Writing data to block 300000
ioctl(MEMGETBADBLOCK): Invalid argument
Data was only partially written due to error
: Invalid argument
mknod: /dev/mtd4: File exists

Skipping bad block at 0x00000000

Skipping bad block at 0x00020000

Skipping bad block at 0x00040000

Skipping bad block at 0x00060000

Skipping bad block at 0x00080000

Skipping bad block at 0x000a0000

Skipping bad block at 0x000c0000

Skipping bad block at 0x000e0000

Skipping bad block at 0x00100000

Skipping bad block at 0x00120000

Skipping bad block at 0x00140000

Skipping bad block at 0x00160000

Skipping bad block at 0x00180000

Skipping bad block at 0x001a0000

Skipping bad block at 0x001c0000

Skipping bad block at 0x001e0000

Skipping bad block at 0x00200000

Skipping bad block at 0x00220000

Skipping bad block at 0x00240000

Skipping bad block at 0x00260000

Skipping bad block at 0x00280000

Skipping bad block at 0x002a0000

Skipping bad block at 0x002c0000

Skipping bad block at 0x002e0000

Writing data to block 0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 20000
Bad block at 20000, 1 block(s) from 20000 will be skipped
Writing data to block 40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 80000
Bad block at 80000, 1 block(s) from 80000 will be skipped
Writing data to block a0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block c0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block e0000
Bad block at e0000, 1 block(s) from e0000 will be skipped
Writing data to block 100000
Bad block at 100000, 1 block(s) from 100000 will be skipped
Writing data to block 120000
Bad block at 120000, 1 block(s) from 120000 will be skipped
Writing data to block 140000
Bad block at 140000, 1 block(s) from 140000 will be skipped
Writing data to block 160000
Bad block at 160000, 1 block(s) from 160000 will be skipped
Writing data to block 180000
Bad block at 180000, 1 block(s) from 180000 will be skipped
Writing data to block 1a0000
Bad block at 1a0000, 1 block(s) from 1a0000 will be skipped
Writing data to block 1c0000
Bad block at 1c0000, 1 block(s) from 1c0000 will be skipped
Writing data to block 1e0000
Bad block at 1e0000, 1 block(s) from 1e0000 will be skipped
Writing data to block 200000
Bad block at 200000, 1 block(s) from 200000 will be skipped
Writing data to block 220000
Bad block at 220000, 1 block(s) from 220000 will be skipped
Writing data to block 240000
Bad block at 240000, 1 block(s) from 240000 will be skipped
Writing data to block 260000
Bad block at 260000, 1 block(s) from 260000 will be skipped
Writing data to block 280000
Bad block at 280000, 1 block(s) from 280000 will be skipped
Writing data to block 2a0000
Bad block at 2a0000, 1 block(s) from 2a0000 will be skipped
Writing data to block 2c0000
Bad block at 2c0000, 1 block(s) from 2c0000 will be skipped
Writing data to block 2e0000
Bad block at 2e0000, 1 block(s) from 2e0000 will be skipped
Writing data to block 300000
ioctl(MEMGETBADBLOCK): Invalid argument
Data was only partially written due to error
: Invalid argument
Remove the temp folder.
DONE copying images
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
Imaging Successful. Please remove the USB drive before the next power on
USB/DOM device is sdc
cat: can't open '/sys/block/sdd/removable': No such file or directory
Drives are sd[ab]

/dev/sda:

/dev/sdb:

/dev/sda:
 setting drive write-caching to 0 (off)
 write-caching =  0 (off)

/dev/sdb:
 setting drive write-caching to 0 (off)
 write-caching =  0 (off)

/dev/sda:
 issuing standby command

/dev/sdb:
 issuing standby command
md: stopping all md devices.
sd 1:0:0:0: [sdb] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Synchronizing SCSI cache
Power down.


Top
 Profile  
 
PostPosted: Tue Mar 15, 2016 8:48 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6048
Don't know if your u-boot supports it. Here you can read a story on how to reset the bad blocks on *some* boards.

In your case there is a complicating factor. Following the directions will erase the nand, including the bootloader, which will kill your box. So you have a few options. Get jtag running, check out of your box can be booted using kw-boot, or boot into a Linux variant where you can do a flash_erase all on the mtd partitions not containing u-boot.

If possible, backup as much as you can from the current flash. After erasing it's gone.


Top
 Profile  
 
PostPosted: Wed Mar 16, 2016 2:36 am 
Offline

Joined: Mon Mar 14, 2016 2:00 am
Posts: 3
Ah, ok. Well I truly appreciate the reply, even if it's not the best of news.

It's a rare day that I'll give up on something like this, but I've invested too much time on this already and I'm only going backwards. The options listed will either (a) require much more research for me to pull off or (b) present enough risk that I'm not sure it even makes sense to continue. Hopefully this thread helps someone in the future. Then again, hopefully no one else gets in this situation. :|


Top
 Profile  
 
PostPosted: Wed Mar 16, 2016 8:37 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6048
Too bad.

pseudorandom wrote:
(a) require much more research for me to pull off
But remember, the result is more knowledge.


Top
 Profile  
 
PostPosted: Wed Mar 16, 2016 1:11 pm 
Offline

Joined: Mon Mar 14, 2016 2:00 am
Posts: 3
Believe me, I normally feel that way. I am a lifelong learner. I'm just in a season of life that I must make choices on what gets use of my time. I'll set it to the side and maybe pick it up again someday soon. Anyway, thanks again.


Top
 Profile  
 
PostPosted: Sun Jul 16, 2017 11:26 am 
Offline

Joined: Sun Jul 16, 2017 11:19 am
Posts: 1
pseudorandom wrote:
Believe me, I normally feel that way. I am a lifelong learner. I'm just in a season of life that I must make choices on what gets use of my time. I'll set it to the side and maybe pick it up again someday soon. Anyway, thanks again.

Did you finally find a way to solve the problem in your ix2-dl? I happen to have exactly the same problem. I am about to turn mine into an ix2-ng (it can be done, sort of...), but I would rather prefer a more neat solution.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 14 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group