| 1 |
G'day, |
| 2 |
|
| 3 |
I've got a USB boot problem. |
| 4 |
|
| 5 |
My target hardware is a PC/104 card with a Vortex86sx processor and a |
| 6 |
128MB DOM (disk-on-module) for mass storage. |
| 7 |
|
| 8 |
Currently the test version of the card has a 1GB DOM which is |
| 9 |
partitioned as follows: |
| 10 |
|
| 11 |
Device Boot Start End Blocks Id System |
| 12 |
/dev/hda1 * 1 141 142096+ 6 FAT16 |
| 13 |
/dev/hda2 142 991 856800 83 Linux |
| 14 |
|
| 15 |
The BIOS boots to the FAT16 partition where ldlinux.sys takes over and |
| 16 |
starts linux and all is fine. |
| 17 |
|
| 18 |
When I insert my USB flash drive, it is recognized as: |
| 19 |
|
| 20 |
usb 1-1.2: new high speed USB device using ehci_hcd and address 3 |
| 21 |
usb 1-1.2: configuration #1 chosen from 1 choice |
| 22 |
scsi0 : SCSI emulation for USB Mass Storage devices |
| 23 |
usb-storage: device found at 3 |
| 24 |
usb-storage: waiting for device to settle before scanning |
| 25 |
|
| 26 |
scsi 0:0:0:0: Direct-Access SanDisk Cruzer Micro 0.1 PQ: 0 |
| 27 |
ANSI: 2 |
| 28 |
sd 0:0:0:0: [sda] 2001888 512-byte hardware sectors: (1.02 GB/977 |
| 29 |
MiB) |
| 30 |
sd 0:0:0:0: [sda] Write Protect is off |
| 31 |
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 |
| 32 |
sd 0:0:0:0: [sda] Assuming drive cache: write through |
| 33 |
sd 0:0:0:0: [sda] 2001888 512-byte hardware sectors: (1.02 GB/977 |
| 34 |
MiB) |
| 35 |
sd 0:0:0:0: [sda] Write Protect is off |
| 36 |
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 |
| 37 |
sd 0:0:0:0: [sda] Assuming drive cache: write through |
| 38 |
sda: sda1 |
| 39 |
sd 0:0:0:0: [sda] Attached SCSI removable disk |
| 40 |
usb-storage: device scan complete |
| 41 |
|
| 42 |
I need to create a rescue/install USB flash drive. |
| 43 |
|
| 44 |
At present my test flash drive has ldlinux.sys and the same kernel used |
| 45 |
by the device. Booting with "linux root=/dev/hda2" works fine. However |
| 46 |
for rescue purposes I need "linux root=/dev/sda" (or equivalent). |
| 47 |
|
| 48 |
When I boot with "linux root=/dev/sda1", I get the following |
| 49 |
|
| 50 |
VFS: Cannot open root device "sda1" or unknown-block(0,0) |
| 51 |
Please append a correct "root=" boot option; here are the available |
| 52 |
partitions: |
| 53 |
0300 1000944 hda driver: ide-gd |
| 54 |
0301 142096 hda1 |
| 55 |
0302 856800 hda2 |
| 56 |
Kernel panic - not syncing: VFS: Unable to mount root fs on |
| 57 |
unknown-block(0,0) |
| 58 |
|
| 59 |
Evidently /dev/sda1 hasn't yet mounted. The boot process runs into the |
| 60 |
same problem when I use /dev/sda or /dev/sda2 for "root=". |
| 61 |
|
| 62 |
In the past I've seen similar kernel panics when the kernel lacks the |
| 63 |
proper disk driver. Since the system boots fine from the DOM, I believe |
| 64 |
my kernel has all the device drivers built in (except scsi_wait_scan.ko |
| 65 |
which is a module). |
| 66 |
|
| 67 |
How do I fix the boot problem? Anybody familiar with this problem and |
| 68 |
have a recommendation or, even better, a solution? |
| 69 |
|
| 70 |
Regards, |
| 71 |
|
| 72 |
David |
Archives