itimpi

You will need to repeat without the -n option for anything to be repaired (and if it asks for it adding the -L option).

Sounds as if you are falling foul of the behaviour described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

I don’t have a fire stick, but have you tried seeing if it has a WireGuard VPN client option? If it does you could then make use of the WireGuard VPN server built into Unraid.

There are facilities like snapshot support, built-in trim support, snapshot send that only a few users will use, but for those they can be very useful options.

I would say the WOW effect is when it is used in a Pool as it gives you the performance that is often one of the frequent criticisms of Unraid. I disagree here. The Unraid type array is not going to go away - it is just going to become another pool type (probably in type 6.13 timescale). The Unraid array has advantages in terms of flexibility around using mixed drives so that will not disappear. At that point the need for the current main array being mandatory will be disappear and the primary/secondary storage types introduced with the 6.12 release will be able to use any combination of pool types (including the current Unraid array type). You will be able to pick the combination of pool types that best suits your particular work mix.

The main reason you might want ZFS (or BTRFS) as s file format for disks in the array is that those file systems will detect bitrot.

The host path for the plex /config folder in your screenshot shows it is pointing to the wrong location.

The main advantage would be the same as if you converted them to btrfs - you would get bitrot detection even if not full protection. There are some other small advantages of zfs over btrfs so if converting while running a 6.12+ release that is the way to go.

Have you tried switching the view to the Advanced view (via the toggle at the top right)?

You could do this the other way around if you install the Parity Check Tuning plugin - it has an option to pause a parity check if mover kicks in while a parity check is running and resume it when mover finishes.

Really up to you. If you are familiar with rsync I would tend to use it as it gives you more control.

The progress only updates in 10% increments, and it will take something like 1-2 hours per TB.

Your original idea is what you need to do. The rebuild process cannot change the file system so going that route you would simply end up with a 10TB disk in ReiserFS format.

No. the idea is to check the emulated disk1 to see if it can be repaired so that the data on disk1 can be recovered. If that is successful that will be the time you put back a physical drive as disk1 so a rebuild can put the emulated contents onto the physical drive.

Maybe a silly question, but have you formatted the drives from within Unraid after adding them to the array?

Yes. The idea is to see whether the 'emulated' disk1 will mount and show data.

Ok - then having the parity drive as well is really senseless.

Agree, but it is only USB slots being used so should not affect any pools.

I would expect this to cause problems /boot is where the flash drive is mounted and Unraid expects to be available all the time it is running.

The log snippet you posted does not look ideal However it is still possible it is something other than the drive itself I would suggest that you: Take current diagnostics so we can see what lead up to that snippet. Power cycle the server to reset all the hardware Wen the server comes back take new diagnostics Post both sets of diagnostics so we can get a more complete view of what is happening You might want to also consider clicking on the drive on the Main tab to run an extended SMART test. That can take some time so from there disable spindown while the test is running. If the drive fails the SMART test then it definitely has a problem. Passing it is less prescriptive but indicative of a factor external to the drive itself.

You should post your system's diagnostics zip file so that we can see what is going on.

FYI: This is covered in more detail in this part of the online documentation.

Probably worth pointing out that the process will enable disk10, but it is the emulation of disk1 that depends on whether anything was written to the array after disk10 got disabled. Having said that sounds like it might be the only approach that might work for recovering the contents of disk1 if that physical drive has really completely died.

If you have Dynamix File Manager installed then you can use it to delete the files Go to the Boot device on the Main tab and then click on the folder icon at the far right to browse the flash drive.

Have you tried adding an & to the end of the command (as is used when launching emhttp in the background from the go file).