Hello there,

 

So I've been running plex / unraid for about a year now. Loving it so far. Very few issues, all of which resolved with some google searching. Until this week.

 

As of late, I've been running into an issue whereby all of a sudden certain unraid shares are empty. I was in the middle of watching a tv series, enjoying some pancakes, when all of a sudden, the episode is buffering - buffering rarely ever happens for me, and when it does, its network related.

So i go through standard diagnostics to see what's causing it, when i find my TV Shows share completely empty when browsing to it via my windows PC, and Windows server. 

This has happened a few times now, each time being fixed with either a full reboot of the unRaid system, or by waiting 10 - 15 minutes. 

I'm new to diagnosing issues with the unRaid system itself. I am not really sure where i should be looking.

 

I am aware that one of disks is missing, being emulated by the parity disk. I have a new drive ordered, eta 2-3 days. Is it related, or coincidence?

I have attached the diagnostics.zip file

 

Any assistance or suggestions are greatly appreciated.

tower-diagnostics-20190510-1650.zip

Are you sure disk3 is dead? Problems communicating with a disk such as connection or cable is a much more common cause of having a disabled disk than is an actual disk failure.

 

You are also having issues with disk7, which could be a reason emulation of disk3 isn't giving good results.

Thanks!

Ill try swapping out some of the SATA cables in use and see what happens.

So do you think it might be possible to get disk3 connected again? Post new diagnostics after checking all disk connections, including power.

 

Note that even if disk3 is OK, it will still be disabled until rebuilt. But we can discuss that after seeing if it still works.

Thanks for your suggestion, I have purchased a secondary RAID card with some SAS > Sata cables. Plugged it in, and away we go. Currently rebuilding ARRAY now.

 

Will touch base again once its all up and running 

Server has rebuilt array. Is back online and all disks are present.

 

There are a few Errors on a few different disks which is concerning.

 

Diagnostics are attached

tower-diagnostics-20190521-0054.zip

Okay, i think i may have solved this on my own (best feeling ever btw).

 

I did some googling, and after being told the same thing over and over - "Disk errors are nearly always related to cabling" - i shutdown my unRaid box. I pulled it out, and unplugged every drive. I re-cabled every SAS > SATA cable from scratch, as well as recabling the SATA Power cables. This is when i noticed that i had used a molex to  5x sata power adapter, at the end of a molex to 2x molex adaptor, at the end of a molex to 2x molex. 

This is pretty stupid, i know.

I simply took one of the molex to 2x molex out of the equation and continued my recabling.

unRaid booted up and voila! 0 errors. all files available in the shares.

 

I guess with the number of drives i have the molex adapters could provide enough power?

 

I will be upgrading the power supply in my unRaid machine soon, and ill be sure to get one that's capable of 15-20 drives, without the need to use so many damn adapters.

 

Cheers for your help Trurl

 

Server is having errors on multiple disks:

 

May 21 00:52:49 Tower kernel: md: disk7 read error, sector=2055473464
May 21 00:52:49 Tower kernel: md: disk7 read error, sector=2055473472
May 21 00:52:49 Tower kernel: md: disk7 read error, sector=2055473480
May 21 00:52:49 Tower kernel: md: disk7 read error, sector=2055473488
...
May 21 00:52:53 Tower kernel: md: disk3 read error, sector=2055473464
May 21 00:52:53 Tower kernel: md: disk12 read error, sector=2055473464
May 21 00:52:53 Tower kernel: md: disk3 read error, sector=2055473472
May 21 00:52:53 Tower kernel: md: disk12 read error, sector=2055473472
May 21 00:52:53 Tower kernel: md: disk3 read error, sector=2055473480
May 21 00:52:53 Tower kernel: md: disk12 read error, sector=2055473480
May 21 00:52:53 Tower kernel: md: disk3 read error, sector=2055473488
May 21 00:52:53 Tower kernel: md: disk12 read error, sector=2055473488

...

May 21 00:52:57 Tower kernel: md: disk7 read error, sector=5868769672
May 21 00:52:57 Tower kernel: md: disk9 read error, sector=5868769672
May 21 00:52:57 Tower kernel: md: disk12 read error, sector=5868769672

 

See if these disks have anything in common, like a power splitter, controller, etc.

1 minute ago, Gobble45 said:

I simply took one of the molex to 2x molex out of the equation and continued my recabling.

unRaid booted up and voila! 0 errors. all files available in the shares.

👍