![]() GUI always showed that drive “healthy” and instead showed I/O command timeout errors on all 4 of the other drives in the DX517 (slots 2-5) ![]() One drive in the DX517 expansion array had actual errors (DX517 slot 1). ![]() But in between then and now other synology support people had me shuffling drives around and between the head unit DS920 and the expansion unit DX517… so it’s all confused and they didn’t realize that the first bay in my expansion unit has been empty for a week because of that… so I’m awaiting another response from them to give me clarity on exactly which drive they think I need to replace….įinally got this resolved with Synology.Had to go to their level 2 and ultimately Dev team. ![]() The reason it’s not resolved yet.l they went into the command line to tell me which drive was bad but it wasn’t clear… they said “first drive” in the expansion unit with sceeen shots thst showed time stamps from 2 weeks ago when I first started having the problema…. I don’t think this logic would apply if your drives aren’t in an expansion unit. on expansion bay#s because of how “port replicator” (serial ATA), they think one drive is bad in the expansion array ( I have a DX517), and the error gets replicated to the rest of the drives… so they think I just need to replace the one drive that is really having the issue and that will make the errors on the rest go away The latest thing they’re thinking is this… which sounds plausible but it’s not resolved yet… Im still working with Synology support, they’ve been dreadfully slow, took more than a week to get a real tech assigned to the ticket after level 1 triage… This again indicates it’s not the drives, it’s how the Synology is suddenly miscommunicating with the drives. I had a spare drive of same make/model, I put it in and repaired the array, and it repaired but within the day it too (a brand new 5th drive) had the I/O command timeouts the others suffered. Status: Normal Drive I/O command timeout condition: Critical Bad sector count: 0 Drive reconnection count: 0 Drive re-identification count: 0“ Please back up your data immediately and then replace the drive… Sept 17, 1:55 AM: “Drive 2 on DX517-1 is damaged and is in critical status. Sept 16, 2:55 PM: “The system detected an I/O command timeout on Drive 3 of DX517-1, but it will continue to monitor and attempt to repair the drive.” The expansion bay is fully populated with 5 drives.Ĥ out of 5 drives (slot 2-5) in the expansion bay all started having the same errors simultanoeusly, details below, All 4 of these drives are 4 TB Hitachi HUS724040ALE641.Įxample for one drive shown - identical errors received at identical times for all 4 drives. My educated guess: Synology updated something, eg “drive batabase settings” that is making the NAS not communicate with this model of drive properly now, resulting in the I/O command timeouts as the drives have been fine for 1-2 years and they haven’t even had a knowledgeable technician do any real troubleshooting! It’s not the drives when 4 of them suddenly have errors simultaneously…. Opened a ticket with Synology on this 5 days ago and so Far the only response I got was about “this drive model isn’t on our compatibility list” … total B.S.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |