ashman70

Right so if I use ZFS as I intend to, convert all my disks to ZFS and just have them operate independently, with no vdevs then I will get the detection and self healing features of ZFS?

RIght but my understanding is the difference between BTRFS and ZFS is BTRFS will alert you to disk corruption but you have to take action to fix it, whereas ZFS does it automatically? Am I correct in this?

Because all the drives are different sizes, I don't want to create pools to lose disk space.

I have a backup server running the latest RC of unRAID 6.12. I am contemplating wiping all the disks and formatting them in ZFS so each dis is running ZFS on its own. Would I still get the data protection from bit rot from ZFS by doing this?

Resolved issue by stopping parity check, taking array offline then re mounting the array, all fixed, everything is back to normal.

I'd prefer not to stop the parity check and rescue the server some how without rebooting if possible, but if the only way is to reboot, then that's what I'll have to do.

I am now able to access the GUI, but its jumping around, only showing a portion of my drives in the array and the rest as unassigned devices.

I was experimenting with a Plex database backup this morning, modifying it and trying to run it. It kept failing telling me no such directory existed. Then all of a sudden the unRAID gui became unresponsive. I can load it up in my browser, it says the array is offline, it was doing a bi monthly parity check, and still appears to be doing that from the disk light activity I can see on the front of the server. I have a monitor plugged into the sever and an login, but the GUI is not responding on my computer. If I try to login to the server from another computer I get this: Any thoughts on what I can do? Not sure what happened or why the server is responding this way. All my dockers including Plex are still running and accessible. I cannot connect to any shares on my server from my Mac but I can from a windows VM. Is there a command I can run to reload NGINX from the command line?

My 16 port HBA is dying, it dropped four drives from the array today, so I need to resolve this quickly, if possible. The board in my server is a MSI Z590 Gaming Plus. It currently has: 1x P2000 1x 8 port HBA 1x 16 port HBA I have additional drives plugged into onboard SATA ports and there are 2 NVME drives on the motherboard as well. I am thinking of getting 2x8 port LSI HBA's to replace my dying 16 port, however this means I lose the P2000, but that shouldn't be a problem for my 11th Gen i5 CPU and quicksync. I can boot the server up, the array just does not mount. Do I just uninstall the Nvidia plugin? Will I be able to edit the Plex docker parameters to remove the Nvidia information?

If you try and access the docker web page like this: 192.168.1.241:32400/web/index.html#! Does it work?

For some reason my Plex docker will not start now, this is the output whenI try to start it. Not sure why it is saying unknown paramater 'Nvidia' I've had a p2000 card in my server working with Plex just fine for ages. I managed to get Plex running by removing the Nvidia parameters and am currently using Quicksync, just not sure what happened to the Nvidia plugin or driver? Any help would be appreciated. Managed to get the Nvidia driver reinstalled and everything is back to norma, was just spooked as this has never happened to me in using unRAID for 6 years and at least four with this P2000.

Are there any supported copper 10GB network cards that work in unRAID? I am aware there are supported fibre cards but I am looking for a copper 10GB network card.

That is disappointing, do you know if this QNAP 10GB card works? QNAP QXG-10G1T

Does anyone know if this 10GB network adapter will work in unRAID?

Today I moved my Plex metadata to a separate SSD that is an unassigned device in hopes that this would resolve the problem, but tonight again, around the same time the same thing happened. Several people on my server streaming, and Plex just becomes unresponsive. I have TOP running and PMS RunServer is at 100% or so and Plex just stops responding, crashes for users, the GUI won't load, I have to restart the docker, which I had to do twice or three times and then its fine.

The past two days, out of the blue, I have been having issues with Plex on my unRAID server. Last night while watching something on Plex it actually crashed kicking myself and remote users off. I had to restart the docker about four times before it settled down, each time I restarted the docker it worked for maybe a minute or two and then would crash again. At the time this was happening I could find nothing in the unRAID logs, or the Plex docker logs to indicate what the issue could be. Last night I ran the TOP command and noticed that SHFS was consuming a lot of CPU cycles. Some Googling led me to posts from others experiencing SHFS high CPU issues in the past. One user had Plex on his cache drive setup in a BRTFS pool, his solution was to either move Plex to its own SSD formatted in XFS I believe. In the past I had Plex running with zero issues on unRAID with Plex on its own SSD. Right now I am on different hardware then previously, and I have a 1TB NVMe SSD and a 500GB 2.5' SSD pooled together for my cache formatted in BTRFS. The file system on my unRAID server is also BTRFS. Oddly enough the Plex issues seemed to occur around the same time both nights, the only thing I had scheduled was mover to run every hour, last night I set to run once a day. I am attaching diagnostics if they will help. I am running unRAID 6.92 I am also not posting this in the Plex forums as I don't think it's an issue with Plex per se, rather an unRAID I/O issue. I am thinking I once again need to move Plex to it's own SSD to isolate it. Does anyone have any insight as to what my ongoing Plex issues could be? backuptower-diagnostics-20220313-0949.zip

