SSD

Was trying to get airsonic working with my Sonus Connect, but no luck. I found this on Reddit: I quoted some of that below. I followed the github link, but could not find the referenced file inside the docker to make this patch. My intended use is strictly behind my firewall, so security concerns not a big concern. Any help appreciated! - SSD From Reddit: "The underlying problem is that the sonos api has a major security vulnerability ... ... With that said, one could easily make the sonos work again in theory with the existing airsonic code with a one line patch. Simply add '/ws/**' to the list here https://github.com/airsonic/airsonic/blob/17915d908152aafcbda5693da190e14158ff064c/airsonic-main/src/main/java/org/airsonic/player/security/GlobalSecurityConfig.java#L128. To be clear, this change has not been made in the actual source because it allows anyone to access the sonos api. However if you don't have airsonic exposed over the internet, you may not care. I'm really sorry for breaking it, but I can't in clear conscience go back to what it was before knowing that lots of people have airsonic exposed."

Thanks @bonienl Important to finish your business in the tab before switching!

If I open a custom tab, the page is empty and the web page opens. That is perfect. Then I click on the unRAID main tab and it shows. Then I click on the custom tab again. It is empty and the page reloads, rather than just displaying the same static content it displayed the last time I was there. The page I am using can take quite a few seconds to refresh. I'd just prefer it preserve the page as it was before I left.

Squid - The page seems to refresh every time you navigate to the tab. Is there an option that the web page state can be preserved? Thanks!

Thanks for taking the time to post this guide! I haven't tested it myself, but it looks detailed and comprehensive! (#ssdindex - GPU Passthru Guide for overcoming Error 43)

Not that I have seen. When the VM is stopped, the screen is blank / no signal.

Can you confirm the USB label is "UNRAID"?

@jpeltoniemi - Writes to the parity protected array are pretty slow. And involve accesses to both the disk involved and the parity disk. Each is required to do a block read followed by a block write of the same block. This means a full revolution of the slower of parity and the data disk. It is a decided write penalty. As @trurl mentioned, there is no existing feature in unRAID to leverage your elegant read-caching paradigm. I can't say with certainty if a duplicate file existed in the same user share on cache as on a disk in the array, that unRAID would use the one on cache or not.

Actually the array is a pretty poor choice for running apps or games. Normally users are utilizing the cache drive (often used more as an.application drive / virtual disk image) for such purposes. The array tends to hold large media files with few if any interactive writes. UnRaid also supports unassigned disks, meaning not in the array or cache. They can be spinners or SSDs and used for various purposes that typically involve a lot of interactive disk writes.

Thanks wgstarks! Wow! @Squid- any way to prevent this from happening so frequently. It was generating a line every 2 or 3 seconds for days. The server spontaneously rebooted and these started logging. I was out of town.

My server rebooted and I got this error: Feb 21 14:23:10 tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token I was out of town and this has been generated every few seconds for days. There are over 80,000 rows. Can you please help explain the issue so that I can repair? There are two remote SMB mounts that would not work - the server they reference is offline. Could that be the problem? Thanks!

I do not think that running a card in x4 slot is going to hold you back much if at all if you are using spinners and your slots are PCIe 2.0 our higher spec. Each lane of a PCIe 2.0 controller provides about 400 MB/sec of bandwidth, which can support 2 200 MB/sec drives. Multiply by 4 lanes, means that the controller can support 8 drives at 200 MB/sec speed. Put one in an x8 slot and now you are up to 400 MB/sec per drive, which no spinner can get anywhere close to. I run a -16I version of that controller in an x8 slot with no problem. Which is equivalent bandwidth per drive of running a -8i version in an x4 slot. If this were a PCIe 1.1 slot, the bandwidths would be cut in half and you would need an x8 slot to not restrict bandwidth. Physically fitting an x8 card into an x4 slot can be a challenge. Newer motherboards have open ended slots that let you insert them. But older motherboards might require melting the back of the slot. But an x8 card will work in an x4 slot. Even an x16 card will work in an x1 slot, just with reduced bandwidth.

I had reserved 25% more space for the metadata, and copied the old to the new and it fit (as expected). But seems Plex wanted to do some database update and it immediately ran out of space. Turns out BTRFS was taking about 25% more space to store than XFS! So it used up all of the excess and the upgrade failed. Going back to XFS for the metadata. I am keeping in a loopback file to avoid the huge file count and associated headaches on the cache drive.

Was just posting. I ran out of space. Fixed and now the Plex docker is up! Thanks!!

