MowMdown

I also noticed the filesystems of two of those drives are really odd choices… exfat and ntfs? IMO once you fix the speed issue you should strongly consider using XFS over the other choices you made. Also parity syncs/checks should normally take about 1.5 hours per TB of your single largest disk. It takes just under 24 hours for my 12TB disks to complete.

What else is plugged into your UPS?

Probably need to either disconnect it if it's a physical USB or disable it in BIOS so unraid does not detect it

there is zero chance that system is pulling 250W idle... I dont even think it would pull 250W running full tilt (maybe but no way idle with disks spun down) CPU is a 65W TDP CPU GPU is 75W Max Power draw Lets say 8W average per HDD is like another 80W Were still under 250W with everything going at full tilt. Couple of questions: 1. What size PSU and what power efficiency is it rated for? 2. How are you measuring wattage? For comparison my system (hardware in signature) with 8x 12TB HDDs, 5x 1TB Sata SSDs, a bluray drive, and an Intel Arc A310 doesn't pull 200W and AMD 5800X is a 105W TDP CPU and this isnt idle (I see about 90W idle on my system which includes some things running on my UPS)

XPG_GAMMIX_S11_Pro_2K482LAAQGXT (nvme0n1) 512 2000409264 => data partition: nvme0n1p3 type: gpt start: 239616 size: 1000084480 code: 0xee (8) . . . Jan 28 00:49:50 NorthernLight root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error. Jan 28 00:49:50 NorthernLight root: dmesg(1) may have more information after failed mount system call. Jan 28 00:49:50 NorthernLight kernel: XFS (nvme0n1p3): Invalid superblock magic number Jan 28 00:49:50 NorthernLight emhttpd: shcmd (96): exit status: 32 Jan 28 00:49:50 NorthernLight emhttpd: shcmd (97): rmdir /mnt/cache Jan 28 00:49:50 NorthernLight emhttpd: cache: mount error: wrong or no file system So it looks like somehow when your VM tried to boot on the wrong disk if that's what happened, the partition table got altered if that's even possible? It looks as if the disk was re-partitioned if you never used this as a windows disk before. Youre gonna have to wait for @JorgeB to see if he can suggest any ways to correct this.

Is there any reason you left the microsoft partitions on the disk? My guess at first glance is unraid is getting confused by the partition layout and doesn't know what to do. I would say it's best to remove these if you're not running Windows OS off of this disk anymore. Also does not appear to be an XFS partition?

Parity does not have a filesystem, that is normal and expected. If either of those 8TB drives dies you will be able to replace the failed disk with another 8TB drive and rebuild it either from the parity information OR the data disk. Parity1 works by XOR'ing the bits of all the "array disks" which you only have the one so far. When unraid does the calculation, and it knows there should a 1 bit but there is only a 0 bit, unraid can assume the missing bit is a 1 and "emulate" it. If the Disk1 dies or goes missing, unraid will emulate the missing disk as if it's still there, you can use the emulated disk as a real disk until you replace the physical disk. The issue you and everyone else can run into with parity is that if the information on the data disk is bad, the parity rebuild will also be bad, with that said parity is not backup. It will only help you in the event of a drive loss. It cannot fix corruption or accidental file deletion. Your "Cache" pool works a little differently. These two drives appear to be configured in a MIRROR, this is similar but different to a parity system. The data on both of these disks is IDENTICAL and each disk has it's own filesystem. If either of these drives dies, the other disk can take over as if it was independent all along, and you can simply replace the bad disk and unraid will make a new MIRROR from the good disk. The cool thing about a mirror is that since there are two identical copies of data, the filesystem can self-heal if it detects that one of the copies no longer matches the other known good copy via checksums and other things. Rest assured you are doing things the proper way it appears and you have drive failure redundancy. You still should make backups of your important data as these can be lost in other ways besides a disk dying.

Please post your system diagnostics (<---Click this link to see how) in a reply to my comment.

Like JorgeB said, without the diagnostics from before a reboot, it's hard to determine a cause. If you haven't already, enabling the remote syslog server and pointing it to the local IP of the unraid box will allow it to save a log to the share or your choosing.

How are the drives powered? Are they all on the same single power cable from the PSU or are you using multiple cables to power the drives? Sometimes you gotta split the drives between two separate cables even though a single cable might have enough "ends" to connect 4 or 5 drives.

Running a parity check cant hurt but the second you start to see errors, stop it and run a correcting parity check. The longer your array sits without valid parity, the more likely you have another failure but this time without parity to recover from.

Those extensions are for editing text files, I don't believe video playback is supported. You're going to want to use something like VLC to connect over the network to view video files through an SMB share or something. You can edit the editor file on the boot usb and add the video extensions but be warned this likely won't work.

