July 12, 20169 yr Hey everyone. I've had a couple instances of my X8SIL-F screeching at me because a drive goes missing. Actually I'm not sure if it's my MB or the Supermicro AOC SATA card I added. Buzzer is annoying as all heck, but it does it's purpose to alert me to a problem. Only thing is I'm not entirely sure what the problem is. In my Unraid log file I get: Jul 12 18:17:04 Tower kernel: mdcmd (4): import 3 8,64 1953514552 SAMSUNG_HD203WI_S1UYJ1CZXXXXXX Jul 12 18:17:04 Tower kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD203WI_S1UYJ1CZXXXXXX size: 1953514552 For all my drives, except one: Jul 12 18:17:04 Tower kernel: mdcmd (9): import 8 0,0 Jul 12 18:17:04 Tower kernel: md: disk8 missing While the array was started, when the above log started (at the first line I pasted in above)... I think all drives were spun down. Any pointers on how to go about diagnosing what happened? One of the red lights on my SUPERMICRO CSE-M35T-1B drive cage was on - bright red. (Although I didn't pay attention to which it was) My thoughts are that it was the SM 5-in-3 that was buzzing at me after a drive stopped responding... Now this happened a week ago - after a power failure... Rest of the system is fine, including all drives connected to that 5-in-3. For hours while I was out, apparently that rather annoying buzzer was on (I'll disable it I think)... So anyway, after rebooting, the drive came up fine. Then today - days later, all drives I believe spun down - little heat being generated and I have fans in the case... Out of nowhere the problem recurs. Any advice?
July 12, 20169 yr Author I will add.. That the temperamental drive (Seagate 8TB) has a 188 Command Timeout raw value of 4295032833 according to the smart data. The parity drive (only other 8TB) is at 0.
July 13, 20169 yr Have you check the cabling and adapters? If it's just a SATA cable have you tried another one?
July 13, 20169 yr Author Thanks guys! I had thought Unraid had an identify drive feature? I can't seem to find it so perhaps I was mistaken?
Archived
This topic is now archived and is closed to further replies.