Well it worked perfectly here, every update from 5.x to 6.8.3 has never given me a single issue. This has to be in your end. Post diagnostics, stop bashing unraid for your incompetence and behave like a rational person. 

17 minutes ago, Abnorm said:

Well it worked perfectly here, every update from 5.x to 6.8.3 has never given me a single issue. This has to be in your end. Post diagnostics, stop bashing unraid for your incompetence and behave like a rational person. 

I posted diagnostics more than an hour before you posted your reply. Why didn't you read them?

You might give an example of a "rational person" if you read posts before you react. If you'd like to set an example of a "rational person", then carefully read the entire thread before reacting. If the way you react you seem fit (given ignorance of not reading the post and data provided), then you are no better than me.

The problem was triggered exclusively by updating UNRAID (and I've done that numerous time), with no changes to any other infrastructure components.

"Bashing"? No, warning of a very serious issue, which severely compromised the server. If other users of UNRAID see how raising issues results in personal attacks on the person who raised the issue, what is the likelihood that UNRAID problems will be raised to begin with?

Edited August 13, 20205 yr by emod

5 minutes ago, emod said:

you are no better than me

Would everyone please stop. I agree this thread was off to a bad start but if you don't have anything constructive to offer regarding the actual problems please go on to another thread.

9 minutes ago, emod said:

I posted diagnostics more than an hour before you posted your reply. Why didn't you read them?

You might give an example of a "rational person" if you read posts before you react. If you'd like to set an example of a "rational person", then carefully read the entire thread before reacting. If the way you react you seem fit (given ignorance of not reading the post and data provided), then you are no better than me.

The problem was triggered exclusively by updating UNRAID (and I've done that numerous time), with no changes to any other infrastructure components.

"Bashing"? No, warning of a very serious issue, which severely compromised the server. If other users of UNRAID see how raising issues results in personal attacks on the person who raised the issue, what is the likelihood that UNRAID problems will be raised to begin with?

Kk, good luck on troubleshooting.

So far, everything screams NETWORK ISSUES and lets confirm that first.

Do the following from a terminal window and post the results.

ping 8.8.8.8

ping www.google.com

 

5 minutes ago, trurl said:

Would everyone please stop. I agree this thread was off to a bad start but if you don't have anything constructive to offer regarding the actual problems please go on to another thread.

It's interesting that I never initiated personal attacks against any forum member (I did react to few insulting ones that were targeting me for sure), yet you quoted me? Very interesting.

 

And after you posted your plea, another member just posted another post, not adding anything to the solution, but, unsuccessfully, trying to be cynical.

2 minutes ago, bonienl said:

So far, everything screams NETWORK ISSUES and lets confirm that first.

Do the following from a terminal window and post the results.

ping 8.8.8.8

ping www.google.com

 

1. PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=9.32 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=12.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=5.64 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=9.27 ms

....

 

2. 64 bytes from yul03s04-in-f4.1e100.net (172.217.13.164): icmp_seq=1 ttl=117 time=18.8 ms
64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=2 ttl=117 time=23.3 ms
64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=3 ttl=117 time=17.1 ms
64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=4 ttl=117 time=20.6 ms
64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=5 ttl=117 time=23.8 ms
64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=6 ttl=117 time=17.4 ms
64 bytes from yul06s04-in-f4.1e100.net (172.217.13.164): icmp_seq=7 ttl=117 time=20.7 ms

.....

Start your system in safe mode and check again.

 

Ps. your diagnostics are of version 6.8.2, which version are you currently running?

 

Also tell us what your original version was prior to upgrading.

Edited August 13, 20205 yr by bonienl

29 minutes ago, bonienl said:

Start your system in safe mode and check again.

 

Ps. your diagnostics are of version 6.8.2, which version are you currently running?

Done.

 

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=10.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=13.3 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=6.22 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=9.14 ms

 

ping www.google.com
PING www.google.com (172.217.8.4) 56(84) bytes of data.
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=1 ttl=118 time=9.50 ms
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=2 ttl=118 time=12.1 ms
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=3 ttl=118 time=5.28 ms
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=4 ttl=118 time=8.18 ms
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=5 ttl=118 time=11.1 ms
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=6 ttl=118 time=4.77 ms
64 bytes from iad23s59-in-f4.1e100.net (172.217.8.4): icmp_seq=7 ttl=118 time=6.83 ms

 

v 6.8.2. Per original post, as soon as I discovered issue with 6.8.3, first thing was downgrading to 6.8.2. System remained on that version.

Edited August 13, 20205 yr by emod

So everything is working fine now with 6.8.2?

21 minutes ago, bonienl said:

So everything is working fine now with 6.8.2?

No. Issues I first saw with 6.8.3 remained, plus: I cannot access apps (loading apps never finishes), Docker returned but many apps have "?" in lieu of app icon. mail server is stopped and cannot be started. Unable to access diagnostics page (the one I provided I manually copied from server onto USB -  I attached monitor/mouse/keyb directly to server).

This all indicates you have another problem unrelated to 6.8.3.

 

A couple of actions

• Do a filesystem check and repair of your usb stick on a windows machine (shutdown first)
• Test using a different browser
• Test in safe mode

Just in case anybody goes looking for the diagnostics mentioned, the user has deleted them.

I am real sorry you are having this issue.  It can be pretty scary when your system starts to have problems.

I am not attacking you and I would like to help.  Just to set the context of my post, I have been on 6.8.3 ever since it has been released (about 5 months)  My system has been rock solid.  Maybe you should change the name of this post to "Unraid not functional after upgrade to 6.8.3"  or something like that.

 

I agree with bonienl who is helping you through this that it is not software, so if it is not software it is hardware.  

 

I looked through the post and could not find your diagnostics.  You might want to post diagnostics so that we can see how your system is booting.  So here are my thoughts.  Slowness from UnRaid might indicate a bad or filled up flash drive.  I just experienced this issue a few days ago, while I was doing a pre-clear, the whole unraid interface was corrupted with errors reporting unable to write to files.  I ended up stopping and starting the web interface engine to clear it up.  But I don't think that is the issue.  If your flash drive is having issues this could cause the slowness and corruption you are seeing. 

 

Have you tried to boot the flash drive in another system?  Yes it will not start because its missing the drives, but I was thinking that either the Flash drive is dying or the USB port is going out.  UnRaid runs in a RAM disk.  The other possibility is that you have bad RAM.  The RAM disk is created in this bad area of RAM and becomes corrupted.  If you boot this USB into another system, and see an improvement, you can eliminate the flash drive as the problem and think about the USB port or bad RAM.  If you still are having the problem, you could back up your config folder and reformat the drive, put 6.8.2 back on the USB drive and copy your config folder over and try that.  It is possible that the upgrade went sideways becoming corrupted.

 

DO NOT use another flash drive, the license will no longer be valid on that new flash drive.  Reformat the old Flash drive and copy the config over to that freshly formatted flash drive.

Edited August 13, 20205 yr by SidebandSamurai