Gouie

I have a drive that’s been disabled and sitting with a red X. My understanding is Unraid has disabled the drive due to a write failure. I’d like to rebuild the drive to see if it’s still salvageable - wise thing to do? All of the material I’ve found about rebuilding talks about replacing the drive, nothing about rebuilding an existing drive. My thought is unassigned, restart the array, stop the array, then re-assign but would like to validate before doing so. Thanks!

RESOLVED So, I called my ISP Friday to inquire into the incentives available for new customers and why existing customers are left in the dark. Long story short they matched the deal. Well, in doing so they changed the external subnet. Coincidently the new subnet matched the subnet I was using on the internal network. Google WiFi was smart enough to see the conflict and changed the internal network subnet. All DHCP enabled devices were working fine while the hard coded devices, i.e. my server, were not. Man, that took some head scratching, thanks for jumping in to assist though @Frank1940, very much appreciated! I am still curious about the errors I was seeing on reboot though. Interestingly enough I did not see any errors during the complete shutdown that you recommended. I’ll try a restart again to see if the errors still exist.

Diagnostics .ZIP attached. Thanks in advance! tower-diagnostics-20190903-1722

Hey everyone, I had a strange problem pop up last week that I haven’t been able to resolve. Through Plex, I started the conversion of a video then left for a few hours. I checked it when I got back and there was an error. From that point Friday I have been unable to access the server through the web interface. In fact, I can’t even reach the address via ping or the like. I can can log into the server directly but to be honest, I know very little of Linux. I’ve done all of the obvious things like changing ports as cables on the switch. One interesting thing I noticed was when I reset the server hoping that would fix the problem, there were four or five lines with an error referring to config/docker.img. Unfortunately it buzzed by fairly quick. I can take a few pictures of the screen when I’m home tonight if that will help. Looking for some guidance as I’m not sure where to start.

Likely a motherboard upgrade as well. Will check out my options but the more I read the more unlikely 4K transcoding will be. Seems there’s a lot of challenge and debate about what will work.

Way more complicated than I originally thought. I use Plex and was hoping there was an easy way of simply relying on the on-the-fly transcoding. Admittedly I don’t know a lot about the hardware details. Is there a specific processor that you’d recommend?

I’m looking for some processor recommendations. I have apple devices throughout the house that haven’t been a problem until recently has UHD media makes its way into my library. Because Apple doesn’t support MKV the server is having to convert on the fly and choking. Any recommendations? I don’t want to break the bank so only looking for something that can handle a single file of this size at a time. Thanks!

Wanted to provide a quick update to close the issue. The system has been stable since re-seating the SATA card - looking like that was the issue. Regarding the heat, I tore into the case one more time and believe I've found that problem as well. The case came with 5 fans installed from the manufacture, 3 under the drive bay and 2 at the rear. Lots of air flow, the only problem was they installed all 5 to be drawing into the case, no venting. I changed the 2 at the rear to exhaust and so far so good.

Argh! I’ll put the case back on. This case is a little different than most, designed as a home theatre case. It looks like an AV receiver. Lots of fans under, along the side and the back. Generally speaking the drives stay within range even when running a big copy - usually under 40C. The cache drive is the real problem, North of 45C at times. Think I’ll replace it with a flash. If I were a gambling man I’d bet in the add-on card as the culprit. I’ll be sure to report back with my findings.

Gotcha, I just figured the odds of tossing more than one drive before a guy had a chance to get a replacement were pretty low. Couple of questions now: Backup; what are folks using? 20+ TB makes backup a little complicated. Failed drive; shouldn’t the console give indication of a failed drive when it happens? I’ve had to take the array offline for it to highlight a failed drive. Update; I downed the server again and gave it a real thorough clean. I’ve also left the case off for now. I have 8 drives, 6 attached to onboard ports with the other 2 attached to a SATA expansion card. Got me thinking perhaps the card is wonky. I lifted and reset it as well as changing the drives connected to it. If 2 drives fail again and they aren’t the same ones it will indicate a bad card. Thanks a a million for the help everyone!

Sorry everyone, appreciate the prompt response then life got really hectic. I've blown the case out and confirmed that all fans are spinning fine. I think I need to take a good look at air flow, push vs. pull to see that the drives are getting proper cooling. I ran into the problem again today. Took the array offline because things were behaving strangely; I couldn't run an LS on the user folder from the console, came back with an error. Once I took the array offline it showed that two drives were bad. I've reset the server a couple of times now and it still shows the 2 drives are bad. Not good. A UPS is in my future and to answer your question no, I don't have a backup of the data - I figured that a redundant RAID system would be enough.

