itimpi

Just to confirm that with those syslog server settings the persistent syslog will be written to the ‘Backup’ share and this should be posted after the crash.

It might be worth posting a screenshot of your syslog server settings so we can check that they are set correctly (many people get them wrong). It will also allow to tell you where its output is being written to (assuming you have correctly enabled the server).

The I put/outputerror message suggest the drive is going offline or something similar when trying to write to the drive. The diagnostics might give more information. Since it is an emulated drive I wonder if the error is elsewhere. It is also a bit strange as the previous attempts to fix the file system successfully read the (emulated) superblock.

I’ve often thought having a Format button against each drive/pool would be a good idea so you never accidentally formatted a drive you did not want to format.

Have you tried looking under /mnt/user/appdata/palworld ? That is the User Share path and should locate it regardless of what drive it is located on.

That is a quite normal result. Now you need to Zero Log

Simply changing the format and starting the array does not cause anything to be written to the disk. Therefore when you stop the array and change it back to XFS then on starting the array Unraid autodetect logic detects the disk is already in XFS format and therefore does not offer to format it. That is why the disk needs to be formatted twice, and only takes a minute or so to do the format so it is not as though it is time-consuming.

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.