2 seagate drives, 1 dead, another I am not sure

I am not much of a hard drive guy (computer enthusiast, gamer, overclocker) so I came here than asking on my home forum.

Here is drive one. This one I know is okay (I think):

Code:: *** DiskCheckup V3.0 Build: 1006 Report *** SysInfo DLL Version: SysInfo v1.0 Build: 1008 Time of export: 11:01:05 28-Mar-2011 Device information: Device ID: 4 Interface: SATA Device Capacity: 238472 MB Serial Number: 6RYAAJTB Model Number: ST3250310AS Firmware Revision: 3.AAF Partitions: N/A ATA information: Disk geometry: Cylinders: 30401 Tracks/Cylinder: 255 Sectors/Track: 63 Bytes/Sector: 512 Total disk sectors: 488395055 Logical sector size: 512 Physical sector size: 512 Media rotation rate: N/A Buffer size: 8192 KB ECC size: 4 Bytes Standards compliance: ATA8-ACS Supported: No ATA/ATAPI-7 Supported: Yes ATA/ATAPI-6 Supported: Yes ATA/ATAPI-5 Supported: Yes ATA/ATAPI-4 Supported: Yes World Wide ID: 0000000000000000 Feature support: SMART supported: Yes SMART enabled: Yes SMART self-test supported: Yes SMART error log supported: Yes LBA supported: Yes IORDY supported: Yes CFast supported: No DMA supported: Yes Maximum Multiword DMA mode supported: 2 Multiword DMA selected: None Maximum UltraDMA mode supported: 6 UltraDMA selected: 6 Maximum PIO mode supported: 4 SATA Compliance: Yes NCQ priority information supported: No Unload while NCQ commands are outstanding supported: No Phy Event Counters supported: Yes Receipt of power management requests supported: No NCQ feature set supported: Yes SATA Gen2 Signaling Speed (3.0Gb/s) supported: Yes SATA Gen1 Signaling Speed (1.5Gb/s) supported: Yes Software Settings Preservation: Supported, Enabled In-order data delivery: Not supported Initiating power management: Supported, Disabled DMA Setup auto-activation: Not supported Non-zero buffer offsets: Not supported Trusted Computing supported: No Host Protected Area (HPA) supported: Yes Read look-ahead supported: Yes Read look-ahead enabled: Yes Write cache supported: Yes Write cache enabled: Yes Power management supported: Yes Security mode supported: Yes Security mode enabled: No Device Configuration Overlay (DCO) supported: Yes 48bit Addressing supported: Yes Auto Acoustic Managment (AAM) supported: No Power-up in Standby (PUIS) supported: No Advanced Power Management (APM) supported: No CompactFlash Association (CFA) supported: No General Purpose Logging (GPL) supported: Yes Streaming supported: No Media card pass through supported: No Extended power conditions supported: No Extended status reporting supported: No Write-read-verify supported: Yes Write-read-verify enabled: No Free-fall control supported: No TRIM command supported: No SCT command transport supported: Yes NV Cache enabled: No NV Cache Power Management supported: No SMART ATTRIBUTES: ID Description Status Value Worst Threshold Raw Value TEC --------------------------------------------------------------------------------------------------------------------------------------------- 1 Raw Read Error Rate OK 100 253 6 0 N.A. 3 Spin Up Time OK 99 98 0 0 N.A. 4 Start/Stop Count OK 98 98 20 2493 N.A. 5 Reallocated Sector Count OK 100 100 36 0 N.A. 7 Seek Error Rate OK 83 60 30 220886062 N.A. 9 Power On Time OK 92 92 0 7711 N.A. 10 Spin Retry Count OK 100 100 97 0 N.A. 12 Power Cycle Count OK 90 90 20 10638 N.A. 187 Reported Uncorrectable Errors OK 92 92 0 8 N.A. 189 High Fly Writes OK 100 100 0 0 N.A. 190 Temperature Difference from 100 OK 76 58 45 705101848 N.A. 194 Temperature OK 24 42 0 24 C N.A. 195 Hardware ECC Recovered OK 119 46 0 216094432 N.A. 197 Current Pending Sector Count OK 100 100 0 0 N.A. 198 Uncorrectable Sector Count OK 100 100 0 0 N.A. 199 UltraDMA CRC Error Count OK 200 200 0 0 N.A. 200 Write Error Count OK 100 253 0 0 N.A. 202 Data Address Mark Errors OK 100 253 0 0 N.A. SMART HISTORY: Attribute ID: 1 Attribute Name: Raw Read Error Rate Date Value Worst --------------------------------------------------------------------------------------------------------------------------------------------- Mon Mar 28 03:30:06 201 100 253 Mon Mar 28 03:30:06 201 100 253 Mon Mar 28 03:30:07 201 100 253 Mon Mar 28 11:00:07 201 100 253 Mon Mar 28 11:00:09 201 100 253 Attribute ID: 3 Attribute Name: Spin Up Time Date Value Worst --------------------------------------------------------------------------------------------------------------------------------------------- Mon Mar 28 03:30:06 201 98 98 Mon Mar 28 03:30:06 201 98 98 Mon Mar 28 03:30:07 201 98 98 Mon Mar 28 11:00:07 201 99 98 Mon Mar 28 11:00:09 201 99 98

