Gizo

After the server became unresponsive the dockers stopped working. I was getting docker service failed to start. Something random I did notice when this first happen was my nvidia shield also was having trouble connecting to my network. That's why I ended up trying to view my server via webgui and got my first 500 internal server error. Restarted server and got dockers services failed to start. When I looked around on how to fix this I saw someone recommend to delete docker.img and increase the size. After doing that and reinstalling the dockers containers my server became responsive but seems to crash and becomes unreachable after a couple of hours. I can change the docker.img back to 20 at least also I'll run a memtest.

That was on completely different hardware actually. I original setup the server using all new parts. I was getting kernel panic errors left and right and could barely use the webgui. So I ran memtest, bought all new parts one by one. Same thing happened. So I used my gaming pc and turned that into my unraid server since I knew all the parts were working in my gaming / windows machine. I was up and running great for months, only went down due to power outage. My UPS had to get sent back for repairs otherwise I'd have longer then 86 days uptime. I'm starting to think it might be network related but I'm really not too sure. Seems the server works fine for a few hours then plex and all my dock containers and webgui become unreachable. I've managed to at least get a couple diagnostics though so maybe someone will know. gizbo-diagnostics-20200820-1251.zip gizbo-diagnostics-20200820-0619.zip

Here is diagnostics. All I've done so far after this happen was delete the docker.img, reinstall my dockers then the same thing happened. Webgui crash's and server unreachable so I did that again. I've been up and running for about 2 hours now without any issues. Isn't it better to try and get diagnostics while the issue is happening? gizbo-diagnostics-20200818-1553.zip

My dockers keep failing to load on webgui and crashing and then i'll get failed to start docker services sometimes. My server was running for about 86days prior to this without much change. No dockers have even updated recently. I could only get a syslog this time before I had to reboot. I've cleared the docker.img and re added the few I truly need. But it seems to just happen all over again. When/if it does I'll try to add a diagnostics. Any help greatly appreciated, Thanks. Edited: updated title and attached a couple diagnostics in latest post. gizbo-syslog-20200818-1912.zip

I recently moved so my ISP and IP some other things changed. The real problem was I didn't make a backup of my webgui password ( i have a back up of every single password but that one 😫). I did pull the flash drive and tried it in a linux(fedora) as well as a win 10 laptop. Both of them had trouble seeing the flash drive even. But I deleted the config/passwd config/shadow config/smbpasswd just as the troubleshooting guide suggested. I couldn't login at this point and it didn't make my password "null" like is suggested. What did solve the issue was, connect a spare monitor to unraid server, login change the password and it seems to be back to normal. Honestly it was a super rookie mistake I should of wrote down all the password prior to making any changes. I haven't made a back up of the flash drive but that is first on my list of things to do today. The problem was me doing a fresh install on my daily pc which had the webgui saved in history. Once I lost the history of the old OS I lost that password.

Unfortunately I decided to do a fresh install on my main PC , webgui pass was saved in browser history. 😑 I tried the recovery password. Deleting config/passwd config/shadow config/smbpasswd on the flashdrive. But after rebooting the password doesn't seem to be reset like the troubleshooting guide suggests "Note that this will reset all user passwords including ‘root’ user to null (blank). " I go back to the webgui and i've tried root with a blank password and get this error Warning: file(/etc/nginx/htpasswd): failed to open stream: No such file or directory in /usr/local/emhttp/login.php on line 23 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/login.php on line 23

Made a test share that's public using SMB. I copied over a random document and I can delete that, even though the perms could not be determined Edit: So my user that I want to be able to delete things should be "guest" that last part has be a bit confused

Can't seem to connect with just SMB enabled, just tried. It only shows the remote login server, which I tried login into. It just say unable to access location and I no longer get the password prompt. I enabled NFS and able to copy to and from but can't delete. Which I suppose I could more then likely use krusader for deletion. Less convenient though

I believe I'm using NFS though I have both enabled on the server itself. I also have the user set to allow both NFS and SMB under Users and under Shares.

SOLVED?: No clue how I fixed it but I did so its all good.😕 I can move and delete freely from my fedora machine just wish i knew why or what i even did I just moved my main pc over to Fedora 31 loving it so far but having some issues accessing my media on my unraid server. I'm unsure if i need the smb shares enabled anymore as I doubt use windows now. It seems I can add new files (only tried 1) but can't delete anything. Things i've tried 1 adding the user 2 setting it up with read/write 3 Tools > Fix perms I've attached a pic and my logs/ diagnostics. Thanks in advance!! gizbo-diagnostics-20200404-0928.zip gizbo-syslog-20200404-1429.zip

Been copying data back and forth fine through windows even did last night. Work up this morning to make some changes add a share to back up my win as im moving to linux on my main PC. Edit: ran docker fix permission after a few google searches and back in business. 🍺

That seem to fix it, Thanks 👍

My power went out this morning, when I went to start my unraid server back up it never showed on the network. Unfortunately i had to send my UPS in on warranty. I plugged a monitor in the check what was going on and got this code. I did plug my unraid flash into my windows machine and copied all the files if any of that is useful let me know. Thanks in advance!

Had a random crash today while moving some files to my multimedia share. After the unclean reboot the usual parity check started, 60% in another crash happened. Was running for 9 days roughly before the first crash. I've attached a the diagnostic that a ran after unclean reboot and and diagnostic I just ran. And also the syslog saved to flash gizbo-diagnostics-20191230-2308.zip gizbo-diagnostics-20191230-1127.zip syslog_12-21-to-12-30

Memtest completed 4 passes no errors found (sorry for crappy phone pic). Is there anyway to check the power supply without just buying a new one?

Okay, started memtest this morning I will report back the finding after a full test. Thanks

Unfortunately I already have C-state set to disabled and Power Supply Idle set to typical current idle. Was hoping it would be that simple.

This is my first build, After setting everything up and doing my first parity check after hours it was unresponsive and crashed. I tried to run another parity check over the night and the same thing happened. I was able to get a the second syslog from the terminal. Here are my spec if it helps Gigabyte B450M DS3H AMD Ryzen 5 1600 Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 Memory LSI 9201-8i (it mode) 1x Samsung SSD 860 EVO 500GB (cache) 1x Shucked Seagate 5tb (1 disk) 2x Shucked WD Easystore 8tb (1 disk, 1 parity) EVGA GeForce 8400 GS 1 GB Video Card Thermaltake Smart 500w psu Thanks gizbo-diagnostics-20191219-0021.zip syslog