Mikkel L. Ellertson wrote: > Frank Millman wrote: > > > > Thanks for the reply, Mikkel. > > > > I tried, but unfortunately I don't know enough to figure it out :-( > > Well, if you were building for kernel 2.6.26.3-14.f8, you would run: > > mkinitrd /boot/test.img 2.6.26.3-14.f8 > > Then you would have something like this in grub.conf (excuse > the line wrap): > > title New Board > root (hd0,0) > kernel /vmlinuz-2.6.26.3-14.fc8 ro > root=/dev/VolGroup00/LogVol00 rhgb quiet > initrd /test.img > title Fedora (2.6.26.3-14.fc8) > root (hd0,0) > kernel /vmlinuz-2.6.26.3-14.fc8 ro > root=/dev/VolGroup00/LogVol00 rhgb quiet > initrd /initrd-2.6.26.3-14.fc8.img Still no luck, I am afraid. This is what I have done. #chroot /mnt/sysimage. 'uname -r' shows 2.6.27.5-117.fc10.i586 I ran 'mkinitrd -v /boot/test.img 2.6.27.5-117.fc10.i586'. I put the -v in to see what was happening, but it just returns to the prompt silently. #ls /boot shows nothing - I don't think it is mounted. I ran 'cat /etc/fstab', and alarmingly (I think) it has changed from what it was before. Before - /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 UUID=b6c62c5a-0afb-4258-a726-6a377a6f3b9e /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 Now - UUID=6e47e294-fc8d-4457-b1e9-03f68a57d0aa / ext3 defaults 1 1 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 UUID=519e0658-aa0a-49a2-9b39-d80e92b0c838 swap swap defaults 0 0 The only thing I can think of that might have changed it is that I booted off the install dvd and selected 'install/upgrade'. It gave a warning that the partition table was unreadable and that device sda will have to be reinitialized. I did not proceed past that point, but maybe it was too late. What seems odd, to me, is that while I am in rescue mode, I can see all the files on my system, so it obviously has no problem actually reading the hard drive. I have not tried Paulo's suggestion of 'yum update kernel' yet. I will try it and report back. Thanks Frank -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
