[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
|
From: list <list-bounces@xxxxxxxxxxxx> on behalf of Simon Waters <simon@xxxxxxxxxxxxxx>
Sent: 26 May 2016 20:24 To: list@xxxxxxxxxxxxx Subject: Re: [LUG] System down... Sounds like sda2 was root, should be obvious from filesystem contents.
Stop fiddling, it was loading a kernel, so grub was right. It was just the wrong kernel. Either boot an older kernel by interrupting grub, or boot from rescue and reinstall a kernel (you boot rescue, mount / as say /mnt, mount other partitions underneath
and then "chroot /mnt", source environment as needed and just install a suitable kernel).
Woah steady there chief - you're right that sda2 turned out to be / after all with boot under it (as sda1 turned out to be the EFI partition) but everything else is (sort of) wrong! Grub isn't *necessarily* right as it could be passing the wrong arguments through, and the good doctor's already confirmed that there *aren't* any old kernels to boot from instead. He doesn't want to chroot from rescue at all either, that's going to be needed to be done from an external media such as USB - you may well have meant that though. You also can't just mount your old data partitions and be done, you have to --bind mount /proc and friends or you will tragically break everything. You may well have meant that as well though :] Cheers * sorry about all the horrid formatting and quoting errors by the way, I'm still stuck answering these in nasty Win10/Outlook |
-- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq