Something happened to this MAC Drive?

[BenDataRecovery]

Hello guys,

already cloned the drive.. wondering why there is a FAT32 partition at the beginning of the drive. Might this be the cause why the HD is not recognized? R-Studio does not have any problems extracting files...

Maybe someone mounted it to a windows pc? Does this write a partition?

some non technical side story: She wanted the MAC to be repaired by a store (the owner owes me 2000 € - weird guys - funny she didn't knew that at that time) they damaged the MAC and said there was a problem with the drive not readable.. but before the MAC worked fine beside the touchpad problem.... really weird story... - after that she was at a PC repair shop maybe the mounted it and the partition was written to the drive

I hope I can use the MAC migration tool to transfer the settings e.g. to the new MAC of a friend of mine. Once the partition is fixed it is worth a try to use the MAC migration tool?

diskutil list with terminal doesn't list the attached usb drive... strange..

Greetings
Benjamin

Attachments

[BenDataRecovery]

Now it have been shown in terminal session using

Code:

diskutil list

but mounting is not possible ? but maybe the target drive has some issues


wondering how to get the partition recoginzable by a mac

[BenDataRecovery]

This is the result of the command.. maybe the error has something to do with the FAT32 partition written to the beginning of the drive?

Code:

diskutil verifyvolume disk2s2
Started file system verification on disk2s2 Macintosch SSD
Verifying file system
File system check exit code is 8
Error: -69845: File system verify or repair failed
Underlying error: 8: POSIX reports: Exec format error
Benjamins-MBP:volumes Benjamin$ diskutil repairvolume disk2s2
Started file system repair on disk2s2 Macintosch SSD
Repairing file system
File system check exit code is 8
Updating boot support partitions for the volume as required
Error: -69845: File system verify or repair failed
Underlying error: 8: POSIX reports: Exec format error

Last edited by BenDataRecovery on May 15th, 2016, 16:14, edited 2 times in total.

[BenDataRecovery]

Tried some things...
time to go to bed

Code:

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Macintosch SSD          239.2 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
Benjamins-MBP:~ Benjamin$ sudo pdisk /dev/disk2s2
pdisk: can't open file '/dev/disk2s2'  (Resource busy)
Benjamins-MBP:~ Benjamin$ sudo diskutil unmount /dev/disk2s2
disk2s2 was already unmounted
Benjamins-MBP:~ Benjamin$ sudo pdisk /dev/disk2s2
pdisk: can't open file '/dev/disk2s2'  (Resource busy)
Benjamins-MBP:~ Benjamin$


edit...

sudo pdisk /dev/disk2
pdisk: No valid block 1 on '/dev/disk2'
Edit /dev/disk2 -
Command (? for help): i
pdisk: can't open file '/dev/disk2' for writing (Resource busy)
Command (? for help):

[BenDataRecovery]

getting crazy on this... now used the original drive ... same pattern... Any tools that can handle this repairing partition issue?... rstudio works fine for recovering files...

Code:

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *240.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Macintosch SSD          239.2 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
Benjamins-MBP:~ Benjamin$ sudo pdisk /dev/disk2s2
pdisk: can't open file '/dev/disk2s2'  (Resource busy)
Benjamins-MBP:~ Benjamin$ sudo diskutil unmount /dev/disk2s1
disk2s1 was already unmounted
Benjamins-MBP:~ Benjamin$ sudo diskutil unmount /dev/disk2s2
disk2s2 was already unmounted
Benjamins-MBP:~ Benjamin$ sudo diskutil unmount /dev/disk2s3
disk2s3 was already unmounted
Benjamins-MBP:~ Benjamin$ sudo diskutil unmountdisk /dev/disk2
Unmount of disk2 failed: at least one volume could not be unmounted
Benjamins-MBP:~ Benjamin$


[BenDataRecovery]

The FAT32 Partiton - it was not a fault..

Wikipedia

On Apple–Intel architecture Macintosh computers, the EFI partition is initially blank and not used for booting.[11] However, the EFI partition is used as a staging area for firmware updates;[12] specifically, it places a firmware flash utility (EFI binary) and data file (FD – "Firmware Device"[13]) in the directory EFI/APPLE/FIRMWARE which is then run when rebooting the system in "flash firmware" mode.[

In the end there is still a question:

How make the the partition mountable?