Dual boot woes - Windows update killed booting both OS's.

I don't know.

In what measurement unit? Which Risk Management ISO standard?

The risk is obviously binary: total annihilation vs. eternal peace on earth.

I was just hoping for a "NO, don't do THAT, you idiot!!!" or else "sure, roll the dice, the odds of a collision down the road are virtually zero."

OBVIOUSLY!!

OK, in that case I will have to figure out how to generate an "official" short UUID. :dizzy_face:

It's answered

Oh, sorry! OK, thank you, I will try to take it from here, and will report back. Thanks again.

1 Like

OK, an update (thanks to all those who have helped):

  • I don't believe there are any remaining duplicate UUIDs. However, I note that there are some duplicate PARTUUIDs.

  • Correcting the duplicate UUIDs did not fix the Windows boot problem (that would have been too easy, right?).

  • I note that GParted claims that it cannot detect a file system on the following "Microsoft reserved partitions": /dev/nvme1n1p3 and /dev/nvme0n1p3. I don't know if this is normal or not.

  • I noticed that my main swap, on /dev/nvme1n1p5, is missing! What!?

Here is the data (redone) that was requested:


sudo parted -l

Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 2098kB 317MB 315MB fat32 boot, esp
2 317MB 963GB 963GB ext4
3 963GB 1000GB 37.1GB linux-swap(v1)

Model: Unknown (unknown)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 524MB 523MB ntfs Basic data partition hidden, diag
2 524MB 629MB 105MB fat32 EFI system partition boot, esp
3 629MB 646MB 16.8MB Microsoft reserved partition msftres
4 646MB 2000GB 2000GB ntfs Basic data partition msftdata

Model: Unknown (unknown)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 524MB 523MB ntfs Basic data partition hidden, diag
2 524MB 629MB 105MB fat32 EFI system partition boot, esp
3 629MB 646MB 16.8MB Microsoft reserved partition msftres
4 646MB 336GB 336GB ntfs Basic data partition msftdata
5 336GB 1000GB 664GB ext4


sudo blkid

/dev/nvme1n1p1: LABEL="Recovery" UUID="FC22225A22221A62" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="976f9c90-a0e0-11e9-bab0-b7f996171c9d"
/dev/nvme1n1p2: UUID="4223-1575" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="976f9c91-a0e0-11e9-bab0-b7f996171c9d"
/dev/nvme1n1p4: UUID="5F2186C97E25E839" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="976f9c93-a0e0-11e9-bab0-b7f996171c9d"
/dev/nvme1n1p5: UUID="a1be17fe-3926-47f9-b824-d395f7f64186" TYPE="ext4" PARTUUID="cdced3bd-a97d-4ba1-ad44-51cba38bc94e"
/dev/nvme0n1p1: LABEL="Recovery" UUID="599647A622221A62" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f923ee65-0b8b-47e3-bf29-aeb03c973e99"
/dev/nvme0n1p2: UUID="2C44-9274" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="c727faf8-af54-4095-a3fd-0fcfbee503f4"
/dev/nvme0n1p4: UUID="BA7E26327E25E839" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5b455e1d-78af-4d9f-94d4-0e3659cb52a2"
/dev/sda1: UUID="E589-8600" TYPE="vfat" PARTUUID="5899f905-b0c3-4ee9-b12f-18ef2c39ef63"
/dev/sda2: UUID="defd1791-59e4-4319-b3f1-4f106f7d4804" TYPE="ext4" PARTUUID="1938c9fa-edbb-415d-9c4e-ee3e272cf041"
/dev/sda3: UUID="115efeec-5e1a-4e2c-985a-20019e4d5008" TYPE="swap" PARTUUID="49ab2337-c0ad-4bb4-8c37-f68cbcfe3638"
/dev/nvme1n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="976f9c92-a0e0-11e9-bab0-b7f996171c9d"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="c34f2009-57bd-4bc6-9e95-c9c637e816e5"


test -d /sys/firmware/efi && echo UEFI || echo BIOS

UEFI


efibootmgr -v

BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0001,0000,0005,0006,0002
Boot0000* Windows Boot Manager HD(2,GPT,c727faf8-af54-4095-a3fd-0fcfbee503f4,0xfa000,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}..._................
Boot0001* Hard Drive BBS(HD,,0x0)..GO..NO........q.S.a.m.s.u.n.g. .S.S.D. .9.6.0. .E.V.O. .1.T.B....................A...........................%8Rq.G.....4..Gd-.;.A..MQ..L.S.3.E.T.N.X.0.J.2.0.4.4.1.6.D........BO..NO........q.S.a.m.s.u.n.g. .S.S.D. .9.7.0. .E.V.O. .2.T.B....................A...........................%8Z.........4..Gd-.;.A..MQ..L.S.4.6.4.N.B.0.K.A.0.6.5.0.5.M........BO..NO........o.S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .1.T.B....................A...........................>..Gd-.;.A..MQ..L.2.S.C.1.S.N.G.A.0.1.2.0.0.9. .F. . . . ........BO
Boot0002
Manjaro VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0005* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO........o.A.S.U.S. . . . .D.R.W.-.2.4.B.1.S.T. . . .j....................A...........................>..Gd-.;.A..MQ..L.3.G.0.D.L.C.0.0.5.8.0.2. . . . . . . . ........BO
Boot0006 Windows Boot Manager HD(2,GPT,976f9c91-a0e0-11e9-bab0-b7f996171c9d,0xfa000,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)..BO
Boot0007* UEFI OS HD(1,GPT,5899f905-b0c3-4ee9-b12f-18ef2c39ef63,0x1001,0x96001)/File(\EFI\BOOT\BOOTX64.EFI)..BO


I mentioned that I've been preparing to wipe and reinstall Windows on its own drive in the eventuality that I cannot fix it. I'm quite low on space in my main Manjaro drive, too, and given all the self-inflicted problems could consider starting over there as well. :anguished:

Thank you again.

What the living heck!?

I made another attempt to use the Windows CD to perform a repair following the UUID changes. It failed again in its usual way. But now... I can't boot into anything, including my backup Manjaro disk (which I didn't think to remove first).

The symptom was that the machine kept trying to boot back into the Windows CD rather than where I was pointing it. After taking out the CD, the Bios still shows everything there, but trying to boot into a proper disk results in a bios complaint: "Reboot and select proper boot device."

This is going from bad to worse. I need to take a break from this and cool off a while.

Morning, hope you have a good break yourself. Now back to work.
Hopefully you cleaned out your double cloned UUID issue by petsam.
BTW, I don't know about cloning windows, I hear windows do not like clone and they do not work, probably ... well, they are (neo-liberal rent-seeking trumpian/clintonian capitalist) micro$oft, not us communist linux.

