Skip to contentSkip to conversation

Booting from USB with initrd

DISCUSSION gabriel 2 participants 3 messages Apr 16, 2005 – Apr 20, 2005

lore
Share & tools
lore

gabriel

author
#0 lore raw
Quoted 1 line

Have you edit the build-initrd.sh script to fit your needs?

Yeah.. but it shouldn't matter much since I've not been able to load the initrd yet?

Quoted 3 lines

Does
http://featherlinux.berlios.de/usb-instructions.htm or
http://www.ussg.iu.edu/hypermail/linux/kernel/0211.1/0551.html help?)

I thought the second one would so I changed the code (took a while to find the right place since I use 2.6 not 2.4) However that's a fix for a problem I don't have. My kernel never complains about root= bla it only says unable to mount on root fs.
I'm not sure what this tells us.

Quoted 4 lines

Totally different Q's:

Have you called syslinux with the correct parameter to find your initrd.gz?

I hope so. I have it setup up like in the loop-aes readme. Is there something special you have in mind?

Quoted 3 lines

Do you have access to DOS bootable drive (To try to boot the kernel using loadlin from DOS command prompt. If that works you know that the issues are regarded to syslinux, if not - initrd/kernel) (?)

Nope. I only have a knoppix and kanotix rescue disc to work off at the time =)

Quoted 2 lines

Have you tried to boot kernel + initrd from your local linux installation?

No, I would if I knew how. Is there any howto for that?

Cheers.

#1 lore raw
Quoted 3 lines · gabriel

Yeah.. but it shouldn't matter much since I've not been able to load the initrd yet?

I had just a look at all those things... It simply was a question coming into my mind...

Quoted 3 lines

My kernel never complains about root= bla it only says unable to mount on root fs.
I'm not sure what this tells us.

Unable to mount root is an error message telling us that /dev/ram0 could not be mounted as root (root=)...

Try to remove the root=/dev/ram0 line from your kernel command line. IMO you don't need it, cause the kernel mounts initrd as root in any case.

One other reason for that could be that syslinux does not find and load the initrd into memory, so the kernel does boot without it.

Quoted 2 lines

I hope so. I have it setup up like in the loop-aes readme. Is there something special you have in mind?

Not in special. I searched some things like that with remote booting linux and *lots* of questions/checks comes into my mind when reading your lines.

Quoted 4 lines
Quoted 2 lines

Have you tried to boot kernel + initrd from your local linux installation?

No, I would if I knew how. Is there any howto for that?

Thats not that big issue. Do you have a linux installation with grub as bootloader (If you only have KNOPPIX/KANOTIX it would be more difficult)?
If, copy your kernel & initrd to /boot and edit grubs config file - normally somewhere within /boot. /etc/grub.conf should be a symlink.

If not copy kernel/initrd to some directory (root would be best) on a known harddisk. Boot some live linux that uses grub as loader. Goto grubs command line (edit the configuration to boot) and use your kernel and initrd to boot (you need to know the number of the harddisk from which you boot: hd(hdd nummer, part. nummer) ). See grubs documentation for details.

Is there a message that initrd was loaded to mem (from syslinux)?

regards

PS: Your mail program does not fill in reference/in-reply-to header fields... I would be very pleased if you could enable that feature (I'd find your mails much easier ;-))

#2 lore raw

Cheers!

Everythings up and running now. It had nothing to do with the kernel and all to do with a wrong word in syslinux.cfg.
I had the wrong default set so it defaulted to running the kernel without options. Which is no good idea when booting an initrd =)

Thanks for the help anyhow.