I'm currently booting 6 distros over two hard drives and periodically dump one and replace it with another testing distro. Mint is one of three 'permanent' distros that have earned their places.
Unfortunately, after dumping Sabayon for a test run of Blag, Mint fails to completely boot, complaining about the change even though the partition size was not affected. Oddly, typing 'reboot' immediately completes the boot to a desktop, however the other partitions are not accessible.
Along with the cute sayings, there's a warning that a manual fix would have to be done. Just wondering how involved that would be and where to find the affected file.
Boot Error After Replacing Another Distro
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Boot Error After Replacing Another Distro
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
clem -
Are you saying that a person can edit out that UUID stuff as long as the rest of it's correct? You know what i mean, device and permissions.
My Ubuntu 6.06 install just reports the dev and permissions. Mint and Edgy (I believe) added the UUID information and I've been wondering about that ever since.
Are you saying that a person can edit out that UUID stuff as long as the rest of it's correct? You know what i mean, device and permissions.
My Ubuntu 6.06 install just reports the dev and permissions. Mint and Edgy (I believe) added the UUID information and I've been wondering about that ever since.
I haven't read about those IDs yet and how to use them... I don't like them too much though and I noticed that they were more volatile than the partitions themselves. I would recommend replacing them with normal devices names.
I "think"... (not sure at all on this one) that Fedora Core 6 is using them as well.
Clem
I "think"... (not sure at all on this one) that Fedora Core 6 is using them as well.
Clem
Also: I must have got that from Slackware... I just like configuration files to be straight and easy to read. These IDs are definitely not good in that respect.
Clem,
now I'd better go and read about them before I say more If they were introduced to replace /dev/xxx in fstab there's probably a good reason.
Clem,
now I'd better go and read about them before I say more If they were introduced to replace /dev/xxx in fstab there's probably a good reason.
I gave up on a multi-boot experiment after upgrading or changing one distro would screw the other ones.
Read a discussion on this at Ubuntu Forums - something abot the UUID's being introduced so that physical devices could be moved around within a system and the OS would pick up the devices. That might be great for a system administrator but creates hassles for the rest of us who just want to play around with multi-boots.
Read a discussion on this at Ubuntu Forums - something abot the UUID's being introduced so that physical devices could be moved around within a system and the OS would pick up the devices. That might be great for a system administrator but creates hassles for the rest of us who just want to play around with multi-boots.