All Activity

The moment you format a drive (which you must have done if you were testing out encryption) the drive is no longer empty and cannot be removed without affecting parity. The fact there is no user data on the drive is irrelevant. Whatever method you now use it is going to take a long time. Doing a New Config followed by the parity sync is probably the easiest.

Thanks I dont want to do a parity sync as my drives are 20TB and it takes 24 hours. It would seem unraid should automate this if you zero a drive or have never put anything on the drive it should be easier to remove a drive without having to run parity again or go through a convoluted dance. I should be able to select a drive choose remove from array then it does what it needs to do to remove that drive. Obviously gives warning that any data would be wiped. But the process is very manual and error prone. Unraid LOVES to restart parity checks. I tried option 2 but failed at step 1 so I assumed maybe the instructions were out of date Start the array in maintenance mode, click on the disk you want to remove, and then click Erase. This erases the file system from the device while maintaining parity, then stop the array. I do not see an "Erase" Feature after selecting the drive in maintenance mode.

The diagnostics confirm that the remote NFS server became unavailable while Duplicacy had active writes on a hard NFS mount. With a hard mount, the Linux NFS client continues retrying indefinitely; the “timed out” messages do not mean that the requests have been abandoned. Unassigned Devices later performed a lazy unmount, which removed the visible mountpoint but did not cancel the outstanding NFS requests. Array stop subsequently became blocked at the global filesystem sync, and both the sync and shutdown processes are now in uninterruptible sleep. Stopping the local NFS service will not affect this because that service controls exports from this server, not its client connection to the other server. If possible, the safest recovery is to bring the remote server back online at the same address and export path. If that cannot be done, a clean shutdown may no longer be possible and a forced reboot may be required. After recovery, also recomemnd correcting the Fix Common Problems warning that the Duplicacy Unassigned Devices path is not mounted with slave propagation.

Brand new flash drive was the answer to regain access. All config lost due to poltergeist (I guess?) Thanks @JorgeB and @itimpi for helping me get back up.

First off thanks for the great work! Something I know quite a few of us have wanted. Would love to use it but keep getting issues installing. Both App store and Manually. When i do a manual install, copy and paste of the link (I think there were two different links i found for it to github) both give this error. plugin: installing: corsairpsucenter.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: downloading: corsairpsucenter.plg ... done Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks When installing it form the app store I get this Downloading plugin plugin: installing: corsairpsucenter.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installedNeither one install. No tab, doesn't show as installed. Running the latest 7.3.2 using internal boot off of a pool of 256GB NVMs. Thanks

There are two options to shrink an array, both described here; typically, we recommend the first one (requires a parity sync/check) https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array/#removing-data-disks

Most likely, you can try the balance while the party check is running. The best bet is to backup and recreate the pool from scratch.

So I had a 2nd unraid server connected through UD as an NFS share. I used this share to backup my appdata using duplicacy. I came home today to find that the connected unraid server had crashed. Duplicacy showed it had been attempting to upload the backup for several hours without progress. So my first port of call was to try stop the duplicacy container... this failed in the normal gui way.. eventually i was able to forcestop it. Grand but I was seeing a persistent "kernel: nfs: server 192.168.1.50 not responding, timed out" in the logs. So I then tried to stop the nfs service... in settings when I changed the setting to No and tried to click apply nothing happened. So again I force stopped the service using "/usr/local/etc/rc.d/rc.nfsd stop" command. I got notified that the service had stopped and the logs also reflected this. Still the nfs timeout warning continued to appear. So i have tried to stop the array and the docker service appears to have stopped successfully however the array will not stop. Also a shutdown doesnt do anything and I continue to get the nfs timeout issue. Not really too sure where to go from here. I havent hard reset the server yet just in case there is something I can do. Any help would be greatly appreciated. Even just to get the server shut down gracefully. server-diagnostics-20260811-1855.zip ***EDIT*** Ok so when I got my 2nd server back up and running... Hard reset its not as vital for me... the server shut down gracefully. But I guess the issue still stands when this instance occurs and I'm not in a position to hard reset the mounted drives what is the best course of action to get to a place to rectify it?

