On Tue, Oct 09, 2012 at 12:52:39PM +0200, Piotr Szymaniak wrote: > > I think that first of all it needs to detect that it is NILFS2 issue but > > not hardware or MMC stack issue. > > Will connect some screen via HDMI to check if there's some error msg. > The card should be fine, but I will dd it to disk to check for read > errors. Sorry for answering my own mail. Connected Raspberry Pi to a screen and here's the output: # -- segctord starting. Construction interval = 300 seconds. CP frequency < 30 seconds NILFS: corrupt root inode. List of all partitions: b300 7883776 mmchlk0 driver: mmcblk b301 57344 mmcblk0p1 00000000-0000-0000-0000-000000000000 b302 262144 mmcblk0p2 00000000-0000-0000-0000-000000000000 b303 7560192 mmcblk0p3 00000000-0000-0000-0000-000000000000 0800 7816704 sda driver: sd 0801 7016688 sda1 00000000-0000-0000-0000-000000000000 No filesystem could mount root, tried: nilfs2 Kernel panic - not syncing: VFS: Unable to mount root is on unknown-block(179,3) [<c001537c>] (unwind_backtrace+0x0/0xfc) from [<c0421c2c>] (dump_stack+0x20/0x24) [<c0421c2c>] (dump_stack+0x20/0x24) from [<c0421de0>] (panic+0x70/0x1a0) [<c0421de0>] (panic+0x70/0x1a0) from [<c05d4cf0>] (mount_block_root+0x1f4/0x254) [<c05d4cf0>] (mount_block_root+0x1f4/0x256) from [<05d4f64>] (mount_root+0xf0/0x114) [<c05d4f64>] (mount_root+0xf0/0x114) from [<c05d50e4>] (prepare_namespace+0x15c/0x1c0) [<c05d50e4>] (prepare_namespace+0x15c/0x1c0) from [<c05d48dc>] (kernel_init+0x100/0x130) [<c05d48dc>] (kernel_init+0x100/0x130) from [<c000f00c>] (kernel_thread_exit+0x0/0x8) # -- Don't know if that is usefull. ;) Piotr Szymaniak. -- Zaphod nie miał ochoty zaczynać z nimi bójki, a ponieważ uważał, że jak w odwadze najlepsza jest ostrożność, tak w ostrożności - tchórzostwo, schował się odważnie do szafy. -- Douglas Adams, "Life, The Universe and Everything"
Attachment:
signature.asc
Description: Digital signature
