1 |
On Wed, 10 Feb 2010 20:43:44 +0100 (CET) |
2 |
joerg.faschingbauer@×××.at wrote: |
3 |
|
4 |
> >>>>> "David" == Relson, David <david.relson@×××××××××.com> writes: |
5 |
> |
6 |
> David> When I boot with "linux root=/dev/sda1", I get the following |
7 |
> |
8 |
> David> VFS: Cannot open root device "sda1" or unknown-block(0,0) |
9 |
> David> Please append a correct "root=" boot option; here are the |
10 |
> David> available partitions: |
11 |
> David> 0300 1000944 hda driver: ide-gd |
12 |
> David> 0301 142096 hda1 |
13 |
> David> 0302 856800 hda2 |
14 |
> David> Kernel panic - not syncing: VFS: Unable to mount root fs on |
15 |
> David> unknown-block(0,0) |
16 |
> |
17 |
> David> Evidently /dev/sda1 hasn't yet mounted. The boot process runs |
18 |
> David> into the same problem when I use /dev/sda or /dev/sda2 for |
19 |
> David> "root=". |
20 |
> |
21 |
> David> In the past I've seen similar kernel panics when the kernel |
22 |
> David> lacks the proper disk driver. Since the system boots fine |
23 |
> David> from the DOM, I believe my kernel has all the device drivers |
24 |
> David> built in (except scsi_wait_scan.ko which is a module). |
25 |
> |
26 |
> David> How do I fix the boot problem? Anybody familiar with this |
27 |
> David> problem and have a recommendation or, even better, a solution? |
28 |
> |
29 |
> You might want to pass "rootdelay=5" (seconds), or "rootwait" for |
30 |
> newer kernels (don't know when the latter was introduced). |
31 |
> |
32 |
> Joerg |
33 |
|
34 |
Thanks to Manuel, James, and Joerg. All 3 of you suggested |
35 |
rootdelay. It helps but isn't a complete solution. |
36 |
|
37 |
My syslinux.cfg now contains: |
38 |
|
39 |
LABEL linux |
40 |
KERNEL linux |
41 |
APPEND rootdelay=10 root=/dev/sda1 |
42 |
|
43 |
and is working better than before. |
44 |
|
45 |
After SCSI messages: |
46 |
|
47 |
sd 0:0:0:0: [sda] Write Protect is off |
48 |
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 |
49 |
sd 0:0:0:0: [sda] Assuming drive cache: write through |
50 |
sda: sda1 |
51 |
sd 0:0:0:0: [sda] Attached SCSI removable disk |
52 |
|
53 |
The boot process fails with: |
54 |
|
55 |
VFS: Mounted root (vfat filesystem) readonly on device 8:1 |
56 |
Freeing unused kernel memory: 176k freed |
57 |
Warning: unable to open an initial console |
58 |
Kernel panic - not syncing: No init found. Try passing init= |
59 |
option to kernel |
60 |
|
61 |
Clearly the wait is helping since 'vfat' and '8:1' are correct. The |
62 |
"init=" suggestion is puzzling. The default boot (from the built-in |
63 |
DOM) uses the following syslinux.cfg: |
64 |
|
65 |
DEFAULT linux |
66 |
|
67 |
LABEL linux |
68 |
KERNEL linux |
69 |
APPEND root=/dev/hda2 |
70 |
|
71 |
there's no "init=" in it. Also, /etc/init.d just contains a single |
72 |
script (named rcS) which does all the initialization. There are no run |
73 |
levels. FWIW, I'm using a 2.6.29.6 kernel. |