Inconsistant Error -36 when copying files

[Gary Milligan]

Is the external drive a new drive? If so, is it formatted for Mac?

[Tim Wingert]

The external is a Mac-formatted 3TB SATA drive in a USB external dock.

[Gary Milligan]

Sorry Tim… I got nuthin’. Hopefully someone with a broader knowledge base will step in.

Good luck.

[Chris Murphy]

Go to the Console application, click system.log, click Clear Display, reproduce the problem, note and post what’s newly added in Console.

Go to Disk Utility, click on the drive icon with model number etc. (not the name of the volume), and click the Info button in the toolbar. Scroll down to the SMART section and copy-paste what’s there.

[Tim Wingert]

From system Log:

Jan 23 10:03:30 edits-mac-pro.imsav.local com.apple.quicklook.satellite[1393]: [QL] Setting up sandbox for failed, exiting!
Jan 23 10:03:30 edits-mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.034F4C43-9B48-4573-B0A9-1FED3E49D931[1393]): Exited with code: 255
Jan 23 10:03:30 edits-mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.034F4C43-9B48-4573-B0A9-1FED3E49D931): Throttling respawn: Will start in 10 seconds
Jan 23 10:03:45 edits-mac-pro.imsav.local globalsand[66]: GLO Daemon: Unable to connect to the persistent target “LIO Target” at 172.25.1.6 (0xe00002f0 – iSCSI portal was not found at the specified address).
Jan 23 10:04:14 edits-mac-pro kernel[0]: smb2fs_smb_cmpd_create: Second close failed 9
Jan 23 10:04:14 edits-mac-pro kernel[0]: 0xffffff83a4d33ea8, 0x2e005ea Intel82574L::rxFrame – blocking allocate OK
Jan 23 10:04:14 edits-mac-pro kernel[0]: FindFileRef: pid not matching
Jan 23 10:04:50 edits-mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.034F4C43-9B48-4573-B0A9-1FED3E49D931[1394]): Exited: Killed: 9
Jan 23 10:04:54 edits-mac-pro.imsav.local globalsand[66]: GLO Daemon: Unable to connect to the persistent target “LIO Target” at 172.25.1.6 (0xe00002f0 – iSCSI portal was not found at the specified address).
Jan 23 10:06:03 edits-mac-pro.imsav.local globalsand[66]: GLO Daemon: Unable to connect to the persistent target “LIO Target” at 172.25.1.6 (0xe00002f0 – iSCSI portal was not found at the specified address).
Jan 23 10:06:12 edits-mac-pro.imsav.local firefox[206]: invalid context
Jan 23 10:06:54 edits-mac-pro kernel[0]: AppleRAID::completeRAIDRequest – error 0xe00002ca detected for set “Local Video” (E08FB46B-DDE5-43AD-B541-E6484E8F04DF), member E7E30B03-70BC-4244-87D5-079DA684E3BF, set byte offset = 289144029184.
Jan 23 10:06:54 edits-mac-pro kernel[0]: disk4: I/O error.
Jan 23 10:07:03 edits-mac-pro.imsav.local globalsand[66]: GLO Daemon: Unable to connect to the persistent target “LIO Target” at 172.25.1.6 (0xe00002f0 – iSCSI portal was not found at the specified address).
Jan 23 10:08:12 edits-mac-pro.imsav.local globalsand[66]: GLO Daemon: Unable to connect to the persistent target “LIO Target” at 172.25.1.6 (0xe00002f0 – iSCSI portal was not found at the specified address).
Jan 23 10:08:22 edits-mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.034F4C43-9B48-4573-B0A9-1FED3E49D931[1405]): Exited: Killed: 9
Jan 23 10:08:28 edits-mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.034F4C43-9B48-4573-B0A9-1FED3E49D931[1434]): Exited: Killed: 9
Jan 23 10:08:28 edits-mac-pro com.apple.launchd[1] (com.apple.quicklook.satellite.034F4C43-9B48-4573-B0A9-1FED3E49D931): Throttling respawn: Will start in 4 seconds

[Tim Wingert]

The file in question lives on a 3-slice RAID 0…so I can’t really pin down where it lives. Here’s the info on one of the 3 slices:

