itimpi

That is how one refers to a local file in URL format. Whether local files are allowed can I believe sometimes depend on security settings in the browser.

Use the instructions here as mentioned earlier.

No. If you use New Config then you can no longer do a rebuild.

You can now set Apps to be primary storage, and set Secondary storage to None. After doing that make sure you have Settings-Global Share Settings->Exclusive Shares enabled so that you get maximum performance on the 'system' share since it is all on the 'Apps' pool (may need to reboot to get this activated). You also want the 'appdata' share to be set up in a similar way. Another point - if you have not already done so make sure you set a Minimum Free Space on the 'cache' pool to avoid it filling up too far and causing problems.

It does take some time. Around 1.5 hours per TB is quite typical, and progress only gets updated in 10% intervals.

The fact that the disk is emulated means that a write to it failed for some reason so New Config is probably the best way to proceed ad you would lose any data written since it was disabled. Instead since the emulated disk seems to have mounted fine you should ne rebuilding it. If you think the disk is healthy then follow these instructions to do the rebuild. In terms of checking disk health, the best way is to run the Extended SMART test (which the diagnostics show has not been done). If that completes without error the dtive is normally OK and the write failed due to an external factor.

If you have the special case of only 2 drives in the array (1 data + 1 parity) then they will be mirrors of each other so it does not matter. In the more general case of 1 parity and multiple data drives then the parity drive will be the one with no mountable file system.

You have to simulate a drive failure to trigger the rebuild stop array Unassign disk3 Start array to make Unraid ‘forget’ current drive. At this point disk3 will show as being emulated. You can browse the contents of the ‘emulated’ drive to check it looks OK as what you see at this point is what will end up on the physical drive after it is rebuilt. If you do not think the contents look correct get diagnostics and then post them here to get advice on how to proceed. Stop array Assign disk3 Start array to rebuild disk3.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one 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.

Are you booting UEFI or legacy mode? If UEFI then no more to do, but if legacy mode then you need to run makebootable.bat in Administrator mode.

Unlikely to be the ZFS drives - more likely a docker contaoiner. You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one 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.

More than that - you need to stop the docker service as well - not just the containers.

D That typically indicates an issue either with the cabling to the drive or a power issue rather than anything wrong with the dtive itself.

Always worth trying rewriting the contents (especially the bz* type files) as that surprisingly frequently seems to help.

If using SATA->SATA splitters then no SATA connection from the PSU should be split more than 2 way. If using Molex->SATA you can normally get away with 4-way.

This would be the approach. Note that sometimes new cables are not needed - existing cables might just need seating more firmly. The other possible issue relates to power to the drives. Do you by any chance use power splitters with the drives - if so give some details.

At the moment the parity already appears it could be messed up so will need rebuilding (or at least checking) anyway. I think the key point at this stage is to identify if you have an identifiable external issue such as cabling or power since passing the extended SMART test normally mean the drive is healthy.

@DavidGoehler I would start by plugging the flash drive into the Mac and checking it can be read there. If it can then it might be worth downloading the ZIP for your release and extracting all the bz* type files overwriting the ones on the current flash drive. This can sometimes fix a problem where it is due to not being able to read one of the standard system files from the flash drive. It would also give you a chance to backup the 'config' folder from the existing flash drive.

Your description makes it sound as if it could be the NVME after all that is limiting speed. Have you done local speed tests on it?

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

Something strange going on as the times in the syslog file in the diagnostics precede those in the syslog_previous file which should not be possible. I suggest you reboot the server and then post new diagnostics if the problem is still occurring.

It can as mentioned in the link by using the ‘diagnostics’ command.

If you can ssh in then you can both reset the GUI and initiate a powerdown. You can then (probably more important) also collect the diagnostics to help with identifying you had the problem in the first place. The powerdown can be initiated via the 'powerdown' command. I do not have the command to reset the GUI to hand but you should be able to find it by googling or someone else could answer here. You can normally also initiate a shutdown by a quick press on the power button.

Never heard of a problem like that using the built-in file manager. Difficult to see how it happened as source files should not be removed until destination file has successfully been created. Having said that your syslog is full of hundreds of messages of the form: Jun 27 13:26:15 NAS nginx: 2026/06/27 13:26:15 [alert] 13542#13542: worker process 160061 exited on signal 6 Jun 27 13:26:15 NAS nginx: 2026/06/27 13:26:15 [alert] 13542#13542: worker process 160121 exited on signal 6 Jun 27 13:26:16 NAS nginx: 2026/06/27 13:26:16 [alert] 13542#13542: worker process 160122 exited on signal 6 Jun 27 13:26:17 NAS nginx: 2026/06/27 13:26:17 [alert] 13542#13542: worker process 160129 exited on signal 6 which I assume must relate to the issue you saw, but I am not sure how.

Looks like it is having trouble reading the flash drive. I suggest you try putting the flash drive into a PC and see if it can be read there. If it can then I suggest downloading a zip copy of the Unraid release and extract all the bz* type files overwriting the ones in the root of the las drive as this sometimes fixes the type of issues you are seeing.