jazbo8

Stop the docker, delete Plex’s Preference.xml then re-start the docker, and that fixes it.

No one can help me? I also tried downgrading to 6.9.2, but it's still not working. Here is the new log. TIA, Log for_ Plex-Media-Server.html

As the title says, Plex no longer works after the OS update, the WebGUI can't be loaded, etc. Here is the log file and a screenshot. What do I need to do to get it working again? plex-log.txt

Did you ever fix this problem? After the unRaid updated the OS to 6.10.3, the Plex WebGUI refused to connected, it was working fine until that happened...

Just an update, I managed to get the new drive to work AFTER I took everything apart and give it a good cleaning - the chassis was full of dust after years of neglect... I then re-seated all the cables, and the DRAM - fire it back up, and it boots properly into the new unRaid OS (6.8.3). So now I can replace and install the key to the new USB drive - that should be it. Whew, it had me worried for awhile. Thanks again for your assistance.

Thanks, I tried another drive but same result, both drives were un-branded, cheapo ones, perhaps I need to get better quality ones. The one that worked for years was the Kingston Datatraveler (2G). Anything else worth trying before I order some new USB sticks?

My USB drive failed last night so I had to replace it with a new one, I managed to recover the data off it and copied its CONFIG folder. I then used unRaid USB Creator to make a new drive, copied the CONFIG folder over, but upon boot up, I got the following kernel panic screen, which BTW, has never happened before. What is the procedure to discover what went wrong and how would I go about getting unRaid up and running again? TIA, jaz

Thanks, I will do that.

Slowly getting there... a strange problem, I have a 2TB drive that is formatted reiserfs, even though the default is set to xfs. Three other drives were formatted xfs, but this one didn't, weird... Since it is a blank disk, what should I do to reformat it to xfs? Should I wait for the Parity build finishes before reformatting it? Thanks, jaz

Ok, I will make a new flash drive and try again, thanks!

Still no luck, no GUI, and the diagnotics file is blank. Here is the syslog, perhaps you can spot something not quite right. Also attached is a screen shot when diagnotics was run. syslog.txt

That's weird, why do you think that is? I just type diagnostics at the console.

Yes, that worked. Now I run into another problem... I want to increase the parity drive to a larger size and upgrade most of the old 1TB data disks, so I did the following: 1) un-share all the existing disks that I want to remove; 2) run New Configuration; 3) un-assign the disks that I want to remove; 4) replace all the disks except for the 2 that I wanted to keep; 5) reboot. So I basically just kept 1 data disk, and the original parity disk. All the other disks are new, i.e., they have not been pre-cleared (which was I planning to do via the Web GUI). The system started, and I can use telnet to login, but I got no GUI, not sure what to do next... Your assistance is much appreciated. Here is the diagnostics file for your information. tower-diagnostics-20170404-1714.zip

I just recently upgraded to 6.3.2, I built an array with 6 disks to begin with, which is working fine. Now I want to add more disks to the array - all the disks were from my old 4.4.2 system. But when I tried to assign the new disks (with existing data), I got a warning that the disk data will be erased when the array is started. Not good! So, what is the correct procedure for doing that?

Yes, a clean install for sure. I read the above linked document several times, and it made no mention of the parity sync, whereas in an earlier document (upgrading from 4 to 5 I think), it says that the parity sync must be completed before the upgrade can take place, so I just want to make sure. Anyway, It seems that I am ready to upgrade to V.6, fingers crossed (again). Thanks for your help as always.