RevelRob

Hi, I'm having trouble with "Failed to mount Home storage for root" errors: [2026-04-11 12:30:58] [INFO] MAINTENANCE: Unlocking Agent storage (RO -> RW)[2026-04-11 12:30:58] [WARN] Mnt Attempt 1 failed: mount: /usr/local/emhttp/plugins/unraid-aicliagents/agents: cannot remount /dev/loop4 read-write, is write-protected. dmesg(1) may have more information after failed mount system call.[2026-04-11 12:30:59] [WARN] Mnt Attempt 2 failed: mount: /usr/local/emhttp/plugins/unraid-aicliagents/agents: cannot remount /dev/loop4 read-write, is write-protected. dmesg(1) may have more information after failed mount system call.[2026-04-11 12:31:00] [WARN] Mnt Attempt 3 failed: mount: /usr/local/emhttp/plugins/unraid-aicliagents/agents: cannot remount /dev/loop4 read-write, is write-protected. dmesg(1) may have more information after failed mount system call.[2026-04-11 12:31:00] [WARN] STALL: Remount RW failed. Triggering robust repair sequence...[2026-04-11 12:31:00] [WARN] Btrfs Rescue: Processing /mnt/user/appdata/aicli-persistence/aicli-agents.img mounted at /usr/local/emhttp/plugins/unraid-aicliagents/agents[2026-04-11 12:31:01] [INFO] Btrfs Rescue: Success for /mnt/user/appdata/aicli-persistence/aicli-agents.img [2026-04-11 12:31:44] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:31:44] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:31:57] [INFO] startAICliTerminal called: ID=sz9cv0, Agent=gemini-cli, Path=/mnt/user/appdata[2026-04-11 12:31:57] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:31:57] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:32:01] [INFO] startAICliTerminal called: ID=temp-terminal, Agent=terminal, Path=/mnt/user/appdata[2026-04-11 12:32:01] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:32:01] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:32:08] [INFO] startAICliTerminal called: ID=temp-terminal, Agent=terminal, Path=/mnt/user/appdata[2026-04-11 12:32:08] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:32:08] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:35:21] [INFO] startAICliTerminal called: ID=sz9cv0, Agent=gemini-cli, Path=/mnt/user/appdata[2026-04-11 12:35:21] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:35:21] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:35:32] [INFO] startAICliTerminal called: ID=sfrv5k, Agent=gemini-cli, Path=/mnt/user/appdata/crafty-4[2026-04-11 12:35:32] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:35:32] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:36:26] [INFO] startAICliTerminal called: ID=temp-terminal, Agent=terminal, Path=/mnt/user/appdata/crafty-4[2026-04-11 12:36:26] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:36:26] [ERROR] ERROR: Failed to mount Home storage for root.[2026-04-11 12:43:04] [INFO] startAICliTerminal called: ID=sfrv5k, Agent=gemini-cli, Path=/mnt/user/appdata/crafty-4[2026-04-11 12:43:04] [INFO] Mounting Btrfs Home (RAM) for root...[2026-04-11 12:43:04] [ERROR] ERROR: Failed to mount Home storage for root. The plugin page looks like this: I'm using Gemini if that matters. Here's my settings page: Any help would be amazing. Thanks!

Hi, Last week (03-30) I had an error where Docker failed to start. I have attached the diagnostics from that date. I tried to fix it myself and decided I would delete the docker.img file and add them all back via the Community Apps Previous Apps feature which was a huge pain since I had a ton of containers installed. Today, I decided to reboot he server and when it came up, it shows "No Docker containers installed". So I first increased the image size and when that didn't work, I pulled the diagnostics and pasted it here. Can anyone tell what is happening? I'm hoping to not have to install everything again and even if I do have to, I am worried there is a bigger issue that is causingthis to happen. Thanks! tower-diagnostics-20260330-1203.zip tower-diagnostics-20260402-1644.zip

So by chance, I rebooted, and everything came up. Weird. Here is the new diagnostics in case there's anything wrong that is making this happen. Thanks again! tower-diagnostics-20250525-1114.zip

Hi All, I updated my machine from 6.12.1 to 7.1.2 yesterday (was holding off due to issues with nfs shares that appear to be fixed now). Everything was working until today when I noticed the gui would hang a lot. I performed a reboot from the gui and it came back up; however, it has been up for 35 minutes and the Arrays is still trying to start. My diagnostics zip is attached and any help would be greatly appreciated. Thanks! tower-diagnostics-20250525-1048.zip

