kaiguy

Yep, same issue here: Atempting to upgrade to: https://downloads.plex.tv/plex-media-server/%20/plexmediaserver_%20_amd64.deb: 2017-02-02 09:32:29 ERROR 404: Not Found. ######################################################## # Upgrade attempt failed, this could be because either # # plex update site is down, local network issues, or # # you were trying to get a version that simply doesn't # # exist, check over the VERSION variable thoroughly & # # correct it or try again later. # ######################################################## Edit: Using the "latest" variable (since I am a PlexPass holder) on unRAID 6.2.4...

Here it is:

Of course. I'm about halfway through converting another drive, so I should have a screenshot this evening after work.

Minor change suggestion to the wiki: It actually is "unassigned" not "no device" on 6.2.4.

Not formatting, per se, but converting. http://lime-technology.com/forum/index.php?topic=37490.0

I've been using unRAID with Macs for years. I was never able to get AFP to work reliably when I first tried (back in the version 4 days), so I just always stuck with SMB for transfers and I've never had an issue with connecting or usage. Every now and then I try to set up a TimeMachine share but that always seems to bomb out on me as well, so I don't do it. You may want to try disabling AFP and sticking with SMB. The only recent change I've encountered with Mac OS is I can no longer connect with "smb://unraidaddress" but instead must use "cifs://unraidaddress". How are you attempting to mount the drives? Truth be told I've never messed with FTP transfers to my server, so I have no clue about that. 10 out of my 14 drives are RFS, but I am currently in process of converting over to XFS. I doubt the drive format has anything to do with your issues, since you're connecting via a network protocol anyway.

Thanks for pointing that out. I don't have any user shares set to cache-no, so I think I'm good in that respect.

I think I'm ready to start the conversion process on 8 RFS disks. Couple questions, if someone would be so kind: I know it will vary based on hardware, but generally, how long should a full 4TB drive take to copy ? Most of my disks are 5400rpm (parity is 7200 though), so I'm already prepared for a long process. I would imagine it would be less than a preclear if I don't do the second checksum validation... If I have a cache pool and disable the mover, assuming I don't delete or change any files, anything added to a user share should stay on the cache and not hit my actual disks, right? I ask because I'd rather speed up the process and not evoke the rsync -rcvPX command. At least not for every disk conversion. Has anyone tried performing 2 simultaneous copies to separate disks before? I wonder if that would speed up the process. Thanks! And thanks to all who contributed to documenting this conversion process.

Congrats, LSIO! This official partnership with Plex is awesome. Please do let us know if the improvements that Plex says they made to the container have been made available on this version.

Had some Docker container updates today, so I thought I'd try to nail down what containers experience the webgui hang, then spin up the drives. I think I have some good observations that someone may find helpful to aid in troubleshooting. First container I updated was an already shut down sabnzbd Docker. It updated without issue. Next container was a running NZBGet container. It seemed hung at the "Stopping container" portion. After about a minute, I got "Error: Error code" and the update completed as expected. No entries in the syslog except 9 entries about port 4 entering a disabled or forwarding state, and a couple about promiscuous mode. This in turn spun up 11 of 14 drives (including parity), none with temperature being reported. But I finally realized what drives don't spin up: the 3 that are formatted xfs. What would be the reason for this? All other containers updated virtually instantly and without any webgui hang.

Thanks for all the replies. /mnt/cache/.docker/docker.img Yep. That's me as well. As I mentioned before, it started happening a few point releases ago. Never an issue before. All data exists on the cache. If this were just related to Plex, I'd understand why all (most) my drives are spinning up, but since this will happen when I restart or stop any of my containers, I feel like it might be related to some change to the underlying Docker handling? I might need to test this again, but weeks ago when I first started investigating, it seemed that there was little rhyme or reason which of my disks would not spin up. There were always like 2 or 3 that would stay spun down, some which even share user shares with others that are spun up. Strange for sure! Not sure then if there's anything I can do then.

unRAID has been so stable for me lately, I haven't really noticed when this started happening, but I think it's been in the last point release or so (currently running 6.2.4). It seems when I update a container, or even just stop it, that there's a long webui lag of 30+ seconds. When it finally becomes responsive again, most (but not all) of my disks go from an idle state to spun up. This most recent time happened with Plex (linuxserver), but it happens any time I update any of my containers as well. Any thoughts on what I can do to troubleshoot this? Nothing in the syslog at all. Thanks!

Unfortunately no. I do see that the two vcpus I've assigned to the VM are frequently maxed out. I think disabling Cortana has helped slightly (at least with the responsiveness of the Start menu), but overall the performance is pretty poor.

Prior to running 6.2, I had a very stable Windows 10 VM using SeaBIOS. When I upgraded, I wanted to reinstall using OVMF instead (since it seemed like most people were having good results with OVMF). I'm really not sure if it's the latest version of Windows 10, 6.2, or something else going on with my config, but I find it to just be all around sluggish. I run it headless, so I access via RDP. I've configured the VM the same (2 vcpus, 4GB of RAM, same unRAID-suggested OS configurations). Everything just seems laggy, and regular usage results in really high CPU usage. Any thoughts or suggestions on what I can do to troubleshoot?

Perhaps it's the Nest plugin. I use the liftmaster2 plugin with my Chamberlain garage opener, as well as the BigAssFans module. It definitely can get a little wonky after a week or two of running, but I can absolutely issue multiple commands or use the iOS 10 home app no problem.

Maybe I'm oversimplifying this, but why not just create a /transcode mapping to whereever you want it to go. Then, within the Plex settings, go to Server Settings | Transcoder | Advanced Settings and enter /transcode to the transcoder temporary directory.

I appreciate your sharing the container with the community. I am getting great use out of it.

Thanks again, Adair! Do you plan on regularly updating the template to keep up-to-date with homebridge, by chance? I ask because there seems to have been quite a bit of development lately on the github. Appreciate your efforts!

Fixed that right up. I had never even seen the force update option before. Thanks!

All of my Linuxserver containers had an update last night except for Plexpy. This is new: Thoughts?

I've always wondered why some people prefer and recommend nzbget over Sab. Perhaps it's my use case, but I've tried nzbget on more than a few occasions and keep going back to Sab because of built-in renaming and browser add-on support.

Sure. Get your running Docker container names with: docker ps Then enter the Docker shell: docker exec -it homebridge /bin/bash Then uninstall your plugin(s) with: sudo npm uninstall -g <plugin name like hombridge-whatever> Doing this from memory so my commands may be off slightly.

Thanks again for your help, Jon! Quick update--created a new Windows 10 VM, but kept the VM's network MAC. It activated straight up without the need to phone in (no clue if keeping the MAC helped, but thought I'd mention it nonetheless). Super easy!

I've had moderate success entering the Docker container shell and executing an npm uninstall command.

Ok, thanks for the advice! I didn't know if perhaps I could keep my current VM's unique identifier or something in order to help out the activation process, but a phone call isn't too difficult.