Vlash

I didn't try booting into safe mode, so I can't say much about your plugins and if it's causing your issue. I don't think the network cable being disconnected would play any role in the system rebooting, but I have not tried that either. I do think I found my issue. I'm testing this weekend to see, but so far the results are good. I think that one of the cables on my multi-lane forward cable is bad. With @Squid pointing out the poor/loose cable connection, I kept thinking about it because I did unplug everything and plug it in again to make sure everything was connecting properly. So I started with disk 6 since it was the one showing in the logs as failing disk and replaced that cable with one not in use. Two of the four sata cables were in use, so I had two I could test with. Once I swapped out the cable and booted back up, I have not had any issues, even network issues. Lesson learned on this one, and it's crazy that the data cable caused my network to drop like it was. So @tripleflip you might try changing cables out to see if it helps.

Guess this one has everyone stumped lol.

Ok I figured out how to grab a diagnostic report. Thought that download was just to grab the system log, but wiki said otherwise. Anyway here it is tower-diagnostics-20191009-0616.zip

I replaced the cable yes. I have reseated all my cables to my drives. Actually unplugged everything and plugged them back in even though the sata cables have the locking clips to make sure. Plus the power cables as well. Same on the controller, unplugged cables and plugged back in. What is it that I need to do to grab a diagnostics? Thanks Edit: Forgot to say switched ports on router too. Even switched from my router to my hub with same results.

**Bump** Anyone have any suggestions?

Recently my server has been loosing connection. I have noticed it when visiting the tower/main, or any other page for that matter. I will often get an unable to connect page when navigating around the gui. To make matters worse, the server will be down when I get home. I mirrored the logs and have the last log when the system powered down. I am not good at understanding the logs so maybe someone can point me to the issues. I am seeing lots of eth0: Link Down but just cannot figure out what is causing it. Looks like it is happening on disk spindown, but like I said I am horrible at these logs. Really the only thing I have tried thus far is changing out the controller card, and changing the ethernet cable. Besides that, I really don't have a clue. Thanks in advance. May 23 17:27:07 Tower kernel: alx 0000:01:00.0 eth0: Link Down May 23 17:27:07 Tower kernel: bond0: link status definitely down for interface eth0, disabling it May 23 17:27:07 Tower kernel: device eth0 left promiscuous mode May 23 17:27:07 Tower kernel: bond0: now running without any active interface! May 23 17:27:07 Tower kernel: br0: port 1(bond0) entered disabled state May 23 17:27:09 Tower ntpd[1581]: Deleting interface #5 br0, 192.168.1.102#123, interface stats: received=86, sent=190, dropped=0, active_time=52874 secs May 23 17:27:09 Tower ntpd[1581]: 45.33.103.94 local addr 192.168.1.102 -> <null> May 23 17:27:09 Tower ntpd[1581]: Deleting interface #6 br0, fe80::4cf2:daff:fe1b:a409%10#123, interface stats: received=0, sent=0, dropped=0, active_time=52874 secs May 23 17:27:13 Tower kernel: alx 0000:01:00.0 eth0: NIC Up: 1 Gbps Full May 23 17:27:13 Tower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex May 23 17:27:13 Tower kernel: bond0: making interface eth0 the new active one May 23 17:27:13 Tower kernel: device eth0 entered promiscuous mode May 23 17:27:13 Tower kernel: bond0: first active interface up! May 23 17:27:13 Tower kernel: br0: port 1(bond0) entered blocking state May 23 17:27:13 Tower kernel: br0: port 1(bond0) entered forwarding state May 23 17:27:14 Tower ntpd[1581]: Listen normally on 7 br0 192.168.1.102:123 May 23 17:27:14 Tower ntpd[1581]: Listen normally on 8 br0 [fe80::4cf2:daff:fe1b:a409%10]:123 May 23 17:27:14 Tower ntpd[1581]: new interface(s) found: waking up resolver syslog

That done the trick. Can't believe I didn't think of that tbh. Just had a nasty storm roll through a few days ago. Lightening strike was .2 miles from house. Lost a power line network adapter and two HDMI ports on a TV.

Ok thanks. As soon as I get home this weekend I will set to work on that.

I've done a lot of searching and reading on my current state, or at least those similar to my situation, but thought it would be best to get feedback and possibly learn something from those more experienced than I. My issues started after I had a disk red balled, and I replaced it. The very next drive I installed didn't last but 2 minutes on the rebuild before it too was red balled. Then yet again with a third disk. Also two other disk were reporting spin retry errors as well. After some searching and almost everything I had found was saying the controller could be bad. I did make check all the cable connections before I done anything else and then decided to try another controller. I already had a backup in case something ever happened to the current controller. It solved these issues. And I got back up and running. That only lasted for a few days. My parity drive dropped off line, it was red balled. So I replaced the drive. That's when the rest has come into play. The parity was being rebuilt, and everything seemed normal. Then I started getting tremendous lag when I tried to access my movies share. Most of the time it would not even load a movie on Kodi on my Pi. Would load on my desktop but none of the Pi's, only it would freeze up. Sometimes it would play sometime it would not. Now my tv shared had no problem just the movie shares. Thought it might be one of the docker apps causing an issue. Well I noticed that the parity rebuild was going to take something like 400+ days to complete. I knew something wasn't right but I'm not exactly sure what it is. I made sure my docker apps were not running. All but MySQL docker as I use it for my database for my Kodi installs. I have noticed a odd sound around my drives the last few days. Like a tick the almost like I hear it writing data the the tick again, and it's almost always going. Stops for a few minutes then starts again. I can only assume something is wrong with this drive. I have added my diagnostics zip and the drive in question is drive 2 (ST6000VN0033-2EE110 ZAD4Q85T) I know the parity drive is red balled right now, but could it be because it was unable to write data that it might not have been able to retrieve from drive 2? Also many many more questions about the smart logs and those high numbers for raw read error rate that appeared recently, and if I'm even reading the right columns to check if my disk are going bad. Sorry for this very long post, but wanted to get as much information as I could think of posted. tower-diagnostics-20191009-0616.zip

Thanks for that. Fortunately, or unfortunately depends on how you look at it, it's working now. Got home from dentist and prepping to revert back to local db on Kodi. Everything was running smooth. No issues since either. While I'm kinda glad it's working, I'm a little uneasy not knowing what the cause is, or was, and if/when it happens again. Thanks for the help. Hopefully it doesn't happen again.

Thanks for the reply. I double checked that and its on the cache drive. I don't believe its a network issue. Video streams fine when I get to it. I have no problems browsing the shares from my desktop (win 10 btw). I am at a loss on what could be causing it. Edit: Forgot to mention that Fix Common Problems returns with no errors or warnings after scanning. Not sure if that helps any or not.

Hi guys. Ran into a problem I cannot seem to find an answer for. I upgraded my mariadb docker today and then started to experience black screen when trying to load anything on my kodi box. Something like 45 to 60 seconds for each selection made. Did not have the issue before I updated, and I mean literally 2 minuets tops before I updated. Only thing the log showed was the custom.cnf is ignored that I fixed by changing the permissions to 644 I had found on a post. I think it was somewhere in this post. Here is the log that shows the cnf is ignored and that i have it fixed after the restart. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30_config: executing... [cont-init.d] 30_config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 180904 00:57:48 mysqld_safe Logging to syslog. 180904 00:57:48 mysqld_safe Starting mysqld daemon with databases from /config/databases Caught SIGTERM signal! [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30_config: executing... [cont-init.d] 30_config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 180904 01:05:24 mysqld_safe Logging to syslog. 180904 01:05:24 mysqld_safe Starting mysqld daemon with databases from /config/databases I also read somewhere to rename the appdata/mariadb/log to log-old and that did not help either. Like I was saying I can connect to the db it but it now takes a while for the results. I tested to make sure the Kodi box ghost was not acting up again by logging into the db via HeidiSQL on my desktop. Got the same long wait time for Heidi to open up. Did not seem to have any delay after logged in though.

Final update. A storm blew over today knocking out the power again. Server was not plugged into the UPS this time. After power came back on, server came up and I've had no problems since.

Updated to latest version with no luck. Tried backing up password and shadow files as one post suggested and it didn't fix it. Looks like I'm all alone in trying to figure this out. So I guess I'm going to see if I can find some information on reinstalling without loosing the array, and possibly docker.

Wanted to give an update on this. I changed from smb to nfs and I still have the issue. I have also noticed that one of my shares doesn't seem to take any security changes. The only way I can get the changes to take effect is if I read settings from another share.