I am running 7.3.2 I installed a new drive and encrypted it. I was just trying out unraids drive encryption features. I now want to remove this drive from the array. Nothing was placed on this drive. How do I remove this drive without affecting my parity?

Hm. restarting triggered a parity check operation, going to take a day to finish. that's weird. In any case, I'd tried restarting last week before making this post, so I don't think it's going to work. I did try to recreate the pool then but was unsuccessful, that's when I made this post. What are the proper steps for remaking the pool?

if you go through walls consider to go to fiber too the same time. Copper is at the end of the line now

Syslog shows the balance is stuck in a loop, try rebooting the server, then try again, but if the same thing happens, you may need to back up and recreate the pool instead.

Yep will test as soon as possible after work.

To be clear I only meant temporary, obviously would be moving to pure wired when I overhaul the networking gear. When I went through my path, it’s the same Powerline adapter. I went through the send and receive flow. So although it’s mentioned twice, there’s only one set (pair) of Powerline adapters. Although I do appreciate Powerline in general is clearly not recommended. Where the fibre line (ONT) enters my home, it’s very far away from everything else. So everything “internet” is in one room, in one corner. I’m in the process of dropping Ethernet cables into every room from the attic, so going through walls etc. So eventually things that need wired will be wired with UniFi switches etc. without going through intermediary mediums e.g. Powerline.

If you're still having this issue, update the repository for the container. The template still uses gcr.io/cadvisor/cadvisor which is for versions prior to v0.53 ghcr.io/google/cadvisor is the container repository for >=v0.53 Using the latest version from ghcr.io/google/cadvisor (v0.60.5) fixed this issue for me, no changes to cadvisor settings needed. Raised https://github.com/selfhosters/unRAID-CA-templates/pull/690 to fix the template.

Maybe he means the New Next Programs Range https://github.com/dlandon/recycle.bin-next

I think we are talking past each other. I understand what you are saying. I did not move or delete anything on the emulated drive. Further, all files are still available and none have been deleted from teh array. Because I did not move anything, I am trying to understand why certain files were on the original physical drive, but on a different physical drive after the drive was rebuilt.

This is the least efficient setting. Highwater is default because it will allow all disks to get used eventually, without constantly switching disks just because one disk temporarily has more free space than another.

First of all: avoid Powerline and Wifi for servers AT ALL COSTS (though UNRAID now supports WiFi, its really a bad idea) Next: even more about DOUBLE Powerline DOUBLE WiFi or mixed Powerline/Wifi And of course, as what I have said already: SMB is bandwidth sensitive, iperf of course not. So iperf results may give a tendency but mean nothing for SMB at all. Why can't you use "normal" cables at least between UNRAID and the router???

syslog is a single text file. Zip the latest syslog from wherever you configured syslog server to save it and attach to your next post in this thread. Also The word Diagnostics in any post on the forum is automatically converted to a link to the documentation that explains how to get diagnostics, including from the command line. Next time it happens before rebooting it might be useful to see the result of this command line: df -h /

If a file was moved from the emulated drive, it wouldn't be on the rebuild but would still be on the physical disk.

It will take me some time together this information. I will be back.

So I have set up the Syslog server and things have been going on for the last few days. I logged in today to try start a vm and when I pressed the vm tab it failed to load. I opened a new browser and could go to the apps tab no problem. Tried the vm tab again and it wouldn’t load. I ssh’d into it and rebooted and it said it was rebooting but stayed replying to a ping. I had to hard reset it again so can anyone tell me what logs in the syslog I can provide to try and determine the issue?

Thanks!

Yup, that would be correct for a regular home PC which would have some swap space and would misuse an SDD/HDD to put stuff on that should be in RAM, but Unraid doesn't do swap. When there's no RAM for the essentials something needs to get killed.