S.M.A.R.T. Status : Verified
Raw Error Rate : 000000000000
Spinup Time : 000000001068
Start/Stop Count : 000000000217
Reallocated Sectors : 000000000130
Seek Error Rate : 000000000000
Power-On Hours : 000000003D7A
Spinup Retries : 000000000000
Calibration Retries : 000000000000
HDD Temperature : 000000000022
Reallocated Sector Events : 00000000012F
Current Pending Sectors : 00000000059B
Offline Scan Uncorrectable Sectors : 000000000000
CRC Error Rate : 000000000000
Multi-Zone Error Rate : 0000000132E4

[Chris Murphy]

Jan 23 10:06:54 edits-mac-pro kernel[0]: disk4: I/O error.

Is disk4 AppleRAID, or is it a member disk? Try this command if you don’t know:
diskutil list

[Tim Wingert]

/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_RAID 999.9 GB disk0s2
3: Apple_Boot Boot OSX 134.2 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_RAID 999.9 GB disk1s2
3: Apple_Boot Boot OSX 134.2 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_RAID 999.9 GB disk2s2
3: Apple_Boot Boot OSX 134.2 MB disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS OS Disk 999.3 GB disk3s2
3: Apple_Boot Recovery HD 650.0 MB disk3s3
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Local Video *3.0 TB disk4
/dev/disk5
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *500.1 GB disk5
1: Windows_NTFS George 500.1 GB disk5s1
/dev/disk6
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *25.8 MB disk6
1: Apple_partition_map 32.3 KB disk6s1
2: Apple_HFS Silverlight 25.7 MB disk6s2
edits-mac-pro:~ Edit$

[Chris Murphy]

If you don’t already have a current backup of this raid0 array, do it ASAP.

Reallocated Sectors : 000000000130
304 sectors have been reallocated by the drive firmware

Current Pending Sectors : 00000000059B
1435 sectors are pending reallocation. Some of these may not be reallocated because they can’t be read without error, and where the source of the problem is. The firmware won’t move the data if it can’t read it. So the data in these locations is already lost, effectively. There are some data recovery techniques to recover that sector despite the read error, but it’s quite tedious and in the realm of specialized data recovery.

Multi-Zone Error Rate : 0000000132E4
This is a kind of write error and there have been 78564 of them.

I personally would have this disk replaced under warranty. To keep it for raid0 usage is asking for more trouble, corrupt files, and an untimely death of the array. For any other purpose, at a minimum I would write zeros [1] to the drive, and then run an extended smart self-test [2]. Afterwards, if current pending sectors isn’t zero, then the drive is toast.

If this drive isn’t in warranty, I’ll gladly accept it as a donation for R&D however. 😀

[1] I prefer booting linux and using hdparm to issue the ATA Security Erase command. It’s obscure but it’s much faster than Disk Utility write zeros, and it also zeros deallocated sectors, i.e. sectors that contain stale data but can’t be erased any other way because they no longer have an LBA due to reallocation events. Another way to do this within OS X is to use dd with a block size of 1MB, which is option bs=1m. That’s also faster than Disk Utility, but can’t erase data in remapped sectors.

[2] smartctl -t long, this is part of the smartmontools package which can be built from Macports (using XCode). It’s not included in OS X. Macports can also build an installer package, so it’s installable on other computers without having to compile per machine.

[Chris Murphy]

Looks like disk4 is the logical device created from disk0s2, disk1s2, disk2s2 as raid0. The previous error message:

Jan 23 10:06:54 edits-mac-pro kernel[0]: AppleRAID::completeRAIDRequest – error 0xe00002ca detected for set “Local Video” (E08FB46B-DDE5-43AD-B541-E6484E8F04DF), member E7E30B03-70BC-4244-87D5-079DA684E3BF, set byte offset = 289144029184.

Use these commands:
diskutil info disk0
diskutil info disk1
diskutil info disk2

In one of those results you should find the UUID above, “member E7E30B03…” which will implicate a particular /dev/diskX device.

Since /dev/diskX can change between boots, you’d want to use this command:

system_profiler SPSerialATADataType

That will return some more detailed information on each physical SATA disk. Look for BSD Name, and find the implicated diskX from above, and about five lines above that you’ll see the serial number for the drive producing the error.