On Mittwoch, 12. April 2017 12:32:59 CEST Dirk Müller wrote:
2017-04-09 12:01 GMT+02:00 Frank Schreiner <fschreiner(a)suse.de>de>:
> and now it is the second time that the filesystem crashed in a few weeks.
> When it happend the first time, I changed the SD Card to prevent HW
did you ever reboot the rpi after the first boot?
Sorry - cannot remember, was about 4-5weeks ago -
did it have power
loss in between at any point in time?
No, not AFAIK
PS: I have a full dump the crashed image for
debugging purposes if needed.
before running fsck? can you check if there are any errors in syslog
on that filesystem from the time before it halted?
I cannot mount the fs:
mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
Seeing this messages in dmesg
[89890.221329] EXT4-fs error (device mmcblk0p2): ext4_ext_check_inode:510:
inode #8: comm mount: pblk 0 bad header/extent: invalid extent entries - magic
f30a, entries 1, max 4(4), depth 0(0)
[89890.346932] EXT4-fs (mmcblk0p2): no journal found
Thanks for you help,