fersal

Current status: Created a boot device with 6.7.0, replaced the config folder with the backup, and booted from the flash drive; same issues I imagine /dev/sda1 must be the flash drive, no problem there apparently. However I can't find a "logs" folder anywhere in the UNRAID flash drive... any way to mount an unassigned device via the command line and copy the diagnostic file from /boot/logs/ to it? Something curious, when I booted into the GUI I saw the following, as you can see the hard drives, cache SSD and flash show up, but the array is not started. The status says "Invalid Key" (as expected because of new USB drive) and the problem of no IP address still persists. Looks like I'm close... any other ideas please?

I used the Flash Device Creator tool to create a 6.6.7 boot drive, replaced the config file with the backup. I boot from it, and still looks the same, with /boot being assigned to /dev/sda1. I could get a diagnostics file if I copy it to a USB drive, but how do I mount an unassigned device from the command line? Any other ideas?

OK thanks, I guess I can use the Flash Device Creator tool, but version 6.6.5 is not an option. Is it OK to download 6.6.7, replace the config file with the backup, make bootable and try again?

I double-checked the USB drive properties and it was labeled UNRAID and formatted as FAT32. I moved it to another USB port, booted and got the same results :-( What else do you suggest, should I try to download the OS and copy over the config file? Anything else?

Hmmm doesn't look like it, here's the output of the df command: Any ideas would be greatly appreciated.

My flash boot drive failed, so I took a new flash drive and copied a backup I had into it. I made it bootable, and apparently it booted successfully. However, the console shows that it doesn't have an IP address (see attached), and the server does not show up on the network. I also never got notified to get a new key. Did I miss something in the process? When I go into MC it looks like none of my volumes or shares are mounted. I created a diagnostics file but the only way to get it out is to copy it to a flash drive... how can I mount a USB drive so I can see it in MC? Thanks in advance for any help!

Maybe you could explain what you did to solve the problem in case some of us here have a similar issue?

As I understand it, even if we preserve the path mappings exactly the same in a new container we may lose a bunch of metadata? So it may be better to keep the same container and just replace the Repository entry? How about the Docker Hub URL? And also the entries in Template Repositories field? Has anyone migrated from Needo Plex docker to a more current one like linuxserver's can you please chime in? Thanks!

Thanks Squid but what is the process to install the new repository? Stop the current PlexMediaServer container, then create a new container with the binhex Plexpass? Is there step-by-step documentation somewhere? So theoretically I could keep the old Plex container (stopped) just in case something doesn't work with the new one?

I'm still getting the same warning but now I'm getting notices on the Plex UI itself that the application is not up to date and may be missing some features. I have 2 Questions if you'd be so kind: What is the process for changing my Plex docker to a new repository? I'm attaching my current settings and mappings. Would my appdata files sitting on my cache need to be updated or can they be used as they are? Thanks!

One thing that I did notice was that in the Docker volume mappings for Plex I have everything under /mnt/user/ except one entry that says: /transcode <--> /tmp Could this be causing this issue?

Actually no major hardware or software changes in the past year other than upgrade to 6.5.3. However maybe it's happened before because I don't look at the log file very often. The only docker is a Plex Media Server. And yes, all files are in user shares under /mnt/user/; I'll keep monitoring the log file to see of this happens again. If anyone else has any ideas please let me know, thanks!

Thanks, as far as I know I have all my data files under /mnt. I tried looking at the Diagnostics file but I don't know where to look... has someone else had this issue before?

While checking the log to determine what was causing some drives to spin up, I saw an entry that mentioned "Warning: Rootfs file is getting full (currently 81 % used)". What causes this usually, and how can I prevent it? I'm attaching diagnostics file, thanks for your help! tower-diagnostics-20180916-0538.zip

Yes I did set the Share switch from the beginning thanks, if not I don't think it would've showed up in MC? But still not visible from Win 10.