This is what I got when I copied the initrd file from my Fedora /boot directory on my hard drive:
Code:
[root@localhost initrd]# cat init |
I believe your mkrootdev command is wrong
Code:
mkrootdev -t ext3 -o defaults,ro /dev/sdb5 Code:
rootdev=/dev/sdb5 mkinitrd Then edit /boot/grub/menu.lst and use your new initrd file that you have put in /boot Also check that /dev/sdb5 indeed is an ext3 filesystem. Code:
su - |
Thank you for the help -- I will try these things. Though I'm wondering why I'd have to edit menu.lst to use the 'new' initrd file. Shouldn't the mkinitrd command just overwrite the existing one?
|
You should give the initrd file to create as argument for mkinitrd.
It won't overwrite unless you specify the -f (force) option. If you feel like you won't need the old one, go ahead. |
When I tried the mkinitrd command this is what I got:
Code:
[root@localhost initrd]# rootdev=/dev/sdb5 mkinitrd btw, I checked, and /dev/hdb5 definitely has the ext3 filesystem |
Did you try from a Fedora system (liveCD or rescue CD)?
|
Yes I did use a Fedora live CD -- I was able to mount my installed partition just fine and view the contents. I copied the initrd-2.6.21-1.3194.fc7.img file to /tmp/initrd -- that's where I ran the "cat init" command to view the contents of the file. It's been a few days now, but I believe I also ran the mkinitrd command in the /tmp/initrd directory (I assumed here that once the new initrd file was created, I could copy it over to the installed partition).
I still don't understand though why it would return "command not found"... |
Hi,
I think I might have the same issue as fire-tick. Exept I installed FC7 with lvm. My system has also 2 SATA drives in raid. I installed FC7 via the boot CD and via ftp. After installation, the kernel paniced at first reboot. I think the system is stuck on "mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00". I used the commands Agrouf provided to read into init after starting from the rescue cd. Code:
chroot /mnt/sysimage Code:
[root@localhost initrd]# rootdev=/dev/sdb5 mkinitrd I read somewhere else that you can use mknitrd with options like --with=lvm --with=raid. So I tried to Code:
[root@localhost initrd] mkinitrd --force-lvm-probe Code:
"VolGroup00" was not found |
Quote:
I'm currently on holidays and don't have access to any fedora system, but from memory, it should be in /sbin or in /usr/sbin. Save your /boot/initrd-2.6.21-1.3194.fc7 somewhere and try this : Code:
rootdev=/dev/sdb5 /sbin/mkinitrd /boot/initrd-2.6.21-1.3194.fc7 2.6.21-1.3194.fc7 If you don't have mkinitrd, copy it from the cd before chroot Code:
cp /sbin/mkinitrd /mnt/sysimage/sbin Regards |
Quote:
Quote:
Quote:
Quote:
You should copy it to /boot Quote:
Quote:
change the line Code:
vg_list="" Code:
vg_list=VolGroup00 Check that the new initrd has the correct vgchange (gunzip, cpio, cat init etc) Copy the generated initrd file to /boot Edit /boot/grub/menu.lst to use this initrd Reboot Good Luck |
I know where I screwed up before -- I missed the first part of Agrouf's post that said basically boot into rescue mode. So I booted into rescue mode, and followed all the steps. When I got to the rootdev=/dev/sdb5 mkinitrd part, I stalled for a bit, because i didn't have the right syntax. Then I did:
Code:
rootdev=/dev/sdb5 mkinitrd initrd-2.6.21-1.3195.fc7.img 2.6.21-1.3194.fc7 |
Agrouf,
I followed your instructions but I still cannot boot Fedora 7 on my system. I copied mkinitrd from /sbin. Updated vg_list which was empty with VolGroup00. I ran mkinitrd with the options previously specified. The first error I receive is: After Reading all physical volumes. This may take a while..., it takes not even a second. The system says, no volume groups found. "VolumeGroup00" not found. I shall submit my init, mkinitrd.log and mount info. Code:
#!/bin/nash Code:
Creating initramfs Code:
rootfs / rootfs rw 0 0 |
The new file I created was already in the /boot folder. I ran the dpkg and cat init command to check if the changes had been made, and indeed...
Code:
mkrootdev -t ext3 -o defaults,ro sdb5 Code:
mkrootdev -t ext3 -o defaults,ro /dev/sdb5 I think I'm going to re-install Mandriva for now. Thanks anyway to everyone for their help. I'll keep an eye on this thread to see if a resolution is reached. <EDIT: so as to not be a quitter, I'll stick it out w/ Fedora for a while. I really appreciate the fact that there is a community of folks that are willing and able to provide support> |
Quote:
I may have had guessed wrong, the problem isn't rootdev then. If you decide to persist with Fedora, please post the first error that is displayed at boot and some errors after this one if possible. If you decide to give up for the moment, that is understandable, you can always come back here later and I'll be happy to help if I can. |
Quote:
|
All times are GMT -5. The time now is 01:55 AM. |