Thanks for the quick reply! Ah, that's unfortunate. I'm going to try to reseat them all to see if that helps. I also have more RAM than I need for this machine so I could remove any that have failed. Also, the CPU utilization is screaming at 100% even though VMs and Docker is disabled for now.

Hi, I posted this Saturday and thought all was good, but I've been experiencing additional issues that are odd: I am in the process of preclearing a new replacement disk for the one that is failing. I've turned VMs and Docker off so that there are no additional resources being used elsewhere and to not stress out the parity drive that would e emulating the disabled disk. The problem is, after a period of time, the server becomes unresponsive with no gui loading nor am I ale to SSH in. Even sending an orderly shutdown via IPMI fails. So I have to power cycle via IPMI. It also runs extremely slowly now even after a reboot. I was on an older version (6.12.6) and updated to 6.12.8 to see if that was the issue. I ran a smart test on the new drive to see if it was the issue but it came back no errors. Can anyone tell me idf they see something awry from the diagnostics file I pulled just now after a restart and pre-clear start? It also took the diagnostics almost 20 minutes to generate. Thanks! tower-diagnostics-20240311-1035.zip

Haha. Nice. Too bad I have half a dozen of these to do this with now. Thanks!

Hi all. I have a disabled disk and am wondering if it looks like it is going bad or if something else is happening here. I already purchased a new drive that is pre-clearing in case it is bad but want to know for sure to avoid throwing it out. Unraid version 6.12.6 Thanks! tower-diagnostics-20240309-1403.zip

Thanks, it had already been replaced but I figured I’d see what the preclear plug-in said about it. She gone.

Only the cache pool; however, it is only CRC Error Count issues which I have read could be due to bad sata cables. I ordered replacement ones in which will hopefully help. I am rebuilding the dead drive with a replacement now. I was wrong about the dead drive being a Seagate barracuda by the way. It’s a Seagate ironwolf which should be better quality than a barracuda. Also, I ran a pre clear on the dead drive for fun and it just finished. Here’s the finished status preview: #################################################################################################### # Unraid Server Preclear of disk Z730W84C # # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 6 - Pre-read verification: [6:27:17 @ 129 MB/s] SUCCESS # # Step 2 of 6 - Erasing the disk: [6:21:54 @ 130 MB/s] SUCCESS # # Step 3 of 6 - Zeroing the disk: [5:48:43 @ 143 MB/s] SUCCESS # # Step 4 of 6 - Writing Unraid's Preclear signature: SUCCESS # # Step 5 of 6 - Verifying Unraid's Preclear signature: SUCCESS # # Step 6 of 6 - Post-Read verification: FAIL # # # # # #################################################################################################### # Cycle elapsed time: 18:38:14 | Total elapsed time: 18:38:14 # #################################################################################################### #################################################################################################### # S.M.A.R.T. Status (device type: default) # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 1000 - # # Power_On_Hours 33334 - # # End-to-End_Error 0 - # # Reported_Uncorrect 37 - # # Airflow_Temperature_Cel 36 - ->Failed in Past<- # # Current_Pending_Sector 800 - # # Offline_Uncorrectable 800 - # # UDMA_CRC_Error_Count 0 - # # # #################################################################################################### # # #################################################################################################### In case that is hard to read, here’s a screenshot: and here are the errors from the log: preclear_disk_Z730W84C_25180.txt looks like it’s a goner. After only 3 years.

Thanks Kilrah. Wondering if the diagnostic files show anything else that may be going on that I can address prior to doing a rebuild.

And here are the attributes for the failing drive.

I wanted to pull the diagnostics file before updating to 11.1. Here's the one I just pulled after updating. tower-diagnostics-20221007-0725.zip

Thanks Truro! I had no idea you responded until now. I used to get emails for responses and even marked this as follow. Attached is my diagnostics file. I greatly appreciate the help. tower-diagnostics-20221007-0648.zip

Hi there, Apologies for my ignorance. Is it safe to assume that the attached smart report for a disabled drive is a dead drive that should be replaced? Also, what part of it should I be looking at to tell that it is a bad drive? Lastly, I probably bought this drive along with quite a few other of the exact brand and size (Seagate Barracuda 3TB) over the course of maybe 1 year around 3 or 4 years ago and this is the 2nd that I've had issues with. Am I ignorant to assume that they should last longer? I switched to buying 8TB WD Elements/MyBook for the last bunch of drives since they started coming down in price a few years ago. I also believe that they are higher quality WD White drives than the desktop based Barracudas. Anyways, Thanks in advance for any help with the above questions! tower-smart-20221004-0900.zip