• Content Count

  • Joined

  • Last visited

  • Days Won


Oubadah last won the day on October 22 2013

Oubadah had the most liked content!

Community Reputation

4 Neutral

About Oubadah

  • Rank
  1. I think this has something to do with the drives being recently secure erased. That graph wasn't an anomaly (I tried multiple times and got the same abysmal results), but a bit later I ran it again and it started giving me normal graphs: So then I rebuilt the array, secure erasing the drives in the process, and now it's back to giving me demented graphs again. This makes no sense.
  2. This is the problem: (I stopped the benchmark early, but it's clearly not right) Read looks fine: Individual writes look normal as far as I can tell: Other benches look normal: So what's going on with that write graph? RST: Drive firmware: DXM06B0Q
  3. The more I search this, the more confused I get. I have a WD20EARX that was used in a PVR for a while, and a couple of days ago I shifted it into a PC. "Raw Read Error Rate" data was at 0 to start with. After writing about 1.5TB to it I happened to notice that the data value is now 3. What does this mean? I have a couple of other WD drives in the PC (one a system drive, the other for programs), and as far as I know the "Raw Read Error Rate" data value has never changed from 0.
  4. I have a server machine running Windows 7 with an SSD for the OS/programs and several other mechanical HDDs for file storage. I have Windows power management set to 'Turn off hard disk after' a certain period of time. The problem is that Windows is regularly spinning up these drives while they are not being used and I don't want to subject them to excessive spin up/down cycles just because Windows likes to play musical drives with them. Windows has no business messing with them - they aren't system drives, and I certainly haven't scheduled anything to be accessing them. How do I stop these unnecessary spin-ups during idle? I've disabled indexing, automated defrag a virus scan schedules.