Here you go. A couple of updates. i thought a restart of the server might help. After bringing down the array it was showing that two drives had failed - red circle. Not sure what the odds of that are, fairly unlikely. i reset anyway and everything came back on line. I also noticed that my older cache drive is running extremely hot, sometimes reaching 50 degrees. I wonder if the heat inside the case is too much and the system is acting up? I'm also noticing our power is a lot less reliable these days. I don't have the server on a UPS so also wondering if the abrupt power down could be causing problems as well. Look forward to your diagnosis tower-diagnostics-20180717-0526.zip

Trying not to panic but am very concerned. I went to watch some content tonight and Plex is showing nothing is available. I hopped on the Unraid console and browsed my share and all of the folders are showing empty. I must of 5 or 6 TB of content that is missing. The last scheduled parity check ran last night with millions of errors. When I look at the parity logs it doesn't show last night's scan. Looking for guidance,, thanks in advance.

I've been able to try from a Mac and everything is working, access as well as delete. What's odd is I'm connecting from the Mac as Guest.

I'm struggling with an issue I hope others have seen or can help with. Running version 6.1.9 and hit an issue out of the blue where Windows PCs aren't able to content on my shares. All shares are public, users can't even read let alone write. When trying to access from a PC authentication doesn't work; login box repeatably says the user name or password is incorrect. I'm now trying to create a new test account to mess around with but it won't let me. It goes through the motions, I hit create and no account shows up. I can't delete an account either. Has me thinking perhaps there's something underlying wrong that's preventing authentication. Appreciate the help.

Figured I'd close the loop on this one but if anyone is ready, would be interested in knowing why it behaved in this way. After a few reboots and nothing I stumbled on the "power down" command. This seems to have resolved the problem and the sever is back up and running.

So, further update, I can telnet into the server from a remote workstation no problem. Could be a problem with the web service? No idea where to go from here.

So, the server has been up for about 20 minutes. I left my browser spinning trying to connect and finally received an authentication. I've entered credentials and it's back thinking again. Is there just a ton of stuff going on after the uncontrolled shut down?

Looking for some direction, not sure where to go from here. I had a power failure this morning and an uncontrolled shutdown of the server. I've since powered back up and things appear to be running but I can't connect to the server over the network. I can login at the console but can't connect from a workstation and browser. I can ping the server fine and can ping the internet from the server, just can't connect. Not sure where or how to trouble shoot from here? Help.

To close the loop on this one. I started to zero in on the network adapter as the server seemed stable even after what I thought was a crash, it just wasn't accessible over the network. I went through a number of potential issues including bios version and network adapter drivers; that led me to the PCI adapter. I had issues with the onboard adapter a couple of years ago. I installed a PCI adapter and all has been running fine on v5.x ever since. It appears that v.6.x is much more sensitive to the number of adapters installed. After removing the PCI adapter and plugging back into the onboard NIC all was stable for a couple of hours of Plex this evening. I'll try disabling the onboard and reinstalling the PCI adapter tomorrow.

Yeah, that's what I could make out as well. I did find that same thread just not sure what my next steps should be. I suppose I could start with a motherboard bios update.

Thanks, noted for next time. A quick update, I am wondering if it is related to the shares in some way. Booting around the server, looking at configurations and fine tuning the installed applications seems to be pretty stable. It's almost as soon as I access the file system in some way that the problem occurs. For example, I've been changing the location of my TV episodes in SickBeard. That took about 45 minutes and everything seemed fine. I had a downloaded episode that was not post processed (I think there's some configuration missing relative to the script?) so I manually processed from within Sickbeard. As soon as I selected the folder to browse the problem appeared; the server is now inaccessible.

Well, I thought things had stabilized as I was able to run through the server and applications, configuring things quite smoothly for about an hour then the network connection dropped again. Attached are a syslog.zip and diagnostics.zip; hoping someone can help shed some light. For what it's worth, I ran through the diagnostics gathering via 'powerdown' at the console then reset the server. I attached over the network to grab the files from the flash drive and it almost immediately crashed again. I powered off and pulled the USB stick to grab the files. syslog.zip tower-diagnostics-20160904-1312.zip

Appreciate that and have taken the first paragraph to heart. I'm breathing and will post up diagnostics before a restart after the next crash.

Honest, I'm trying to find the resolution to each of my issue before posting but some of them are real head scratchers. I have an interesting problem going on where randomly the server will become unreachable. I can log onto the console without an issue but I can't even ping the box. It does seem to happen when I'm configuring my Plex container. I did have issues installing Plex but after a container removal and deletion of the associated application files, I was able to successfully install. This is an interesting problem. Perhaps there is an internal crash occurring effecting the network interface but I'm not sure how I would go about determining that and is it possible that such a network failure could be related to a docker container?