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.