Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.mint > #39560 > unrolled thread

Linux Mint 21.1

Back to article view | Back to alt.os.linux.mint

Contents

  Linux Mint 21.1 Jeff Layman <Jeff@invalid.invalid> - 2022-12-08 17:04 +0000
    Re: Linux Mint 21.1 Mike Easter <MikeE@ster.invalid> - 2022-12-08 09:53 -0800
      Re: Linux Mint 21.1 Big Al <Bears@invalid.com> - 2022-12-08 13:50 -0500
        Re: Linux Mint 21.1 Mike Easter <MikeE@ster.invalid> - 2022-12-08 12:08 -0800
          Re: Linux Mint 21.1 yossarian <nomail@gmail.com> - 2022-12-08 23:07 +0100
            Re: Linux Mint 21.1 Mike Easter <MikeE@ster.invalid> - 2022-12-08 14:34 -0800
              Re: Linux Mint 21.1 dillinger <dillinger@invalid.not> - 2022-12-09 00:02 +0100
      Re: Linux Mint 21.1 Jeff Layman <Jeff@invalid.invalid> - 2022-12-08 18:59 +0000
        Re: Linux Mint 21.1 Mike Easter <MikeE@ster.invalid> - 2022-12-08 12:10 -0800
          Re: Linux Mint 21.1 Rob H <rob@despammer.com> - 2022-12-09 17:41 +0000
            Re: Linux Mint 21.1 Big Al <Bears@invalid.com> - 2022-12-09 13:07 -0500
              Re: Linux Mint 21.1 Rob H <rob@despammer.com> - 2022-12-10 13:01 +0000
              Re: Linux Mint 21.1 Gordon <Gordon@leaf.net.nz> - 2022-12-11 22:42 +0000
    Re: Linux Mint 21.1 Jeff Layman <Jeff@invalid.invalid> - 2022-12-08 20:25 +0000
    Re: Linux Mint 21.1 Big Al <Bears@invalid.com> - 2022-12-20 18:17 -0500
    Re: Linux Mint 21.1 Yrrah <Yrrah-aolm@aolm.invalid> - 2022-12-21 15:01 +0100
      Re: Linux Mint 21.1 yossarian <nomail@gmail.com> - 2022-12-21 21:31 +0100
        Re: Linux Mint 21.1 yossarian <nomail@gmail.com> - 2022-12-22 08:11 +0100
        Re: Linux Mint 21.1 Yrrah <Yrrah-aolm@aolm.invalid> - 2022-12-22 14:18 +0100
          Re: Linux Mint 21.1 Big Al <Bears@invalid.com> - 2022-12-22 09:28 -0500
      Re: Linux Mint 21.1 Monsieur <Monsieur@notreal.invalid> - 2022-12-23 20:42 +0100
        Re: Linux Mint 21.1 Jeff Layman <Jeff@invalid.invalid> - 2022-12-23 20:10 +0000
          Re: Linux Mint 21.1 Mike Bott <mbott001@gmail.com> - 2022-12-23 15:23 -0500
            Re: Linux Mint 21.1 Nic <Nic@none.net> - 2022-12-23 15:36 -0500
              Re: Linux Mint 21.1 Mike Bott <mbott001@gmail.com> - 2022-12-23 15:54 -0500
          Re: Linux Mint 21.1 Monsieur <Monsieur@notreal.invalid> - 2022-12-28 09:16 +0100
            Re: Linux Mint 21.1 Jeff Layman <Jeff@invalid.invalid> - 2022-12-28 08:51 +0000
              Re: Linux Mint 21.1 Monsieur <Monsieur@notreal.invalid> - 2022-12-28 14:09 +0100
            Re: Linux Mint 21.1 Nic <Nic@none.net> - 2022-12-28 07:04 -0500
              Re: Linux Mint 21.1 Monsieur <Monsieur@notreal.invalid> - 2022-12-28 14:09 +0100
                Re: Linux Mint 21.1 Nic <Nic@none.net> - 2022-12-28 08:24 -0500
                  Re: Linux Mint 21.1 Jack Strangio  <jackstrangio@yahoo.com> - 2022-12-29 04:25 +0000
                    Re: Linux Mint 21.1 Nic <Nic@none.net> - 2022-12-29 07:23 -0500
                      Re: Linux Mint 21.1 mechanic <mechanic@example.net> - 2022-12-30 11:44 +0000
                        Re: Linux Mint 21.1 Nic <Nic@none.net> - 2022-12-30 09:03 -0500
                          Re: Linux Mint 21.1 Big Al <Bears@invalid.com> - 2022-12-30 15:37 -0500
                        Re: Linux Mint 21.1 Paul <nospam@needed.invalid> - 2022-12-30 09:59 -0500
                      Re: Linux Mint 21.1 Jack Strangio  <jackstrangio@yahoo.com> - 2022-12-31 08:48 +0000
                      Re: Linux Mint 21.1 Monsieur <Monsieur@notreal.invalid> - 2023-01-04 21:28 +0100

