Raid 10 + wd red (cmr not smr)
-
There are many possible reasons, often involving firmware. But there's one reason more likely than any other... 4TB is not 4Tb and any replacement drive must be absolutely identical in size, or larger. Not "almost" the same size but a byte or two short. There's every possibility that the 4TB Red is just the tiniest bit smaller than whatever you had in there previously and the Gold is as big or bigger.
-
interesting old drive model # WD40EFRX new/replacement drive# WD40EFRX
hmmm. and the other drives in the array are all WD40EFRX
-
@pattonb said in Raid 10 + wd red (cmr not smr):
WD40EFRX
Oh, it was a match? Have you tested the drive on its own somewhere, then? Maybe the drive is just bad or needs a firmware update?
-
@scottalanmiller I did attach the drive to a windows machine, and was recognized immediately.
The raid card 9750 is up to date as well, with the latest firmware -
@pattonb said in Raid 10 + wd red (cmr not smr):
@scottalanmiller I did attach the drive to a windows machine, and was recognized immediately.
The raid card 9750 is up to date as well, with the latest firmwareI meant the firmware on the drive itself.
-
@scottalanmiller I thought so, i thought I would add that bit about the controller. I couldn't find
any firmware available at all on the wd site. the new drive shows a date of 01 Nov. 2020
I have another lsi 9750 4i , so I may put that in another pc and see if I get the same result. -
Hmm, unrelated to the problem but this is one of the reasons I very much prefer software raid over hardware.
For testing I suggest plugging in the drive into sata directly. No raid controller.
If the drive isn't recognized it's broken, DOA. -
@Pete-S said in Raid 10 + wd red (cmr not smr):
Hmm, unrelated to the problem but this is one of the reasons I very much prefer software raid over hardware.
For testing I suggest plugging in the drive into sata directly. No raid controller.
If the drive isn't recognized it's broken, DOA.I believe that drive is actually broken.
Even if you had a different sized drive it should still be visible because it could be used to configure a second array. -
@Pete-S as mentioned earlier in this thread, attached to a windows pc, and performs as one would expect.
even ran some of Western Digital's tools (data life guard) on the drive, no issues. -
@pattonb have you zero'd the drive so it's like new? I've seen raid controllers act funny if any partitions etc exist on "new drives".
-
@DustinB3403 I have my doubts about that with this controller. I have used a variety of LSI/3ware controllers
over the years, and have never experienced that, in fact have attached previously used formatted hard drives sans issue. nonetheless, the hard drive was new (straight out of the bag). I will test with
another lsi raid controller and see, thanks -
Here's another thought - is the LSI firmware updated? any possibility old firmware doesn't talk to the new drive? I mean really this shouldn't be an issue, but I've seen issues like this in the past between equipment, but not RAID controllers.
-
@Dashrender clearly stated earlier in the thread, 'raid controller firmware is current'
this is from the both drives, (alleged failed drive & new drive) after attaching to external usb device on the same server, using "parted"
Model: WDC WD40 EFRX-68N32N0 (scsi) Disk /dev/sdd: 4001GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 17.4kB 16.8MB 16.8MB Microsoft reserved partition msftres 2 16.8MB 4001GB 4001GB ntfs Basic data partition msftdata Error: /dev/sdd: unrecognised disk label Model: WDC WD40 EFRX-68N32N0 (scsi) Disk /dev/sdd: 4001GB Sector size (logical/physical): 512B/512B Partition Table: unknown -
the next thought is a faulty miniSAS SFF-8087 to 4x SATA cable but why would the WD gold drive work ?
