summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorAndy Whitcroft <apw@shadowen.org>2006-05-15 09:44:29 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2006-05-15 11:20:57 -0700
commitbe6e028b6422878df2e799a74609a03a553c7dad (patch)
tree8903854a9d6f82f3ec0b4e6087ff0fbad80578db /init
parent3835a9bd07778d87dea37fbf190f70883515e8fc (diff)
downloadlinux-3.10-be6e028b6422878df2e799a74609a03a553c7dad.tar.gz
linux-3.10-be6e028b6422878df2e799a74609a03a553c7dad.tar.bz2
linux-3.10-be6e028b6422878df2e799a74609a03a553c7dad.zip
[PATCH] root mount failure: emit filesystems attempted
When we fail to mount from a valid root device list out the filesystems we have tried to mount it with. This gives the user vital diagnostics as to what is missing from their kernel. For example in the fragment below the kernel does not have CRAMFS compiled into the kernel and yet appears to recognise it at the RAMDISK detect stage. Later the mount fails as we don't have the filesystem. RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 1604KiB [1 disk] into ram disk... done. XFS: bad magic number XFS: SB validate failed No filesystem could mount root, tried: reiserfs ext3 ext2 msdos vfat iso9660 jfs xfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) Signed-off-by: Andy Whitcroft <apw@shadowen.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'init')
-rw-r--r--init/do_mounts.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/init/do_mounts.c b/init/do_mounts.c
index adb7cad3e6e..f4b7b9d278c 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -310,6 +310,11 @@ retry:
panic("VFS: Unable to mount root fs on %s", b);
}
+
+ printk("No filesystem could mount root, tried: ");
+ for (p = fs_names; *p; p += strlen(p)+1)
+ printk(" %s", p);
+ printk("\n");
panic("VFS: Unable to mount root fs on %s", __bdevname(ROOT_DEV, b));
out:
putname(fs_names);