You are not logged in.
I was multi-booting Windows 7 and just done with latest Arch install on MBR. I wanted to delete one of the logical partition Windows was installed on and clicked delete partition on either nvme0n1p6 or nvme0n1p7 in Disk Management (Windows) and left it alone. After I came back to my PC, the laptop was in the Grub Rescue Menu.
Now
$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
nvme0n1
├─nvme0n1p1 ntfs System Reserved A6EADA08EAD9D521
├─nvme0n1p2 ntfs 786EEDEC6EEDA35C 68G 32% /media/mint/786EEDEC6EEDA35C
├─nvme0n1p3 ntfs CE8AD1BC8AD1A16F 83.6G 16% /media/mint/CE8AD1BC8AD1A16F
├─nvme0n1p4
└─nvme0n1p5 ntfs Program E624102A240FFBEDBefore
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 [SWAP]
nvme0n1
├─nvme0n1p1 ntfs System Reserved A6EADA08EAD9D521
├─nvme0n1p2 ntfs 786EEDEC6EEDA35C
├─nvme0n1p3 ntfs CE8AD1BC8AD1A16F
├─nvme0n1p4
├─nvme0n1p5 ntfs Program E624102A240FFBED
├─nvme0n1p6 ntfs F8C0665DC06621DC
├─nvme0n1p7 ntfs F4D6AD0FD6ACD2E2
└─nvme0n1p8 btrfs f9df1b06-24cf-495b-9ef7-e37dd0aeff7a 374.3G 9% /var
/tmp
/opt
/home
/.snapshots
/Last edited by ochinko (2022-09-22 12:58:07)
Offline
Why would you do these kind of operations on Windows which literally doesn't have good concepts of logical partitions with an MBR boot? Why do you even have an MBR boot on an nvme drive in the first place, it's nearly a miracle this even works in but I'd assume there are a lot of assumptions on the BIOS and operating system parts that aren't really designed around this and actually and effectively expect GPT.
Check whether you can restore the partition with testdisk/photorec or so. Other than that this is technically a Windows question so you'd need to ask on a Windows board what it's behaviours are in regards to using it's disk manager.
Last edited by V1del (2022-02-16 18:48:52)
Offline
Offline
Why would you do these kind of operations on Windows which literally doesn't have good concepts of logical partitions with an MBR boot? Why do you even have an MBR boot on an nvme drive in the first place, it's nearly a miracle this even works in but I'd assume there are a lot of assumptions on the BIOS and operating system parts that aren't really designed around this and actually and effectively expect GPT.
Check whether you can restore the partition with testrec or so. Other than that this is technically a Windows question so you'd need to ask on a Windows board what it's behaviours are in regards to using it's disk manager.
Was said that Windows 7 was more stable on MBR than GPT. Learnt my lesson the hard way, would avoid any disk-partition-related operations on Windows from now on.
I tried looking for testrec but I only found testdisk. Was that the one you meant?
Sorry for asking here, I thought since there was still a Grub Rescue Boot it was still technically Arch-related and I wouldn't mind if I lost all of my Windows to recover my Arch.
Plus, the forum help here has always been the best I've ever experienced. I have no idea what Windows boards there are, could I trouble someone to link me?
Last edited by ochinko (2022-02-16 18:38:53)
Offline
AS mentioned, check whether you can restore the partition table with testdisk (flubbed the name there) and/or photorec.
Not sure where you got that from, GPT is definitely supported by Win 7, any UEFI capable board/operating system needs to support GPT.
Last edited by V1del (2022-02-16 18:50:40)
Offline