Jan 19 07:21:04 TowerII kernel: [Hardware Error]: Corrected error, no action required. The check event was resolved. Ill be honest with my AMD machine, I often see one of these per boot.

Memtest86+ ideally should be ran for a period of 24 hours or a fail whichever occurs first. A single failure is enough to say a stick of ram is bad

Also is there a reason you’re adding the extra parameter instead of using the network dropdown from the template page?

I’d probably look into using rclone and wrapping it in a crypt mount to encrypt your data…

Regarding these few things. The macvlan issue was resolved on unraid not too long after it became an issue. No real need to use either over the other.I prefer macvlan) The 2nd thing is that unraid introduced "exclusive shares" which bypasses FUSE for shares that reside on a single array disk or pool. This can be enabled in the global settings. Lastly, unraid no longer prioritizes the core/thread 0/1 anymore it will just use whatever core/threads are most free. Pinning is probably doing more hard than good in this instance, I understand you were troubleshooting.

This confirms plex can physically see the file, which means the issue is something other than plex not being able to read the contents of the folders. I don't think it's a permissions issue either. So the only two scenarios I can think of is: The file was scanned and tagged with the wrong metadata (this happens to me, I import something and have to manually match the file to the correct metadata) The plex db is in need of repair. Not uncommon but not super common either. Never hurts to run the dbrepair anyways. My suggestion is to post in the plex forums for them to look at your plex logs and whatever other information comes from the plex container. You can link them to this post here too so they can see everything we tried. I'm kinda out of ideas and I'm fairly confident this is not an unraid related issue.

I don't think those are actually a part of the filename. It's just being displayed that way by the console.

Not that I recommend it but you can try to find a browser extension that simply turns off horizontal scroll bars. Note: This may break the webgui so if you have issues turn off or remove the extension should you use one.

If you can see the movie file when you cd /MOVIES/HORROR/The\ Black\ Phone\ \(2022\)/ and then from inside this folder type in ls -lah and it shows you the file plex can see it and should be detecting it. Please confirm. But like I mentioned in the past, how you organize your files is paramount to how plex properly detects them. With you straying from the expected conventions of just a single "Movie" folder (and you using sub-categories), plex may have a more difficult time finding them and displaying them. It's not that your way cant work it's just that it may be hit or miss. You can try doing the "plex shuffle" and moving the movie folder out of HORROR and putting it temporarily in another folder and then forcing a library re-scan to see if it can pick it up, then moving it back and scanning again. The only other thing I can think of right now is there is a possibility the plex database is in need of repair and @bmartino1 has a special docker container that you can use to repair it. You can search the unraid APPS tab for dbrepair and use his forum post to see how to use it. I would only suggest doing the repair IF the database is actually in need of repair.

My ultimate guess is plex is having trouble finding that folder/file due to a matching content issue where it's seeing "black phone (2022)" and assigning it to another movie title. It appears clearly in the folder so I dont suspect that it cant see it. It probably does see it but it's giving it a assigning it to a different movie name+poster. If you hover of the movie poster in plex, and click the 3 dots and at the bottom of the menu click on "get info" and look at the file path. Maybe one of your movies is improperly identified as something else? OR you can try adding "The" to both the file and folder for Black Phone and re-scanning your plex library to see if anything changes.

Alright now we are getting somewhere... so if you cd /MOVIES/HORROR/The\ Black\ Phone\ \(2022\)/ (yes the slashes are necessary) When you do get into the movie folder, then run ls -lah so we can see the file permissions and user:group assignment Or you can: cd /MOV (press TAB) cd /MOVIES/H (press TAB) cd /MOVIES/HORROR/The\ B (press TAB) cd /MOVIES/HORROR/The\ Black\ Phone\ \(2022\) (now you can hit enter) Also why do you have another "MOVIES" folder inside MOVIES next to the HORROR folder...? Is this on purpose?

With having zero clue about your system or what your issues are... The fix is: 1) Enable exclusive shares in the global settings. 2) make sure you are downloading to an SSD pool of some sort 3) dont host the docker.img vdisk on the unraid array To diagnose high IOWait, during a period of unresponsiveness, ssh in and open top and look for the wa: statistic and see if this number is high or low. If you cannot access the console from the webgui, you can try to SSH into the system, otherwise you may need to connect a monitor/keyboard to the server itself and run it there. If none of this works, you need to start your own topic and post your diagnostics.

You can try and download UFS Explorer which is a data recovery software tool. Not sure if the trial lets you mount btrfs disk/pools but it doesn't cost anything to try. You'd need to purchase the software to actually recover the files.