riahc3 Posted April 18, 2014 Share Posted April 18, 2014 I dont trust this drive much but just wanted to ask Neowin members.... A couple of days ago, my RAID5 controller said a drive had failed. Here is the log: B 0 E 04/13/14 16:06:45 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:06:51 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:06:59 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/13/14 16:07:07 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x4789a200 sectors 0x48 . B 0 I 04/13/14 16:07:07 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x4789a248 sectors 0x38 . B 0 I 04/13/14 16:07:07 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x4789a280 sectors 0x48 . B 0 E 04/13/14 16:07:27 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:07:34 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:07:42 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:07:49 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:07:57 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 E 04/13/14 16:08:03 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 1 E 04/13/14 16:08:03 Disk 'ST3000DM001' at Controller1-Channel1 failed. B 1 I 04/16/14 18:50:55 Array 'RAID_5_0' rebuilding started. B 1 I 04/16/14 20:25:10 Array 'RAID_5_0' rebuilding started. B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x187d80 sectors 0x80 . B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x188300 sectors 0x80 . B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x188848 sectors 0x38 . B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x188d80 sectors 0x80 . B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x189298 sectors 0x68 . B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x189800 sectors 0x80 . B 0 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/16/14 22:15:13 Successfully repaired bad sector on disk 'ST3000DM001' at Controller1-Channel1: LBA 0x189d00 sectors 0x80 . B 1 E 04/16/14 22:15:13 An error occured on the disk at 'ST3000DM001' at Controller1-Channel1. B 0 I 04/17/14 11:12:04 Array 'RAID_5_0' rebuilding started. B 0 I 04/17/14 22:46:40 Array 'RAID_5_0' rebuilding completed. As you can see, it even says one of the disks straight up failed. I checked that my backup of nonreplaceable stuff was up to date then I did a backup of the entire array. Im busy with a couple of other things but today I look up and I see those two last entries: The RAID5 rebuilt itself without any errors :huh: I dont really trust that drive anymore but what could have happened here? Thank you Link to comment Share on other sites More sharing options...
Starbuck84 Posted April 18, 2014 Share Posted April 18, 2014 From what I know, most hard drives have a build in mechanism to "report" / "block" bad sectors. It doesn't repair itself, it just "marks" those bad sectors and tries to move data from those bad sectors to good sectors. With your RAID5 set-up it's possible the RAID array "repaired" itself just fine. But I don't trust any disk which has bad sectors. I'd say: just replace the disk, as the ST3000DM001 isn't an expensive disk to replace anyway. Thief000 1 Share Link to comment Share on other sites More sharing options...
riahc3 Posted April 18, 2014 Author Share Posted April 18, 2014 From what I know, most hard drives have a build in mechanism to "report" / "block" bad sectors. It doesn't repair itself, it just "marks" those bad sectors and tries to move data from those bad sectors to good sectors. With your RAID5 set-up it's possible the RAID array "repaired" itself just fine. But I don't trust any disk which has bad sectors. I'd say: just replace the disk, as the ST3000DM001 isn't an expensive disk to replace anyway.Its already been replaced; Just surprised that it was able to "mark" a drive as a bad sector and then repair the array. And this RAID5 card sucks... Link to comment Share on other sites More sharing options...
T3X4S Posted April 18, 2014 Share Posted April 18, 2014 I wonder if it simply moved the data to the spare sector reserved on the drive... and your RAID controller just says "repaired sector" - hell I dunno really. I'd like to know as well.LOL I didnt know Starbuck just said the same thing.... so this post is kinda unnecessary. Link to comment Share on other sites More sharing options...
Steven P. Administrators Posted April 18, 2014 Administrators Share Posted April 18, 2014 Yep it just means those bad sectors won't be used anymore :) goretsky 1 Share Link to comment Share on other sites More sharing options...
Starbuck84 Posted April 18, 2014 Share Posted April 18, 2014 From what I can gather, the ST3000DM001 is a simple desktop disk. It will move the data from the bad sector to another (spare) sector on the disk. Using RAID5 it was able to rebuild itself as the disk reports itself as healthy again. Steven P. 1 Share Link to comment Share on other sites More sharing options...
John.D Posted April 18, 2014 Share Posted April 18, 2014 What's the version of the firmware on this hdd?? They have been reported as having random failures in RAID arrays. Link to comment Share on other sites More sharing options...
Starbuck84 Posted April 18, 2014 Share Posted April 18, 2014 What's the version of the firmware on this hdd?? They have been reported as having random failures in RAID arrays. Nice find, although the OP was getting "bad sector" messages. The article you link to states: "The array keeps failing drives. The controller error log shows continuous "aborted command" and/or "link failure" messages when using Seagate Barracuda 7200.14 drives (models: ST3000DM001, ST2500DM001, ST2000DM001, or ST1000DM003)." His RAID array was working fine, but the disk itself reported bad sectors. Just a case of replacing the disk and "nothing to see here people" :) Link to comment Share on other sites More sharing options...
John.D Posted April 18, 2014 Share Posted April 18, 2014 If its been replaced and doing the same thing with the same model. The raid card maybe the prob not the hdd. Altho no harm in updating the FW if CC4H isnt on it. But I would connect it to a SATA port to do it Link to comment Share on other sites More sharing options...
Hum Posted April 18, 2014 Share Posted April 18, 2014 Just a random question -- can you have SSD's in a RAID system ? Link to comment Share on other sites More sharing options...
Starbuck84 Posted April 18, 2014 Share Posted April 18, 2014 Just a random question -- can you have SSD's in a RAID system ? Altough not related to the OP's question, yes you can have SSD's in a RAID system. Link to comment Share on other sites More sharing options...
Thief000 Posted April 18, 2014 Share Posted April 18, 2014 Yes Link to comment Share on other sites More sharing options...
riahc3 Posted April 18, 2014 Author Share Posted April 18, 2014 What's the version of the firmware on this hdd?? They have been reported as having random failures in RAID arrays.I run Seatools on drives that fail as well. Just a random question -- can you have SSD's in a RAID system ?Yes. Link to comment Share on other sites More sharing options...
snaphat (Myles Landwehr) Member Posted April 18, 2014 Member Share Posted April 18, 2014 riahc3, the complete failure you seeing in the logs was probably just a intermittent fault. Those can and do happen with hardware. The other possibility is that the error log is incorrect and giving you inaccurate information (i.e. it wasn't actually a complete failure). Praetor 1 Share Link to comment Share on other sites More sharing options...
riahc3 Posted April 18, 2014 Author Share Posted April 18, 2014 riahc3, the complete failure you seeing in the logs was probably just a intermittent [/size]fault. Those can and do happen with hardware. The other possibility is that the error log is incorrect and giving you inaccurate information (i.e. it wasn't actually a complete failure).Problem is that Ive had these models before and Ive failed so.....yeah it could be inaccurate (still working as of this writing) but... Anyways I bought already another (better) drive to replace it. Link to comment Share on other sites More sharing options...
StarkWiz Posted April 18, 2014 Share Posted April 18, 2014 Yes these desktop drives dont work well with RAID. I would suggest getting drives in SV35.6 series, ST3000VX000. Which drive did you get ? Link to comment Share on other sites More sharing options...
riahc3 Posted April 18, 2014 Author Share Posted April 18, 2014 Yes these desktop drives dont work well with RAID. I would suggest getting drives in SV35.6 series, ST3000VX000. Which drive did you get ? WD30EFRX Link to comment Share on other sites More sharing options...
Praetor Posted April 18, 2014 Share Posted April 18, 2014 Problem is that Ive had these models before and Ive failed so.....yeah it could be inaccurate (still working as of this writing) but... Anyways I bought already another (better) drive to replace it. that error could be a soft error, not a hard error; since the array rebuild itself (i assume your aren't using spare disks right?) then it still is OK to use that disk, since those faults do happen, although buying a new HDD in the upcoming weeks would be a good idea (since you already done that then it's OK). In my clients i see like every month an HDD error, either a soft one that the arrays just fixes itself or a hard one that requires a new HDD. HUM: you can RAID everything! - USB RAID: http://analogbit.com/node/4 - SSD RAID: Link to comment Share on other sites More sharing options...
Recommended Posts