trurl

You should always make sure your plugins are updated before updating Unraid.

Remove Community Apps and install the latest version.

You also have to set the Remote syslog server field. If logging to the same server, you can put localhost.

You can have a single drive, but you won't have any redundancy until you have at least 2 drives. Normally, HDDs go in the Unraid array, with one disk as parity.

Lots more detailed information in the Unraid Docs linked at the top of the page.

Or just ask here if you have some specific questions.

Your appdata and system shares have files on the array. These files are usually always open. You have these shares configured to put new files on cache, but existing files on the array won't be moved because there is no Mover action because there is no Secondary.

Also, nothing can move open files so you have to disable Docker in Settings before these can be moved.

config folder on flash contains all of your configuration, and is all you need to get all of your configuration going again on a new install.

config/super.dat is your array assignments, config/pools folder is your pools.

config/pro.key is your license. After you boot you will have to do a license transfer to the new flash in Tools - Registration.

Changing the boot device | Unraid Docs
The boot device is critical to your Unraid server as it stores the operating system, configuration files, and license. (For typical USB installs this is a USB flash drive; with internal boot it is ano

Your go file appears to be empty, even though it seems to be the correct size. Put the stock go file in your config folder.

In binary this is
1000000000000000010000000000000000000000

If you flip that most significant bit it is a more reasonable
4194304 in decimal
= 4 x 1024 x 1024
= 4 MB


Do memtest before anything else.

Your pool (named "pool") doesn't exist, and appdata is configured to only use that pool. Also, "pool" might not be a good name for a pool.

Your system share is on the array, better if it were on a pool.

USB not recommended for assigned disks for many reasons.

I have reproduced this behavior on 7.3 by using the command line to create a top level folder on disk1. It results in a new share. The settings for that share show Primary:cache; Secondary:none. However, no .cfg file is created for that share. And, if I create a folder in that test share, it is created on cache.

This is not the way it is supposed to work.

Memtest immediately.

More likely a problem with cache, since /mnt/user0 was mounted, but /mnt/user was not mounted.

Not only has it created a user share, but it is going to create another user share next time it runs, named ab_whatever_date_time.

What is the Backup Destination you have set in the plugin? You must have told it to store it directly to a pool or array disk.

User shares are simply the combined top level folders on array and pools. If you create a top level folder on array or pool it is automatically a user share named for the folder.

Backup Destination needs to be a path to a user share you create for the purpose, or a subfolder of a user share you already have.

Where do you see this?

The onboarding wizard is new for 7.3. There is another wizard for setting up internal boot.

https://docs.unraid.net/unraid-os/release-notes/7.3.0/#onboarding-and-internal-boot

Since you have dual parity you can rebuild both at once.

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

Did you rebuild after you made that change? Parity will remain disabled until it is successfully rebuilt.

Parity doesn't contain any of your data of course. It just allows the data from a missing disk to be calculated from all the other disks. And format doesn't completely wipe out every trace of the original disks data from the array. It just writes an empty filesystem to the disk, and parity agrees the disk has an empty filesystem after that.

But maybe if we make it emulated and rebuild it from parity, even though the result would be an empty filesystem, all the rest of the bits from the original data would still be there and UFS Explorer might be able to recover some of it.

Try refreshing the page

Looks like your Downloads share is fixed now.

I guess you will have to delete media.cfg file in config/shares on your flash drive, then apply settings to your Media share.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

What could it hurt? If the flash drive can't be reused you will have to do a license transfer.

Might be some useful "flash drive" research for you to do here:
https://forums.unraid.net/topic/196967-unraid-boot-device-guide-usb-and-nvme-hardware-selection/

Also, Unraid v7.3 (currently beta) allows for "internal boot", which doesn't require a flash drive:
https://docs.unraid.net/unraid-os/release-notes/7.3.0/#onboarding-and-internal-boot

USB not recommended for assigned disks for many reasons.

This sounds like a power issue.

Looks like your flash drive is read-only. Put it in your PC and checkdisk. Or reformat and restore from your flash backup.

What I've noticed examining some diagnostics is xfs img is named docker-xfs.img. So maybe both exist as separate files.

Disks and pools are mounted, user shares are not. But something is trying to access user shares, perhaps too early. Perhaps some rogue plugin, you have a large number of plugins.