And here is drive 2. This one I am sure is bad, but want to make sure. It is what broke my RAID0

Code:: Disk geometry: Cylinders: 30401 Tracks/Cylinder: 255 Sectors/Track: 63 Bytes/Sector: 512 Total disk sectors: 488395055 Logical sector size: 512 Physical sector size: 512 Media rotation rate: N/A Buffer size: 8192 KB ECC size: 4 Bytes Standards compliance: ATA8-ACS Supported: No ATA/ATAPI-7 Supported: Yes ATA/ATAPI-6 Supported: Yes ATA/ATAPI-5 Supported: Yes ATA/ATAPI-4 Supported: Yes World Wide ID: 0000000000000000 Feature support: SMART supported: Yes SMART enabled: Yes SMART self-test supported: Yes SMART error log supported: Yes LBA supported: Yes IORDY supported: Yes CFast supported: No DMA supported: Yes Maximum Multiword DMA mode supported: 2 Multiword DMA selected: None Maximum UltraDMA mode supported: 6 UltraDMA selected: 6 Maximum PIO mode supported: 4 SATA Compliance: Yes NCQ priority information supported: No Unload while NCQ commands are outstanding supported: No Phy Event Counters supported: Yes Receipt of power management requests supported: No NCQ feature set supported: Yes SATA Gen2 Signaling Speed (3.0Gb/s) supported: Yes SATA Gen1 Signaling Speed (1.5Gb/s) supported: Yes Software Settings Preservation: Supported, Enabled In-order data delivery: Not supported Initiating power management: Supported, Disabled DMA Setup auto-activation: Not supported Non-zero buffer offsets: Not supported Trusted Computing supported: No Host Protected Area (HPA) supported: Yes Read look-ahead supported: Yes Read look-ahead enabled: Yes Write cache supported: Yes Write cache enabled: Yes Power management supported: Yes Security mode supported: Yes Security mode enabled: No Device Configuration Overlay (DCO) supported: Yes 48bit Addressing supported: Yes Auto Acoustic Managment (AAM) supported: No Power-up in Standby (PUIS) supported: No Advanced Power Management (APM) supported: No CompactFlash Association (CFA) supported: No General Purpose Logging (GPL) supported: Yes Streaming supported: No Media card pass through supported: No Extended power conditions supported: No Extended status reporting supported: No Write-read-verify supported: Yes Write-read-verify enabled: No Free-fall control supported: No TRIM command supported: No SCT command transport supported: Yes NV Cache enabled: No NV Cache Power Management supported: No SMART ATTRIBUTES: ID Description Status Value Worst Threshold Raw Value TEC --------------------------------------------------------------------------------------------------------------------------------------------- 1 Raw Read Error Rate OK 100 253 6 0 N.A. 3 Spin Up Time OK 99 98 0 0 N.A. 4 Start/Stop Count OK 98 98 20 2493 N.A. 5 Reallocated Sector Count OK 100 100 36 0 N.A. 7 Seek Error Rate OK 83 60 30 220886087 N.A. 9 Power On Time OK 92 92 0 7711 N.A. 10 Spin Retry Count OK 100 100 97 0 N.A. 12 Power Cycle Count OK 90 90 20 10638 N.A. 187 Reported Uncorrectable Errors OK 92 92 0 8 N.A. 189 High Fly Writes OK 100 100 0 0 N.A. 190 Temperature Difference from 100 OK 73 58 45 705101851 N.A. 194 Temperature OK 27 42 0 27 C N.A. 195 Hardware ECC Recovered OK 109 46 0 216110688 N.A. 197 Current Pending Sector Count OK 100 100 0 0 N.A. 198 Uncorrectable Sector Count OK 100 100 0 0 N.A. 199 UltraDMA CRC Error Count OK 200 200 0 0 N.A. 200 Write Error Count OK 100 253 0 0 N.A. 202 Data Address Mark Errors OK 100 253 0 0 N.A. SMART HISTORY: Attribute ID: 2132 Attribute Name: (Unknown attribute) Date Value Worst --------------------------------------------------------------------------------------------------------------------------------------------- Wed Dec 31 19:00:00 196 0 0 Wed Dec 31 19:00:00 196 0 0 Wed Dec 31 19:00:00 196 0 0 Wed Dec 31 19:00:00 196 0 0 Wed Dec 31 19:00:00 196 0 0 Wed Dec 31 19:00:00 196 0 0 Wed Dec 31 19:00:00 196 0 0

