similar to: hard drive question - WD red

How can I diagnose why a resilver appears to be hanging at a certain percentage, seemingly doing nothing for quite a while, even though the HDD LED is lit up permanently (no apparent head seeking)? The drives in the pool are WD Raid Editions, thus have TLER and should time out on errors in just seconds. ZFS nor the syslog however were reporting any IO errors, so it weren''t the disks.

John R Pierce wrote: > On 10/7/2015 3:14 PM, Matt wrote: >> I have 3 4TB WD drives I want to put in a RAID1 array. >> >> Two WD4000FYYZ >> >> and >> >> One WD4000F9YZ >> >> All enterprise class but two are WD Re and one is WD Se. I ordered >> the first two thinking 2 drives in the raid array would be sufficient >> but later

I have a question that has been puzzling me for some time ... what is the reason RedHat chose to go with btrfs rather than working with the ZFS-on-Linux folks (now OpenZFS)? Is it a licensing issue, political, etc? Although btrfs is making progress, ZFS is far more mature, has a few more stable features (especially Raid-z3) and has worked flawlessly for me on CentOS-6 and Scientific Linux-6.

I have 3 4TB WD drives I want to put in a RAID1 array. Two WD4000FYYZ and One WD4000F9YZ All enterprise class but two are WD Re and one is WD Se. I ordered the first two thinking 2 drives in the raid array would be sufficient but later decided its a long drive to the server so I would rather have 3 drives and ordered a third in accidentally did not get EXACT same thing. Would there be ANY

On 8/5/2015 1:00 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> How would I go about pointing it at the partition? >> >> What I am currently doing is this: >> device (hd0) /dev/hdg >> root (hd0,0) >> setup (hd0) > > setup (hd1,0) > > It's hd1 if your device map is correct and

Might be slightly OT as it isn't necessarily a CentOS related issue. I've been using WD Reds as mdraid components which worked pretty well for non-IOPS intensive workloads. However, the latest C7 server I built, ran into problems with them on on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error write fpdma queued". Googling on it threw up old suggestions to

While researching another issue unrelated to Syslinux, I found some mildly disturbing news that affects Syslinux. As HPA stated back on 2009-06-04, hard drive manufacturers are pushing towards a 4096B (4kiB; 4k) native sector size. They're calling it "Advanced Format Technology". It appears that WD (Western Digital; WDC) is the first with some products being released back in

Hi people, I am building a cheap remote rsync backup server using a software raid 5 array of 4 500GB disks. What I have available on the market is: 1. HITACHI GST Deskstar T7K500 500GB 7200rpm 16MB cache Serial ATA II-300 2. SEAGATE Barracuda 7200.10 with NCQ 500GB 7200rpm 16MB cache Serial ATA II-300 3. Western Digital 500GB SATAII RAID EDITION Caviar SE16 7200rpm 8.9ms 16MB cache I am

According to various posts the LSI SAS3081E-R seems to work well with OpenSolaris. But I''ve got pretty chilled-out from my recent problems with Areca-1680''s. Could anyone please confirm that the LSI SAS3081E-R works well ? Is hotplug supported ? Anything else I should know before buying one of these cards ? Thanks, Arnaud

On 03/01/2016 09:53 AM, Emmanuel Noobadmin wrote: > > Since I'm likely to use Reds again, it is a bit of a concern. So > wondering if I just happen to get an unlucky batch, or is there some > incompatibility between the Reds and the Intel C236 chipset, or > between Red / C236 / Centos 7 combo or the unlikely chance WD has > decided to do something with the firmware to make

Emmanuel Noobadmin wrote: > Might be slightly OT as it isn't necessarily a CentOS related issue. > > I've been using WD Reds as mdraid components which worked pretty well > for non-IOPS intensive workloads. > > However, the latest C7 server I built, ran into problems with them on > on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error > write

Hello, Having a problem with software RAID that is driving me crazy. Here's the details: 1. CentOS 6.2 x86_64 install from the minimal iso (via pxeboot). 2. Reasonably good PC hardware (i.e. not budget, but not server grade either) with a pair of 1TB Western Digital SATA3 Drives. 3. Drives are plugged into the SATA3 ports on the mainboard (both drives and cables say they can do 6Gb/s). 4.

> However, the latest C7 server I built, ran into problems with them on > on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error > write fpdma queued". Googling on it threw up old suggestions to limit > SATA link speed to 1.5Gbps using libata.force boot options and/or > noncq. Lowering the link speed helped to reduce the frequency of the > errors (from

On 3/1/2016 9:53 AM, Emmanuel Noobadmin wrote: > However, the latest C7 server I built, ran into problems with them on > on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error > write fpdma queued". Googling on it threw up old suggestions to limit > SATA link speed to 1.5Gbps using libata.force boot options and/or > noncq. Lowering the link speed helped to

Hi All, I have a WD RE4-GP which dropped an Adaptec 51645 RAID controller. I ran a smartctl short test on the drive and it failed with a read error. So I ran the Western Digital's own diagnostic software (DLGDIAG), both the short and extended test on the drive and it passed with no errors. So I ran the smartctl short test again and again it failed. I then ran smartctl long test and that

I have a desktop system with 2 ZFS mirrors. One drive in one mirror is starting to produce read errors and slowing things down dramatically. I detached it and the system is running fine. I can''t tell which drive it is though! The error message and format command let me know which pair the bad drive is in, but I don''t know how to get any more info than that like the serial number

Hi, Whenever I issue this commands (as in the help for the threshold function), # # Do a 1D decomposition # tdecomp <- wd(test.data) # # Threshold it # tdecomp.thresh <- threshold(tdecomp) # # Reconstruct from the thresholded coefficients # trecons <- wr(tdecomp.thresh) # #

On Thu, Oct 27, 2016 at 12:03 AM, Larry Martell <larry.martell at gmail.com> wrote: > This site is locked down like no other I have ever seen. You cannot > bring anything into the site - no computers, no media, no phone. You > ... > This is my client's client, and even if I could circumvent their > policy I would not do that. They have a zero tolerance policy and if >

hw wrote: > Richard Zimmerman wrote: >> DO NOT buy the newer HPE DL20 gen9 or ML10 gen9 servers then (especially >> if using CentOS 6.x) > > What would you suggest as alternative, something from Dell? Yep, Dell's are good. And I do *not* want to buy from HP, because their support is nothing like good. And once you run out the warranty, they don't want to even let you

Matt Garman wrote: > On Thu, Oct 27, 2016 at 12:03 AM, Larry Martell <larry.martell at gmail.com> > wrote: <snip> > On Thu, Oct 27, 2016 at 3:05 AM, Larry Martell <larry.martell at gmail.com> > wrote: >> Well I spoke too soon. The importer (the one that was initially >> hanging that I came here to fix) hung up after running 20 hours. There >> were no