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

    • Microsoft had to shut down 70+ GitHub repos after getting hacked, brings back some by Aditya Tiwari The self-replicating malware campaign known as Miasma took the open-source world by storm. It was reported that almost 73 Microsoft GitHub repositories were infected by the worm and had to be temporarily shut down to determine how attackers compromised projects and stuffed password-stealing malware in the code. These GitHub repos span across different organizations, including Microsoft Azure, Azure-Samples, Microsoft, and MicrosoftDocs. The malware enabled attackers to steal passwords and credentials when compromised tools were opened in popular AI coding apps, including Claude Code, Gemini CLI, VS Code, and Cursor. The security firm Cloudsmith, malware analysis site OpenSourceMalware, and 404 Media were among the first to report the hack. For background, Miasma is a variant of the Mini Shai-Hulud worm, open-sourced by the threat group TeamPCP. It started its journey by compromising a Red Hat employee's GitHub account to attack the @redhat-cloud-services npm namespace. Earlier this month, Microsoft Threat Intelligence reported that the Miasma attackers published 32 malicious packages across more than 90 versions under the @redhat-cloud-services npm scope to steal cloud credentials. The worm didn't take long to start attacking source repos directly rather than package registries. It is known to skip the npm registry entirely for several targets and plant malicious code straight into public repos like "icflorescu/mantine-datatable." The delivery approach was designed to weaponize AI coding tools. Miasma's malicious payload embedded into projects can trigger automatic code execution when the infected repo is opened in an AI coding tool or IDE. The list of affected projects includes "durabletask", a Python package compromised by TeamPCP a month earlier to deliver an information stealer designed for Linux systems. That said, Microsoft has begun restoring some repos affected by the malware campaign, The Hacker News reports. A company spokesperson stated the following: Microsoft will continue to investigate the attack. It has notified a small number of customers who may have removed their content from the affected repos. The company will reach out to customers again through established support channels "if anything further is identified that requires customer action."
    • Why is Opera doing this notification at all? They have their own extension store. They don't have to obey anything dictated by Google. Others like Brave and Vivaldi that rely on Chrome's extension store, not so much. Firefox is entirely separate as well with its own extensions store. I honestly don't understand why entire world is just insisting on Chrome. Like, why? It's a stupid fat browser with barely any functionality. But sure, it's installed on everything by default. I don't understand how people even use web that's filled with tracking garbage and ads all over the place.
    • Just for anyone reading, AdGuard (the free, standalone MV3 extension) is quite good now, a direct competitor to uBlock Origin Lite and much more built-out than it.
  • Recent Achievements

    • Week One Done
      rubentuben8 earned a badge
      Week One Done
    • Week One Done
      ARaclen earned a badge
      Week One Done
    • One Year In
      jojodbn earned a badge
      One Year In
    • One Month Later
      jojodbn earned a badge
      One Month Later
    • Week One Done
      jojodbn earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      531
    2. 2
      PsYcHoKiLLa
      231
    3. 3
      +Edouard
      130
    4. 4
      ATLien_0
      88
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!