Recommended Posts

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
https://www.neowin.net/forum/topic/1209947-hdd-fixed-itself/
Share on other sites

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.

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...

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.

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.

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" :)

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).

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.

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:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Playground Games confirms Forza Horizon 6 save wipe bug by Taras Buria Forza Horizon 6 was launched last month to critical acclaim (check out our review here), and it became a smash hit in an instant. Now, weeks into the launch, with die-hard fans clocking hundreds of hours, Forza Horizon 6 is facing a serious issue: save wipes. After multiple complaints on Reddit and social media, the studio issued a statement. The problem with missing saves came shortly after Playground Games promised the initial batch of gameplay tweaks and improvements. Unfortunately, there seems to be no temporary fixes for those affected by unexpected save wipes. However, the studio published a new support document with a few important steps users should try. First, affected gamers should open a support ticket immediately (go here to file one) so that the support team can try recovering the lost progress by reverting to an earlier save. Playground Games says this should be done the same day the issue occurs. Meanwhile, gamers are urged not to start new play sessions or create new saves. The studio also published a few things gamers should try to avoid to prevent potential progress loss: Ensure your Gaming Services app on PC or XBOX Series X|S console is fully up to date. On XBOX Series X|S consoles, disable Quick Resume for Forza Horizon 6: To disable Forza Horizon 6 from using Quick Resume, highlight the game box art anywhere in the console experience (Home, My Games & Apps, Pins, etc) and then press the Menu button, then go to Manage game and add-ons > Quick Resume settings > Disable Quick Resume. Ensure you are online when ‘quitting’ the game. Give your saved time to sync to the cloud before powering off or switching devices. Do not force quit the game during save screens. Do not power off the device during gameplay. Always "Quit" (console) or "Exit to desktop" (PC) once you've finished your play session, ensuring the save icon is not visible when you’re closing the game. Before turning off your console, shutting down your PC, or force-closing the Steam app, give your devices or clients at least a few minutes to ensure your latest progress has been synchronized with the cloud. This will reduce the risk of progress reversions as you switch between different platforms. XBOX Series X|S consoles, Steam, and the XBOX app on PC all include game save indicators that confirm your progress has been synced. You can read more about the bug in the official support document here. Forza Horizon 6 is currently available on PC (Steam and the Microsoft Store), Xbox Series X|S, and Game Pass. The game is also coming to PlayStation 5 later this year.
    • If only Windows would have a toggle switch labeled "Get the latest updates as soon as possible" inside Windows Update settings... But nah, let's hide the new stuff inside a controlled feature rollout, even if the user is explicitly asking for the new stuff as soon as possible. Awesome idea!
    • After watching the Apple event earlier this week it is quite the contrast. Apple is going back and tweaking the code to make things more efficient in many areas of MacOS. Windows is boosting your electric build to hide their issues.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      199
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      74
  • Tell a friend

    Love Neowin? Tell a friend!