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

    • Exactly what I was thinking. All of a sudden in span of a month multiple CEO's from scam altman to this clown has had sudden change of heart does not seem organic change lol
    • Microsoft releases Visual Studio Code 1.124 with smarter autonomous AI agents by Paul Hill Microsoft has just released Visual Studio Code 1.124 with a focus on faster agent workflows and improved agent autonomy. Microsoft outlined the following features as the key items in this update: Autopilot: Autopilot, enabled by default, is now smarter to determine when a task is truly done. Background sessions: Quickly send a request in the background and keep composing the next session. Session navigation: Search, jump, and step through agent sessions with the keyboard. Browser history: Revisit and search pages you've already opened in the integrated browser. With VS Code 1.124, Microsoft has enabled Autopilot by default. For those that don’t know, Autopilot is a chat permission level that you can pick to give agents permission to take initiative and act autonomously, without needing explicit user approval for each action. Also related to Autopilot, Microsoft introduced Advanced Autopilot, which changes how Autopilot decides when to keep iterating and when to finish. This helps you get more complete results without manually monitoring loops. This feature works using a small utility model that reads a transcript of the chat and decides when the task is done. Another new feature in 1.124 is the Agents window, which lets you easily explore, iterate on, and review agent sessions across projects and machines. Previously, starting a new agent session meant waiting for it to load before you could compose the next one. With this update, sessions can be requested in the background. This VS Code update also brings session navigation updates to switch between them more quickly. The update also lets you reload or reopen the Agents window so that it no longer loses your layout, so you will land back where you left off. If you use the integrated browser in VS Code, you will notice that it now retains the history of visited pages. Suggestions will now show when typing in the URL bar and can be managed by using Ctrl+H within a browser tab. The browser now also lets you customize the toolbar more; just right-click on the toolbar area to the right of the URL input. Finally, the browser has faster agentic text entry. Another improvement is experimental enterprise-managed Copilot plugin policies that allow admins to centrally control which chat plugins and plugin marketplaces are available to developers. If you have VS Code installed, 1.124 should install automatically, or you'll get a prompt. If you don't have it installed, get it here.
    • Ray-Tracing is the Radeon RX 9070 XT's biggest weakness. The Radeon RX 9070 XT might not be able to match in the GeForce RTX 5070 Ti in ray-tracing, but it can beat the GeForce RTX 5070, which is around the same price.
    • I am also on latest experimental with possible insider flags on and aiming in settings for 26h1.. Also see just this wasted space. I do love "movable" small taskbar though but would love more if it had date next to it now just time.
    • Does not make it more readable for me though. The majority of your screenshot is just pitch black.
  • Recent Achievements

    • First Post
      X-No-file earned a badge
      First Post
    • One Month Later
      johnjacobb40 earned a badge
      One Month Later
    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      512
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      +Edouard
      145
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      86
  • Tell a friend

    Love Neowin? Tell a friend!