What is your symptom ? what have you done so far to troubleshoot your symptom ? more details needed to be able to offer assistance.

Okay, first off my computer started to act slow. Mouse was laggy, everything was just slow. I restarted and Intel RAID (Using onboard RAID controller on my GA-EP45-UD3P which is integrated into the south bridge) and it said RAID status - Failed. I have tried to fix my raid but that isn't going to happen... Anyway really have done much other than run smart. I can run more diagnostic tests once I get my machine up and running again (installing to a spare 500GB drive).

I see no clear evidence that drive 2 is more faulty than drive 1, in the evidence you've given.

The only point of slight concern is attribute 187 having a non-zero raw value - however that is true for both drives and, interestingly, is the same value on both drives (8). Therefore that is inconclusive, since you are reporting that drive 2 is the only problem.

If I was in your situation, I would:

a) collect the output from "smartctl -a /dev/sdX" for both drives, after installing smartmontools (there is a version for Windows, which I assume is what you run on this games system). That will include extra info, in addition to what you have provided above.

b) check the Windows event log for anything worrying, especially around the time when you believe the system was slow.

c) install HD Tach Pro trial (or any other graphical benchmarking utility of your choice) and see whether, when benchmarked individually, the read test graphs for the two drives have the same correct shape - or not.

d) the only evidence you're reporting of a drive problem seem to be that error report from the Intel RAID. Therefore any extra info that you can collect from that about exactly what it thinks the problem was (e.g. read error, timeout, or whatever), will also be important. I use different RAID systems, so I don't have extra advice about what info is available, but I would certainly be looking for it, since a reported "RAID error" is not going to be helpful for you to find what problem there really was (if any).

Raid0 striped drives if one drive failed you loose the entire raid volume. What did you do when you mentioned "I tried to fix my raid ?" Do you have another drive in this computer that is the boot drive ? My idea would be to image each drive then use a raid reconstructor program to attempt to resurrect the raid set and recover the data if that is the end goal.