Page 2 of 2 — ← Prev page 1 [2]

#39617

Anybody successfully switched back after upgrading? I can't say I'm very 
impressed with what they did to the Themes, it's even a bigger mess than 
before. Also since I upgraded there are now suddenly KDE packages in the 
update manager, I don't get it.

Will a simple timeshift back do the trick and will it get rid of all the 
stuff that's been added? Any risks?

Thanks,

[toc] | [prev] | [next] | [standalone]

#39618

On 23/12/2022 19:42, Monsieur wrote:
> 
> Anybody successfully switched back after upgrading? I can't say I'm very
> impressed with what they did to the Themes, it's even a bigger mess than
> before. Also since I upgraded there are now suddenly KDE packages in the
> update manager, I don't get it.
> 
> Will a simple timeshift back do the trick and will it get rid of all the
> stuff that's been added? Any risks?
> 
> Thanks,

I've used Timeshift to go back to 20.0 from 20.1 a couple of times, and 
it worked without problem. It does take several minutes, though - 
perhaps even longer.

-- 

Jeff

[toc] | [prev] | [next] | [standalone]

#39619

On 12/23/2022 15:10, Jeff Layman wrote:
> On 23/12/2022 19:42, Monsieur wrote:
>>
>> Anybody successfully switched back after upgrading? I can't say I'm very
>> impressed with what they did to the Themes, it's even a bigger mess than
>> before. Also since I upgraded there are now suddenly KDE packages in the
>> update manager, I don't get it.
>>
>> Will a simple timeshift back do the trick and will it get rid of all the
>> stuff that's been added? Any risks?
>>
>> Thanks,
> 
> I've used Timeshift to go back to 20.0 from 20.1 a couple of times, and 
> it worked without problem. It does take several minutes, though - 
> perhaps even longer.
> 
Sounds like one should have used Clonezilla prior to updating. :)

-- 
Mike

[toc] | [prev] | [next] | [standalone]

#39620

On 12/23/22 3:23 PM, Mike Bott wrote:
> On 12/23/2022 15:10, Jeff Layman wrote:
>> On 23/12/2022 19:42, Monsieur wrote:
>>>
>>> Anybody successfully switched back after upgrading? I can't say I'm 
>>> very
>>> impressed with what they did to the Themes, it's even a bigger mess 
>>> than
>>> before. Also since I upgraded there are now suddenly KDE packages in 
>>> the
>>> update manager, I don't get it.
>>>
>>> Will a simple timeshift back do the trick and will it get rid of all 
>>> the
>>> stuff that's been added? Any risks?
>>>
>>> Thanks,
>>
>> I've used Timeshift to go back to 20.0 from 20.1 a couple of times, 
>> and it worked without problem. It does take several minutes, though - 
>> perhaps even longer.
>>
> Sounds like one should have used Clonezilla prior to updating. :)
>
You are making me laugh:-)

[toc] | [prev] | [next] | [standalone]

#39621

On 12/23/2022 15:36, Nic wrote:
<snip>
>>
> You are making me laugh:-)
> 
> 

