You are not logged in.
Hello,
i have one ssd with a well running Q4OS 4.12. in it's /boot directory there are 4 files:
config-5.10.0-22-amd64
initrd.img-5.10.0-22-amd64
System.map-5.10.0-22-amd64
vmlinuz-5.10.0-22-amd64
On a second ssd, with a similar (i thought: identical) 4.12 installation i found 4 additional files in /boot:
config-5.10.0-28-amd64
initrd.img-5.10.0-28-amd64
System.map-5.10.0-28-amd64
vmlinuz-5.10.0-28-amd64
Please please forgive: i deleted the latter four ...-5.10.0-28-amd64 files on the second ssd.
Now that second disk doesn't boot Q4 any more (fortunately the grub bootmenu is not affected: the other OSs are accessible).
The immediate error message is: ...-5.10.0-28-amd64 not found
(and it returns back to grub bootmenu).
1) What did cause the gap on these two installations, was there an update on the second, which the first didn't get?
2) Is it somehow possible to edit/manipulate files on the corrupted second ssd so that it will boot ...-5.10.0-22 (and not 28)?
3) Or is ist possible to re-install Q4-4.12 onto the corrupt partition of the second disk?
Many thanks in advance!
Offline
1. It seems the first installation is not up to date for some reason. Updater is not installed maybe ?
2. It's not so easy, you would need to edit /boot/grub/grub.cfg on the corrupted partition and temporarily change kernel references.
3. A full reinstall with data override is possible.
Offline
Many thanks @q4osteam.
1. Yes, the first system was a test-instllation, maybe i was simply not long enough online with it...
2. i'll try to edit the "/boot/grub/grub.cfg" - just for curiosity, but then
3. try to make a full re-installation - just for safety, and curiosity as well, never done that before...
Thanks again & Bye!
Offline