April 22, 20242 yr Hi all, I'm really having an issue here. I have a Seagate Ironwolf disk that is giving me consistent greif. Last month it disabled during a parity check, and I rebuilt it. Then, parity check has rolled around this month, and I get the same thing. I've checked into the SMART, and can't seem to figure out what the issue is. The server is just a PC build from parts laying around. I've got 7 disks in my system (including parity drive). I am using an HBA card, but I don't believe this disk is plugged into the HBA. I've attached the log from the time parity check started, as well as the SMART report, which does report as healthy. Any help would be SUPER appreciated, as I'm very lost on what else to do :| EDIT: Just noticing the power cycle count is 878 (other drives are in the range of 30-200), I think this is absurdly high? (assuming this is power on count?), and I have another disk with supposedly a count of 3268 (this disk hasn't been giving me grief though), I don't have any spindown set. So is this most likely then a PSU issue? ST8000VN004-2M2101_WSD5AVYD-20240422-1019.txt syslog.txt Edited April 22, 20242 yr by Rubble
April 29, 20242 yr Author On 4/22/2024 at 5:48 PM, JorgeB said: Could be this issue: I'll give this a shot! I've also replaced the power supply as a drive was going to 1.5GBPS (and there were lots of power cycles) and that might help, we shall see!
July 15, 20241 yr Author Solution Just coming in here after 3 months and a few parity checks to say that all is now well. I did both the HDD settings changes that were mentioned and changing the PSU. I do think the PSU was the culprit due to the power cycles on the HDDs and also that the parity check (and starting of the array) is much quicker now. Hopefully this can help anyone who is having this issue.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.