I have that effect on many people.  :)

-- 
Mike

[toc] | [prev] | [next] | [standalone]

#39622

Jeff Layman wrote:
> On 23/12/2022 19:42, Monsieur wrote:
>>
>> Anybody successfully switched back after upgrading? I can't say I'm very
>> impressed with what they did to the Themes, it's even a bigger mess than
>> before. Also since I upgraded there are now suddenly KDE packages in the
>> update manager, I don't get it.
>>
>> Will a simple timeshift back do the trick and will it get rid of all the
>> stuff that's been added? Any risks?
>>
>> Thanks,
> 
> I've used Timeshift to go back to 20.0 from 20.1 a couple of times, and 
> it worked without problem. It does take several minutes, though - 
> perhaps even longer.

Well I timeshifted back to Vanessa. The restoring process was long but 
smooth and ended with a message saying that the restore was succesful. 
However, when I rebooted the computer I was greeted by the famous "grub 
rescue" mode - you know that command-line mode where you can do 
absolutely nothing useful.

Did a boot repair (twice!) using a live Mint XFCE, but that didn't help 
and I kept booting into rescue mode. Only when I switched the boot order 
of my 2 ssd's in the BIOS, I got an incomplete "Ubuntu" menu at startup. 
I booted into that, saw that it was indeed the right partition and then 
did a sudo update-grub there, which brought everything back to normal.

Lesson learned: Timeshift isn't as reliable as I thought it was.

[toc] | [prev] | [next] | [standalone]

#39623

On 28/12/2022 08:16, Monsieur wrote:
> Jeff Layman wrote:
>> On 23/12/2022 19:42, Monsieur wrote:
>>>
>>> Anybody successfully switched back after upgrading? I can't say I'm very
>>> impressed with what they did to the Themes, it's even a bigger mess than
>>> before. Also since I upgraded there are now suddenly KDE packages in the
>>> update manager, I don't get it.
>>>
>>> Will a simple timeshift back do the trick and will it get rid of all the
>>> stuff that's been added? Any risks?
>>>
>>> Thanks,
>>
>> I've used Timeshift to go back to 20.0 from 20.1 a couple of times, and
>> it worked without problem. It does take several minutes, though -
>> perhaps even longer.
> 
> Well I timeshifted back to Vanessa. The restoring process was long but
> smooth and ended with a message saying that the restore was succesful.
> However, when I rebooted the computer I was greeted by the famous "grub
> rescue" mode - you know that command-line mode where you can do
> absolutely nothing useful.
> 
> Did a boot repair (twice!) using a live Mint XFCE, but that didn't help
> and I kept booting into rescue mode. Only when I switched the boot order
> of my 2 ssd's in the BIOS, I got an incomplete "Ubuntu" menu at startup.
> I booted into that, saw that it was indeed the right partition and then
> did a sudo update-grub there, which brought everything back to normal.
> 
> Lesson learned: Timeshift isn't as reliable as I thought it was.

It's not, unfortunately, a new issue:
<https://forums.linuxmint.com/viewtopic.php?t=370085>
And it's not limited to Mint:
<https://forum.endeavouros.com/t/stuck-on-grub-rescue-after-timeshift-restore/29930>
(Is that similar to your problem? Is it more a problem with Grub than 
Timeshift, or perhaps an interaction between them? It's all way above my 
pay grade...)

-- 

Jeff

[toc] | [prev] | [next] | [standalone]

#39625

Jeff Layman wrote:
> On 28/12/2022 08:16, Monsieur wrote:

