itimpi

Not in place! To encrypt a disk it needs to be formatted as encrypted which wipes any existing content. You are therefore going to do a lot of copying to get your array to an encrypted state. it is worth checking that you really want encryption and it is worth the hassle? If you later have problems with the array then encryption can make it more difficult to recover without data loss.

If you are going to do a New Config then I would think the easiest thing to do is: do the New Config and select the option to keep current assignments Unassigned the current disk2 Assign the replacement disk in as disk2, if you want it encrypted set the file system for disk2 to say this start the array to commit the new assignments format the replacement disk2. You can then mount the old disk2 via Unassigned Devices so you can copy the data back to the new disk2. This avoids the need to ever have a disk11 in the array which will later need removing.

You need at least one spare drive as all drives in the UnRaid array need to be partitioned/formatted by Unraid. unassigned Devices might help with the copying of data onto the array but it does not avoid the need for the getting a drive into the UnRaid array before copying any data over.

You said that you were updating so I assume that was to 6.9.2 ? The reason for the approach I suggested is that I have seen that in the past occasionally that when updating via the GUI the new files for the new release seem to not have been written successfully to the flash resulting in the symptoms you got and rewriting them outside the update process gives you a good copy.

OK with that information the behaviour you are seeing is expected. With the “High Water” setting on the share that disk will get used until 3TB has been written (the next switch point since your largest data drive is 6TB). More detail on how high-water works can be found here in the online documentation accessible via the ‘Manual’ link at the bottom of the Unraid GUI.

OK. Perhaps I need to do more investigation into why I was having problems with XFS disks from UnRaid. I guess I should also test with BTRFS formatted disks from UnRaid to get a more complete view. I like the Paragon software so will be happy if I can get it working well with UnRaid formatted drives.

It is possible, but without more information it is impossible to be certain what is going on. It will depend on the names of the files you are putting on the array, the shares they belong to and the settings for those shares.

Just for interest which file system were you using? I have that software installed on my Windows system and it is recognising my XFS format drives from Unraid, but can only show the top level folder on the drive! I have a bug report outstanding with Paragon but they do not seem very hopeful they can resolve what is going wrong as they have offered to give me a refund (which I have not taken as the software is handling ext4 format drives fine for me).

I would suggest you try downloading the zip file for the release and then extract all the bz* type files over-writing those on the flash.

Has anyone asked in the Nerd Pack plugin support thread whether this is a package that can be added? I have no idea if it can be installed easily as a free-standing package (and thus suitable for Nerd Pack) or whether there are other requirements that would make this difficult.

You should definitely try turning off XMP until you have your server in a stable state. The problem with any over-clocking is that it is impossible to predict with any certainty when it might cause a failure regardless of tests you do in advance. it seems that servers are more prone to this sort of issue than desktops, but I suspect it is just more noticeable as they tend to be left running 24x7.

Yes

Reiserfsck checks can take a long time (many hours) particularity with large disks, with the only sign of activity being fact that the disk is still being read.

Not a direct answer to your question, but would it not be easier to by-pass this issue by running the Plex docker container on your Unraid server as you could then map the media through directly without using any shares?

The memtest supplied with Unraid will not work when booting in UEFI mode. You can get one that will from memtest86.com

OK, was just wondering as that might have affected any suggestions for recovery. Never like it when the superblock cannot be found.

Not so good. Is the disk also disabled (with a red ‘x’) or not?

That looks good. Running without -n and (if requested) with -L should fix things.

This would not achieve anything and might even be counter-productive if a drive is reading unreliable. Handling of unmountable disks is described here in the online documentation accessible via the ‘Manual’ link at the bottom of the Unraid GUI.

I suspect that the files are actually on an another drive. Note that the /mnt/cache/appdata location is part of the ‘appdata’ share which can be referenced by /mnt/user/appdata, but this latter version also includes any ‘appdata’ folders on the main array drives.

There is normally a BIOS setting that allows you to operate without a keyboard. Assuming you want to run headless then you can use a "Dummy HDMI plug" to make the system think a monitor is connected.

There is comprehensive documentation accessible via the ‘manual’ link at the bottom of the Untaid GUI. All the information you need should be in the Storage Management section.

Did you actually run xfs_repair without -n and with -L? All the examples of the xfs_repair output you gave earlier indicated that -n had been used so no changes were being made. The xfs_repair is normally very fast - just a few minutes. Despite the ominous sounding warning about the -L option it virtually never causes data loss, and in the rare cases where it does it only affects the last file being written.

Something strange going on - the syslog in those diagnostics is the same as the one in the earlier one? Since you can get to the console maybe you need to directly get the current syslog from /var/log/syslog via the console to see if it is different.

If the drive is no longer showing as unmountable can you see any contents? Just guessing as you seemed to have missed the attachment you mention.