itimpi

Those two settings are not really related to each other. one controls grouping of items while the other controls overflow to another dtive. I do not see why a Split Level of 1 is not working for all new files if you are using High Water Allocation method. Unraid will not move files between drives, so if your previous settings scattered files then it is a manual clean up activity.

Not sure I understand you. That allows you to control exactly which disk any file ends up on so you are manually making sure files are not split when not wanted.

No - select from /mnt/disk1/media_Movies and move it to /mnt/disk2/media_Movies, etc. do not try to mix User Shares And Disk Shares in the same operation. Dynamix File Manager will not let you transfer between User Shares and Disk shares (or vice Vera) as this can lead to data loss if you are not careful.

Maybe you are misunderstanding Split Level? What is the path for the files for a given movie? If they are all in a folder named after the movie then you might need a split level of 2 to keep them all together. If you do have everything at the top level, then you want to be using the Highwater allocation method as that would keep files together except in the rare cases where a particular file reaches a trigger point so Unraid switches to the next disk for the next file. The Most Free allocation method would almost certainly put related files on different drives a lot of the time.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. it is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

The last diagnostics you posted showed that it appeared that disk1 is being emulated correctly. It should now be possible to simply stop the array; assign the accidentally formatted disk to the disk1 slot; and then Unraid will tell you that will cause the disk to be rebuilt with the contents of the emulated disk1 when you start the array. When rebuilding it is irrelevant what format the target disk is currently in as every sector gets overwritten by the rebuild process.

If you install the Parity Check Tuning plugin then even if you do not use its other features you will find that history entries get enhanced with that type of information.

Yes. With parity drives the only requirement is that none of them are smaller than the largest data drive.

You can do the rebuild in maintenance mode if you want to do this, but the array will be unavailable until the rebuild completes and you restart the array in normal mode.. Having said that Unraid will correctly handle any writes to the array during a rebuild process if you do it with the array started in Normal mode.

If you have 2 8TB drives then you can rebuild both disk2 and disk3 at once, but I thought you only had one 8tB drive at this point?

You cannot use 12TB disks for data until all parity drives are at least 12TB in size. However you need to decide if going forward you want 2 parity drives with only a small number of data drives. the simplest first step would be to simply replace the missing 8TB disk with the good 8TB drive and rebuild its contents. At that point you still have a disabled disk3 You could then use parity swap process to get parity1 upgraded to 12TB and replace disk3 with the old parity1 drive. At that point you should be back to having no disabled drives and with 2 valid parity drives. You could then decide how you want to end up to plan out next stages.

@Thomas Gunn FYI: Diagnostics includes SMART results for all drives so normally no need to include it separately.

You need to have all disks selected EXCEPT the one that was accidentally formatted. Just having parity is not sufficient.

You need to restart the array in normal mode to see if the disk now mounts OK and looks like it has all its data intact.

In which case the container does not need to access the gateway itself (it is just accepting inbound requests FROM the gateway) as long as you can access the container via the wg3 network remotely then that should be enough.

You can use Tools->New Config and just have the drives you want left assigned before starting the array. Easiest to use the "Keep Current Assignments" with the New Config tool and then just remove the drive you no longer want assigned before starting the array.

If you are referring to the disk that was accidentally formatted, then just not currently assigned to the array.

Does the docker need to be able to make outgoing connections to the internet, or are you just trying to secure it for purposes of inbound connections?

Which disk is it? Most of the time it is not the drive that is the issue.

You can add (or remove) parity disks in the main Unraid array at any time without affecting drives that have data on them.

That is no quite right - you need to have all disks except the disk that was accidentally formatted connected and then start the array so we can see if Unraid can emulate the missing disk using the combination of parity plus the other data drives. If so then the standard Unraid rebuild process can be used to restore its contents.

@Wzyss Perhaps you did not realise that a correcting check reports as "errors" every sector that it corrects. Any check run after that will report 0 unless a new error is found.

This is a bad sign for disk2: 197 Current_Pending_Sector -O--C- 100 099 000 - 50 so I think the drive should be replaced. When you add a parity disk then Unraid is unable to recover a failed disk unless all other disks can be read error free. There is also this: # 1 Extended offline Completed: read failure 90% 34760 1693889040 and we normally say that any drive that cannot pass the Extended SMART test should be replaced.

As long as the emulated drive is mounting OK then you should follow the standard procedure for replacing a disabled drive as documented here inthe online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

There is an icon at top right of the GUI for looking at the contents of the current syslog which is in RAM.