>> Well I timeshifted back to Vanessa. The restoring process was long but
>> smooth and ended with a message saying that the restore was succesful.
>> However, when I rebooted the computer I was greeted by the famous "grub
>> rescue" mode - you know that command-line mode where you can do
>> absolutely nothing useful.
>>
>> Did a boot repair (twice!) using a live Mint XFCE, but that didn't help
>> and I kept booting into rescue mode. Only when I switched the boot order
>> of my 2 ssd's in the BIOS, I got an incomplete "Ubuntu" menu at startup.
>> I booted into that, saw that it was indeed the right partition and then
>> did a sudo update-grub there, which brought everything back to normal.
>>
>> Lesson learned: Timeshift isn't as reliable as I thought it was.
> 
> It's not, unfortunately, a new issue:
> <https://forums.linuxmint.com/viewtopic.php?t=370085>
> And it's not limited to Mint:
> <https://forum.endeavouros.com/t/stuck-on-grub-rescue-after-timeshift-restore/29930> 
> 
> (Is that similar to your problem? Is it more a problem with Grub than 
> Timeshift, or perhaps an interaction between them? It's all way above my 
> pay grade...)

Those are interesting articles thanks. Yes, my problem was similar, 
although in my case I got a "error: symbol 'grub_verify_string' not 
found" right before the grub rescue mode. I didn't pay much attention at 
first, because I was pretty sure Boot Repair would fix this, as it has 
fixed booting problems a few times before in the past. But not this time.

I then got the idea to try switching the boot order of my disks in the 
BIOS because I thought that maybe grub was looking for that particular 
string on the wrong disk. It was just a wild guess, but it worked.

[toc] | [prev] | [next] | [standalone]

#39624

On 12/28/22 3:16 AM, Monsieur wrote:
> Jeff Layman wrote:
>> On 23/12/2022 19:42, Monsieur wrote:
>>>
>>> Anybody successfully switched back after upgrading? I can't say I'm 
>>> very
>>> impressed with what they did to the Themes, it's even a bigger mess 
>>> than
>>> before. Also since I upgraded there are now suddenly KDE packages in 
>>> the
>>> update manager, I don't get it.
>>>
>>> Will a simple timeshift back do the trick and will it get rid of all 
>>> the
>>> stuff that's been added? Any risks?
>>>
>>> Thanks,
>>
>> I've used Timeshift to go back to 20.0 from 20.1 a couple of times, 
>> and it worked without problem. It does take several minutes, though - 
>> perhaps even longer.
>
> Well I timeshifted back to Vanessa. The restoring process was long but 
> smooth and ended with a message saying that the restore was succesful. 
> However, when I rebooted the computer I was greeted by the famous 
> "grub rescue" mode - you know that command-line mode where you can do 
> absolutely nothing useful.
>
> Did a boot repair (twice!) using a live Mint XFCE, but that didn't 
> help and I kept booting into rescue mode. Only when I switched the 
> boot order of my 2 ssd's in the BIOS, I got an incomplete "Ubuntu" 
> menu at startup. I booted into that, saw that it was indeed the right 
> partition and then did a sudo update-grub there, which brought 
> everything back to normal.
>
> Lesson learned: Timeshift isn't as reliable as I thought it was.
>
For the record, are you you a dual-booter?

[toc] | [prev] | [next] | [standalone]

#39626

Nic wrote:
> On 12/28/22 3:16 AM, Monsieur wrote:

>> Well I timeshifted back to Vanessa. The restoring process was long but 
>> smooth and ended with a message saying that the restore was succesful. 
>> However, when I rebooted the computer I was greeted by the famous 
>> "grub rescue" mode - you know that command-line mode where you can do 
>> absolutely nothing useful.
>>
>> Did a boot repair (twice!) using a live Mint XFCE, but that didn't 
>> help and I kept booting into rescue mode. Only when I switched the 
>> boot order of my 2 ssd's in the BIOS, I got an incomplete "Ubuntu" 
>> menu at startup. I booted into that, saw that it was indeed the right 
>> partition and then did a sudo update-grub there, which brought 
>> everything back to normal.
>>
>> Lesson learned: Timeshift isn't as reliable as I thought it was.
>>
> For the record, are you you a dual-booter?


Actually a quad-booter: I have Mint on sda 1, another Mint on sda2, 
Windows 7 on sda3, and finally another Mint on sda4.

[toc] | [prev] | [next] | [standalone]

#39627