Need a little help. I am trying to move my Plex installation from serverA to serverB. I copied over the appdata folder to the new server. Installed the my_plex template. Tweaked the mappings a little to match new server. And started the docker. But the WebUI refuses to connect. And in the log it continues to say "Starting Plex Media Server." over and over - updating every 15 seconds or so. See detailed log below. Any help appreciated. How do I debug this to understand what might be going wrong. The server name is different and the IP address is different, everything else is same. Thanks! ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... ##################################################### # Login via the webui at http://<ip>:32400/web # # and restart the docker, because there was no # # preference file found, possibly first startup. # ##################################################### [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. dbus[271]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted [services.d] done. Starting Plex Media Server. Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fec8:a4c0. New relevant interface vnet0.IPv6 for mDNS. Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv6 with address fe80::7804:13ff:fec6:9dc6. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.252. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface bond0.IPv6 with address fe80::7285:c2ff:fe54:d3c3. New relevant interface bond0.IPv6 for mDNS. Network interface enumeration completed. Registering new address record for fe80::fc54:ff:fec8:a4c0 on vnet0.*. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for fe80::7804:13ff:fec6:9dc6 on br0.*. Registering new address record for 192.168.1.252 on br0.IPv4. Registering new address record for fe80::7285:c2ff:fe54:d3c3 on bond0.*. Server startup complete. Host name is merlin.local. Local service cookie is 3021989262. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Got SIGTERM, quitting. Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fec8:a4c0. Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Leaving mDNS multicast group on interface br0.IPv6 with address fe80::7804:13ff:fec6:9dc6. Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.252. Leaving mDNS multicast group on interface bond0.IPv6 with address fe80::7285:c2ff:fe54:d3c3. avahi-daemon 0.6.32-rc exiting. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

There is a free tool called "TeamViewer that you can install in Windows on your home network. And you can install the Teamviewer client on a variety of devices (even phone and tablet). Once installed, you can access your Windows workstation from a computer on the internet. Obviously you want a strong password, but it is hardened for Internet use and won't be hacked (or at least the risk is very low). Once connected you are remote controlling the workstation, which would let you access your files as though you were sitting at home. It also has upload/download features depending on the client you are using. Is this what you are looking to do?

You're welcome. Use the reputation feature when you feel you've gotten good support here in the forums. (Click the heart on lower right of any post) Glad you got your VNC connection working. Now is a good time to install NoMachine. It's free and works very well - as close to pass through performances I've seen. And as you've seen, it is good to have a couple connection options to avoid losing access completely! Good luck and enjoy your array!

No, you need to install NoMachine. You need VNC access to do so. Weird VNC not working. I do remember have a VNC problem and was able to access with RealVNC. You might give that a try. This licensing story seems a little odd. Earlier you said the license was a financial hardship. Now suddenly you are ready to buy another license. Seems odd. If you legitimately purchased a license Tom will get you squared away. I am 100% sure of that. I'd suggest getting it straightened out now. If you don't, or if you got a resale or something, it is unlikely the flash will fail, but you are at risk should it ever happen. Please understand that the only person that can help you with that is LimeTech. Discussions here in the forum not productive.

I highly recommend NoMachine, a VNC like tool that provides a much better experience than VNC IMO. It is the first thing I install in a new VM. It will also run alongside passthrough video. It is therefore very handy if the passthrough should ever stop working to gain access to the server and fix the issue. VNC might work the same, but as implemented, VNC is not enabled when video is passed through. And VNC sorta sucks compared to NoMachine. Sorry can't help with your VNC challenge. A PM / email to @limetech might straighten this out. He is very fair with these situations. Not sure all the details of what happened with you. License transfers are not allowed.

Would Plex metadata create a significant write amplification issue? Plex metadata files are tiny, but there are a zillion of them!

Looking at the Samsung 960 PRO, the endurance of the 512G version is 400TB. That basically means that it can be filled 800 times. That is a pretty big number. But I am assuming that is looking at a usage pattern in which wear is effectively managed. If wear were to be poorly managed, let's say the hardest hit blocks get hit 10x more than other parts, that number goes from 800 to 80. (Maybe that is not realistic - I am not an expert. But without trim I am not sure.) Running frequent parity rebuilds re-writing every sector would take chunks out of its lifespan that would add up. Generally I would say that the cache pool is a better place for data requiring high speed access. That or a HW RAID controller that is designed with SSD usage in mind, running as a UD. High speed access to a large media library really doesn't make a lot of sense.

I have not. Instead of using an unassigned device ssd, could you make the ssd the cache. Then I think the mover would do what you want.

Rebuilding parity is a particularly expensive operation for an SSD given its limited # of writes.

I would not hold my breath for unRAID to offically support SSD arrays. I don't know how SSD parity would ever work. The whole idea of unused space has no real meaning with parity, unless we treat a block of parity as unused if the corresponding blocks on all disks are unused. unRAID would have to be very aware of the inner workings of the file systems to know. And if you filled a disk, parity would always be considered full and never able to be trimmed - hence would slow down. I think we're looking at a paradigm shift for SSDs to be supported. You could use SSDs in the array if parity is a spinner and trim runs periodically (let's say ever 2 months), and that when you trim all the SSDs, you rebuild parity. Not sure it is worth it. So I'd stick with spinners for the array. If you have a specific use case that requires faster speed and redundancy, go with a cache pool and you'd get speed and redundancy . Or go with a RAID card in the unRAID server and run it as a UD alongside the array on the server.

I'll check. Updated it pretty recently but its a new board and there might be another.