Lonrisun Solo2 Mini: Bad block table erweitern

[Kermit00]

Hallo,

Vorgeschichte:
ich habe ein seltsames Problem: Meine Festplatte verschwindet gelegentlich. Der Bootvorgang aus dem Deep-Standby dauert plötzlich mehrere Minuten und die Festplatte wird nicht erkannt. Das erste mal passierte dies vor einigen Monaten. Ich habe die Festplatte ausgebaut und an einem PC mit fsck problemlos reparieren können.
Das Problem trat dann vor längerer Zeit noch ein einziges mal auf. Diesmal habe ich sie via telnet direkt auf der Box mit fsck reparieren können und hatte nun längere Zeit Ruhe. Gestern trat der Fehler dann gleich 2mal an einem Tag und vor allem im laufenden Betrieb auf: Archiv-Festplatte war einfach verschwunden. Mit fsck lies sie sich problemlos reparieren. Heute nur eine halbe Stunde die Box angehabt und das Problem tritt wieder auf!

root@vusolo2:~# mount /dev/sda1
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
mount: mounting /dev/sda1 on /media/hdd failed: Invalid argument
root@vusolo2:~# mount -t ext3 /dev/sda1
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
mount: mounting /dev/sda1 on /media/hdd failed: Invalid argument
root@vusolo2:~# fsck.ext3 /dev/sda1
e2fsck 1.42.9 (28-Dec-2013)
Superblock has an invalid journal (inode 8).
Clear<y>? yes
*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock has_journal flag is clear, but a journal inode is present.
Clear<y>? yes
hdd was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data.  Clear<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(60850176--60882943)
Fix<y>? yes
Free blocks count wrong for group #1857 (0, counted=32768).
Fix<y>? yes
Free blocks count wrong (104290245, counted=104322598).
Fix<y>? yes
Recreate journal<y>? yes
Creating journal (32768 blocks): 
 Done.

*** journal has been re-created - filesystem is now ext3 again ***

hdd: ***** FILE SYSTEM WAS MODIFIED *****
hdd: 7852/30531584 files (0.5% non-contiguous), 17806815/122096645 blocks
root@vusolo2:~# 
root@vusolo2:~# mount -t ext3 /dev/sda1
root@vusolo2:~# blkid
/dev/sda1: LABEL="hdd" UUID="ff66bc85-c3d4-4799-b0f9-045ead79cf88" TYPE="ext4"

Im Kernelringpuffer habe ich dabei folgendes gefunden:

brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
JBD2: no valid journal superblock found
EXT4-fs (sda1): error loading journal
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
JBD2: no valid journal superblock found
EXT4-fs (sda1): error loading journal
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5395 to a partition!
mount: sending ioctl 5395 to a partition!
mount: sending ioctl 5395 to a partition!
mount: sending ioctl 5395 to a partition!
UDF-fs: warning (device sda1): udf_fill_super: No partition found (1)
JBD2: no valid journal superblock found
EXT4-fs (sda1): error loading journal
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
JBD2: no valid journal superblock found
EXT4-fs (sda1): error loading journal
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
UDF-fs: warning (device sda1): udf_fill_super: No partition found (1)
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
brcmnand brcmnand.0: uncorrectable error at 0x900000
end_request: I/O error, dev mtdblock3, sector 0
Buffer I/O error on device mtdblock3, logical block 0
JBD2: no valid journal superblock found
EXT4-fs (sda1): error loading journal
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
JBD2: no valid journal superblock found
EXT4-fs (sda1): error loading journal
UDF-fs: warning (device sda1): udf_fill_super: No partition found (1)

Das sieht für mich eher nach einem Fehler im Flashspeicher aus! Vermute das nur aus dessen Folge meine HDD FS-Konsistenz flöten geht!


Weiß jemand wie ich die Stelle 0x900000 zu den bad block hinzufügen kann, bzw. wie/womit ich den Flash-Speicher überprüfen und die Stelle entsprechend markieren lassen kann?
Beim Booten des Kernels wird ja jedesmal eine Bad block table geladen:

NAND device: Manufacturer ID: 0x98, Chip ID: 0xda (Toshiba NAND 256MiB 3,3V 8-bit)
brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
Bad block table found at page 131008, version 0x04
Bad block table found at page 130944, version 0x04
nand_read_bbt: bad block at 0x000000700000
nand_read_bbt: bad block at 0x000001aa0000
nand_read_bbt: bad block at 0x0000030c0000
nand_read_bbt: bad block at 0x000006b40000
nand_read_bbt: bad block at 0x000007fe0000
nand_read_bbt: bad block at 0x00000a780000
nand_read_bbt: bad block at 0x00000bfa0000
nand_read_bbt: bad block at 0x00000c260000
nand_read_bbt: bad block at 0x00000de80000
nand_read_bbt: bad block at 0x00000e4e0000
Creating 4 MTD partitions on "brcmnand.0":
0x000001f00000-0x000010000000 : "rootfs"
0x000001f00000-0x000010000000 : "rootfs(redundant)"
0x000000200000-0x000000900000 : "kernel"
0x000000900000-0x000000a00000 : "mac"

Danke im Voraus,
Kermit