Soup

I came across a spare 256GB NVMe and don't really have anything else to do with it. The system is an OptiPlex SFF that doesn't really have a way to properly mount the 2 x SSD's. I want to move the SSD's to my MD1200, but it doesn't look like I can boot off of them if it's there.

Thanks for the link @JorgeB Just so I get this straight... I need to create a new bootable flash drive (can it be the one I recently transferred off of to move to internal boot, or will that cause license issues?). Create and mount the newly created flash drive to the currently running unraid and copy the /boot/config folder to it Boot the "new" flash drive, then run the wizard to remove the old boot pool and create the new one.

Good afternoon, I moved (successfully) my boot from a USB drive to a raid1 SSD pool. I now have an internal NVME I want to move it to... but I'm getting a few errors with the wizard. Specifically: BOOT_ELIGIBLE_FALSE The system reported that storage boot is not eligible. ENABLE_BOOT_TRANSFER_DISABLED Boot transfer is disabled by the current system state. Not sure how to move forward with these errors. Thanks for any help you may be able to provide.

any way to manually run the script to see if it works post-boot?

No other available PCI slots on the PC I'm using (SFF chassis). What would the race condition be? The interface is detected after the network configuration loads?

Tried that, same result. Network.cfg is created but the rules file is not

Good morning everyone, I'm trying to switch over my primary interface in UnRAID to the 2.5G NIC currently associated to eth1. From my searching, I should be able to swap what's assigned where via Interface Rules, but that tab doesn't exist for me. (7.2.3) I've tried manually creating network-rules.cfg in /boot/config but the file is removed on reboot. I've tried manually creating the file on USB, but again, it's deleted on boot. For the time being, I went into /boot/config/network.cfg and simply modified the following: - IFNAME[0]="eth0" + IFNAME[0]="eth1" Seems to have done the trick, but I feel like it's a band aid, not a fix Any help apricated. Thanks tower-diagnostics-20260108-1057.zip

I'm mounting the NFS share on a Ubuntu VM. The NFS server is UnRAID.

Sorry for the stupid question... but what's UD?

I changed the fstab entry on my plex server from: 10.0.0.20:/mnt/user/Movies /mnt/user/Movies nfs defaults 0 0 to: 10.0.0.20:/mnt/user/Movies /mnt/user/Movies nfs hard,timeo=50,retrans=5,relatime,rsize=1048576,wsize=1048576 0 0 Have not had a reoccurance of the issue since doing that... will continue to monitor If that does indeed end up being the solution, I'd love for someone (anyone) to try and explain it to me. These NFS options are kinda over my head, got it from the link posted by @JorgeB

The issue just happened again. Host1-VM1 lost access to NFS share Host2-VM2 still had full access to a NFS share Host2-VM2 unmount NFS share, unable to remount NFS share... log only shows Jan 30 14:23:36 Tower rpc.mountd[18574]: v4.2 client attached: 0x33d49064679ae870 from "10.0.0.53:904" Attempted to restart NFS root@Tower:~# /usr/local/etc/rc.d/rc.nfsd restart rc.nfsd: Restarting NFS server daemon... rc.nfsd: Stopping NFS server daemon... Hangs at this.

Thanks, I've increased the number of threads and the number of fuse file descriptors already (16 threads and 500,000 file descriptors). I have no idea if those numbers are appropriate, is there a way to tell if those values are set too low or harm to setting them too high?

Good morning, I recently moved my UnRAID from a HP DL380g9 to an Optiplex 3080 SFF. With the old hardware, every once and a while, NFS would seem to hang (mounts would become unreadable on a guest) df -h would hang and data would be inaccessible until UnRAID rebooted UnRAID (10.0.0.20) - Optiplex 3080 PLEX (10.0.0.55) - Proxmox Ubuntu 24.04 LTS VM (Optiplex 3010 i5-13500T) with iGPU passthrough) Since the migration to the 3080, NFS seems to hang every day... frequently. If I attempt to stop the array, it gets to the following and just hang Jan 29 15:21:44 Tower emhttpd: shcmd (1073): /etc/rc.d/rc.nfsd stop Jan 29 15:21:44 Tower rc.nfsd: Stopping NFS server daemon... Jan 29 15:21:44 Tower rc.nfsd: /usr/sbin/rpc.nfsd 0 Diag attached... Happy to share the output of any other commands needed. tower-diagnostics-20250130-0907.zip

Possibly a stupid question, but how do I go about updating? Current Container ID: 52ae973bcbfe Showing "up to date" now