MowMdown

Well it's hard to track down what's going on due to the massive log spam, there are three whole log files just full of this alone: Jan 20 07:00:06 Linc sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl --scan Jan 20 07:00:06 Linc sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Jan 20 07:00:06 Linc sudo: pam_unix(sudo:session): session closed for user rootWhat do you have running?

The horizontal scroll bars? You cant.

Weird, blkid /dev/nvme0n1p1 should have output something like UUID="xxxxxxxx" UUID_SUB="xxxxxxxx" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="xxxxxxxx"

Please post your diagnostics. Since you're using zfs, make a snapshot of the habackup dataset, this will prevent unraid from destroying the dataset when mover operation moves the data to the array. This may help. Otherwise this is one of those NFS things that has plagued unraiders for some time. Im not sure if there was ever a fix. Someone else would need to chime in.

Backs up how? Also it never hurts to post the unraid diagnostics even if it doesn't seem relevant to the question. Please attach those.

So the data that is on the disk you want to remove will remain on the removed disk? If that's the case, with the array stopped, click on TOOLS > New Config > preserve all slots and confirm you want to do this. Back on the MAIN page, set the slots of the disk(s) you want to remove to "unassigned", start the array in maintenance mode to make it permanent and then shut the system down to remove the disks. The data on those disks will remain. Once you reboot you will need to re-sync parity

you're missing the space between cd and /movies also the space is required to be between cd and the two dots. cd /movies but that will only work if movies is listed when you type in ls and press enter

Check all your plugins and scripts to see if any of them are configured to stop docker containers.

My suggestion is to boot into MemTest86 from the boot screen and run a memtest. I suggest for up to 24 hours or a failure, whichever occurs first. If a single failure is detected, you would be wise to replace the RAM. I noticed you're running an AMD CPU and would advise doing the following things: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Have you recently rebooted your system? Check the server uptime in the top right corner of the webgui. Based on what I see in the logs the server recently rebooted and if you didnt manually do this, this suggests the server is crashing. It would be likely a hardware issue.

Open the unraid console and type in ls /boot/config/shares you should see a list of your "share_names.cfg"\ Also please attach your diagnostics to your next post

Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Corruption detected! Free inode 0x8a not marked free! (mode 0x41ff) Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Internal error xfs_trans_cancel at line 978 of file fs/xfs/xfs_trans.c. Caller xfs_create+0x28e/0x310 Jan 19 11:42:21 UNR1 kernel: CPU: 5 UID: 99 PID: 459364 Comm: KIO::WorkerThre Tainted: P O 6.12.54-Unraid #1 Jan 19 11:42:21 UNR1 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Jan 19 11:42:21 UNR1 kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D43/PRO B660M-A WIFI DDR4 (MS-7D43), BIOS 1.N1 05/13/2025 . . . . Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0xd1/0x110 (fs/xfs/xfs_trans.c:979). Shutting down filesystem. Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Please unmount the filesystem and rectify the problem(s)Disk 9 seems to have corruption. Stop the array, put it in maintenance mode, click Disk 9 and run the xfs repair tool. Post the results.

you can use cd .. to move backwards.

Hmm... my last suggestion is to do some more advanced digging, you will need to enter the container console and use command line to manually browse through the path youve assigned to your media and see if you can see the files that way. Click on Console When the console opens you are inside the plex container, use ls to list the files/directories and use cd to change directories (commands you type in) First run ls to get the folders, then you can use cd /movies in my example to move into the movies folder, now you have subfolders so you will need to use something like cd /movies/HORROR to move into the subfolder. Once you're inside the folder where you expect to see the movie folders/files use ls to print out everything, and see what you can see. If you cant see the specific file you expect to be there we can start to rule out if it's plex or something else. Pro Tip: use can use the TAB key to auto-complete names when typing them in so like if you start cd /movies/H and hit TAB it will fill in the rest to make it -> cd /movies/HORROR (then press enter key to move into it) use ls to list out the next folders and continue cd /<name_of_next_folder> (replace with actual folder name)

You seem to be suffering from severe segfaults. There is so much log spam that the actual unraid syslog cannot be read. Reboot into MemTest86+ and run a 24hour memtest. (Note: If you get so much as a single failure, replace RAM)

Well the array lets you expand disk by disk. The only limiting factor is the size of the parity disk needing to be at least as large as the largest disk you use in the array. In your case it would be a 12TB HDD. (Parity is optional) Furthermore data is not striped meaning each disk is an independent filesystem. A failed disk does not wipe out the entire array unlike a zpool which would be entirely lost if more than a single disk fails in a raidz1 configuration. https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/configure-your-array/ https://docs.unraid.net/unraid-os/advanced-configurations/optimize-storage/zfs-storage/ Ultimately there is no wrong answer, setup your disks however you please.

As Trurl said, in plex, if you look at your list of "libraries" did you add a separate library for each of the sub-genre folders you have or did you just add one single library for the "movie" directory? This Or this

Ok well the mystery of two similar shares is solved. it's DOCUMENTS and DOWNLOADS... Both are 9 letters beginning and ending with the same letters. Diagnostics must have confused these two because of that. Can you share how you setup your plex movie library inside plex? Do you have a single movie library or did you add a movie library for each of your genre categories like a separate one for HORROR and MOVIES?

What does smartctl -c /dev/nvmeXnX report (replace X's with the appropriate disk numbers) Edit: nvm youre talking about C- states not the reported wattage... my bad

No, you dont need server grade hardware to run unraid. I run WD Blue SATA SSDs for my cache pool. However I have them running in mirrored pairs for redundancy if/when one of them fails. Ideally you want components rated for your expected workloads but the only thing that may happen is you wear the drive out sooner rather than later. Move the data ASAP or you risk losing it entirely. That drive is about to die. Your last concern should be whether or not the other disk is server grade.

often those things need active cooling directly on the card if not installed in a server chassis with high airflow. Using thing cards in normal consumer PC cases definitely requires them to have a fan blowing directly on them

You may want to look into the "AutoHeal" docker container.

Yeah what threw me off was his post seen below, windows is making movies lower case when HORROR is upper case and his share is upper case as well... I must've skimmed over the diags. Youre right though, there isn't a lower case movies share. I still believe this to be a pathing issue within plex. The other way to check is to click on the plex icon, click on console and manually browse the movie share from within and see if the files are visible. It could also be a plex database issue as ive seen plenty of times these get corrupted/need repair.

Can you not stop the array and edit this: to say DHCP?

@Mark Holwill Do you have all your movies under /mnt/user/MOVIES because if not plex wont see them. With all your screenshots it's not abundantly clear what exact shares and paths you are using. I can only suggest that you double check that ALL your content falls under a single path otherwise you need to add more paths to plex. Also keep in mine capitalization matters as linux is case-sensitive. /mnt/user/MOVIES and /mnt/user/movies are NOT the same in linux. Physically go to the unraid shares tab, click on the little blue Box/Arrow next to MOVIES and see if you can see all your files under that share. if not, plex wont either.