Utilizing my Mac, I partitioned an external hard drive as exFAT. diskutil
and the next instructions:
diskutil listing
diskutil unmountDisk drive disk2
I'll improve the text as a professional editor.
sudo yes | pv -n 1000000 -s 100M > /dev/disk2
`diskutil partitionDisk disk2 GPT APFS "Windows Partition" 0GB`
After partitioning, the output of diskutil listing
is:
/dev/disk2 (Exterior, Physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *251.0 GB disk2 1: EFI EFI 209.7 MB disk2s1 2: Microsoft Fundamental Information HDD 250.8 GB disk2s2
After transferring numerous record files, including JPG and PDF formats, to an external drive and connecting it to a Windows machine, I received a warning message advising me that ignoring it could result in the disk opening with limited access, allowing me to view most records except for some initially high-quality PDFs on my Mac. Despite this, whenever I try to access these PDFs on Windows, they become corrupted, and reattaching the HDD to my Mac fails to allow me to open the files. The files appear to be grayed out within the list. Despite attempting to resolve the issue through Windows’ built-in scan and repair function, the problem persists.
I successfully adopted the same course with another disk without any issues. This former interior hard drive of my Mac, having been replaced, now seeks a new purpose as an external storage device. Files may become inaccessible due to a variety of reasons such as disk errors, corrupted file systems, or malware infections. In Windows, you might encounter an error message stating that the file is being used by another process or it’s currently in use by another application. This can occur when a file is open in a specific program and cannot be accessed until the program is closed.
I successfully employed Disk Utility, selected the “Verify All Devices” option, and securely formatted the primary external storage device. All files appear immediately when using the disk in Windows now; however, the “repair disk” error still persists. Despite attempting to repair the issue by pressing “repair,” the problem persists even after reconnecting the device.