grub note: I have a multi-boot install, one of which is Cauldron.
For testing, I do a clean Cauldron net install and use rsync to backup /,
and change the boot location from /cauldron/boot to /mga7/boot.
That way mga7 is the master/production boot manager.
When I restore /cauldron from backup, and boot cauldron, grub feels
sad about what it sees.
I have to boot back into mga7, and reinstall grub with mga7 grub
and everything goes back to normal.
After your ssd boot restore, and you want to boot from ssd, then
you have to tell grub to use the ssd data.
On Tue, 02 Jun 2020 08:46:17 -0500, Bit Twister wrote:
<big snip>
grub note: I have a multi-boot install, one of which is Cauldron.
For testing, I do a clean Cauldron net install and use rsync to backup /,
and change the boot location from /cauldron/boot to /mga7/boot.
That way mga7 is the master/production boot manager.
When I restore /cauldron from backup, and boot cauldron, grub feels
sad about what it sees.
I have to boot back into mga7, and reinstall grub with mga7 grub
and everything goes back to normal.
After your ssd boot restore, and you want to boot from ssd, then
you have to tell grub to use the ssd data.
What happens if you use /usr/bin/update-grub instead of reinstalling
grub with mga7 grub?
You are using grub, are you not, rather than grub2?
update-grub2 possibly followed by dracut -f once booted into the correct
os, seems to fix any rare problem I have with booting.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 371 |
Nodes: | 16 (2 / 14) |
Uptime: | 172:40:47 |
Calls: | 7,915 |
Files: | 12,983 |
Messages: | 5,797,572 |