liquidate

Fwiw, the USB Manager seems to work. The VM settings page still shows my USB devices unselected, but I instructed the USB manager to attach to HA on VM start. When I reboot and start the array, the USB device is passed through correctly. Thank you @Espressomatic!

You are not the only two, I just read the thread also hoping to get this solved. Will try the USB manager plugin to see what that does.

It appears that something may have gone sideways with the latest Ghost update. Getting this when updating, been working without issue for years: Pulling image: ghost:latest IMAGE ID [1073305513]: Pulling from library/ghost. TOTAL DATA PULLED: 0 B Error: manifest for ghost:latest not found: manifest unknown: manifest unknown

Thank you, I should have remembered this basic step! I've enabled syslog (pointing it to my cache drive) and I'll try another upgrade over the weekend.

I will, but first I need to access my cache drive. I've reverted unraid back to 6.8.3, and I can see the appdata folder when I mount the nvme in unassigned devices (in readonly mode currently). I need to access one of my dockers before I do anything else. Is there anything I can do to mount the cache and get my dockers started again?

I have a problem where unraid is hanging on builds greater than 6.8.3. Over the weekend, I decided to try my luck to see if the new 6.10 RC2 would make a difference. Unfortunately, I woke up to the server hung again (the login screen will appear, but you can't actually log in). After force rebooting the system, my cache drive is unmounted and currently in unassigned devices. I really need to get this back online so that I can access my dockers. Does anyone have any suggestions or pointers for my troubleshooting steps? Thanks! tower-diagnostics-20220117-0725.zip

Hi @corgan Were you able to get this to work? I'm having similar problems. I'm sure it's user error on my part, but when I create the admin user from the unraid console, it appears to be applied to a different docker, and I need to start this extra manictime docker up via the console too. Is there a way for me to create this admin account on the docker I install from apps/dockerhub? Thanks!

Thank you for your help! I've run scrub multiple times and deleted the files that were reported in the log. It appeared all of the corrupted files were in my unifi-controller appdata folder. Once those were all deleted, and scrub returned no errors, I tried to delete the entire unifi-controller app data folder. While windows reported the folder was deleted, it still existed. I then put the array into maintenance mode and the file system check came back with errors. I ran a repair, did another scrub, deleted the unifi-controller folder (for real this time), and everything seems back to normal. I am concerned about upgrading this system to 6.9.2, given the hangs that occurred with 6.9, but that's another issue and not a pressing matter given 6.8.3 runs rock solid for me.

Thank you for the response! Could it be the instability I saw when I updated to Unraid 6.9 from 6.8.3? I found that Unraid would just hang on me, so I downgraded back to 6.8.3 and things have been solid since. What steps should I take to retain my data and fix this issue? I do not want to loose my bitwarden or other docker appdata.

I'm getting the following error when I attempt to recreate my docker image (by deleting the current image): Apr 29 21:03:59 Tower root: ERROR: unable to resize '/var/lib/docker': Read-only file system Any suggestions? I was getting 403 errors trying to start one of my dockers, now I can't start anything. tower-diagnostics-20210429-2111.zip

I'm curious, why have this limitation/restriction? I ran into the same permissions issue but I don't see this behavior in similar dockers (nzbget, syncthing, etc) that create and access files on my public shares. Edit: Changing the UMASK to 0022 fixes this permission issue. The project as outlined on github uses 022 as the default, but for some reason my docker was set to 044 which was too restrictive for my use case.