|
On Monday, 23 October 2017 18:42:44 BST stan wrote: > On Mon, 23 Oct 2017 12:11:39 +0100 > Andy Paterson <andy.paterson@xxxxxxxxxxxx> wrote: > > > > My apologies, > > > > /boot:/dev/sda3 on /boot type ext4 > > > > (rw,relatime,seclabel,data="" Not (I agree!) that that tells > > you much! > > > > All I can see is that in /etc/grub2.cfg : > > > > Previous menu entries (eg 4.12.14-200.fc25.x86_64) have an initrd16 > > line, But the entry for 4.13.5-100.fc25.x86_64 has not initrd16 line. > > Is that significant? > > > Yes, I think that is your problem. That's what loads the initial > ramdisk for the OS. Edit that file (/boot/grub2/grub.cfg) as root, copy > one of the other initrd16 lines into that entry, change it to reflect > the initramfs file you want to use, and reboot. It should work at that > point. > > What is troubling is that this would occur on an update. Was there an > interruption or outage during update? > > > > Otherwise I have no idea what is wrong. > > > > Its a long time since I had trouble booting, so forgive me if I am a > > little baffled! > > > > I guess I will have to try to capture the actual panic messages. > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
HI, well I think its a bit deeper than that - there is no /boot/initramfs-4.13.5-100.fc25.x86_64.img! The others are there though, I don't recall any problem with something like a power outage that could have caused what now seems to be an incomplete update. I will try to reinstall the package. Thanks Andy |
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