There are a few things. To make it simple, for a start...(there's more)

  1. Your manjaro entry (directed to /boot/efi) is not there in efibootmgr
    It must be there. But since it is default to bootx64.efi, we can also copy our grubx64.efi to it.
  2. More serious and harder is that you have 2 nvme drives.
    I do not have nvme drives but special parameters needed to be in kernel line or (more difficult) you can hide unwanted nvme in udev partition rules.
    We'll need to @Hipster and @Cagnulein help here as they have fixed it themselves. I'll do my best (under their supervision).

Let's start with the simple one first.
Try to boot up manjaro installed OS (which one?) by using this first post here. Start manjaro live media in uefi and (if you have 2 manjaro's) use the one your want to use.
search.file /etc/manjaro-release
set root=(hdx,y)

Oh, now we need your /etc/fstab
But continue to fix it and don't forget the 2 [Additional UEFI commands] when booted up.
It is important we must do these 2 commands.

Now here (for the 2 nvme disks you have) add "nvme_core.multipath=0" to this line in your /etc/default/grub and 'sudo update-grub'

GRUB_CMDLINE_LINUX_DEFAULT="quiet nvme_core.multipath=0"

Reboot normally and see if you can boot to manjaro.
We'll handle windows next (hopefully).

@Hipster (on nvme)
So far so good?

[EDIT] -
While using the live media grub prompt, add in the linux line the nvme parameter

grub> linux /boot/vmlinuz-4.19-x86_64 root=UUID=$abc  nvme_core.multipath=0 rw

Sorry i cannot help at all with your current in-progress rescue operation [good luck], but wrt your two extracts i quoted... given afaik from interpreting your words, windoze just needs to be around in case you occasionally need to use it, but most of the time you'll not be using it. Therefore, consider doing what i did years ago... blow away the windoze partition/s & instead install windoze in a VM. I hate it passionately, & feel very dirty anytime i fire it up, which is very rarely & in all honesty is only to keep in touch with it for the times i need to remotely support my Dad's win10 via TeamViewer. The point being however that if you make this change, you'll certainly never risk any future upgrade conflicts, yet you'll still have the redmond rubbish on hand for those rare times you need it.

2 Likes

Good as new. No problems at all. No more swapping. :ghost:

1 Like

Hello all,

Yesterday I repeated a mistake (using MS's "competing OS elimination disk" again while other OS's were in the system). I don't completely blame myself - surely a "repair" function shouldn't fail to fix anything at all but instead lay waste to your entire system, right? Right!?

From this point, I need to make a plan and act more carefully.

  • No more attempts at repair of the Windows drive unless I have specific information about the problem (MS provides none at all) and its solution, which is probably not going to happen.

  • Get something running: Right now, I can boot into Mint (I had another old OS drive around), albeit only in fall-back mode, I believe since I have a newer graphics card in the system and can't update the old drivers so far. This can see the other drives.

  • I'm able to have Manjaro on a live CD running. It can see all the drives too.

  • Using gohlip's instructions (thank you!), I was able to boot into my main Manjaro drive. Some commands failed after that, though (I'll detail later if important). For the moment I want to make an additional backup of this drive.

  • I hear there are issues having more than one nvme drive. Ugh. I hadn't seemed to have issues with this myself, aside from weirdness given the duplicate UUIDs. From the sound of it, the fixes for two drives may be a little above my pay scale, so I have to decide whether to settle on one drive only or go down that rabbit hole.

  • I've toyed with virtual machines in a very limited way (on a Mac, actually), but not really enough to know what I'm doing. I agree that running Windows within one must be safer, but I'm not sure how satisfactory the performance may be for my uses. Without more research, I'm not inclined to plan for this.

  • I have some components from an earlier machine that I could assemble a new machine (if I buy some supplementary components) specifically to run Windows only. But this will be inconvenient in several ways, as it would be more difficult to share keyboards, mice, audio out, etc., and I already have 2 displays and keyboards, etc., on my desk as it is (the other system is a Mac).

  • At the moment, I'm inclined to start over. It's a royal pain, but I've done it before more than once. If one nvme drive is not a problem, but two are, I could wipe the 2 TB Windows disk and install a dual boot system on that single drive. BUT, will later MS updates upset this combo again anyway?

I guess the overriding question is what should my plan be regarding the drives and OSs.

The easiest way is do as I did for 15 years, never had a problem.
2 separate drives Win on one Linux on the other keep them separate totally that way they cannot mess with each other

Yes, but I've been using two nvme drives not SATA, and apparently there's a problem with that.

If one NVME works fine, I suppose I could use NVME for one and SATA for the other?

I've got two nvme drives. One windows, one manjaro. No problems at all once I added the above line to the kernel.

nvme_core.multipath=0

Can you provide a link or explain a little more about how you added this to the kernel and its ramifications? For example, does the addition have to be redone after updating to a new kernel, etc?

To dodge as many potential issues as possible, I'm inclined to start over with Manjaro on the NVMe drive and Windows on the SATA drive. I imagine that this may be safer than a single drive dual-boot configuration. Does anyone have any wisdom about this choice?

I'm going to remain paranoid about Windows updates. In the past, I've found that it's safer to remove drives that aren't involved in updates. This is extremely annoying with NVMe drives due to the need to dig way into a machine to remove it. But Windows can be very impatient about updates, and sooner rather than later will force them without further warning. In my opinion, this is extremely hostile behavior ("we own your computer, lowly consumer, not you!").

Have a look here:


I added a little more to the first post for you.

Thank you Hipster, I may give that a try.

Epilogue:

I started over and created a dual-boot system on a single NVMe drive. Everything is OK now.

Not a fun experience, but I learned a few things thanks to the generous help I received here.

Thank you all for your help!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.