curtis-r

Now I'm (more) perplexed. I uninstalled 2 modules I wasn't using, uninstalled the CodeProject Docker app entirely. Manually deleted through MC the residual CodeProject Cache folder. Restarted unraid. Now when I reinstall the CodeProject Docker, it not only shows installed the Module I can't seem to update, but the other 2 modules I had uninstalled. This is on a fresh install! Where is it getting this ghost data from?

I was able to update the Docker image last night via the unraid/docker page, by clicking 'update' in the Version column, but I can't update modules (through the CodeProject GUI). This github link from an ealier post describes my issue exactly but claims it was fixed in a release last October. Anyone else having trouble when they try to update a module?

Wow, what an ordeal. But I'm so close I can taste it. EDIT: SOLVED! While array stopped, I used this to format the original cache drive (using 'i' in my case for 'X', but to others, make sure you have the correct drive letter) blkdiscard /dev/sdX -f Then started array & clicked to format the cache drive pool. Then used MC to restore the backed-up cache data. Rebooted (default mode) Cache shows green balls & proper size, but VM says "Libvirt Service failed to start." and Docker "Docker Service failed to start." Diagnostics attached. EDIT: Turned off Settings/VM, then through MC deleted libvirt.img, and copied it again. Same goes for docker.img It they started and all is back and running!!! Thank you for your help. Still wonder what went wrong when I added the cache 2 drive, but I jsut want to move on. tower-diagnostics-20231219-0853.zip

Ok, some good news. After much trial and error, I was able to get MC to copy all the cache to an array disk. I guess I should format the cache next? And do I just use MC to copy back the cache data?

Ok, did a hard reboot. Forgot to mention that it won't boot unless in safe mode. It hangs on Starting Samba (see attached photo). Again, tried to Start, but gives the BTRFS error of "no space left". Tried your instructions, but there is no indication anything worked. mkdir /temp mount -o degraded,usebackuproot,ro /dev/sdi1 /temp I decided to go the copy Cache, format, restore route. Tried copying with MC but would always freeze at 2%. Not sure if there is another way to copy the cache because it luckily seems like it's still all there. Can you copy without mounting? EDIT: When I removed the new/secondary cache drive, changed the pool to 1, and started the array, it starts. It says the cache is "Unmountable: not mounted". So I then ran the above commands and they went through, but still says unmountable.

Correct. cursor is not back. Nothing changed on the Main tab so I tried to reboot, but the reboot button, nor does "reboot" command-line work, and I'm remoting in from work, so I'll try a hard reboot when I get home.

Ugh, sorry. The instructions were certainly clear. So now it appears to be working since nothing has returned yet. Should it take a while?

mkdir /temp worked but mount -o rescue=all,ro /dev/sdX1 /temp returned mount: /temp: special device /dev/sdX1 does not exist. Also mount -o rescue=all,ro /dev/mapper/sdX1 /temp returned mount: /temp: special device /dev/mapper/sdX1 does not exist. Do I need the array in a stopped state to do this?

Ok, will try mounting, backup, & reformatting when I get home, and will report back. Thanks for your help!

Here you go: root@Tower:~# btrfs fi usage -T /mnt/cache Overall: Device size: 223.58GiB Device allocated: 111.79GiB Device unallocated: 111.79GiB Device missing: 0.00B Used: 83.79GiB Free (estimated): 138.19GiB (min: 138.19GiB) Free (statfs, df): 111.79GiB Data ratio: 1.00 Metadata ratio: 1.00 Global reserve: 226.67MiB (used: 0.00B) Multiple profiles: no Data Metadata System Id Path single single single Unallocated -- --------- --------- --------- -------- ----------- 1 /dev/sdi1 109.78GiB 2.01GiB 4.00MiB 1.02MiB 2 /dev/sdb1 - - - 111.79GiB -- --------- --------- --------- -------- ----------- Total 109.78GiB 2.01GiB 4.00MiB 111.79GiB Used 83.38GiB 422.45MiB 16.00KiB

That worked. Thanks. Hopefully you can make sense of it. BTW, here is how it still looks. syslog.txt

I decided to add a additional identical cache drive as raid protection for cache 1. After adding the drive and rebooting, I selected the new drive to 'cache 2'. Once I clicked 'start', it just hung on 'starting...'. After 10 hours I decided to reboot. The array still wasn't started, but now 'cache 2' was also green ball. I clicked start, and again, just hangs on 'starting...'. I can access my unraid data across the network, including the cache drive, but the array hasn't started, so no Docker or VM's. Shares are working though. Did I do something wrong? I should also note that I muddied things but upgrading the CPU at the same time, and thus I reset my BIOS to factory. I made sure to turn back on virtualization. I don't think there are any other BIOS settings that could have led to this problem, but figured I should mention it. Still wating after a few minutes for diagnostics to download...

Yeah, I was afraid of that. Thanks.

My parity disabled again & the rebuild had parity disk errors, so I swapped out with a new drive. Though that rebuild isn't finished (no parity errors), as the parity is 4TB larger than any other drive, I think it's done with scanning my existing drives, and there are 108 errors on disk5. Any thoughts on the problem (diagnostics attached)? Thanks in advance. tower-diagnostics-20230602-0800.zip

Got it. Rebuilding... Thanks.

Though I'm not aware of any notifications, I just noticed my parity drive is disabled with the red 'x'. Mouse-over displays, "Parity device is disabled. Click to spin up device." Clicking starts the progress arrows, but when complete is still disabled. Then the mouse-over says, 'Click to spin down device'. I rebooted earlier, so hopefully there is something useful in the diag (attached). A SMART short self-test was good. Thanks in advance. tower-diagnostics-20230129-1104.zip

Though I had it working properly for while, I stopped using WOL when I started running docker apps on an SSD. All my mechanical drives spin down after 15 minutes, so I doubt there is much power used.

I can't answer why, but when I tried the Docker last year it did not have Supervisor, so I changed to the VM route which does. Been using it perfectly ever since. There was a good YouTube video or two that walks through the install.

Wish I could help, but I followed the VM YouTube tutorial & all works.

@ghost82, you are correct! I hadn't updated this post since I figured that out a day ago, but I actually just rebooted unraid all-together, and I could then verify the USB-serial through the Home Assistant VM. Thank you!

Ended up having another (working) USB-serial device laying around, but now have a new issue: Device shows up in unraid terminal. It's the PL2303 It shows up in my Home Assistant VM settings: But it doesn't show up within my Home Assistant VM terminal: Any ideas?

I used JuanMTech's YouTube video to setup the VM, but prior when I was trying Docker I followed Spaceinvader One's post which shows how to setup remote access. I don't have my own domain so used duckdns.org. As for https access to the HA VM, I didn't try anything unraid-based, but from within HA used an add-on. I'd tell you the add-on but ironically, for the first time, Supervisor is not loading remotely (but HA core is running fine). I'm pretty sure it's nginx. As for memory usage, that's a bit surprising. I think I only have like 8GB of RAM on my unraid & haven't seen any issues running HA, Plex, and a couple of minor Dockers. I only allocated like 2GB of RAM to HA.

Though I eventually got Docker HA working with Swag through a lot of trial and error, it was all for nothing because I moved to VM so I could have Supervisor (which I highly recommend). Not sure you should waste your time with HA in Docker IMO.

Ok, so sorry for wasting everyone's time. It must be something with my USB-serial device, because I just tried a USB mouse and it shows. Win10 also has some issue with my USB-serial device. Will get another one. Thanks for the effort. EDIT: found a different USB-serial laying around and it shows up!

Let me experiment with a completely different USB device and report back. Thanks.