corrupted partition table, need help fixing

Hello LonerT,

sorry for the delay with replying ....

The RE partition sneaked itself in with the Windows 10 April update. Didn't notice it because it's hidden by default.

The HFS+ partition is my share space between Windows/macOS. I don't recall how I created it initially (either with du, or with Paragon HDM). But yesterday I did use HDM (against your past advice on the subject), to merge some space that HDM was showing as unused/unallocated (something around 130MB) with the HFS+ partition. Unfortunately HDM screwed up the partition table again.

here is the output you requested:

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 100.1 GB disk0s2

3: Microsoft Basic Data Windows 140.3 GB disk0s3

4: Windows Recovery 513.8 MB disk0s4

5: Apple_HFS SHARE 9.9 GB disk0s5

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +100.1 GB disk1

Physical Store disk0s2

1: APFS Volume macOS - Data 38.2 GB disk1s1

2: APFS Volume Preboot 79.5 MB disk1s2

3: APFS Volume Recovery 528.6 MB disk1s3

4: APFS Volume VM 1.1 GB disk1s4

5: APFS Volume macOS 10.3 GB disk1s5

output of sudo fdisk /dev/disk0:

Disk: /dev/disk0   geometry: 30515/255/63 [490234752 sectors]
Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
 1: EE 1023 254  63 - 1023 254  63 [         1 -  490234751] <Unknown ID>
 2: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 3: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

no, im ok with what’s there now.

though you mentioned something about getting rid of the windows RE partition. so i assume if its safe for me to do that (probably is), then we would combine that space with SHARE ?

if so, i’m ok with moving forward ...

both OS's boot normally

In Windows, File Explorer, the SHARE partition is no longer shown, whereas before the restructuring, it was present and browsable. I have an HFS driver in Windows that allows me to read/write on HFS/HFS+ partitions.

I had a look at Disk Management in Windows while I was booted in, this is what I saw:

do not know if that unallocated space of 128MB is of any concern ... ?

ah yes, the drive letter was unassigned. went into Disk Management, assigned a letter and now it appears in File Explorer. Thanks for mentioning that.

before moving on, wanted to show you these errors from DU. Only "Container disk 1" and "macOS - Data" are showing fsroot tree errors. the errors have been around dating back to High Sierra days. would be beneficial for you to know I'm on the next macOS version beyond Mojave.

for reasons that escape me, i cannot find the reason or source of the errors and have been unsuccessful with fixing.

i suppose that if it doesn't impact the APFS partition integrity or fixing the GPT, i'll ignore these errors.

output:

apfs_load_inode_internal:4825: Set VNFS_CANTCACHE for firmlink source vnodes
apfs_get_firmlink_target_vnode:1791: inode is a firmlink, need to return vnode of target path
error: container /dev/rdisk1 is mounted with write access.

here is the output:

error: container /dev/rdisk1 is mounted. repairs in a mounted container is not supported yet.

i have tried to unmount macOS and macOS - Data, and ran disk utility first aid on macOS - Data, it would not repair the fsroot tree error.

i also have SIP disabled.

the output i posted earlier (2 responses up) was from single user mode.

the link you gave referred me to recovery mode, i tried that as well in case i was misinterpreting. those results are my most previous post.

/dev/disk1s5 on / (apfs, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
/dev/disk1s4 on /private/var/vm (apfs, local, journaled, nobrowse)
/dev/disk0s3 on /Volumes/Windows (ntfs, local, read-only, noowners)
/dev/disk0s4 on /Volumes/SHARE (hfs, local, journaled)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
//admin@wdmycloud/Public on /Volumes/Public (smbfs, nodev, nosuid, mounted by *****)
//*****@wdmycloud/***** on /Volumes/***** (smbfs, nodev, nosuid, mounted by *****)
//admin@wdmycloud/My_Book on /Volumes/My_Book (smbfs, nodev, nosuid, mounted by *****)

i was able to merge the unallocated 128mb of space with the SHARE partition, and went back to gdisk to do a verify.

results say there are no problems with the GPT. aside from 3 segments of unallocated space totaling about 900kB, it seems the table is in good shape.

since my partitions are functional, working well ... i dont think theres a need to focus on the GPT anymore.

but it would be nice to try to fix the fsroot tree errors i have, if they are fixable.

concerning unmounting disk1, looks like disk1 contains the parts of macOS that im booted into. how would i unmount it ?

i went into recovery once more, I issued the mount command to see what's there (below). not sure if it's normal to see so many disks present.

sorry to have used up your time for the help, i'm going to give up on this.

i used COMMAND + R, i did not think that was internet recovery ... just regular recovery.

either way, i think its best to start clean. i could use extra space so i might go with an owc ssd.

my apologies for consuming your time, and thank you for the help i greatly appreciate it.

do you think there is a possibility that my recovery partition is corrupted ?

if so, can that be corrected by doing a reinstall of macOS from external drive ?

i think a reinstall would preserve my apps and data.

my model is 11,2 ... the model i wanted to buy (aura N) supports bootcamp with this model i believe.