Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[dbaps2]

I have a 2006 Mac Pro using a Newertechnology Maxpower Raid card that is configured for RAID10,

I have four ST3000DM001-9YN166, three on firmware CC4B and one on CC4C.

32096 bad sectors on one drive and repaired. This has happened over a period of just three days.

I saw the article about not upgrading a RAID config under Windows. Does the same apply to a boot disc on an Intel Mac? Will it possibly help? I can't find any release notes for all of the changes since CC4B.

My concern is the short span of time that I'm getting so many bad sectors.  I'm running Lion. First Aid failed to fix the array. But a rebuild does fix it.

I can't seem to find a Seetools type tool for a Mac. What should I use to test the drive? If there is nothing I have a Vmware Fusion Windows 7 VM that I could try and test the drive. Is this supported?

Everything is backed up. Worst case I could break the array and test the drive on a Windows computer with Seatools. Suggestions?

Thanks,Paul

[dbaps2]

The drive is now getting s.m.a.r.t error code b8 value 60.

184

0xB8

End-to-End error / IOEDC

This attribute is a part of Hewlett-Packard's SMART IV technology, as well as part of other vendors' IO Error Detection and Correction schemas, and it contains a count of parity errors which occur in the data path to the media via the drive's cache RAM.

[dbaps2]

Just to give everyone an update. I updated the firmware on all of my drives to CC4H. Then I switched from RAID10 to RAID5 with a spare. This week I started getting the same B8 error on two other drives.

I'm beginning to think these drives are just bad. The first drive this happened to I did a low level format and upgraded the firmware. That drive I'm still testing but seems fine. These two drives, getting the same B8 Smart error, are not showing any bad sectors found and repaired like the first drive did. What's weird is that the event log says the two drives have or had bad sectors. Does the RAID rebuild reset the bad sector count to 0? 

In any case I'm copying all of my data off just to be sure. This is very frustrating. I don't know if I should report this or not? Three out of five drives with a B8 SMART error.

Any suggestions?

Thanks, Paul

Date Time	Description
	2012/12/24 20:54:15	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-S1F0K4ZN' at Controller1-Channel3: LBA 0x41be4f0 sectors 0x8 .
	2012/12/24 20:53:59	An error occured on the disk at 'ST3000DM001-9YN166-S1F0K4ZN' at Controller1-Channel3.
	2012/12/22 8:52:26	Array 'RAID_5_0' rebuilding completed.
	2012/12/22 0:46:39	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0xbf14e80 sectors 0x8 .
	2012/12/22 0:46:15	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/20 1:47:58	Array 'RAID_5_0' rebuilding started.
	2012/12/20 1:47:58	Array 'RAID_5_0' data is not consistent.
	2012/12/20 1:45:4	Array 'RAID_5_0' verifying started.
	2012/12/20 1:45:2	Scheduled task (Verify Raid Task) started.
	2012/12/17 13:25:29	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x4e8f18 sectors 0x10 .
	2012/12/17 13:25:3	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x2a57cef8 sectors 0x8 .
	2012/12/17 13:25:3	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x25b3500 sectors 0x18 .
	2012/12/17 13:25:3	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x25b3680 sectors 0x18 .
	2012/12/17 13:25:3	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x25b3080 sectors 0x18 .
	2012/12/17 13:25:3	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x25b3980 sectors 0x18 .
	2012/12/17 13:25:3	Successfully repaired bad sector on disk 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4: LBA 0x25b3298 sectors 0x68 .
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/17 13:25:3	An error occured on the disk at 'ST3000DM001-9YN166-W1F04J9Z' at Controller1-Channel4.
	2012/12/13 15:39:26	Array 'RAID_5_0' rebuilding completed.
	2012/12/13 3:15:49	Array 'RAID_5_0' rebuilding started.
	2012/12/13 3:15:49	Array 'RAID_5_0' data is not consistent.
	2012/12/12 22:55:3	Array 'RAID_5_0' verifying started.
	2012/12/12 22:55:1	Scheduled task (onetime) started.