networks wrote:My idea would be to image each drive then use a raid reconstructor program to attempt to resurrect the raid set and recover the data if that is the end goal.

Good point.

In my suggestions, I had interpreted the OP as wanting to try to find out whether their "drive 2" was faulty, but you're right that the OP's end goal hasn't been clearly specified, so that was an assumption on my part, due to the focus of the data presented by the OP.

Hopefully he'll clarify what assistance he is requesting...

It looks like I got a lot of work ahead of me. Give me a few days and I can get all the data you need. Right now I have them running in RAID1 for the time being just so that I can move some data around.

Lord Xeb wrote:Give me a few days and I can get all the data you need.

I can't tell what your expectations are in your post, so let me be clear - I've given suggestions above, about where I would start to look for any evidence that drive 2 has a problem, if I was in your situation, and if I wanted to try to find such evidence.

However your comment about getting "all the data you need" might mean you're expecting that I'll keep working on this until there is a definite conclusion - that isn't the case.

It is possible that no evidence of a problem will be found in the areas which I have suggested - which would then be inconclusive as to what problem (if any) did occur when your system was slow.

My suggestions also assume (as networks pointed out) that investigating "drive 2" is what you are asking - but I can't see a clear statement that this is your goal.

It also seems that you actually may not be able to supply some of the info that I suggested looking at, since you mention that you're re-installing that system. Specifically, have you still got the Windows event log from the time when you report that RAID volume was slow, and any other logs / evidence from that time, from the Intel RAID functionality (which you will need to investigate, since I don't have any experience with that type of RAID)? Or are you hoping that you'll be able to recreate the problem again, and gather the logs at that time?

Just to be accurate, in the title of this thread, you report that there is "1 dead" drive (your "drive 2"). No, there isn't a dead drive.

The fact that you could extract its SMART data shows that it isn't dead.