On 12/28/22 8:09 AM, Monsieur wrote:
> Nic wrote:
>> On 12/28/22 3:16 AM, Monsieur wrote:
>
>>> Well I timeshifted back to Vanessa. The restoring process was long 
>>> but smooth and ended with a message saying that the restore was 
>>> succesful. However, when I rebooted the computer I was greeted by 
>>> the famous "grub rescue" mode - you know that command-line mode 
>>> where you can do absolutely nothing useful.
>>>
>>> Did a boot repair (twice!) using a live Mint XFCE, but that didn't 
>>> help and I kept booting into rescue mode. Only when I switched the 
>>> boot order of my 2 ssd's in the BIOS, I got an incomplete "Ubuntu" 
>>> menu at startup. I booted into that, saw that it was indeed the 
>>> right partition and then did a sudo update-grub there, which brought 
>>> everything back to normal.
>>>
>>> Lesson learned: Timeshift isn't as reliable as I thought it was.
>>>
>> For the record, are you you a dual-booter?
>
>
> Actually a quad-booter: I have Mint on sda 1, another Mint on sda2, 
> Windows 7 on sda3, and finally another Mint on sda4.
>
>
It is no wonder that with all that complexity your device can even boot:-)

[toc] | [prev] | [next] | [standalone]

#39628

Nic <Nic@none.net> writes:
> On 12/28/22 8:09 AM, Monsieur wrote:
> > Nic wrote:
> >> On 12/28/22 3:16 AM, Monsieur wrote:
> >
> >> For the record, are you you a dual-booter?
> >
> > Actually a quad-booter: I have Mint on sda 1, another Mint on sda2, 
> > Windows 7 on sda3, and finally another Mint on sda4.
> >
> It is no wonder that with all that complexity your device can even boot:-)
> 

He's not the only one. Even when I don't have a Windows partition, I will
still have three linux root partitions: One every-day system, one emergency
backup system if the every-day system dies for some reason. And then there's
root partition number 3 for any time I feel like experimenting with another
distro.

It save a lot of angst having somewhere to experiment with, and having a
good system that's working when disaster strikes.

Regards,

Jack
-- 
My wife says I have two faults:
I don't listen and something else.

[toc] | [prev] | [next] | [standalone]

#39629

On 12/28/22 11:25 PM, Jack Strangio wrote:
> Nic <Nic@none.net> writes:
>> On 12/28/22 8:09 AM, Monsieur wrote:
>>> Nic wrote:
>>>> On 12/28/22 3:16 AM, Monsieur wrote:
>>>> For the record, are you you a dual-booter?
>>> Actually a quad-booter: I have Mint on sda 1, another Mint on sda2,
>>> Windows 7 on sda3, and finally another Mint on sda4.
>>>
>> It is no wonder that with all that complexity your device can even boot:-)
>>
> He's not the only one. Even when I don't have a Windows partition, I will
> still have three linux root partitions: One every-day system, one emergency
> backup system if the every-day system dies for some reason. And then there's
> root partition number 3 for any time I feel like experimenting with another
> distro.
>
> It save a lot of angst having somewhere to experiment with, and having a
> good system that's working when disaster strikes.
>
> Regards,
>
> Jack

That sounds like a good strategy, except when the experiment disturbs 
the grub boot loader.

[toc] | [prev] | [next] | [standalone]

#39630

On Thu, 29 Dec 2022 07:23:58 -0500, Nic wrote:

> On 12/28/22 11:25 PM, Jack Strangio wrote:
>> Nic <Nic@none.net> writes:
>>> On 12/28/22 8:09 AM, Monsieur wrote:
>>>> Nic wrote:
>>>>> On 12/28/22 3:16 AM, Monsieur wrote:
>>>>> For the record, are you you a dual-booter?
>>>> Actually a quad-booter: I have Mint on sda 1, another Mint on sda2,
>>>> Windows 7 on sda3, and finally another Mint on sda4.
>>>>
>>> It is no wonder that with all that complexity your device can even boot:-)
>>>
>> He's not the only one. Even when I don't have a Windows partition, I will
>> still have three linux root partitions: One every-day system, one emergency
>> backup system if the every-day system dies for some reason. And then there's
>> root partition number 3 for any time I feel like experimenting with another
>> distro.
>>
>> It save a lot of angst having somewhere to experiment with, and having a
>> good system that's working when disaster strikes.
>>
>> Regards,
>>
>> Jack
> 
> That sounds like a good strategy, except when the experiment disturbs 
> the grub boot loader.

