Here’s the output of the commands asked for, I appreciate the help. I’m curious what went wrong because I want to learn from this so I put some questions/my understanding at the end – feel free to ignore
[manjaro@manjaro Desktop]$ inxi -Mxa
Machine:
Type: Desktop Mobo: Micro-Star model: B450 GAMING PRO CARBON AC (MS-7B85)
v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.F4
date: 04/22/2021
[manjaro@manjaro Desktop]$ test -d /sys/firmware/efi && echo efi || echo bios
efi
[manjaro@manjaro Desktop]$ sudo efibootmgr -v
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0000,0004,0002,0007,0006,0001,0005
Boot0000* Windows Boot Manager HD(2,GPT,4b35f749-00e9-4788-87a8-5e6c03abd4c1,0x109000,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.}...9................
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........S.a.m.s.u.n.g. .S.S.D. .9.7.0. .E.V.O. .5.0.0.G.B...................\.,.@.r.d.=.X..........A...........................%8T.B~}.....4..Gd-.;.A..MQ..L.S.5.H.7.N.J.0.N.4.1.4.1.6.7.L........BO
Boot0002* manjaro HD(2,GPT,4b35f749-00e9-4788-87a8-5e6c03abd4c1,0x109000,0x32000)/File(\EFI\MANJARO\GRUBX64.EFI)
Boot0004* UEFI OS HD(5,GPT,a54c3b62-5111-f040-b0c4-ff899245d586,0x19df2000,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005 USB HDD BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0900)..GO..NO..........K.i.n.g.s.t.o.n.D.a.t.a.T.r.a.v.e.l.e.r. .3...0.P.M.A.P...................\.,.@.r.d.=.X..........A.............................F..Gd-.;.A..MQ..L.6.0.A.4.4.C.4.1.3.D.F.8.E.4.9.1.1.9.2.E.0.4.A.3........BO
Boot0006* UEFI: KingstonDataTraveler 3.0PMAP PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(2,0)/CDROM(1,0x4d88ac,0x8000)..BO
Boot0007* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2 PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(2,0)/HD(2,MBR,0x0,0x4d88ac,0x2000)..BO
[manjaro@manjaro Desktop]$ sudo parted -l
Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sda: 62.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 2602MB 2606MB 4194kB primary esp
Model: Samsung SSD 970 EVO 500GB (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 556MB 555MB ntfs Basic data partition hidden, diag
2 556MB 661MB 105MB fat32 EFI system partition boot, esp
3 661MB 677MB 16.8MB Microsoft reserved partition msftres
4 677MB 222GB 222GB ntfs Basic data partition msftdata
5 222GB 223GB 537MB fat32 msftdata
6 223GB 225GB 2147MB linux-swap(v1) swap
7 225GB 246GB 21.5GB ext4
8 246GB 500GB 254GB ext4
[manjaro@manjaro Desktop]$ sudo lsblk -fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squashfs 4.0 0 100% /run/miso/sfs/livefs
loop1 squashfs 4.0 0 100% /run/miso/sfs/mhwdfs
loop2 squashfs 4.0 0 100% /run/miso/sfs/desktopfs
loop3 squashfs 4.0 0 100% /run/miso/sfs/rootfs
sda1 iso9660 Joliet Extension MANJARO_XFCE_2106 2021-06-07-19-55-50-00
└─sda iso9660 Joliet Extension MANJARO_XFCE_2106 2021-06-07-19-55-50-00 0 100% /run/miso/bootmnt
sda2 vfat FAT12 MISO_EFI 4A03-D73C
└─sda iso9660 Joliet Extension MANJARO_XFCE_2106 2021-06-07-19-55-50-00 0 100% /run/miso/bootmnt
nvme0n1p1 ntfs Recovery 34DECF54DECF0CD4
└─nvme0n1
nvme0n1p2 vfat FAT32 2ACF-93D6
└─nvme0n1
nvme0n1p3
└─nvme0n1
nvme0n1p4 ntfs 9C0CD0A00CD076AC
└─nvme0n1
nvme0n1p5 vfat FAT32 1EB7-C94B
└─nvme0n1
nvme0n1p6 swap 1 afd121e3-cca8-40fd-8535-3e241d39435c
└─nvme0n1
nvme0n1p7 ext4 1.0 88ec38db-9f99-4ff1-8f7a-41b7f1ec6589
└─nvme0n1
nvme0n1p8 ext4 1.0 d1447f1e-654f-435c-9153-0b6e4472eb4e
└─nvme0n1
This all started when I update mobo drivers on Windows (I did the guide by aarhus found here which has Windows first, so all my drivers were windows side).
It looks like this somehow overwrote my GRUB and windows MBR is the default, correct? I suspect my /etc/fstab might be slightly off as well because it doesn’t have entries for all the partitions I remember, but it seems weird that a Windows update would be able to edit that?