FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Rep:
Creating a new initrd image to USB boot Fedora 15
Hi,
I used to run Fedora 15 x64 on my old laptop which doesn't work any more now.
I would like to use my HD as a USB bootable device in an enclosure which I have on my new machine.
The issue seems to be that I need to create a new initrd to pre-load the USB drivers so when the GRUB of the new machine tries booting the USB disk I don't get the H/C/I error (sorry can't remember the letters directly) that I'm facing.
Buildwise the disk is sound as I can boot it in the family laptop as it's the same hardware as my old one.
Unfortunately I encountered many errors with this as I don't think the system could find all the modules:
Code:
# mkinitrd /boot/initramfs-2.6.41.4-1.fc15.x86_64.img 2.6.41.4-1 --preload kernel/drivers/usb/usbcore:kernel/drivers/usb/usb-storage:kernel/drivers/scsi/scsi --force
/sbin/mkinitrd: line 52: read_args: command not found
find: `/lib/modules/2.6.41.4-1/': No such file or directory
find: `/lib/modules/2.6.41.4-1/': No such file or directory
find: `/lib/modules/2.6.41.4-1/': No such file or directory
find: `/lib/modules/2.6.41.4-1/': No such file or directory
find: `/lib/modules/2.6.41.4-1/': No such file or directory
find: `/lib/modules/2.6.41.4-1/': No such file or directory
find: `/lib/modules/2.6.41.4-1/': No such file or directory
Is the error I kept getting. <I tried with various module names after using the locate command to search for them as the original directive I got from Salix (Slackware)>
In any case which ones would I need in general for what I'm trying to do?
These are all the dracut options available for download:
Code:
dracut-caps.noarch : Dracut modules to build a dracut initramfs which drops
: capabilities
dracut-fips.noarch : Dracut modules to build a dracut initramfs with an
: integrity check
dracut-modules-olpc.x86_64 : OLPC modules for dracut initramfs
dracut-network.noarch : Dracut modules to build a dracut initramfs with network
: support
dracut-tools.noarch : Dracut tools to build the local initramfs
osr-dracut-module.noarch : Dracut modules for open sharedroot
dracut.noarch : Initramfs generator using udev
osr-dracut-module-chroot.noarch : Additional chroot modules for chroot required
: open-sharedroot
osr-dracut-module-cluster.noarch : Additional base cluster modules for shared
: booting with open-sharedroot
So am wondering which ones contain the modules I would need; am guessing not the last 2.?
You need kernel modules, not dracut modules. Have a look at the -d and --add-drivers options on the man page.
Although I haven't yet tried what I'm recommending, I hope hou canget it to work. I've got a nice new 2TB external drive from which I'd like to be able to boot on occasion.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Quote:
You need kernel modules, not dracut modules. Have a look at the -d and --add-drivers options on the man page.
Although I haven't yet tried what I'm recommending, I hope hou canget it to work. I've got a nice new 2TB external drive from which I'd like to be able to boot on occasion.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
well....
am totally out of ideas now.
I managed to figure out that a line in Grub was wrong: '(hd1,msdos1)' should infact read '(hd1,msdos0)'.
Personally I think that the modules I'm trying to load are either incorrect or their names are wrong!
Code:
locate usb | grep storage
revials usb-storage not usb_storage... so in this case until I know that I have the right modules and 'are' infact loading them I will wait for someone with better/more ideas.
did generate an initramfs file called test3initramfs (as it should); it's less than half the size of the default initramfs. Haven't tried booting from it, and don't currently have my external drive to try it on.
Location: Under the bridge where proper engineers walkover
Distribution: Various Linux, Solaris, BSD, Cisco
Posts: 443
Original Poster
Rep:
Ok not sure if one needs to do this actually!
I did manage to boot in the end and let this be a lesson for anyone with USB3.0 architecture/port in their machine... the BIOS detection is still iffy - for booting at least!
The problem was solved ...ok am gona tell the long and boring version
insmod part_msdos
insmod usb
insmod usbms
insmod ext2
insmod gzio
set root (hd1,msdos1)
This didn't work why????
I typed in ls and hd0 was mentioned and all the partitions that were on it but no hd1????
Ok so referring to the link I thought that Grub being installed on the USB drive may make Grub2 of F16 go funny as the disk sectors would be all screwy from Grubs perspective.
I then tried a failing (or failed) USB IDE enclosure of a really old disk and tried to ls from Grub with that.
Before I got into Grub the BIOS came up with no bootable partition found LOL
Right now the issue was just to stick my USB 3.0 enclosure into the same port and viola everything works!!!!! Bypass Grub2 of hd0 or sda altogether......
I think the USB 3.0 architecture still has a few kinks in it that need to be ironed out or my particular BIOS version can't boot it? Either way the 'powered' USB 2.0 port did the trick.
RockDoctor.... thanks for all the help much appreciated.... now GO BOOT YOUR ENCLOSURE :P
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.