If screwing with grub causes anxiety attacks, explore the idea of
running virtual machines on your windows host.

[toc] | [prev] | [next] | [standalone]

#39631

On 12/30/22 6:44 AM, mechanic wrote:
> On Thu, 29 Dec 2022 07:23:58 -0500, Nic wrote:
>
>> On 12/28/22 11:25 PM, Jack Strangio wrote:
>>> Nic <Nic@none.net> writes:
>>>> On 12/28/22 8:09 AM, Monsieur wrote:
>>>>> Nic wrote:
>>>>>> On 12/28/22 3:16 AM, Monsieur wrote:
>>>>>> For the record, are you you a dual-booter?
>>>>> Actually a quad-booter: I have Mint on sda 1, another Mint on sda2,
>>>>> Windows 7 on sda3, and finally another Mint on sda4.
>>>>>
>>>> It is no wonder that with all that complexity your device can even boot:-)
>>>>
>>> He's not the only one. Even when I don't have a Windows partition, I will
>>> still have three linux root partitions: One every-day system, one emergency
>>> backup system if the every-day system dies for some reason. And then there's
>>> root partition number 3 for any time I feel like experimenting with another
>>> distro.
>>>
>>> It save a lot of angst having somewhere to experiment with, and having a
>>> good system that's working when disaster strikes.
>>>
>>> Regards,
>>>
>>> Jack
>> That sounds like a good strategy, except when the experiment disturbs
>> the grub boot loader.
> If screwing with grub causes anxiety attacks, explore the idea of
> running virtual machines on your windows host.

Running a virtual machine is somewhat confusing for me, I am not sure if 
you are referring to the Oracle VM or some other native Linux VM. I have 
installed Oracle VM on my primary platform, and installed M$ W7 in the 
VM, but I find that it can be a bit of trouble now and then. It seems 
that Oracle VM at times becomes corrupted and I have to use a copy/clone 
to get it to run run the VM. Since my needs for W7 are now non existent 
and have not used the W7 in quite a while now, preferring to use LMint 
for all of my day to day operations. It is nice to know that all of my 
computer requirements are fulfilled by LMint.

[toc] | [prev] | [next] | [standalone]

#39633

On 12/30/22 09:03, this is what Nic wrote:
> On 12/30/22 6:44 AM, mechanic wrote:
>> On Thu, 29 Dec 2022 07:23:58 -0500, Nic wrote:
>>
>>> On 12/28/22 11:25 PM, Jack Strangio wrote:
>>>> Nic <Nic@none.net> writes:
>>>>> On 12/28/22 8:09 AM, Monsieur wrote:
>>>>>> Nic wrote:
>>>>>>> On 12/28/22 3:16 AM, Monsieur wrote:
>>>>>>> For the record, are you you a dual-booter?
>>>>>> Actually a quad-booter: I have Mint on sda 1, another Mint on sda2,
>>>>>> Windows 7 on sda3, and finally another Mint on sda4.
>>>>>>
>>>>> It is no wonder that with all that complexity your device can even boot:-)
>>>>>
>>>> He's not the only one. Even when I don't have a Windows partition, I will
>>>> still have three linux root partitions: One every-day system, one emergency
>>>> backup system if the every-day system dies for some reason. And then there's
>>>> root partition number 3 for any time I feel like experimenting with another
>>>> distro.
>>>>
>>>> It save a lot of angst having somewhere to experiment with, and having a
>>>> good system that's working when disaster strikes.
>>>>
>>>> Regards,
>>>>
>>>> Jack
>>> That sounds like a good strategy, except when the experiment disturbs
>>> the grub boot loader.
>> If screwing with grub causes anxiety attacks, explore the idea of
>> running virtual machines on your windows host.
> 
> Running a virtual machine is somewhat confusing for me, I am not sure if you are referring to the Oracle VM or some 
> other native Linux VM. I have installed Oracle VM on my primary platform, and installed M$ W7 in the VM, but I find that 
> it can be a bit of trouble now and then. It seems that Oracle VM at times becomes corrupted and I have to use a 
> copy/clone to get it to run run the VM. Since my needs for W7 are now non existent and have not used the W7 in quite a 
> while now, preferring to use LMint for all of my day to day operations. It is nice to know that all of my computer 
> requirements are fulfilled by LMint.
> 
I use VirtualBox in my Linux Mint 20.3   It's been flawless for me.   I do put the VM Hard disks on my SSD so the VM 
runs a bit faster than if they were on a spinner.   A lot of activity when I run them but I don't use the VMs that much.
I use the Virtualbox software in synaptic.
	Al.

