twice, but to no avail this time - yet they have worked flawlessly in the past.
For the life of me I can’t figure out why this keeps happening? It seems that the bootloader files ‘may’ be the culprit as they seem to be getting overwritten on updates but why, I haven’t a clue. This has never happened before on any distro I’ve used in the past. :o I’m wondering if the Update Manager itself may be at fault but truthfully, I’m clutching at straws!
After the Meltdown/Spectre fiasco and the faff I had to get the patched kernel installed, I’ve deliberately unchecked updated kernels from the Update Manager list but something else must have slipped through this time. I’m currently booted from the M18.3 install disk and have disconnected my 2nd (slave) drive as in the past so as to work only with my main HDD.
Any guidance would be welcome!
EDIT: I also ran an integrity check from the install disk but no errors were reported.
In the meantime I tried swapping the data ribbon for a spare I have (in case it was a faulty cable) but that hasn’t worked either so I’ve returned to original set up. From the install disk, GParted ‘sees’ both sda1 (160 GiB with M18.3 installed) and sdb1 (40GiB with M18.1 installed) and from the Desktop, ‘Computer’ ‘sees’ all the users and files so everything looks to be intact - it just refuses to boot to anything. ??? I’ve double-checked all connections etc so now I’m stumped!
What really bothers me is why this keeps happening? It’s done it twice since my original post but both times your instructions worked fine. Perhaps there is a more serious underlying problem? I’ve never had this issue with other distro’s (as far as I can recall) so it’s a real puzzle.
Quote from my first post -
I’m currently booted from the M18.3 install disk and have disconnected my 2nd (slave) drive as in the past so as to work only with my main HDD.
I disconnected the 2nd drive in preparation for any repair to the main drive - as you have requested in the past. When both drives are connected, both are recognised by BIOS and also by Grub but neither will boot. GParted sees both and all can be mounted and viewed from the install disk.
I get an error… something/something about hd0, press any key to continue … then after a few seconds it changes to an output, ending - not syncing: VFS unable to mount root fs on unknown-block (0,0)
I had this the last time I posted (Meltdown and Spectre post) and you altered the last command from ‘update-grub’ to … 'update-initramfs -uk all… and I’ve tried this again but, unfortunately, with the same result.
As I said, this has happened a couple of times since my original post and either/or of your previous instructions worked fine - but not this time. The OS performs beautifully ordinarily, it’s just the updating that screws things up. From memory, I may have ticked the middle (let me choose?) option at install but I never let the level 5 updates install. When up and running, can I change that option to ‘just keep my computer safe’ or can it only be done at the installation stage?
I am willing to re-install from fresh if necessary but there’s no guarantee that this fault won’t re-occur - plus the added hassle of getting everything off and on to the drive every time. Is there a utility or terminal script I could run that would indicate where the fault lies? Researching ‘kernel panic’ throws up many causes, one of the most prevalent seems to be about ‘ram timeout’ or some such which stalls the boot process. Can this be increased in any way?