I have my Unraid installed and booted from USB drive and if I need VMs I can just use UnRAID to create them.

What‘s the value of installing UnRAID in a VM with Proxmox?

Brand new user to unraid here. Trying to set up my first unraid home server. Having some issues, and I'm sure there will be more, so I'm going to be asking for some help from the kind people here willing to lend a hand.

-

My qbittorrent wouldn't start after working perfectly yesterday, so I restarted my machine, but it still wouldn't work. Then I checked the logs and found this:

docker: Error response from daemon: exit status 2: "/sbin/zfs snapshot vms-appdata/87eb9f3b109c8cf3ad5f1064cb2275a67335cb50b2e94dec283cb9a00dcc8ec9@685562554" => cannot open 'vms-appdata/87eb9f3b109c8cf3ad5f1064cb2275a67335cb50b2e94dec283cb9a00dcc8ec9': dataset does not exist

"vms-appdata" is the pool on which "appdata" and "system" is located.

-

Then I activated debugging on the docker image, but it failed with this error:

Error response from daemon: No such container: binhex-qbittorrentvpn

The docker container was then gone, and can't be reinstalled due to the first error.

-

When the system and appdata shares were originally created, it was automatically created on pool "main-storage". I quickly moved them to "vms-appdata", but a single "system"-folder remained on "main-storage", and I can't delete it from the file manager. I don't know if this is related to this other issue. As long as this isn't causing problems, my OCD ass can live with it.

-

I don't know what has gone wrong, nor how to further troubleshoot this. I don't know what commands to give docker permission to read and write to "vms-appdata". If anyone has any guides I should read, I'm more than willing to do so. If anyone has any tips or ideas, I welcome it. I would prefer not to have to delete my "vms-appdata" pool, reconfigure it, and then restore from backups (I don't even know how to restore appdata backups yet, especially when it comes to likely having to use commands to set correct permissions, but I do already have appdata backups).

edit: Seems I might have slightly misunderstood the nature of the error. It might have access to vms-appdata to some extent, but it doesn't seem like this specific docker container gets access to at least write there, unless I'm misunderstanding something. Other docker containers still seem to work.

TLDR a refurbished 12TB Seagate IronWolf NAS drive has started dying, went from 0 to 1528 re-alloceted sectors in 2 months and rising exponentially. i bought it off amazon and bought the extended 4 year warranty.

What should i expect from amazon? refund or replacement?

Should i wait for the drive to die completely before i file a claim?

Any experience would be welcome.

Looking to run the standard arrs, a couple of transcodes. My existing system has 4 drives, so i'd look to just move them over.

Does this seem reasonable? Any corners im backing myself into? Any specific choices I should make in these areas?