CyberMew

I’m thinking of using this to use Claude Code to make changes to a repo… Is there a way for this container to setup and run some script commands, so on container startup I can ask it to git pull from some repo, install Claude Code, so I can run commands remotely? Is this doable?

I tried to restart but the slot says no drive and I start the array without it and it didn’t appear. I don’t know if the array is still serving the files from the dropped disk? It says array turned good. So, how can I replace it with another drive in this case?

Hi. Not sure what happened, sabnzbd says it is not able to create folder.. tower-diagnostics-20260117-1021.zip

Attached a new one since I got the email tower-diagnostics-20260107-2314.zip

How come the HGST 7tb drive suddenly died and red balled, and is there a way I can reuse it? If it’s not possible to revive it, and given the high hdd prices now, I would rather remove the drive and shrink the array if that’s possible…? Not sure if related to the drive dying but I also am getting these emails: bin/sh: line 1: 18095 Aborted /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null tower-diagnostics-20260107-2252.zip

Thanks, noted on that, but that's what the GUI showed, so seems like there is no way to go there, and I assume it showed 7.0.1 only because it is a safe version to jump from 6.9.2, before suggesting 7.2.3?

In Tools -> Update OS, I am seeing Unraid OS v7.0.1 is available. Can I use the update button to upgrade it, and it will do the necessary preparation and checks to ensure there is no issue with 7.0.1 (e.g. check for compatibility issues with existing plugins etc., or backup my flash drive contents etc.)? Or is it safer to upgrade in sequence, e.g. 6.10.x then 6.11.x then 6.12.x etc.? How can I do this manually because there is option in the web GUI to select version... And what else do we have to take note between the versions to ensure existing things won't break? I am only upgrading because I want the auto backup plugin feature and currently I don't have it installed because it's not possible.

I am running unRAID 6.9.2, can I install this? I tried to and I get this (even after a restart without starting array): Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8192 bytes) in /usr/local/emhttp/plugins/community.applications/include/helpers.php on line 48

Forced reboot and had to set the disks again and then it was thankfully fine afterwards and it ran as expected! Once parity copy was done it rebuilt and all is fine. Thank you!

Small question, will changing the size (turn off and on docker service to do increase it) cause me to need to reinstall my containers?

Ok I tried to click reboot but it seems like it didn’t take. I went back and click Cancel also nothing happened. Typing command reboot does nothing too. Any idea what is going on? Should I force power off?

I didn’t want to upgrade now while there is an issue.. unless the os cannot support 26tb... will I be able to copy it still if I cancel it now and I start it again? I’m just worried it won’t know to provide me the copy option anymore.

Recently my data drive of 6tb was disabled. My two parity drives were 22TB and 24tb. I had a new 26tb drive so had to do parity swap. Everything seems fine so I started to copy as per instructions. However it has almost been 12 hours and it is still at 1%, and I don’t see any increase in numbers for reads and writes count between 22tb and 26tb drive. Something is wrong..? Is it supposed to be like this? How can I restart the process without breaking anything? tower-diagnostics-20251109-1012.zip

Please see attached. Does this mean disk1 is not in use (yet still green)? tower-diagnostics-20251027-0633.zip

I found out that it was in Yes instead of Prefer (or Only), which was why it moved. We can close this now!

Any idea how I can prevent the folder and its content from being moved out of my cache drive?

I have already configured my appData folder to remain in cache only, but seems like the mover moved everything to user0. Why is that?

I’m seeing lots of disk read error but it’s not failing or anything. Is this bad? Oct 1 10:14:10 Tower kernel: sd 10:0:2:0: [sdh] tag#3169 ASC=0x11 ASCQ=0x0 Oct 1 10:14:10 Tower kernel: sd 10:0:2:0: [sdh] tag#3169 CDB: opcode=0x88 88 00 00 00 00 02 41 75 20 e0 00 00 04 00 00 00 Oct 1 10:14:10 Tower kernel: blk_update_request: critical medium error, dev sdh, sector 9688129888 op 0x0:(READ) flags 0x4000 phys_seg 112 prio class 0 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129824 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129832 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129840 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129848 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129856 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129864 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129872 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129880 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129888 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129896 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129904 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129912 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129920 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129928 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129936 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129944 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129952 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129960 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129968 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129976 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129984 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688129992 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130000 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130008 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130016 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130024 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130032 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130040 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130048 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130056 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130064 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130072 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130080 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130088 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130096 Oct 1 10:14:10 Tower kernel: md: disk1 read error, sector=9688130104

So now I don’t know if it is parity drive bad or the array is bad. With 87 parity errors, how can I go about deciding and how do I set it to use array data or to use parity data?

Unraid should have the information of what files are in that mismatch parity block correct?

I have 87 parity errors since a few months ago when it was previously 0. I don’t know why that is the case…. But so far I have not elect to overwrite parity drive, and is deciding to upgrade to a bigger drive and to rebuild from from parity. However is there a way to see the range of files that’s not matching over those parity errors? It should be technically possible right? This way I can decide to keep parity data or overwrite it during the next parity check.

Should I revert the setting from "Yes" back to "Prefer"? I will also stop the Docker/VMs service and set Mover to run monthly for now to be safe.

I am surprised there are duplicates in array and cache.. I don't know what 'Prefer' did exactly but it the mover moved all to array and now my folders are messed up. E.g. when I run a diff I see: Only in /mnt/user0/appdata/swag/: .DS_Store Only in /mnt/user0/appdata/swag/: ._.DS_Store Only in /mnt/user0/appdata/swag/: crontabs Files /mnt/user0/appdata/swag/dns-conf/cloudflare.ini and /mnt/cache/appdata/swag/dns-conf/cloudflare.ini differ Only in /mnt/user0/appdata/swag/dns-conf: cloudxns.ini Files /mnt/user0/appdata/swag/dns-conf/cpanel.ini and /mnt/cache/appdata/swag/dns-conf/cpanel.ini differ Files /mnt/user0/appdata/swag/dns-conf/domeneshop.ini and /mnt/cache/appdata/swag/dns-conf/domeneshop.ini differ Only in /mnt/user0/appdata/swag/dns-conf: dynu-credentials.ini Files /mnt/user0/appdata/swag/dns-conf/dynu.ini and /mnt/cache/appdata/swag/dns-conf/dynu.ini differ Files /mnt/user0/appdata/swag/dns-conf/gandi.ini and /mnt/cache/appdata/swag/dns-conf/gandi.ini differ Only in /mnt/user0/appdata/swag/dns-conf: google-domains.iniSo it is 'safe' to use whatever is newer and move/replace the once in Cache right? I don't know how duplicates is even possible and how it even worked in the first place.. very surprised

Previously my appdata folder for Use cache pool (for new files/directories): is configured as "Prefer", but I recently changed it to "Yes", because I wanted any creation to be done in Cache first, then if it is really full then go straight to array (because I dont want the creation to fail, e.g. if I am downloading something I rather it go array behind the scenes, etc.). Then I was curious why my apps from Dockers are not working. Then thereafter I see the logs of mover moving the entire appdata folder into the array ☠️ In some cases it says the files already exists, so I have no idea what is happening right now.. I mainly use appdata for the Dockers. Now I need to move them back to the Cache and hope the data wasn't messed up.. anyone knows why this is happening? What should I do in this case? I did not know pressing Apply for that change means instantly the mover is triggered...

Are you able to share your final build?