| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Sat, 25 Jun 2016 20:33:31 +0200, Helmut Jarausch |
| 5 |
(jarausch@××××××.be) wrote about "[gentoo-user] booting - I don't |
| 6 |
anystand how the (Linux) world works anymore" (in |
| 7 |
<YseLVsRteFjBS+5CTTP64t@7zc0huhpDvqcKwT48Q8b0>): |
| 8 |
|
| 9 |
[snip] |
| 10 |
> So, I came up with root=UUID=uuid_number of the root file |
| 11 |
> system. |
| 12 |
> |
| 13 |
> But to my surprise I now got a kernel panic syncing: VFS: unable |
| 14 |
> to mount root fs on unknown block(0,0) |
| 15 |
> |
| 16 |
> So, please tell me what I'm missing? |
| 17 |
|
| 18 |
How are you configuring the kernel modules to operate your disk |
| 19 |
controllers? This situation is usually typical of having more than one |
| 20 |
set of disks from which the system can boot. |
| 21 |
|
| 22 |
I always statically link the driver that operates the controller that |
| 23 |
connects the root device and modprobe the drivers that operate the |
| 24 |
other disk controllers. This ensures that the controller for my |
| 25 |
/dev/sda device is probed first and its drives get "a", "b" and "c" in |
| 26 |
/dev/sd?, and those letters are assigned in device address order on |
| 27 |
the controller. |
| 28 |
- -- |
| 29 |
Regards, |
| 30 |
|
| 31 |
Dave [RLU #314465] |
| 32 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
| 33 |
dwnoon@××××××××.com (David W Noon) |
| 34 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
| 35 |
|
| 36 |
-----BEGIN PGP SIGNATURE----- |
| 37 |
Version: GnuPG v2 |
| 38 |
|
| 39 |
iEYEARECAAYFAldu3fQACgkQRQ2Fs59Psv9+DgCg0bhVfl8qw9JG9KF2655vgd5y |
| 40 |
GHUAoJpVpMFqCvro/LIFAjHAMkKdXb8V |
| 41 |
=HIdO |
| 42 |
-----END PGP SIGNATURE----- |
Archives