The BOOT folder has a boot-noemulation.img and the boot folder has an isolinux folder, which should be the boatloader, allowing it to boot. This is on Knoppix 7.2.0 DVD (not CD or bootonly). The knoppix partition is the only one marked bootable on the drive, and t didn't get confused last night when I booted to Tiny Core (which used extlinux).

1. Knoppix 8.5 Iso

I'm trying to boot a Knoppix ISO from Grub like so:

My question is the bootfrom parameter. If I don't include the double slash the system will never boot. It will complain that it couldn't find the KNOPPIX folder on the drive (Because it's inside the ISO).

It will search the drives in an attempt to locate this folder - by the end of which drives have appeared in /dev/ from sda1 to sdz15.

• If I include the double-slash in the bootfrom parameter it will search the drives a few times, then (presumably after mounting /mnt-iso) it will triumphantly state 'Yay! I found it in /dev/sdd5/boot/iso/knoppix.iso'
  Of course by this time sda1 through sdh15 have been generated in /dev/ so this can't be a good thing.

• If I use bootfrom=/dev/sdd5/boot/iso/knoppix.iso it works straight away, but I can't guarantee it will be this device on all systems. Can I use UUID?
  I read that in fedora 15 you could use root=live:UUID={uuid}:{isofile} but this doesn't seem to be the case any more

• Why does it behave differently if I have only one slash?

This is very confusing.

Edit: Progress!

With the following menuentry I've managed to get knoppix to claim to open and check an ISO file, only to claim it can't find the KNOPPIX folder therein.

Cannot find KNOPPIX dir in iso image:

Knoppix 8.5 Iso

It's hard to tell what's going on because the TTY is small and the text doesn't wrap.

Edit: Yet more progress. After going through half the the knoppix repo with a fine tooth grep I decided to see if the problem was in the kernel since obviously the rest of the system wasn't being loaded anyway.

strings linux grep 'Cannot find' - No results

Well what about initrd.gz? (Note that I have no idea what's in here, I heard somewhere that it was an actual chunk of memory)

Ooh there's another archive in there... Ooh there's a filesystem! What's in this big file named init?...

REALLY? Who on earth makes the error message use a clearly separate variable from the condition?

All right, at least I know the exact line of the problem (591) but the only way I see out of this is an extremely hackish attempt to mess with this bash and hardcode it to let me through... Or to set my partition in question to sda. And of course I don't know how to do either yet. Yay! So. How do I go about editing init?

1 Answer

Turns out the init script in knoppix's initramfs is spaghetti code.

In particular it was hardcoded to only really accept devices in the format /dev/sdxy causing problems with longer pathnames and UUID alike.

I just made a new initrd, cut out that whole section and hardcoded my UUID into it. Of course it's not that easy. The knoppix initrd is so small it doesn't have things like blkid or the ability to mount by UUID=.

I ended up finding the device file with fdisk and grep:

The partition in question is fairly unique in size, so I doubt I'll have a collision any time soon.

Not the answer you're looking for? Browse other questions tagged bootgrub2 or ask your own question.