/dev/sda1 not available from initramfs - unable te boot

Hello!

I tried to install debian on an USB flashdrive, using this tutorial: http://jeff.doozan.com/debian/

Everything seemed to be fine, but if i try to boot the system, initramfs is unable to access rootfilesystem on /dev/sda1
Here is the logfile:

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1430120 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
1135864 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1430056 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1135800 Bytes = 1.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
...
[   23.480388] NET: Registered protocol family 17
[   23.485204] registered taskstats version 1
[   23.489988] /build/buildd-linux-2.6_2.6.32-21-armel-oPaHL5/linux-2.6-2.6.32/debian/build/source_armel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   23.504595] Initalizing network drop monitor service
[   23.509643] Freeing init memory: 124K
Loading, please wait...
[   23.560972] udev: starting version 160
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/sda1 does not exist.  Dropping to a shell!
(initramfs)

The full bootlog is available at http://paste.debian.net

Does it makes sense, to re-run the install script?

Any suggestions?



Edited 1 time(s). Last edit at 09/13/2010 06:42AM by Liontamer.

Liontamer Wrote:
-------------------------------------------------------
> Everything seemed to be fine, but if i try to boot the system,
> initramfs is unable to access rootfilesystem on /dev/sda1

From the boot log, it looks like there is no USB support (either built into the kernel or loaded from the initramfs.) So Linux isn't seeing your USB drive. I'd check the contents of the initramfs (it's a cpio archive) and rebuild it if necessary to include usb-storage and its dependencies.

ecc Wrote:
-------------------------------------------------------
> Liontamer Wrote:
> --------------------------------------------------
> -----
> > Everything seemed to be fine, but if i try to
> boot the system,
> > initramfs is unable to access rootfilesystem on
> /dev/sda1
>
> From the boot log, it looks like there is no USB
> support (either built into the kernel or loaded
> from the initramfs.) So Linux isn't seeing your
> USB drive. I'd check the contents of the
> initramfs (it's a cpio archive) and rebuild it if
> necessary to include usb-storage and its
> dependencies.

That sounds senseful, cause the /lib/modules tree is empty...

(initramfs) ls /lib/modules/2.6.32-5-kirkwood
drwxr-xr-x 2 0 0   0 .
drwxr-xr-x 3 0 0   0 ..
-rw-r--r-- 1 0 0  52 modules.devname
-rw-r--r-- 1 0 0  49 modules.symbols
-rw-r--r-- 1 0 0 131 modules.softdep
-rw-r--r-- 1 0 0  12 modules.symbols.bin
-rw-r--r-- 1 0 0  45 modules.alias
-rw-r--r-- 1 0 0  12 modules.alias.bin
-rw-r--r-- 1 0 0   0 modules.dep
-rw-r--r-- 1 0 0  12 modules.dep.bin

But why didn't the install script what it ought to do?