[toc] | [prev] | [next] | [standalone]

#39632

On 12/30/2022 6:44 AM, mechanic wrote:
> On Thu, 29 Dec 2022 07:23:58 -0500, Nic wrote:
> 
>> On 12/28/22 11:25 PM, Jack Strangio wrote:
>>> Nic <Nic@none.net> writes:
>>>> On 12/28/22 8:09 AM, Monsieur wrote:
>>>>> Nic wrote:
>>>>>> On 12/28/22 3:16 AM, Monsieur wrote:
>>>>>> For the record, are you you a dual-booter?
>>>>> Actually a quad-booter: I have Mint on sda 1, another Mint on sda2,
>>>>> Windows 7 on sda3, and finally another Mint on sda4.
>>>>>
>>>> It is no wonder that with all that complexity your device can even boot:-)
>>>>
>>> He's not the only one. Even when I don't have a Windows partition, I will
>>> still have three linux root partitions: One every-day system, one emergency
>>> backup system if the every-day system dies for some reason. And then there's
>>> root partition number 3 for any time I feel like experimenting with another
>>> distro.
>>>
>>> It save a lot of angst having somewhere to experiment with, and having a
>>> good system that's working when disaster strikes.
>>>
>>> Regards,
>>>
>>> Jack
>>
>> That sounds like a good strategy, except when the experiment disturbs
>> the grub boot loader.
> 
> If screwing with grub causes anxiety attacks, explore the idea of
> running virtual machines on your windows host.
> 

Multibooting is a learning experience.

Nothing wrong with that.

With a GPT disk, you can always "dd" /dev/sda1 (the ESP partition)
and loopback mount it as FAT32 and look at the grub materials.
Leaving just the MBR and the boot track as unknown quantities.
As far as I know, UEFI looks in the ESP on its own, so the boot
process there, might well start with the contents of the ESP.

Grub might be harder to "manage" on a legacy partitioned disk.
As there are "more moving parts" and confusion about what
is being used at the moment.

You might find things work better, without a swap partition,
as then you won't be "fixing identifier issues related to swap"
all the live long day. Distros can set up a swap file for
themselves, instead.

*******

You can use a Linux daily-driver and run Linux VirtualBox,
Gnome boxes, and a couple that use qemu-kvm as the engine
(kqemu and one other whose name escapes me). Like foreign
beers, each is an acquired taste. For example, some
virtualization products use a paternalistic approach
to new users, cutting down their install choices.

When I tried Hyper-V, I was immediately turned off by the
experience, without installing anything. You may find
Gnome Boxes using a similar approach. What they're doing
is totally unnecessary. The other extreme is the
qemu-kvm end of the spectrum, where they give you
a list of a couple hundred processors to emulate...
which is just silliness. There are only a few good
choices, and conflicting info on the web as to
which to use and what their side effect is.

Nothing has the straightforward simplicity of Connectix Virtual PC.

