itimpi

It should work. Unraid never relies on the sdX designations as they can change between boots - it just relies on the drive serial numbers.

Unraid does not install to a drive in the traditional sense - instead it installs fresh to RAM on every boot from the archives on the flash drive. A flash drive that is 2GB or larger is enough.

I would not be at sure of the lifetime of USB sticks used as part of an Unraid array and performance might be a limiting factor. However there is nothing I can see from a technical perspective that should stop it working.

Do you have the shares. In question set to be exported for SMB? The default is no which means they are not visible on the network,.

That is the max size of the rootfs which is normally set to half the available RAM. If it ever gets full then Unraid will start crashing. Start by doing ls -l /mnt from a console session to see if there are any unexpected entries at that level. You can then use a command of the form du -sh /mnt/path-to-investigate to look at the size of any unexpected folders

CRC errors never disable a drive by themselves - it takes a write failure to do that. They most frequently indicate cabling issues (either SATA or Power) and that could lead to a write failure.

The parity drive shows quite a lot of reallocated sectors so is a bit suspect. Which was the other drive that had a thumbs down? You can acknowledge the SMART error by clicking on the icon and then Unraid will only tell you again about if it changes.

It may be more convenient to set this up in a VM as 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 would expect it to be in the UD plugins folder

It can be either, particularly if you are using splitters on the power cabling.

When you checked the cabling did you also check the power cabling (and avoid the use of splitters if possible)? That disk failed an extended SMART test so that is normally a very strong indication that it should be replaced.

Have you checked that Settings->Unassigned Devices->SMB Security is not set to No as this would stop it being visible on the network? If so you probably want the 'Public' settings.

Have you tried rebooting yet? There seem to be a lot of processes running of type [ffmpeg] <defunct> that are not normal. FYI: You have mover logger enabled - you probably do not want this unless you are investigating a mover related issue.

You can get the diagnostics zip file either via Tools->Diagnostics in the GUI, or by using the 'diagnostics' command from a console session. That zip file contains the logs, the SMART information for all drives plus a lot of configuration information to help with diagnosing problems.

A rebuild always puts back the original file system.

I guess emulating sectors is probably the easiest way to think about it in this scenario. At the beginning of the rebuild all sectors are being emulated, but as the rebuild progresses the number of sectors being emulated is decreasing. For simplicity sake Unraid will only remove the emulated text in the GUI when the rebuild completes and no sectors are now being emulated.

Do not quite understand what you mean by this. There is no concept within the plugin of ‘old’ notifications that need clearing as they are simply generated in real time as appropriate and then no record kept within the plugin of this happening. Are you talking about clearing notifications at the Unraid level?

You can set any array drive to be ZFS and then format it just like you would for any other file system type on the array. Note that when used in the array each drive is a single drive zfs system.

The rebuild process knows what sector it has reached (it works serially through the sectors on the disk). If you write data that goes to a sector earlier than the point reached by the rebuild then it is written to both the physical drive and parity updated accordingly. If it is after that point then just parity is updated so that when that point in the rebuild is reached then the correct data can be written. FYI: Although you can write to the drive during the rebuild process that will badly degrade performance of both write and rebuild while they are running in parallel due to disk contention.

@Ezekial66 FYI: The process is covered here in the online documentation accessible via the Manual link from the Unraid GUI or the Documentation link from the forum

A restore is a sector level process - not a file system level process so it is putting back what it thinks should be on each sector based on the emulated drive. Neither parity or rebuild are aware of the meaning of the contents of the sectors. The drive will stay flagged as 'emulated' until the rebuild process completes. In theory it should be possible to run xfs_repair on the emulated drive while a rebuild is happening as long as you have the array running in Maintenance mode. If you do not then I would think it is easier to let the rebuild finish and try the xfs_repair on the rebuilt drive.

Unraid pulls its data from drive SMART reports.

The New Config is about resetting array drive assignments as 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..

Have you made sure you have no plugins that are incompatible with 6.12 and break the dashboard as mentioned in the release notes? A quick way to check is to boot in Safe Mode and see if you still have the problem.

A rebuild will put on the replacements disk exactly what is showing on the emulated drive before starting the rebuild. If the emulated drive is showing as unmountable then the rebuilt one will be as well. You do not create a new file system on the disk being rebuilt because the rebuild process is going to restore exactly what was on the emulated drive. You can attempt a repair on the emulated drive before starting a rebuild. At that point you still have the original disabled disk unchanged in case it was just a glitch that caused it to be disabled which gives you extra recovery options.