RiskyKangaroo

total 148 -rw------- 1 root root 256 May 8 17:02 Pro.key -rw------- 1 root root 23 May 12 14:24 dashboard_settings.json drwx------ 2 root root 4096 Jan 10 15:25 default/ -rw------- 1 root root 14126 May 12 16:24 disk.cfg -rw------- 1 root root 412 May 12 17:24 docker.cfg -rw------- 1 root root 300 May 11 03:51 domain.cfg -rw------- 1 root root 10 May 12 16:09 drift -rw------- 1 root root 40 Aug 10 2022 editor.cfg -rw------- 1 root root 127 Dec 6 2021 flash.cfg -rw------- 1 root root 0 May 12 16:23 forcesync -rw------- 1 root root 70 Jan 10 15:26 go -rw------- 1 root root 71 Jan 10 15:26 go~ -rw------- 1 root root 708 May 12 16:22 ident.cfg -rw------- 1 root root 33 Nov 30 2021 machine-id -rw------- 1 root root 4096 Nov 30 2021 modprobe.d -rw------- 1 root root 561 May 11 14:22 network-rules.cfg -rw------- 1 root root 106 May 12 05:44 network.cfg -rw------- 1 root root 7049 May 10 23:38 parity-checks.log -rw------- 1 root root 628 May 12 16:23 passwd drwx------ 16 root root 4096 May 1 17:59 plugins/ drwx------ 2 root root 4096 May 8 16:40 plugins-error/ drwx------ 2 root root 4096 May 11 20:46 plugins-removed/ drwx------ 2 root root 4096 May 12 16:23 pools/ -rw------- 1 root root 32 May 12 16:09 random-seed -rw------- 1 root root 472 May 12 16:23 shadow -rw------- 1 root root 498 Mar 14 2022 share.cfg -rw------- 1 root root 8192 May 8 10:48 shares -rw------- 1 root root 1 Oct 12 2022 smb-extra.conf -rw------- 1 root root 101 May 12 16:23 smbpasswd -rw------- 1 root root 4096 Nov 30 2021 ssh -rw------- 1 root root 4096 Nov 30 2021 ssl -rw------- 1 root root 4096 May 10 23:38 super.dat -rw------- 1 root root 4096 Nov 30 2021 wireguard

-rw------- 1 root root 8192 May 8 10:48 /boot/config/shares

I just had a chance to try this out, removed those files and booted but I am still getting the same issue where I hit save and it doesn't save settings. I attached the diags from after reboot in case they are different. diagnostics-20250512-2.zip

diagnostics-20250512.zip

Long story short I had a usb that borked, I transferred to a different usb and my server does not want to save when I change settings like SMB security settings or primary/cache settings. syslog-20250512.zip

Yes, I should have mentioned I looked for both mentions of USB and of hard drives and nothing at all. Still the only options in the BIOS boot menu are: SATA Port E: PLDS DVD-ROM DS-8D9SH NIC 1 Port 1 Partition 1: BRCM MBA Slot 0200 v21.6.0 There is a button to change the "Hard-Disk Drive Sequence" but it is greyed out which I am guessing is because it doesn't have any hard-disks with anything bootable on them and it isn't seeing the USB drive.

I went back through every screen in the BIOS, iDRAC, and lifecycle controller and I am unable to see any mention of the USB being disabled. I did find that if I try to deploy an OS through the lifecycle controller (still using BIOS not EUFI) it can see the USB as an available OS media but it fails when I select finish to reboot the server and install the OS. The error given is "Unable to apply the boot mode settings for BIOS (SEC0018) Recommended Action: Exit the OS Deployment wizard and retry the operation. If the problem persists, exit Lifecycle Controller and perform an AC power cycle."

The title tells it all, I am trying to boot into unraid on a new (to me obviously) Dell R520 but when I go into the BIOS boot menu there is no option for the USB drive. I have options for my NIC and DVD drive but nothing else pops up. I have another R520 that is in production (has upgraded CPUs and more ram) but I cannot find any differences in them. They are both running 2.9.0 for bios and are on 2.65.65.65 for iDRAC. I checked the other firmware versions I can, and nothing seems to be different or blatantly missing. I know the USB drive works becuase it will attempt to boot into unraid when I switch to UEFI before running into the dell no RAM issue that seems to still be prominent. I also attempted to do an update search through iDRAC but it wouldn't connect to the dell server which I am guessing is just because the server is older and no longer supported by dell,

I have a share called MegaStore and recently a new share called Megastore keeps getting created without my input. The share has a single folder in it and no other contents. I have deleted it but it eventually comes back. Is there a way I can find out what is creating this share? I am guessing I may have spelled my share wrong at some point when giving a device/service access but haven't been able to find that source.

I have been working on specifying which cores my docker containers have access to and after working through all this I think it would be super helpful if we could create "Core Groups" that we could add our containers to. For example if I have a total of 15 containers, 6 of which use very few system resources I think it would save a lot of time if I could do the following: 1. Create Core Group named "Background Processes" 2. Add the 6 containers (either from this page or in the pages of the individual docker setup screens) 3. Select which cores/threads this group has access to 4. Complete and update all required docker containers 5. Rinse and repeat for any other groups you need Use cases and benefits: Fewer clicks required when creating docker containers, just add them to a existing group and bam it has access to cores 7, 19, 8, and 20 without you needing to remember those numbers. If you have a group of docker containers that need more/fewer resources you can go into the group and add/remove cores all in one place. In a system with multiple CPUs you can balance their usage by moving whole groups from one CPU to another. If there was a Core Group overview you could visually see if any of your dockers or groups have overlapping resources.