Aquinus
Resident Wat-man
- Joined
- Jan 28, 2012
- Messages
- 13,147 (2.94/day)
- Location
- Concord, NH, USA
System Name | Apollo |
---|---|
Processor | Intel Core i9 9880H |
Motherboard | Some proprietary Apple thing. |
Memory | 64GB DDR4-2667 |
Video Card(s) | AMD Radeon Pro 5600M, 8GB HBM2 |
Storage | 1TB Apple NVMe, 4TB External |
Display(s) | Laptop @ 3072x1920 + 2x LG 5k Ultrafine TB3 displays |
Case | MacBook Pro (16", 2019) |
Audio Device(s) | AirPods Pro, Sennheiser HD 380s w/ FIIO Alpen 2, or Logitech 2.1 Speakers |
Power Supply | 96w Power Adapter |
Mouse | Logitech MX Master 3 |
Keyboard | Logitech G915, GL Clicky |
Software | MacOS 12.1 |
Hi everyone,
Lately I started having issues with my RAID, it has started ever since I moved my RAID to my LGA2011 rig. It is kicking drives out, at first it kicked my WD green out of the RAID, so I removed it, bought a WD black to replace it and popped in and boom, quick and simple rebuild. A couple days later one of my Hitachi drives gets kicked out of the RAID. So I'm skeptical, I rebuild and it works fine for the next couple days. So I took the WD green drive I took out to work and plugged it into one of our servers with an eSATA dock and I run SMART on it. 26000 hours of time active and not a single error or any smart attribute out of whack. So I bring it back home and when the hitachi "failed" again, I took it out and switched drives (I tried changing ports in-between as well, but it didn't seem to make a difference.) So I bring the Hitachi drive to work and check the SMART logs on that drive, 3 relocated sectors was the worst I could see, and 23000 hours of run time.
With all of this said now, Intel Rapid Storage enterprise will say "SATA array disk removed." then it says, "Unknown disk on Controller 0, Port Unknown Detected.", Then "SATA Disk on Controller 0, Port 3 Detected." the right back to "SATA array disk removed." (It repeats this over and over and over again until you restart.)
If I try to re-add the disk to the RAID right now, it will error out. If I restart and use either the RAID BIOS or the Utility in Windows it will re-add it fine and start rebuilding.
Has anyone else noticed this behavior? This never happened to me on the nVidia RAID, and I'm wondering if anyone else has something to add. I might also add that I have two Corsair Force GT 120Gbs in RAID-0 on the SATA6 ports and I haven't had a single issue with that, so I'm not inclined to believe that it is the driver (it could, I mean there is data parity being calculated data gets checksumed.) I also replaced all of the SATA cables as well.
Right now the drives in RAID are (in this order from port 3 to port 5) are:
Hitachi 1
WD Black
WD Green
with Hitachi 2 on my desk in a static proof bag. WD Green and Hitachi 2 both exhibit the same behavior, but the other two drives appear fine, even though Hitachi one is from the same batch as 2 and should have the same exact active time. The drives are getting old but that isn't reason enough for me to get rid of them and buy another new 1Tb drive.
Lately I started having issues with my RAID, it has started ever since I moved my RAID to my LGA2011 rig. It is kicking drives out, at first it kicked my WD green out of the RAID, so I removed it, bought a WD black to replace it and popped in and boom, quick and simple rebuild. A couple days later one of my Hitachi drives gets kicked out of the RAID. So I'm skeptical, I rebuild and it works fine for the next couple days. So I took the WD green drive I took out to work and plugged it into one of our servers with an eSATA dock and I run SMART on it. 26000 hours of time active and not a single error or any smart attribute out of whack. So I bring it back home and when the hitachi "failed" again, I took it out and switched drives (I tried changing ports in-between as well, but it didn't seem to make a difference.) So I bring the Hitachi drive to work and check the SMART logs on that drive, 3 relocated sectors was the worst I could see, and 23000 hours of run time.
With all of this said now, Intel Rapid Storage enterprise will say "SATA array disk removed." then it says, "Unknown disk on Controller 0, Port Unknown Detected.", Then "SATA Disk on Controller 0, Port 3 Detected." the right back to "SATA array disk removed." (It repeats this over and over and over again until you restart.)
If I try to re-add the disk to the RAID right now, it will error out. If I restart and use either the RAID BIOS or the Utility in Windows it will re-add it fine and start rebuilding.
Has anyone else noticed this behavior? This never happened to me on the nVidia RAID, and I'm wondering if anyone else has something to add. I might also add that I have two Corsair Force GT 120Gbs in RAID-0 on the SATA6 ports and I haven't had a single issue with that, so I'm not inclined to believe that it is the driver (it could, I mean there is data parity being calculated data gets checksumed.) I also replaced all of the SATA cables as well.
Right now the drives in RAID are (in this order from port 3 to port 5) are:
Hitachi 1
WD Black
WD Green
with Hitachi 2 on my desk in a static proof bag. WD Green and Hitachi 2 both exhibit the same behavior, but the other two drives appear fine, even though Hitachi one is from the same batch as 2 and should have the same exact active time. The drives are getting old but that isn't reason enough for me to get rid of them and buy another new 1Tb drive.