VirtualBox comes closest, but with its Soup Nazi approach
to media management, will annoy the hell out of you after
a short while. If the media management has some magical
"protect the user from themselves" objective, I've yet
to run into a case where interference from VirtualBox
protected any of my "materials". With Connectix, it would
only stop you if you did something logically inconsistent
(attempting to use a disk that was hibernated in one
Guest, as materials in a second Guest you were trying to
boot).

    Paul

[toc] | [prev] | [next] | [standalone]

#39634

Nic <Nic@none.net> writes:
> On 12/28/22 11:25 PM, Jack Strangio wrote:
> >
> > It save a lot of angst having somewhere to experiment with, and having a
> > good system that's working when disaster strikes.
> 
> That sounds like a good strategy, except when the experiment disturbs 
> the grub boot loader.
> 
Then you run a 'repair' script that works to chroot into one of the root
partitions and then you either reinstall grub or update grub or both.

I'll see if I can dig one up. ...   This looks like it might be the most
recent one:   "repair.grub.efi.old.installation.nvme"

=======================================================================
# 2018
#When doing a UEFI installation of Mint, it seems fairly common that there
#is a bug which aborts the installation, and gives an error of
#   " grub-efi-amd64-signed failed installation /target/"
# repeat the installation by running this script from the
# "testing Mint option" - IOW run the installation with the script rather
#than clicking in the 'Install' icon.

#    Boot Ubuntu Live DVD/USB in testing mode and open terminal

echo -n "This needs to be run from a live disk. OK????   (ctl-C to abort)   "
read ANSWER

if [ "$LOGNAME" = "root" ]; then
        echo    " NVME Disks have the format /dev/nvmeXXnYY where "
        echo    "   XX is the Controller Number and YY is the Drive Number"
        echo    "   (USE 'fdisk -l' if you want to see what's on the system)" 
        echo    " "
        echo    " "
        echo    "give the Controller Number of the Hard Drive(s) we're using:"
        read XX
        echo " " 
        echo -n "give hard-drive number containing the root partition: (number ONLY) "
        read YY

        fdisk -l /dev/nvme${XX}n${YY}
        echo " "

        echo -n "give PARTITION number of the root partition on /dev/nvme${XX}n${YY}: (NumberONLY) "
        read TARGET

        echo -n "give PARTITION number of the EFI partition on /dev/nvme${XX}n${YY}:  "
        read UEFI

        #    Mount the newly installed file system into /mnt:

        sudo mount /dev/nvme${XX}n${YY}p${TARGET} /mnt
        sudo mkdir -p /mnt/boot/efi
        sudo mount /dev/nvme${XX}n${YY}p$UEFI /mnt/boot/efi
        for x in /dev /dev/pts /proc /sys /run
         do 
            sudo mount -B $x /mnt/$x
         done


        sudo chroot /mnt
        grub-install /dev/nvme${XX}n${YY}
        update-grub

else
      echo " "
      echo "Must be root to do this"
      echo " "

fi
=========================================================================

Regards,

Jack
-- 
My wife says I have two faults:
I don't listen and something else.

[toc] | [prev] | [next] | [standalone]

#39635

Nic wrote:

>>> It is no wonder that with all that complexity your device can even 
>>> boot:-)
>>>
>> He's not the only one. Even when I don't have a Windows partition, I will
>> still have three linux root partitions: One every-day system, one 
>> emergency
>> backup system if the every-day system dies for some reason. And then 
>> there's
>> root partition number 3 for any time I feel like experimenting with 
>> another
>> distro.
>>
>> It save a lot of angst having somewhere to experiment with, and having a
>> good system that's working when disaster strikes.
>>
>> Regards,
>>
>> Jack
> 
> That sounds like a good strategy, except when the experiment disturbs 
> the grub boot loader.

I have been quad-booting for years and never had any problems. Well, 
maybe a few times, but a Boot Repair from a live cd always fixed the issue.

This is the first time I got an error which Boot Repair couldn't fix.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | alt.os.linux.mint

csiph-web