Re: kernel panic error
On Sun, Jul 18, 2010 at 13:39, Andrei Popescu <firstname.lastname@example.org>
On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> > Could you please elaborate on that? How can UUID fail if you have
> > modules compiled in the kernel, since UUID is a property of the
> > filesystem?
The link only talks about /dev/disk/by-uuid/... which is correct. Those
> Even if every driver is compiled into the kernel, an initrd may be required
> use root=UUID=....format.
> That is what my experience too, finally I swithed to root=/dev/sda2
> There are many suggestions that root=/dev/disk/by-uuid/....
> could be used instead without an initrd.
> See the link,
are actually symlinks created by udev and I'm guessing they are not
present if you don't have an initrd. But passing root=UUID=... should
not require an initrd, because it doesn't rely on /dev being present.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----
I am using a custom 2.6.34 kernel with every driver built in. Currently it is booted with root=/dev/sda2 option.
Just to see how it works, I changed that to
1) linux /boot/vmlinuz-2.6.34 root=UUID=ddc23ac8-37bf-4e89-a1cd-d77aefc011c8 ro quiet
2) linux /boot/vmlinuz-2.6.34 root=/dev/disk/by-uuid/ddc23ac8-37bf-4e89-a1cd-d77aefc011c8
In both cases the system did not boot up. The error was unable to mount root device.
So finally, to use uuid option in either way, it is required to use initrd.