USB booting :: Frugal USB install can't find KNOPPIX filesystem
I did a frugal-grub install to my USB pendrive/thumbdrive, and immediately had problems with grub when trying to boot from it. These problems, and the fix, are detailed in a previous thread:
NOW grub works fine, and the boot sequence begins, whizzing along beautifully UNTIL this jolly message pops up:
Code Sample
Scanning for USB devices... Done. Can't find KNOPPIX filesystem, sorry. Dropping you to a (very limited) shell. Press reset button to quit.
Additional builtin commands avaliable[sic]: cat mount umount insmod rmmod lsmod
knoppix#
I searched on this forum and found out that this problem is extremely common. However, there are no cut and dried fixes for it. I did attempt changing the KNOPPIX directory and the KNOPPIX file names to all lower case, individually and together, to no avail. Had a look at the linuxrc file contained in minirt24.gz, and it does refer to both the directory and the file in upper case.
Another fix suggested on this forum was to disable USB 2.0 support in the BIOS. Tried this also made no difference.
Both of those fixes were made 9-12 months ago, in reference to earlier versions of DSL than the one I am now using, which is 2.1
I formatted the thumbdrive and installed DSL to it using a late-model IBM Thinkpad running the DSL live CD. I intend to use it on a barebones fanless mini-ITX box I purchased from the DSL store. Both my Thinkpad and my barebones system will boot DSL just fine from a different thumbdrive on which I have installed the OS using the USB-HDD. But a USB boot from my frugal install has the same results on either machine: 'Can't find KNOPPIX filesystem'.
So, again, I'm stumped. Any ideas?this means somewhat clearly, that the combination of pendrive, usb chipset, bios and dsl's minirt24 is unable to mount your pendrive file system.
is your new pendrive handled as a harddisk by your bios?Why is it desireable to use grub for pendrives? The install scripts in DSL are made for specific devices.
Frugal grub was made for hard drives hence the device map used. It is not a bug or oversight.
We offer two kinds of pendrive installs. One for each of the booting offered by most bios. It is ceratainly easy to change boot parameters using either of the two pendrive scripts offered.
Is grub expected to offered something that the others cannot?
We often get complaints at having too many of the same kind of programs. But it seems that no matter which scripts we provide, someone want it installed an alternate way.
IMHO, this method seems to be the most difficult when the others are so easy.The only justified reason to install grub that I can think of is:
USBHDD install needed for a drive that is larger than 2.0, aka uses a FAT32 partition instead of a FAT partition. As far as I know, SYSLINUX does not work with FAT32 partitions.I don't know if your problem was resolved or not, but if you edit the menu.lst file and remove the noscsi option, it might solve your problem.Next Page...
original here.