Hmm, ich habe mal etwas ganz neues:
Wenn ich meine 7080 flashen will, erscheint im Rescue Mode folgendes Log:
[*] Remounting '/dev/mmcblk0p2' to '/data'[*] Creating ext4 filesystem 'dreambox-rootfs' on /dev/mmcblk0p1
mke2fs 1.43-WIP (18-May-2015)
Creating filesystem with 243712 4k blocks and 60928 inodes
Filesystem UUID: 9c532fdf-e001-45cb-9eec-312148c5f93a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: 0/8 done
Writing inode tables: 0/8 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/8 done[*] Mounting '/dev/mmcblk0p1' to '/mnt'
mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
Fatal: Failed to mount root filesystem
Alles anzeigen
Ein Online Recovery zeigt denselben Fehler. Ich habe Rescue Loader #103
Wenn ich über Telnet auf der Box dmesg aufrufe sehe ich unter anderem:
[ 1610.375000] mmcblk0: retrying write for general error
[ 1610.376000] mmcblk0: mmc_blk_err_check: general error sending status command, card status 0x80900
[ 1610.377000] mmcblk0: retrying write for general error
[ 1610.377000] end_request: I/O error, dev mmcblk0, sector 184408
[ 1610.378000] JBD2: recovery failed
[ 1610.379000] EXT4-fs (mmcblk0p1): error loading journal
Das sieht ja nicht gut aus...
...ich habe zu diesem Thema hier im Forum zwei Threads gefunden, leider ohne Lösung.
Die Partition zu formatieren klappt auch nicht:
root@dm7080:~# mkfs.ext4 /dev/mmcblk0p1
mke2fs 1.43-WIP (18-May-2015)
/dev/mmcblk0p1 contains a ext4 file system labelled 'dreambox-rootfs'
last mounted on / on Thu Jan 1 00:00:02 1970
Proceed anyway? (y,n) y
Creating filesystem with 243712 4k blocks and 60928 inodes
Filesystem UUID: a0e807e7-1b1e-40a4-8069-3801295194a7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
root@dm7080:~# fsck.ext4 /dev/mmcblk0p1
e2fsck 1.43-WIP (18-May-2015)
dreambox-rootfs: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on dreambox-rootfs
dreambox-rootfs: ********** WARNING: Filesystem still has errors **********
Alles anzeigen
hat noch jemand eine Idee?