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

    • Although AI is great and has it's use cases they likely have massively overhyped it and it has not delivered as per their expectations. I fully expect them to start saying the same things again when it does get to a certain level of intelligence!
    • Microsoft wants to end printer driver headaches with Windows Ready Print by Usama Jawad A few days ago, Microsoft released Windows 11 Experimental build 26300.8553, bringing a ton of enhancements such as Start menu customization, search improvements, Taskbar polish, and other minor UI tweaks. Another relatively major enhancement snuck deep within the change log was related to upgrades to the Windows printing experience. Now, Microsoft has shared more details about these benefits. For starters, Microsoft has renamed its Modern Print Platform to Windows Ready Print. The company believes that this name highlights its shift in strategy, which now focuses on modernizing, securing, and streamlining the printing experience for Windows devices. Some of the upgrades present in Windows Ready Print have already been seeded to customers and partners. This includes ending support for third-party printer drivers via Windows Update and transitioning towards the Internet Printing Protocol (IPP) and the native Windows IPP printer driver. In line with these changes, new printer installations will default to Windows Ready Print on eligible devices starting from July 2026. However, Microsoft recognizes that not all environments will be able to migrate to this platform immediately, so it will allow users to choose between installing the printer via Windows Ready Print or the traditional OEM process. Users will be able to toggle this configuration through Settings > Bluetooth & Devices > Printers & Scanners > Printer preferences. This control applies only to new printer installations, and its functionality can also be modified via Group Policy as follows: Launch Group Policy Editor Navigate to Local Computer Policy -> Administrative Templates -> Printers Find and select 'Configure Windows Ready Print driver ranking' -> double click to open it Select 'Enabled' (if you wish to enable Windows Ready Print driver selection) or 'Disabled' (if you wish to explicitly disable Windows Ready Print driver selection). Select Apply Select OK Similarly, if you set up Windows protected print mode through the same setting in Windows 11, it will also default to using Windows Ready Print exclusively. Microsoft hopes that these improvements will help eradicate dependency on OEM-specific driver installation processes and simplify printer installations. We'll likely find out more about other tangible benefits in the coming months.
    • Hey what's about the proton vpn firefox extension ? It's not working today
    • On what though? Not Ray Tracing.
  • Recent Achievements

    • 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
    • Week One Done
      rubentuben8 earned a badge
      Week One Done
    • Week One Done
      ARaclen earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      PsYcHoKiLLa
      229
    3. 3
      Edouard
      137
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!