On Sun, 12 Jun 2005, Willy Tarreau wrote:
- you don't know the root device, so the kernel will
panic at boot because it cannot find the root device.
In this case, you have the partition list still on
the screen as it's among the latest things in the
boot order. And if your kernel reboots upon panic,
just boot it with panic=30 so get 30 seconds to read
the partition table.
I have one machine inmy lab that turns out to need to boot from /dev/sdq1
trust me, that partition info has LONG since scrolled off the screen by
the time it fails to mount and panics.
I ended up setting up a serial console to capture the boot to figure this
machine out, but that's a pretty extreme measure to have to go to.
David Lang
P.S. I had to do this after grub failed to mount by label (my guess is
that grub only looks at so many drives before giving up on finding the
label) so don't tell me that I should just use labels and then I wouldn't
have to worry about this type of thing
--
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
-- C.A.R. Hoare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]