A couple weeks ago I attached a new 4 bay DAS to my Hades Canyon (Windows 11) and I populated it with three older 4TB red label drives. After a week one of the drives started failing. I put a WD80EMZZ from a easystore in the same bay as the drive that failed and started loading files on it (I pooled the three drives in the DAS together as one virual drive using Drivepool). This morning the computer shows the new drive as missing (the other two drives in the DAS are still present).
I read about the 3.3v pin issue with white label WD drives but this doesn't seem to qualify - those issues seem to be with the computer not seeing the disk on bootup. The Hades Canyon sees everything on bootup. I began to worry that maybe the DAS is faulty since I put the new drive in the same bay as the old one, but that seems unlikely.
I also read a thread on here from 2019 about a similar issue (https://forums.tomshardware.com/thr...b-white-drive-after-sleep-or-startup.3466040/) but I don't know if it ever got resolved.
Anyone have suggestions?
Harry
I read about the 3.3v pin issue with white label WD drives but this doesn't seem to qualify - those issues seem to be with the computer not seeing the disk on bootup. The Hades Canyon sees everything on bootup. I began to worry that maybe the DAS is faulty since I put the new drive in the same bay as the old one, but that seems unlikely.
I also read a thread on here from 2019 about a similar issue (https://forums.tomshardware.com/thr...b-white-drive-after-sleep-or-startup.3466040/) but I don't know if it ever got resolved.
Anyone have suggestions?
Harry
Facebook
Twitter
Instagram