In fact it is quite common for RAID controllers (of many different types that I've worked with over the years), to declare a drive as "dead" or "failed" or whatever term that specific controller uses, when the drive is not really dead or faulty, and the problem is actually elsewhere - or there was no actual fault, just a drive behaviour which the RAID controller didn't like (e.g. drive taking a long time performing internal read recovery retries, and the RAID controller reached its timeout limit, and gave up waiting - you can read about TLER & ERC if you're interested in this type of potential issue, but I have no idea if it applies to the Intel RAID on your motherboard).

Until you can find more info about exactly what problem the Intel RAID "thinks" it detected (using whatever error logging it does), then the only thing I can suggest (which is why I suggested it!) is to start to look for evidence of typical drive problems in the places that I mentioned - but it's quite a shot in the dark, without you having more info about specifically what problem you're looking for.

Good error logging is one of the features you pay for with business RAID systems, in order to be able to quickly identify the cause of problems, and it is one of the limitations that I see with smaller SOHO RAID systems. If the behaviour you observed didn't leave any error messages (or they have been erased), and the problem can't be reproduced, then there may not be evidence to reach a conclusion about what happened.

Hm... well I just learned a lot XD If anything I am using this as a learning experience. Right now I have the drives running in RAID1 and I am going to play around with them... Sorry I messed up and wasn't able to provide what you needed... Also I wasn't even able access my drives and I didn't know I could rebuild my raid to begin with.

Could an error that occured within the ECC memory on the hard drive (one that couldn't be corrected) break the raid?

Lord Xeb wrote:Hm... well I just learned a lot XD If anything I am using this as a learning experience.

OK.

As part of that learning, I'd suggest checking where your RAID controller stores its error log (if any), for future reference.

Lord Xeb wrote:Right now I have the drives running in RAID1 and I am going to play around with them...

Great, and if they continue to both work OK, that suggests that there is no fundamental/obvious problem with the disks. FYI there are sometimes limitations with gathering the detailed SMART details from the individual disks in a RAID volume - depending on whether software like smartmontools knows the "pass-through" commands for your specific RAID controller.

Lord Xeb wrote:Sorry I messed up and wasn't able to provide what you needed...

No need to apologise - it's just that without that sort of evidence, then I'm unlikely to be able to help you find root cause for the original event, that's all.

Lord Xeb wrote:Also I wasn't even able access my drives

That may be deliberate behaviour by the RAID controller - after what it believed to be a faulty disk in a non-redundant RAID volume (e.g. RAID 0). This is quite typical behaviour on RAID systems I'm familiar with, but in your case, there is no evidence (error logs etc.) about what disk problem the RAID controller thinks it detected, as I've mentioned. Just because a RAID controller thinks a disk is faulty, does not mean that the disk is actually faulty.

Lord Xeb wrote:Could an error that occured within the ECC memory on the hard drive (one that couldn't be corrected) break the raid?

Have you got any evidence to suggest that this happened? Also, I haven't met a disk which actually has ECC memory (those I've seen use different techniques to detect any corruption of the data within the disk drive controller memory). I'm wondering if perhaps you don't mean an ECC error within the disk's memory (i.e. its controller SDRAM), but instead perhaps you mean an ECC read error (i.e. UNC) from the media?

If that is what you mean, then you'll need to investigate what behaviour your RAID controller has in that case. The RAID controllers I'm familiar with, would not change the state of a disk or RAID volume (even non-redundant) after just UNC errors on a disk - you'd just have some unreadable blocks on that RAID volume. Personally, I think your suggestion would be poor behaviour for a RAID controller to have, but it is something you could investigate via the support channels for your RAID controller, if you want to investigate your hypothesis further.

I just ran seagate tools (ISO) on my drives, and the one that I though had failed was reported as failed. Error code 98e6e361.

The other drive (which has 2 reallocated sectors) is fine.

RMAing to seagate but I need to find some foam... e-e I have no idea where to get it. Anyone got a clue where to get what I need in the New York, New York area? Or can I call seagate and have them send me it?

I haven't RMAed a drive to Seagate, however from my experience with WD you should be able to select an option stating that you want the HDD MFG to send you the new (it's really a recertified drive) first. Once you get the new hdd setup you can send them the failing drive back to them using the box which had the new hdd.

Lord Xeb wrote:I just ran seagate tools (ISO) on my drives, and the one that I though had failed was reported as failed. Error code 98e6e361.

Congratulations on making some progress.

It would have been interesting to see exactly what behaviour the RAID controller originally detected, but you explained, that isn't available.

Lord Xeb wrote:The other drive (which has 2 reallocated sectors) is fine.

I guess what you mean by that statement, is that Seagate's tool doesn't report that drive as failed - which is not the same thing as the drive being fine, at all.

a) The data you provided at the beginning shows 0 reallocated sectors on both drives (look at the raw value of SMART attribute 5 from both drives in your first post), so something has changed.

b) The Google data centre study on disk drive reliability (as well as my personal experience), shows a significant correlation between a disk having non-zero reallocated sectors, and premature disk failure. Therefore I'd suggest closely monitoring the health of any drive with reallocated sectors, and make sure you have up-to-date, verified, backups of that drive's data.

Anyway, since you've got the answer you wanted from the Seagate tool, it looks like the analysis phase is done, so I'll wish you good luck

Well I think my other drive is in not so good of health either.

It has 3 current pending sector.

Currently doing an error scan (see more issues if any), then doing a zero fill to see if that fixes anything and a reformat.

UPDATE:

1 more current pending sector just went up on the hard drive...

Attachments

Sounds like you have it figured out drives going south time to replace

Yes and it is with the help of you guys. Thank you very much... now if only there was a rep button

Just got my drives back from Seagate and just sold them. Now I have 2 750GB drives going out for RMA that I will be getting back and getting a 3rd from newegg. RAID5 baby! w00t!

2 seagate drives, 1 dead, another I am not sure

2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure

Re: 2 seagate drives, 1 dead, another I am not sure