ronmcmxci

I'm also having the same problem.

Following-up here, the update seems to have worked. I haven't had the issue in 2 weeks.

I was able to get it to launch by following this. In summary, creating a 'db' directory in the wallabag data directory -- for me this was /mnt/user/appdata/wallabag/ -- and changing the permissions of the db folder to nobody:users. mkdir /mnt/user/appdata/wallabag/db chown nobody:users /mnt/user/appdata/wallabag/db --recursive

I'm also getting this same error. Have there been any solutions?

Just finished the update, hopefully it helps

I'm all set here. Easy with no problems. Thanks all

Just to confirm, after assigning the new drive in the pool slot for the old drive I should see this? Cache 4 is the drive I'm replacing. Empty slot after removing old drive: After assigning new drive:

Okay that makes much more sense. Just to confirm, I can leave the data on the pool?

Hi all, I need to replace a disk in a pool and was reading the docs: https://docs.unraid.net/unraid-os/manual/storage-management#replace-a-disk-in-a-pool In summary: Stop the array. Physically detach the disk from your system you wish to remove. Attach the replacement disk (must be equal to or larger than the disk being replaced). Refresh the Unraid webGui when under the Main tab. Select the pool slot that previously was set to the old disk and assign the new disk to the slot. Start the array. If presented with an option to Format the device, click the checkbox and button to do so. Full stop I may be misinterpreting this but it reads like this is to be done while the Unraid server is running. Is this required or can I do the drive swap while the server is powered off? Some drives are inaccessible while the server is running. For example: Stop the array. Disable auto-start Shut down Unraid Physically detach the disk from your system you wish to remove. Attach the replacement disk (must be equal to or larger than the disk being replaced). Start Unraid Open the Main tab. Select the pool slot that previously was set to the old disk and assign the new disk to the slot. Start the array. If presented with an option to Format the device, click the checkbox and button to do so. Thanks!

My Crucial MX500 issues seem to be this:

As an additional data point, my 1 month-old 4TB MX500 has been having this issue. Glad I found an explanation but I wish I found it before I bought the drive :).

I ran into this same issue. As @hoffsays it looks to be an arp issue for me also. The arp table for br0 will occasionally go <incomplete> for my gateway. To workaround it I configured arp manually for my gateway with "arp -s <gateway> <gateway mac> -i br0". I'll follow up if I see an issue

Scrub completed. Containers and VMs are running properly. Thanks for the help

Looks okay I think? Error summary: verify=12891 csum=11905024 Corrected: 0 Uncorrectable: 0 Unverified: 0 Should I rerun the scrub with the repair corrupted blocks checked?

Update: I must have enabled repair mode under filesystem check. I re-entered maintenance mode to run another file system check and disabled repair mode. File system check was good. I was then able to restart in normal mode and the scrub is now running.

Very similar situation to this post: Version: 6.11.5 btrfs cache drives: 4: 2x Samsung 970 Evo Plus nvme 1x Samsung 850 Evo sata 1x Crucial mx500 sata 1. The dashboard's log was reporting 100% full 2. I restarted unraid based on a forum recommendation. Dashboard log was back to normal Crucial drive is reported missing 3. I shut down Unraid, checked connections and started again and Crucial drive is back in cache pool as normal 4. Docker containers won't start, VM wont start either. System log shows "read error corrected" and "parent transid verify failed" 5. I've tried a scrub but it aborts immediately. When run in Cli the error reads "ERROR: scrubbing /mnt/cache failed for device id 1: ret=-1, errno=30 (Read-only file system)" I'm not sure how to proceed. I don't have any current backups and my array is a USB drive as my setup is SSD only and my understanding was SSDs in the array was ill-advised. Diagnostics attached. tower-diagnostics-20230524-0923.zip