• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About lunadesign

  • Rank
  1. This is probably a silly question, but is it safe to run chkdsk on an NTFS partition on a RAID1 volume like you would on a normal drive? My drive health is fine but I may have some filesystem-level issues and wanted to check. In case it matters, the system is running Windows 7 and the RAID card is an LSI 9260-8i.
  2. In case anyone is interested, I spoke with my contact at WD and he didn't seem to think this was normal. I got two more new WD60EFRX units and they not make the squealing noise. These new ones sound very similar to the WD30EFRX but the single click sound made at power down is a bit louder on the new WD60EFRX units (probably due to the increased platter count) but it still sounds totally normal. I'm definitely returning the original set of drives.
  3. Sorry for the delay....I finally got some decent audio recordings tonight. I recorded a WD60EFRX unit and then a WD30EFRX to compare. In each case, I powered up the drive by itself outside of the cage with no OS or other drives connected, then hit the power button to spin the drive down. In the WD60EFRX recording, you can hear the drive spin up at the 7 sec mark and the spin down squeal starting at 32 sec. In the WD30EFRX recording, you can hear the drive spin up at the 5 sec mark and the quiet spin down starting at 26 sec. I've never attached files on this forum so if someone could please let me know that they could access the attachments, I'd greatly appreciate it. Thanks! WD60EFRX.mp3 WD30EFRX.mp3
  4. I agree about the drives not having different speeds while reading/writing. And it certainly wouldn't make sense for a 5400 RPM drive to go to 7200 RPM (if you believe the tech) if its not reading/writing. So the tech clearly has been hanging out in the Marketing Dept too much. It make sense that Windows would have an opportunity to send a signal that triggers a more elegant spin-down. I tried both drives in 2 different systems including one situation where I had the bare drive outside of the system and all combinations exhibited the problem. So, it doesn't appear to be specific to a single mobo or case. No. The easiest way for me to reproduce this is to turn on the system with one of these drives connected and no others. Since the drives have no data yet, the system BIOS POSTs and then stops because there's no OS. At this point, if I power off the system, I get the squeal. I'll try to find a way to record the is quite unique. Does anyone know if there is a way on this forum to upload audio clips?
  5. Thanks! Much appreciated! For what its worth, one of the two drives has gone through the full WD Lifeguard set of tests and came out fine. That said, the noise sounds like its going to damage something. (As an aside, the very friendly WD Red tech originally thought it might have something to do with IntelliPower varying the drive speeds between 5400 and 7200 RPM. I thought it was already proven conclusively that the WD Red/Green drives only have one speed and that IntelliPower is just Marketing silliness. Or did something change with NASware 3.0 that I missed?)
  6. I just bought 2 WD Red 6 TB (WD60EFRX) drives and noticed something odd while doing some testing on my usual test system. When I power off the system using the PC's power button (i.e., because I've just finished doing some DOS-based tests), the drives emit a noticeable squeal/screech noise for about 2-3 seconds. If I shut down from Windows (not using the power button), the drives shut down quietly like one would expect. I have over a dozen WD Reds (3 TB and 4 TB) and none of them have ever made this noise. In fact, I've never heard a noise like this out of a drive. Is this normal for the newer WD Reds? I tried the WD Red support line and the very friendly support person wasn't sure.
  7. I'm familiar with the often discussed scenario where a RAID 5 array has a URE (unrecoverable read error) during a rebuild and therefore kills the array. What about RAID 1 or RAID 10? I've heard that since these are mirrors, a URE during a rebuild will rot the affected bit but not kill the array. Is this true?
  8. LSI 9270 shredding my hard drives?

    UPDATE #3: The RAID 1 with two WD Se drives (both with upgraded firmware) worked well. The LSI card still seems to be acting oddly and not using both drives as much as it should be for simultaneous reads. When the LSI card is only using one drive and there are multiple reads going on, the WD Se (with upgraded firmware) works well. For most of the time, the single drive runs at or near the speed it would be if a single reader was reading a single drive. Every few minutes, I saw the single drive fall for about 2 seconds to the 10-15 MB/s level with the growling noise but otherwise worked great. I'm still working with LSI on the controller issue.
  9. LSI 9270 shredding my hard drives?

    UPDATE #2: The new WD Se firmware seems solid. I ran some benchmarks on a single drive before and after the firmware update and the results were nearly identical except the updated drive is a bit slower (~10%) on small random writes. The benchmark tests didn't trigger the big problem I was seeing with two readers but my own testing so far (connected to motherboard) shows that this problem has been completely solved. I've updated two of my drives and am trying them on the LSI in a RAID1 configuration today.
  10. LSI 9270 shredding my hard drives?

    UPDATE: It looks like I've got a fix for problem #2. WD's Level 3 support guy was really helpful and provided me with the latest firmware (01.01A02) for the Se drives. Now, when I hit a single WD drive with two long read ops, the drive deals with it very well. If I start both read ops at the same time, the drive struggles like before for about a second or two (with a little of the growling noise) and then quickly (within about 4-5 seconds) ramps up to 170 MB/s. If I start the second read op after the first one, it skips the struggling stage and settles in at around 170 MB/s. I'm still testing to make sure that this firmware didn't make a huge sacrifice in other areas to improve multi sequential read performance but so far it looks really good. I'm still working with LSI on problem #1 (controller doesn't read from both drives when it should).
  11. LSI 9270 shredding my hard drives?

    I assume you're referring to the first problem (RAID controller sometimes reads from one RAID1 drive instead of two). If so, that's a good question. I'll see if I can borrow a drive from another system to give RAID10 a try. If you're referring to the second problem (super slow/noisy performance with 2 read operations on same physical disk), I've got that reproducing even on the onboard controller (Intel C602 chipset) so LSI is out of that equation.
  12. LSI 9270 shredding my hard drives?

    UPDATE - I've made some progress in figuring this out. It looks like I've got two problems: 1) The LSI controller should be reading from both drives in the RAID 1 VD but sometimes decides to only read from one. I can reproduce this on WD Se drives and WD Red drives. 2) The WD Se drives, even when connected to the motherboard, get angry when hit with two long read operations at the same time. With regards to problem #2, consider the following test when connected to the motherboard's controller and reading large (10-15 GB) files A) WD Red, one read process: Read rate is 150 MB/s WD Red, two read processes: Read rate is 140 MB/s C) WD Se, one read process: Read rate is 180 MB/s D) WD Se, two read processes: Read rate is 10-15 MB/s and drive makes growling sound I've put in a call to WD to see if there's a firmware update for this drive. I got to Level 2 support but apparently there's only one Level 3 guy and he was out today so I'll try again tomorrow.
  13. LSI 9270 shredding my hard drives?

    Quick update: I've tried all of the following and have been unable to stop this problem from happening: 1) Installing the 9270-8i in a PCIe 2.0 slot 2) Trying four different 9270-8i controllers (2 originals, 2 recently received from LSI Support) 3) Installing on a different motherboard (same model but with different proc and no other cards installed) 4) Trying with a base install of Win 8.1 5) Trying with a base install of Win 7 6) Disabling PCI-X slots in the motherboard BIOS 7) Trying a different app to trigger two simultaneous reads from the RAID 1 8) Trying different read ahead / write back settings 9) Trying different versions of the LSI driver 10) Trying another set of WD4000F9YZ drives 11) Trying a smaller set of test data I'm running out of things to try although I'm currently setting up two 3TB WD Red drives (WD30EFRX) to see if somehow the drive model is part of the equation. I'll also try a single drive config as suggested above but I really doubt that's going to trigger it as the problem seems to be related to the controller's ability to read from two drives in a RAID 1 simultaneously to speed up read performance. LSI Support is also trying to reproduce this. Any other ideas? Also, any thoughts on Adaptec Series 8 controllers? I'm currently using LSI exclusively but if I can't get this working ASAP, I'm tempted to give Adaptec a try. I'd be curious for any thoughts on the quality of their hardware, software and support as compared to LSI. (But please, no religious wars. )
  14. LSI 9260, 9266 and 9271 for home server

    In theory, you are correct in that it's backward compatible. However, I've seen some odd compatibility issues. For example, my 9260's run much better in my older, slower PCIe 2.0 systems than my much faster PCIe 3.0 systems, even if I tell the BIOS to run in 2.0 mode. I've also received guidance from LSI about the x8 cards having issues in some x16 slots. Bottom line - wherever possible, buy your components from vendors that have decent return policies in case some of your desired components won't play nice with others.
  15. LSI 9260, 9266 and 9271 for home server

    I thought it would be backward compatible but the other day I tried a 9270 in my trustworthy X48 test system and couldn't get the system to POST until I removed the 9270. I quickly skimmed the LSI docs and didn't see any mention of PCIe 2.0 support but its possible I missed something and/or the issue is limited to my system.