brentdog

One of my 2 unRAID servers requires me to login every time I visit the webGUI. This is even within the same browser session. If I close the tab and open the webGUI in a new tab, then it forces me to login again. My other server keeps me logged in for a long time even across difference browser sessions. I don't see any differences in how these servers are setup. I've attached diagnostics from the problem server. I'm using Firefox and have cleared all data (cookies, cache, etc.) and that has not resolved the issue. Any help would be appreciated in resolving this annoying issue. locutus-diagnostics-20250805-1005.zip

Good to know. I have removed the tailscale part from the path. I'm not sure why I had that in there. I guess at some point it was necessary.

The part that was causing my problem was this: echo "export PATH=$PATH:/tmp/bin:/usr/local/emhttp/plugins/tailscale/bin" >> /root/.bash_profile Not escaping the dollar sign was causing the PATH to just be hardcoded to whatever it was when the go file ran. The corrected version is this: echo "export PATH=\$PATH:/tmp/bin:/usr/local/emhttp/plugins/tailscale/bin" >> /root/.bash_profile

I solved my problem. The 'node' command not being found was the key. I had a typo in my go file that was causing the PATH not to get setup correctly. When I fixed that Connect started working as expected.

When I run that "pm2 start" command from @Gex2501 I get the "/usr/bin/env: ‘node’: No such file or directory" error again. I forgot to mention I'm running unRAID 7.0.0. Also I don't have my server behind any other services.

A soon as I installed the new version I got a red triangle at the top of the UI. Clicking on it gives "Warning: API is offline!". In the settings it says "Disabled until you have signed in" but the Sign in button is disabled. Log is attached. Rebooting didn't help. Uninstall/reinstall Unraid Connect plugin didn't help. Running unraid-api gives "/usr/bin/env: ‘node’: No such file or directory". At some point the settings page said I needed to add my internal IP to my unraid machine as an extra origin. I did that and it didn't help. Trying to register the server through account.unraid.net gives a "Sign in Failed" error. logs.json

I figured since the cache was still readable, I would just back it up, recreate it with just the 2 new drives which is what the end state was going to be anyway, and then restore. This seemed to work and all my dockers started successfully. Thanks, Brentdog

I'm moving to a new system and got to the point where I added some new drives to the cache. The rebalance ran surprisingly quick and then all my dockers started crashing. Balance does nothing and Scrub aborts immediately. Rebooted and that didn't fix it and now Docker service won't start. Lots of BRTFS errors in the log. Not sure what to do at this point. I've attached diagnostics. I hope someone can help. unraid-diagnostics-20250101-1448.zip

@bmartino1 Thanks for the responses. That plugin looks interesting but doesn't show up for me in Apps. Maybe because it is a beta. I looked a little at zfs for the array but isn't something I really need.

I have an existing server that is running low on storage, is difficult to upgrade storage on, and is ageing out. So I am building a new server that will newer hardware and be much easier to expand in the future. The new server will get some new drives plus some of the drives from the old server and assume all the functions of the old server. The old server will keep some of its drives and act solely as a data backup for the new server. Note I have an old Synology DS411+ that acts as a backup now but will finally be decommissioned at end of this project and its drives will go into the old Unraid backup server. Existing server: License: Legacy Unraid OS Pro Lifetime 6.12.14 Will acquire new Lifetime license as part of this project, but part of the question is whether it goes to this server or in the new server. Don't plan to move to version 7 during this migration. Array (all spinners, xfs): 2 x 18 TB (one is parity) 2 x 12 TB 2 x 10 TB 2 X 8 TB Cache (all SATA SSD, btrfs): 2 x 1 TB 1 X 2 TB Unassigned devices: 1 TB NVME Plex app data and transcode lives here due to a performance issue with cache at one point in time that has since been resolved but never moved Plex back to cache. Also have several VMs on here for performance. New server: Array: Will start with new 4 x 24 TB drives (precleared on a tertiary system, 1 will be parity) Will move the 2 x 18 TB and 2 x 12 TB drives from the old server. Cache: New 2 x 2 TB NVMEs (RAID1) This will hold what is currently on the existing system cache plus unassigned NVME (ie, cache, appdata including Plex, and VMs) Looking for advice/best practices as it pertains to the following: Should I start by just pulling all the drives (array/cache/unassigned/boot) to the new server? Note I have plenty of room in the new server to do this. Everything should come up as if it was the existing server, right? Then I would use unbalance to clear out the 10 TB and 8 TB drives, remove them, and transfer back to old system. Then I would add in the new 4 x 24TB drive making one of them the new parity. Then I would transfer stuff from the SSDs and old NVME to the new NVME cache. Finally I would rebuild the old server with the new Unraid license and the 10/8 TB drives plus the drives from the Synology. Or should I just use only the new drives into the new system using the new Unraid license? I would need to transfer over the network (rsync probably) the array data (66 TB) from the existing server to the new server. It wouldn't all fit but there is plenty of room on the Synology for the extra. Then I would transfer the 18/12 TB drives from the old server to the new servers array. Maybe run unbalance to evenly distribute the data in the array. Then I would restore appdata from a backup (using Appdata Backup plugin). Then I would transfer VM images from existing server to new server. Finally I would rebuild the old server with the new Unraid license and the 10/8 TB drives plus the drives from the Synology. Note that I have friends and family that I share my Plex server with, so I want to minimize downtime of Plex as much as possible but I also want to proceed in the safest, cleanest, and easiest fashion. I think the first option is the way to go but I am curious what the Unraid community thinks. While I know all these steps are well documented both in the documentation and in the forums, any extra details on how to best do the various steps would be appreciated. Thanks, Brentdog

I see this error on boot as well but it does not stop or slow down the boot process for me. Just annoying. Why is the solution to remove the mover tuning plugin? I'm using that plugin so I really do not want to remove it. Is that plugin deprecated? I cannot find any documentation that its deprecated.

Thanks @JonathanM. Yeah I understood that one of my 18TB would have to be the new parity drive which is why I pointed out that current parity was 12TB and that I wanted to avoid a parity swap, but I should have been more explicit.😀 I'll report back when complete.

I am replacing 2 6TB drives with 2 new 18TB drives. I currently have a single 12TB parity drive. What is the best way to do this with minimal array downtime? I would really like to avoid a parity swap which would probably take a day and a half at the rate the preclear on the 18TB drives is going. I'm fine with being without redundancy temporarily (while parity is rebuilt) as everything important is backed up. I also can temporarily have all drives connected at the same time although the end state will have the 2 6TB drives removed. Running unRAID 6.10.0-rc2

I had some time to try to debug this myself today. Turns out you need one of the yes/no criteria (age, min size, etc.) set or the base mover is used. This is different than previous versions of the plugin where you could just set the percent threshold and it would move everything when you hit that threshold. I set the age limit to something reasonable and it is working as expected now. Just curious if this change was intentional?

Just upgraded to 6.9 and subsequently upgraded the mover tuning plugin to latest. Now it seems as if the plugin isn't used at all when the mover is invoked. Everything gets moved when the mover is invoked even though I have the used space threshold set to 70%. I see that there are still some debugging echo statements in age_mover script and none of these show up in the syslog (I have mover logging enabled). I uninstalled and reinstalled the plugin and still just seems to use the base mover.