any experts in mkinitrd?

[Hyperblaze]

I've got a linux box which I want to get up and running on it's own.

It's contents are from a ghosted drive from ide hard disks

now it's using raid

so need to get grub working on there again

the problem i'm encountering is wanting to make a new init image

unfortunately, all the examples i've been reading about are focused on the system being local

ie.

mkinitrd /boot/2.4.9.img 2.4.9

in my situation, they are mounted partitions running on koppix

for example

/mnt/disk1/boot/2.4.9.img would be the location of the image

trying mkinitrd /mnt/disk1/boot/2.4.9.img 2.4.9 gives me the error that /lib/modules/2.4.9 doesn't exist
(which it doesn't), since it's using knoppix.

can't create any soft links since cdrom is read-only.

anyone have ideas? if you have any questions, please feel free to ask.

 

[cquark]

Why do you want to build a new initial ramdisk? The primary use for an initial ramdisk is to load kernel modules at boot time before the filesystem is available, which is useful for RAID disks and the like. That's why mkinitrd is searching /lib/modules for loadable kernel modules for your kernel version. If you don't have any modules to load, there's generally no need for an initial ramdisk.

 

[Crusty]

chroot into the mounted drives then try it

 

[Hyperblaze]

Originally posted by: MCrusty
chroot into the mounted drives then try it

doh....

thanks. i'm going to try that tomorrow!

with any luck.....

 

[n0cmonkey]

Originally posted by: Jero

Originally posted by: MCrusty
chroot into the mounted drives then try it

doh....

thanks. i'm going to try that tomorrow!

with any luck.....

I was going to recommend that, but depending on what exactly is on the mounted drives it could be a PITA. Remember, everything you need for this should exist within the chroot.

 

[EmperorRob]

I've never had much success with mkinitrd. I follow the example in kernel sources Documentation directory. It's in a file called initrd.txt.