- Joined
- Nov 20, 2015
- Messages
- 11
- Motherboard
- AsRock H97M Pro4
- CPU
- Xeon 1231v3
- Graphics
- GTX 980
- Mac
- Classic Mac
- Mobile Phone
Based on the experience of other tonymacx86-users who seem to have had no issues with upgrading similar dual boot setups, I decided to give it a go. In fact, the upgrade it self went fine, but I can’t boot into Windows anymore.
I didn’t disconnect the other SSD with Windows during the upgrade, which probably was a mistake.
Now, when I select the boot option for Windows (either in Clover or UEFI boot menu), Windows starts an automatic repair mode which tells me, that it’s unable to repair the PC. Using the command prompt to execute bootrec manually didn’t help either.
Booting back into High Sierra, I looked at the partition tables using diskutil list:
As you can see, I’m using two separate SSDs for Mac and Windows, as well as an HDD for storage.
The upgrade to HS created /dev/disk3. This seems to be the contents of the APFS container at disk1s2, which is mounted as a virtual drive when OS X boots up, correct?.
The sidebar of the disk utility app looks quite messed up now (see screenshot attached).
But have a look at disk0, my Windows drive:
The partition disk0s4 is of type Apple_HFS. This is supposed to be the partition where my Windows data used to be.
Any idea what happened there? How can I fix this and recover my Windows partition?
I didn’t disconnect the other SSD with Windows during the upgrade, which probably was a mistake.
Now, when I select the boot option for Windows (either in Clover or UEFI boot menu), Windows starts an automatic repair mode which tells me, that it’s unable to repair the PC. Using the command prompt to execute bootrec manually didn’t help either.
Booting back into High Sierra, I looked at the partition tables using diskutil list:
Code:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: Windows Recovery 471.9 MB disk0s1
2: EFI NO NAME 104.9 MB disk0s2
3: Microsoft Reserved 16.8 MB disk0s3
4: Apple_HFS 249.5 GB disk0s4
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *256.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk3 255.9 GB disk1s2
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk2
1: Windows_NTFS Disk 1.0 TB disk2s1
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +255.9 GB disk3
Physical Store disk1s2
1: APFS Volume macOS 218.6 GB disk3s1
2: APFS Volume Preboot 19.0 MB disk3s2
3: APFS Volume Recovery 520.0 MB disk3s3
4: APFS Volume VM 20.5 KB disk3s4
As you can see, I’m using two separate SSDs for Mac and Windows, as well as an HDD for storage.
The upgrade to HS created /dev/disk3. This seems to be the contents of the APFS container at disk1s2, which is mounted as a virtual drive when OS X boots up, correct?.
The sidebar of the disk utility app looks quite messed up now (see screenshot attached).
But have a look at disk0, my Windows drive:
The partition disk0s4 is of type Apple_HFS. This is supposed to be the partition where my Windows data used to be.
Any idea what happened there? How can I fix this and recover my Windows partition?