On 6/20/06, Ken Cobler <[EMAIL PROTECTED]> wrote:
> Wojciech Kromer wrote:
> > Dnia 2006-06-19 13:13, Użytkownik Jinesh K J napisał:
> >
> >> On 6/19/06, Wojciech Kromer <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>> After reading lot of discusions on this issue, I can't still get
> >>> why there is an error booting from root=/dev/sda1 or even root=8:1.
> >>>
> >>>
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(2,0)
> >
> > ^^^ Same error with root=8:1
> >
> >
> >>> and I can mount it after booting  the same kernel from network.
> >>>
> >>>
> >>>
> >> what does that mean?
> >>
> >>
> >>
> >
> > The same kernel (binary the same, and no modules loaded) can be loaded
> > via network boot, and mounting my usb-storage device is possible.
>
>  From the looks of your posting, the issue is not that you cannot boot
> from a USB device, but, rather you cannot mount the root filesystem when
> the filesystem is on a USB device.
>
> I think this issue comes from that fact that even though you have SCSI
> emulation for USB devices built into the kernel, the USB device is not
> registered with the kernel at the time when the root filesystem needs to
> be mounted.  Thus, the root filesystem mount fails.
>
> To get around this problem, I've solved it by building a ramdisk for the
> root filesystem.  Boot off the USB device, mount the ramdisk (initrd) as
> the root filesystem.
>
> Once the ramdisk is mounted, you can then mount the USB device or the
> hard drive.
>
> Don't forget to add some basic commands to your ramdisk image.
>

cool solution. remember that the initrd image is just a gzipped cpio
archive. just extract an already existing one and modify the init file
in it. add your modules. and rebuild the initrd out of it.

i hope i'm right...

best of luck...

_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to