'Command Timeout' HDD Status Showing 'Failed', Is This Important? reddit / selfhosted ---------------------------------------------------------------------- RB5Network · 2023-11-05 01:35 Hey, everyone. I'm not too educated on the science behind hard drive testing. That said, I spun up a Scrutiny container to check my hard drive health and my 12TB Seagate drive posted a 'Command Timeout' test failed. That said, I'm confused because my HGST 10TB hard drives don't even use this test whatsoever. And I oddly cannot find any information on this, online. Any help would be great! ---------------------------------------------------------------------- autogyrophilia · 2023-11-05 01:58 There are multiple possible causes for this (as a quick Google would have shown you). Easiest one it's faulty power or data cables. Check checksum smart data by showing all attributes. The other possible one it's that you are using a surveillance HDD , and overloading it with commands. Those don't handle well high queue depth. And the most likely it's that the disk it's in the process of failing. Expect more issues quickly. ---------------------------------------------------------------------- RB5Network · 2023-11-05 02:08 Damn, man. Blasting me over using Scrutiny lol. It's a docker container called Scrutiny that is used by a ton of people. The specific drive is a parity drive in an Unraid server. Not sure if Unraid has the ability to use smartctl due to not having a traditional package manager. (Sadly.) ---------------------------------------------------------------------- autogyrophilia · 2023-11-05 02:16 I'm joking man. It's a tool. But, in my job, I always emphasize that people need to know the basics before using shortcuts because when things go wrong, you don't know if it's the shortcut or the tool failing. As well as knowing how things actually work under the hood being very helpful. In this case it is a special attribute that seems it isn't reading properly. It really should not show a failure for something like that, a warning at most Smartctl it's a basic tool, I expect that if unRAID has any shell interface you have access to it. ---------------------------------------------------------------------- Salt_MasterX · 2023-11-05 04:23 who let bro cook ---------------------------------------------------------------------- autogyrophilia · 2023-11-05 05:04 Haven't slept since Friday. Still better at finding information in Google apparently. ---------------------------------------------------------------------- RB5Network · 2023-11-05 07:02 That’s a you problem, man. No need to be a dick to random people on the internet with unlimited anonymity. There’s enough of that already. I do appreciate the link you shared and that gives a ton of clarification. ---------------------------------------------------------------------- autogyrophilia · 2023-11-05 07:30 Man, it is very hard to convey tone in the internet. Things that are written in a friendly but scolding tone can be easily reas as being a grumpy asshole. I still get annoyed by the fact that some basic googling easily led me to an indepth explanation. But I gave helpful as advice that has never failed me on how to handle situations like these ---------------------------------------------------------------------- fruppster · 2023-11-05 11:20 Dude scrutiny literally runs smartctl and displays the results in a more readable way. That's all it does. Please get some sleep. ---------------------------------------------------------------------- Hairless_Human · 2023-11-05 14:38 You ok dude? Scrutiny just turns the smartcl results into a pretty and more human readable interface. ---------------------------------------------------------------------- creamyatealamma · 2023-11-05 17:47 I'm not 100% sure what it means either. I have three 16tb exos failing for the same reason. Noticed it a while back, say 6mo in. Power on times around 2 years. I take more as a warning. They have not been a problem, but when there is array disk errors I check to see if it's one of them. If it happens enough I will replace them as it happens. Regardless, even if all your drives are showing as passed: backups backups backups! ---------------------------------------------------------------------- bendem · 2023-11-05 18:00 > you should feel bad. Not sure how any tone can make this positive ---------------------------------------------------------------------- autogyrophilia · 2023-11-05 18:22 https://youtu.be/4mcD5jd-RAU?si=PLpWs1AvLZD_zXq3 ---------------------------------------------------------------------- lilolalu · 2023-11-05 18:55 1. its not good 2. its not necessarily your drive 3. can be the controller 4. or a cable ---------------------------------------------------------------------- RB5Network · 2023-11-05 19:49 If you check the link another person commented, it said this is a common thing that will pop up for Seagate drives that are not of real concern, luckily. Definitely getting a second parity drive after this though. ---------------------------------------------------------------------- Fungled · 2023-11-05 23:29 Is this a Seagate drive? I think it is. There was a bug with the custom reporting for this property and there’s a fix in the testing image. Search the issues on the GitHub page and you’ll see ---------------------------------------------------------------------- RB5Network · 2023-11-05 23:38 Ah, got it. Yes it is! ---------------------------------------------------------------------- mil1ion · 2023-11-06 00:17 I just ran Scrutiny for the first time the other day and the same thing happened to me. I have 4 matching brand-new (about 8 months old) 14tb Seagate Ironwolf drives. It was my parity drive that showed this 'error', same as you. None of my other Unraid-initiated smart tests have shown any cause for concern, so I chalked it up to a bug and removed Scrutiny :shrug: ---------------------------------------------------------------------- RecursiveIterator · 2023-11-06 08:17 Same thing happened to 3 of my disks when my RAID controller overheated... 15 months ago. All 3 disks are still working perfectly fine today. I wouldn't worry about it. One of the most requested features in Scrutiny is to ignore certain "failures" like this one... ---------------------------------------------------------------------- kooori213 · 2023-12-03 05:13 I'm going through the same issue, I have the Ironwolf Pro 16tb ST16000NE000. I sent one back to seagate for replacement (kudos received the new drive in 1 week from sending it in.) The replacement drive they sent me had bad sectors so I sent it back to them. Kudos again received a new drive in 1 week. Now the error popped up after 10 days. ---------------------------------------------------------------------- RB5Network · 2023-12-03 05:24 Yup. Likely a false positive and nothing to worry about. Mine is still going strong. SeaGate documents this with it's SMART metrics.