Having tremendous issue with Plex tonight, out of the blue. Users dropping connection, restarted the docker, they were fine for 5 min then dropped again. I rolled back to a previous version of Plex, same thing. I optimized my Plex database, same issue happened. I am now running the latest version of Plex and when a user connects to my server the dashboard says nothing is playing. Still having serious issues, yesterday two users playing the same media file caused my CPU to spike to 98% and sit there. When I killed their sessions the CPU went back to normal, when they recconnected to play the same file again, the same thing happened, my CPU spiked to 98%. Other users were connected to Plex at the time and able to play media. Just now I tried to access the Plex web gui on my server and it's unresponsive, I will have to stop and restart the docker so I can get in. backuptower-diagnostics-20220205-0000.zip Plex Media Server Logs_2022-02-04_23-58-44.zip

I have copied all the file off a drive I want to remove from the array, essentially shrinking the array by one disk. I also have a disk I want to replace with a larger one in the array. Both of these tasks require a parity check. Can I accomplish both of these tasks at once or do I have to do them one at a time? What would be my steps?

If I wanted to reduce the number of drives in my array by one disk, say a 3TB drive. Would I do the following: Use the unbalance plug in to scatter the contents of the drive to all other drives. Confirm there is no data on the drive when completed Stop the array Remove the disk from the configuration Go to tools/new config and do a new config preserving drive assignments Save and rebuild parity based on the new config? Does this sound like the correct steps/actions to take? After running the Unbalance plugin I am getting a report that says 11 files or folders don't have the correct permissions and to run the Safe dock permissions, which I ran and then I reran the Unbalance plugin dry run and I am still getting the error. There are some permission issues with the folders/files you want to transfer 11 file(s)/folder(s) with an owner other than 'nobody' 0 file(s)/folder(s) with a group other than 'users' O folder(s) with a permission other than 'drwxrwxrwx' O files(s) with a permission other than '-rw-rw-rw-' or '-r--r--r-- You can find more details about which files have issues in the log file (/boot/logs/unbalance.log) At this point, you can transfer the folders/files if you want, but be advised that it can cause errors in the operation You are STRONGLY suggested to install the Fix Common Problems plugin, then run the Docker Safe New Permissions command

You want to use a SAS PCIe HBA that can support SAS and SATA cards, these card typically support up to 8 drives each, so if you want more than 8 drives you would need two. There are breakout cables you can buy that connect to the HBA cards and then to each drive itself. They look like this: The hardware you listed is fine for what you want to do. it is a good idea to have an SSD for cache and VM's for performance.

Not fixed for me. if I go to management access the page just flickers, still appears to be broken.

I recently had to spin up my backup server and also changed hardware. Ever since getting Plex up and running, I've had issues with various people who never had issues before on my previous server. These issues include, buffering for certain shows, errors such as 'Multimedia format not supported' Today I noticed I am getting this error in my Plex Linuxserver.io logs: Jobs: Exec of /config/Library/Application Support/Plex Media Server/Codecs/EasyAudioEncoder-1699-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13) I see this error a lot in my plex logs is this a permissions issue? [Transcoder] [eac3_eae @ 0x150064a90240] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-4cbfb3e7-66d4-45a8-8cbc-ac5afe203d58/EasyAudioEncoder/Convert to WAV (to 8ch or less)/ef3749eb-fffe-4b0e-b6ee-743259d1bb48_1398-0-1103.wav' Any help would be appreciated. I resolved the issue by stopping Plex, deleting the contents of my Codecs folder and restarting Plex, forcing it to download new Codecs.

What are you running on your server? I would block that IP address in your firewall 142.93.8.2

Same here on 6.9.2

Attaching diasgnostics backuptower-diagnostics-20220126-1530.zip