Jump to content
1 post in this topic

Recommended Posts

Dear Community,

 

I just finished installing my new Hackintosh box with the following basic specs (working really fast BTW):

 

MSI K8T Neo2 v.2 (K8T800 chipset)

AMD Athlon 64 3200+ (SSE2 + SSE3)

1GB Generic Ram (one infenion and one crappy chip)

ATI Radeon 9800 Pro 128MB

 

I have a serious problem with my /TEMP partition, which resides on a drive connected as slave on IDE2 together with my DVD-Burner. I use this partition to store my SuperDuper! backup (sparse image) files and old windows files I am planning to burn soon.

 

The problem happens only when I will mount one of the backup files to recover a kext file and try to copy it onto TEMP (yes on itself but outside the image). The Finder will abort the copy function every singe time with an "error -36" message. It says that it cannot read some of the files in the kext file (or any other file for that matter), period. I know this is normally an I/O Issue but the drive has never complained before.

 

 

EDIT: While writing this I was saving all my backup files onto my boot drive (single partition with 30GB free). I then mounted an image and everything worked fine this time. At this point I'm starting to think that the drive might really be broken.

 

I then copied one 2,5GB image file back to the original TEMP drive and tried to reproduce the error but this time everything worked fine.

I then concluded that the drive might just have been too full (with the backups in it it had only 550MB free) so I started copying the rest of the images back to TEMP (yes, I am crazy). This time Finder threw an error -36 again while copying the last and largest file (10GB). I retried, and the problem persisted. It seems that Finder will copy almost all of the file and abort with an error on the last portion (around 99%). Ok, so now I'm sure it has something to do with the drive being too full to handle the images. Since the images are so-called sparse files (dynamic images) it could be that the system requires a minimum of free space on the host partition to able to handle it. Probably a sparse file issue then. Comments?

 

EDIT: OK, so now I erased all the images from TEMP and tried to copy them back in different orders. The drive would ALWAYS abort when it got almost full. The funny thing is that it still has 500MB by the time it aborts! I mean, why should it abort if there is still some free space, right? I don't know if this only happen with sparse files or with other files as well but I will continue to experiment.

 

The last thing I would like to comment is that the partition in question, TEMP, cannot be repaired via diskutill using "Repair Disk Permissions". I can however, press "Repair Disk". The drive has "owners enabled" and my primary user is set as the owner. What he heck?

 

I would like to hear what you guys have to say about this. I assume this could be documented somewhere but I was just able to find some posts discussing "error -36" while using Windows SMB.

 

:angel: I really don't know what to make of this.

 

hecker

×
×
  • Create New...