On 06/25/2016 09:39:32 PM, David W Noon wrote:
On Sat, 25 Jun 2016 20:33:31 +0200, Helmut Jarausch
(jarau...@skynet.be) wrote about "[gentoo-user] booting - I don't
anystand how the (Linux) world works anymore" (in
<YseLVsRteFjBS+5CTTP64t@7zc0huhpDvqcKwT48Q8b0>):
[snip]
> So, I came up with root=UUID=uuid_number of the root file
> system.
>
> But to my surprise I now got a kernel panic syncing: VFS: unable
> to mount root fs on unknown block(0,0)
>
> So, please tell me what I'm missing?
How are you configuring the kernel modules to operate your disk
controllers? This situation is usually typical of having more than one
set of disks from which the system can boot.
Yes, or several partitions on a disk.
I always statically link the driver that operates the controller that
connects the root device and modprobe the drivers that operate the
other disk controllers. This ensures that the controller for my
/dev/sda device is probed first and its drives get "a", "b" and "c" in
/dev/sd?, and those letters are assigned in device address order on
the controller.
Thanks Dave,
but I do statically link the corresponding device drivers, as well.
But I don't understand why my only hard drive is named sdb?
It looks as if my kernel named my built-in CDROM device as /dev/sda .
And if I have plugged in an USB drive it seems to influence the naming
scheme, as well.
And, to make it even more complicated, once the system is up, it has a
different naming scheme.
E.g. now my internal hard disk has the name /dev/sda but if I tried to
boot by this name it fails.
For a normal human as me, this is just crazy!
Helmut
