Most memory intensive application is frigate. Almost all my docker containers are restricted to the RAM amount I specify, except some newer containers like paperless-ngx and redis. Frigate is allowed 20gb and is currently in at 16gb. Most of my cameras are running higher detection resolutions (and I have many) so this is expected, not misconfigured.

Finally, why isn't there protective code in the Unraid OS? 99% of my issues would probably not be an issue if UnRaid would just kill things like docker if it was getting out of hand. Even better if it specifically kills a container with a log entry. Even better if there weren't 2-3 places to find the logs. It just baffles me that UnRaid doesn't protect itself, it just seems to go down with the ship.

uhive-diagnostics-20260720-1009-outofMemory.zip

unraid-diagnostics-20260719-0806.zip

I added a new nic card so now I have two one on the MB and on in a pcie slot. How can i tell if they are set up correctly? After I added the card I went to settings network interface rules and switched the MAC addresses so that the new nic should be eth0 and the old one eth1.

When i rebooted the server it looks like I am at 2.5Gb speed but it looks like it bonded the two NICs. Is this the way it should be run? It also looks like eth0 is down? But shouldn't it be the other way around?

Is this expected behaviour (stopping the array with no user notice) and how do I stop it ever changing its license so this doesn't happen again?

Not sure how concerned I should be about this error and what I need to do to resolve it. Error spit out by the CPU sounds a tad scary though...Thanks for you help!

lansdownebrain-diagnostics-20260720-2247.zip

Anyway it might stay up for a few weeks to a few days before it happens. I've tried most recently to shutdown all docker apps to see if that helped, it didn't. I ran a memtest when this first started and it passed. I enabled the syslog server and see a few things such as:

kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: Unsuccessful self-config (-ETIMEDOUT) key 0x906 value 0x1123800

kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Failed to register RECV buffer (-ETIMEDOUT)

kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Failed to enable CTB (-ETIMEDOUT)

kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: mmio request 0x508: no reply 508

and also

rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2102.0 try https://www.rsyslog.com/e/2359 ]

rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]

rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]

rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2102.0 try https://www.rsyslog.com/e/2007 ]

and also

kernel: get_swap_device: Bad swap file entry 4003ffff848bc9df

This has been driving me crazy so I really appreciate any help.

yougotserved-diagnostics-20260720-1138.zip

Wrong Pool State

cache - invalid expansion

and no matter what I do I can't seem to get the array back online. I found a few threads talking about this same error, and most of the solutions involved removing the pool and adding it again and the config imports and fixes itself. However, I don't seem to have that option for this pool! I'm assuming that's because it was set up as a partition on the boot drive. My only option is to erase the pool entirely, which is expressly described as deleting everything on the drives. This is obviously not ideal. Am I missing something obvious, or have I fucked up beyond repair due to ignorance and panicking?

Below is the initial error I received that was the start of the issues, then the alert that showed up after rebooting, and attached is my diagnostics. The Patriot drive is the drive I initially had installed as the boot drive, and the TEAMGROUP drive is the newly installed drive.

Event: Unraid Flash 2 error
Subject: Alert [J-SERVER] - Flash 2 in error state (disk dsbl)
Description: No device identification ()
Importance: alert

Event: Unraid pool status
Subject: Notice [J-SERVER] - Pool flash recovered to ONLINE
Description: Pool: flash (zfs) - Mountpoint: /boot
Importance: normal

j-server-diagnostics-20260720-2211.zip

Unraid 7.2.4: My "docker" share wasn't showing a comment so I went to add one. I discovered I cannot modify anything on that share page. At the bottom, I see "Case-insensitive Share name is not unique". Additionally, the share is showing as residing on my Cache pool on the share page, but this is incorrect. My docker image is actually on a pool named Virtualization. I have confirmed the image exists at /mnt/virtualization/docker/docker.img and that no docker.img is on /mnt/cache. Cache is an xfs-encrypted pool of 1 devide. Virtualizaton is a zfs-encrypted pool of 2 devices.

I have no idea what to do here. Any help appreciated.

Thanks!

I replaced my router recently and am no longer able to access my Unraid server (WebGUI, mapped network drives, cmd line 'ping') from one windows 10 machine. A chromebook, android phone, and a windows 11 machine are all able to access the WebGUI (and mapped network drives in the case of the windows 11 machine).

Here's a picture of the error I get when trying to access mapped network drives:

Here's a list of things I have tried:

Using both the IP address of the Unraid server as well as http://tower.local 

Cleared my saved credentials in Windows Credential manager.

Changed this setting as recommended in a different thread: Computer Configuration > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons.

Renamed "/config/network.cfg" and restarted the server

Manually assigning an IP (to the address assigned by my old router) in my router, in unraid settings, and manually assigning the same IP in both the router and in unraid (this was mostly to make it so my family could access Jellyfin the way they were used to, but it didn't fix the problem either)

Probably a few other things I'm forgetting

I've read through a number of threads regarding Windows-Unraid issues without finding a solution, although I am sure there are more out there. Also, it seems like most of those threads relate to SMB issues, which I don't think would prevent me from accessing the WebGUI (please feel free to correct me if I'm wrong).

I'll be grateful for any help you can provide.

I tried to restart but it never came back up. Seems the USB drive is dead. I tried downloading the Boot Device Backup from Connect, first coupel times it gave me an error. Then it downloaded a backup, but when i used it to create the USB, it didn't install any data. Theres just an empty "syslinux" folder and the normal files on the root of the usb. No Config folder nor EFI folder. Does unraid connect have a bad backup? it says its from just 3 days ago.

unraid-diagnostics.zip

Anyway, since PIA recently changed some of their endpoints, the configurator doesn't seem to work. I'm not sure if these two are related or not but ever since the change, I'm having issues getting a proper config file from a server that supports port forwarding. Does anyone know how I can fix this? The wg0.conf file in my /cache/appdata/wireguard-easy/ directory has file permissions that won't allow me to view it. I know how to change them but thought I'd ask here first if anyone knows why SI's docker isn't working?

EDIT: Ok, I was able to find a server (Netherlands) that generated a file correctly. I then had another issue to get Prowlarr and Flaresolverr talking to each other behind by custom WG PIA VPN network (had to add a Host variable of 0.0.0.0 to Flaresolvver to look at all incoming traffic) and now my indexers are working again. Prefer a physically closer server than Netherlands but for now at least I'm running again.

Now my server seems to be going to sleep or something, and the console(on the actual machine), the webgui and the shares all become unresponsive, the machine is still running( fans, LEDs etc. still on).

If its running a parity check, it stays awake during the parity check and everything works during the parity check. then sometime after the check finishes ( not immediately ) everything stops working.

cycling parity check is the only thing that keeps it useable, but that is not a long term solution =(.

Any help would be appreciated. Diagnostics below.

Ebein

ava-diagnostics-20260713-1246.zip

I’ve noticed the following: with < 7.3.2 i reached only CPU-Package-C9, but now I reach C10.

Is the driver package "RTL8152 Drivers" disabled ?

Before I start debugging myself, I wanted to ask the experts first.

Maybe this has something to do with:

Linux Kernel

The Linux kernel has been upgraded to 6.18.38-Unraid. This release also sets CONFIG_USB_AUTOSUSPEND_DELAY=-1.

greetings

syslog.txt

tower-02-hobby-diagnostics-20260721-0702.zip

Found instructions to bring that drive back into the array, with the first step being to stop the array. It's here where I got stuck on "Array Stopping•Retry unmounting disk share(s)..."

I have tried following workarounds on a couple of threads from the forums, but these do not seem to have helped and I am still stuck with the array attempting to stop.

https://forums.unraid.net/topic/145821-cant-unraid-stop-when-array-already-unmounted/

https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/

Also spotted cache disk doesn't appear to show in the UI anymore, and key file is missing.

Diagnostics attached.

Console output also included below in case it helps to see what's been tried:

root@Nebula:~# umount /var/lib/docker
umount: /var/lib/docker: target is busy.
root@Nebula:~# lsof /mnt/cache
lsof: status error on /mnt/cache: No such file or directory
lsof 4.93.2
 latest revision: https://github.com/lsof-org/lsof
 latest FAQ: https://github.com/lsof-org/lsof/blob/master/00FAQ
 latest (non-formatted) man page: https://github.com/lsof-org/lsof/blob/master/Lsof.8
 usage: [-?abhKlnNoOPRtUvVX] [+|-c c] [+|-d s] [+D D] [+|-E] [+|-e s] [+|-f[gG]]
 [-F [f]] [-g [s]] [-i [i]] [+|-L [l]] [+m [m]] [+|-M] [-o [o]] [-p s]
 [+|-r [t]] [-s [p:s]] [-S [t]] [-T [t]] [-u s] [+|-w] [-x [fl]] [--] [names]
Use the ``-h'' option to get more help information.
root@Nebula:~# lsof /var/lib/docker
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME
dockerd   8180 root   13u   REG   0,47    32768     293 /var/lib/docker/volumes/metadata.db
dockerd   8180 root   19u   REG   0,47    16384    5689 /var/lib/docker/buildkit/containerdmeta.db
dockerd   8180 root   20u   REG   0,47    16384     304 /var/lib/docker/buildkit/snapshots.db
dockerd   8180 root   21u   REG   0,47    16384    5690 /var/lib/docker/buildkit/metadata_v2.db
dockerd   8180 root   22u   REG   0,47    32768     309 /var/lib/docker/buildkit/cache.db
dockerd   8180 root   28w   REG   0,47   433199 1023963 /var/lib/docker/containers/7eab7a44d5f408d3a06712bfd9716239e245a76bb6cd60aa850fadf5c4e0dfed/7eab7a44d5f408d3a06712bfd9716239e245a76bb6cd60aa850fadf5c4e0dfed-json.log
dockerd   8180 root   34w   REG   0,47 31724307 1360831 /var/lib/docker/containers/63f3828ac3d799f8a4f894e49a33bfba7e0057bdfc722cac272f684289aaa11d/63f3828ac3d799f8a4f894e49a33bfba7e0057bdfc722cac272f684289aaa11d-json.log
dockerd   8180 root   40w   REG   0,47 32079446 1275318 /var/lib/docker/containers/bdd9b652e9b0032f28a64db857cfce965e27e302f794e65ee4d415b6417f1266/bdd9b652e9b0032f28a64db857cfce965e27e302f794e65ee4d415b6417f1266-json.log
dockerd   8180 root   43w   REG   0,47    25224    7963 /var/lib/docker/containers/e79ef2ed99dcf1aa372fc5c208fabe7462199a253a1009c8bf09925319999aa2/e79ef2ed99dcf1aa372fc5c208fabe7462199a253a1009c8bf09925319999aa2-json.log
dockerd   8180 root   51w   REG   0,47 19761177 1019027 /var/lib/docker/containers/6bd8577a078676c766e55153002bd82ea82a8c29d329fe3c76dac82ac99749a8/6bd8577a078676c766e55153002bd82ea82a8c29d329fe3c76dac82ac99749a8-json.log
dockerd   8180 root   57w   REG   0,47 47846993 1326681 /var/lib/docker/containers/04f5a25174258a0a9c0ab2179c881246204884e0dcaa758967e217d3873a434a/04f5a25174258a0a9c0ab2179c881246204884e0dcaa758967e217d3873a434a-json.log
container 8195 root    4u   REG   0,47   524288     272 /var/lib/docker/containerd/daemon/io.containerd.metadata.v1.bolt/meta.db
root@Nebula:~# losetup
NAME       SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE                           DIO LOG-SEC
/dev/loop1         0      0         1  1 /boot/bzfirmware                      0     512
/dev/loop2         0      0         1  0 /mnt/disk1/system/docker/docker.img   1     512
/dev/loop0         0      0         1  1 /boot/bzmodules                       0     512
root@Nebula:~# umount -l /dev/loop2
root@Nebula:~# lsof /var/lib/docker
root@Nebula:~# losetup
NAME       SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE                           DIO LOG-SEC
/dev/loop1         0      0         1  1 /boot/bzfirmware                      0     512
/dev/loop2         0      0         1  0 /mnt/disk1/system/docker/docker.img   1     512
/dev/loop0         0      0         1  1 /boot/bzmodules                       0     512
root@Nebula:~# lsof /mnt/disk1
root@Nebula:~# lsof /mnt/cache
lsof: status error on /mnt/cache: No such file or directory
lsof 4.93.2
 latest revision: https://github.com/lsof-org/lsof
 latest FAQ: https://github.com/lsof-org/lsof/blob/master/00FAQ
 latest (non-formatted) man page: https://github.com/lsof-org/lsof/blob/master/Lsof.8
 usage: [-?abhKlnNoOPRtUvVX] [+|-c c] [+|-d s] [+D D] [+|-E] [+|-e s] [+|-f[gG]]
 [-F [f]] [-g [s]] [-i [i]] [+|-L [l]] [+m [m]] [+|-M] [-o [o]] [-p s]
 [+|-r [t]] [-s [p:s]] [-S [t]] [-T [t]] [-u s] [+|-w] [-x [fl]] [--] [names]
Use the ``-h'' option to get more help information.
root@Nebula:~# ls
root@Nebula:~# mkdir tmp
root@Nebula:~# ls
tmp/
root@Nebula:~# cd tmp
root@Nebula:~/tmp# dd if=/dev/zero of=disk2 bs=1M count=310
310+0 records in
310+0 records out
325058560 bytes (325 MB, 310 MiB) copied, 0.291545 s, 1.1 GB/s
root@Nebula:~/tmp# ls
disk2
root@Nebula:~/tmp# mkfs -t xfs disk2
meta-data=disk2                  isize=512    agcount=4, agsize=19840 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1
data     =                       bsize=4096   blocks=79360, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=1368, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
root@Nebula:~/tmp# ls
disk2
root@Nebula:~/tmp# cd disk2
bash: cd: disk2: Not a directory
root@Nebula:~/tmp# cd ..
root@Nebula:~# ls
tmp/
root@Nebula:~# cd ..
root@Nebula:/# ls
bin/   dev/  home/       init@  lib64/  opt/   root/  sbin/  tmp/  var/
boot/  etc/  hugetlbfs/  lib/   mnt/    proc/  run/   sys/   usr/
root@Nebula:/# cd mnt
root@Nebula:/mnt# ls
disk1/  user/
root@Nebula:/mnt# mkdir disk2
root@Nebula:/mnt# ls
disk1/  disk2/  user/
root@Nebula:/mnt# cd ..
root@Nebula:/# cd tmp
root@Nebula:/tmp# ls
ca.backup2/  community.applications/  emhttp/  notifications/  plugins/
root@Nebula:/tmp# cd root
bash: cd: root: No such file or directory
root@Nebula:/tmp# cd ..
root@Nebula:/# ls
bin/   dev/  home/       init@  lib64/  opt/   root/  sbin/  tmp/  var/
boot/  etc/  hugetlbfs/  lib/   mnt/    proc/  run/   sys/   usr/
root@Nebula:/# cd root
root@Nebula:~# ls
tmp/
root@Nebula:~# cd tmp
root@Nebula:~/tmp# ls
disk2
root@Nebula:~/tmp# mount disk2 /mnt/disk2
root@Nebula:~/tmp# 

nebula-diagnostics-20260717-0945.zip

Mobo: MSI Pro Z790-P WI-FI with 12700K

Drives: 22 mostly WDC SATA in BTRFS

Upgrade went smoothly. Rebooted and immediately noticed that UNRAID CLI was reporting the following repeatedly when tyring to scan the hard drives:

May 28 09:21:55 BigBoi kernel: I/O error, dev sdh, sector 128 op 0x0:(READ) flags 0x80700 phys_seg 48 prio class 2

May 28 09:21:55 BigBoi kernel: sd 0:0:10:0: attempting task abort!scmd(0x00000000fcba39fa), outstanding for 30463 ms & timeout 30000 ms

May 28 09:21:55 BigBoi kernel: sd 0:0:10:0: [sdk] tag#5615 CDB: opcode=0x28 28 00 00 00 00 80 00 01 80 00

May 28 09:21:55 BigBoi kernel: scsi target0:0:10: handle(0x0018), sas_address(0x300062b202aed2ce), phy(14)

May 28 09:21:55 BigBoi kernel: scsi target0:0:10: enclosure logical id(0x500062b202aed2c0), slot(4)

May 28 09:21:55 BigBoi kernel: scsi target0:0:10: enclosure level(0x0000), connector name( )

May 28 09:21:55 BigBoi kernel: sd 0:0:7:0: Power-on or device reset occurred

This happened over and over -- eventually the server booted (30-40 mins) and then allowed me to login where it struggled for another 30 mins to start the array (It eventually did)

I was able to grab snippets and diags prior to rolling back to 7.3.0.

Roll back successful and everything is running perfect on 7.3.0.

Happy to provide more information.

Skip

bigboi-diagnostics-20260528-0934.zip

If you have Unraid initiate a clean shut down of the machine when the UPS is running low (say 25%), how do you stop the BIOS from just immediately rebooting the machine and repeating that loop until the battery is completely drained and you experience another dirty shutdown?

Will that not happen for some reason? I need the machine to try to turn on as there is no one within a thousand miles of it for 51 weeks of the year. Do i need to set an interval so the machine waits at least an hour between power on attempts? Or is there some level of intelligence that tells the machine dont restart until main power is restored and the battery starts charging?

Attached a picture of the console. Is my flash drive dead? What do I do now?

I thought I'd be done with this, but hey. Another crash, after a long history of crashes.

hard data:

• today, 13:54h, I got an automatic notification from Tautulli that Plex is offline. This means, the Plex container stopped before Tautulli (if Tautulli stopped at all)

• from the log of my Tasmota plug (attached below; time is -2h for whatever reason) I can see that power-consumption rose around 13:50h, rather quickly to ~130W, staying around that value

• an externally recorded syslog (also attached below) stops at 13:56h, reading SMART data

• the syslog is also spammed with a reoccurring message regarding "docker0", but did this since early in the morning; however, those stopped around 13:49h; coincidence?

• WebUI completely unresponsive, SSH as well. I had the same form of crashes before (server starting to run wild with power consumption, being unresponsive); I am not at home, and won't be for hours, so I can't tell if pushing the power button would have shut it down safely

• I hard-cut its power and switched the Tasmota back on, server boots normally (unclean shutdown lead to Parity check of course)

• that docker0 still spams the log after reboot

I attached logs and diagnositics, but something tells me it's as obscure as it was in the past :(

Things I tried since all those earlier crashes this year:

• switched RAM (passed memtest 5 times)

• switched CPU (to rule out 13th gen issues)

• recently, I switched the whole mainboard, newest BIOS installed (to get more SATA ports/throw out extenders)

• threw out all SATA extenders, all disks now attach natively to the board (as I thought it could've been the ASM cards)

• generally removed disks, and replaced SATA SSD cache with NVMe

The mainboard was switched some weeks ago, and on July 4th the Server went back to its designated place and ran there well till now. There were no crashes in this config before.
Before the mainboard switch, I deactivated all ASPM/C-State stuff inside the BIOS; it crashed less, but still did.
I also tweaked C-States/ASPM with this new Mainboard, to be able to save some power again (got great help in the german part of the forum)
Messages in syslog nearly always related to reading SMART data. I am not sure how accurate all timestamps are, the SMART-readings came a bit after it "went wild" on the power consumption (I never know if it's the disks or the CPU; during the Parity check now it uses 95-99W so I kinda assume both, to a degree). The disk that gets SMART-read last is never the same as the last crash.

After I changed and switched so much, I really don't know what else to try :(

lunas-diagnostics-20260720-1432.zip 260720_tasmotaHistory.csv 260720_lunas_syslog.log

Also unable to start in maintenance mode. Check the box, hit start and it just reloads the page.

Got it into maintenance mode after a couple reboots. Disk 7 xfs check says

Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.

Clicking fix results in

Phase 1 - find and verify superblock...
bad primary superblock - bad CRC in superblock !!!

attempting to find secondary superblock...
.found candidate secondary superblock...
verified secondary superblock...
writing modified primary superblock
sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129
resetting superblock realtime bitmap inode pointer to 129
sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130
resetting superblock realtime summary inode pointer to 130
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If the filesystem is a snapshot of a mounted
filesystem, you may need to give mount the nouuid option. If you are unable
to mount the filesystem, then use the -L option to destroy the log and
attempt a repair.  Note that destroying the log may cause corruption --
please attempt a mount of the filesystem before doing this.

tower-diagnostics-20260702-1337 2.zip

I have a disabled data disk (Disk 3) that I cannot re-enable due to a ghost Parity 2 slot (slot 29) in my superblock keeping mdNumDisabled=2. The UI never offers a Recover or Re-enable option because of this.

System:

• Unraid 7.3.1

• LSI SAS2008 HBA (new replacement)

• 4x Seagate Exos X20 20TB in array (BTRFS)

• Disk 3 serial: ST20000NM007D-3DJ103_ZVT64229

The problem:
Disk 3 went disabled after what appears to have been a backplane connection issue. SMART on Disk 3 is completely clean — no reallocated sectors, no pending sectors, no uncorrectable errors. The filesystem is intact and mounted.

However there is a ghost Parity 2 slot (slot 29 internally) that is permanently stuck as DISK_NP_DSBL. This keeps mdNumDisabled=2, which prevents Unraid from offering any re-enable or rebuild option for Disk 3.

Diagnostics:

mdState=STARTED

mdNumDisabled=2

rdevStatus.3=DISK_DSBL

diskState.29=4

rdevStatus.29=DISK_NP_DSBL

Superblock has diskState.29=4 at byte offset 3852.

What I've tried:

• New SAS cables

• New HBA

• Editing disk.cfg to remove slot 29 entries (reverts on boot)

• Writing remove 29 to /proc/mdcmd — returns "Invalid argument" whether array is started or stopped

• Patching superblock byte offset 3852 from 0x04 to 0x00 — cleared all disk assignments unexpectedly, restored from backup

• Maintenance mode — /proc/mdcmd still rejects writes

• Unraid updated from 7.2.3 to 7.3.1 during troubleshooting — no change

Questions:

1. Is there a supported way to clear a ghost disabled Parity 2 slot from the superblock?

2. Is there a tool or procedure to force-clear slot 29 and drop mdNumDisabled to 1?

3. Why does /proc/mdcmd reject all writes even with the array stopped?

Data is intact and array is running degraded. No urgency but need a path forward.

Thanks!

Seeking your guidance.

I have downloaded Palword from Apps with no modifications.  

Gave it time to download and watched it in the logs -- no issues.

The Docker is up and running.

I have stopped it to change the ini files:

    hoping to change the Server Name, Password, Admin Password -- then planned on logging in.

Well, I went to where the files should be and I am baffled.

/mnt/cache/appdata/palworld

I cannot seem to find this folder.

I do fave the shares set for primary storage to Cache-nvme -- and other apps do appear here get moved appropriately, I think.

Secondary storage is set to Array 

Mover action is set to Array -> Cache-nvme

Yet for the life of me I can not find my Pal

I have removed it and have reinstalled and continue to have the same issue, cant seem to find the folder so I can access the ini file.

Its been a few day so I have been trying to figure this out but not sure how or why it occurred.

I did originally notice this in early version 6 of Unraid — when I was trying to do Dedicated ARK server — same thing shows listed to show in /mnt/cache/appdata/ but when I go to find the files — no ARK; did not purse it then as I was too busy.  SO I believe what ever occurred has been an issue but I do have a few other files that do show up correctly which is why this troubles me.

Appreciate any help you can give.

I do not wish to go to v7.3. I was more stable on v6 and I'm anxious about the updates causing this.

This particular failure, I couldn't see the remote screen with my kvm. Any thoughts/ suggestions would be welcome, I'm absolutely exhausted. It also keeps wiping out my docker.img and I have to rebuild (service could not start). I've opted to do direct to disk to stop this from happening. Probably the most intensive process I have running is Frigate, which is pretty light on CPU when using coral + nvidia graphics card.

uhive-diagnostics-20260712-1210.zip

uhive-diagnostics-20260712-1210-PRE-RESTART.zip

But, I upgraded UNRAID to the latest version this afternoon and it will not let the array start saying that the USB GUID is blacklisted.

Any ideas?

Thank you for your quick and effective help !

My unraid server has been upgraded to 7.3.2 recently but I'm not sure the following issue is (only) related to this version update.

After normal boot I can't connect to unraid webUI from any other computer on my local network (no other hardware or router configuration change recently, few days ago I was still able to connect).

When I boot my unraid server in safe mode, I can connect to its webUI as usual.

I haven't see any error message during boot log when I connected my unraid server hdmi output to my computer screen.

For a silly reason I can't connect directly on this server : my root password has been generated and stored in a password manager and keyboard default conf is qwerty (I have an azerty keyboard)...too long and too complex to enter this password (I f******g don't know on which key I have to click ;-).

As I am an unraid newbie I really don't know what I can diagnose from these diag files attached.

Any help would be really warmly welcome !

Thank you !

seilnetmemini-safemode-diagnostics-20260719-1822.zip

orion-diagnostics-20260718-0345.zip

Most of the time I unassigned those and reassigned them to activate them, and that's it.

Sometimes, like now, that does not help. Either while the data rebuild is running or after the rebuild is done, the disk will go into the error state again.

That's what happened again:

Disk 2 error disabled -> reassigned -> rebuild failed -> reassigned -> rebuild successful -> a few hours later, error disabled again...

A few days after, Disk 3 also wants to be in an error state.

Does anyone have an idea why this keeps happening? I'm tried of worrying about my data.

Are the drives the issue here? Unraid does not recommend you use SMR drives but they should work: https://unraidcalculator.com/drive-recommendations.html

The SMART data looks fine.

In the last thread I made the conclusion was a Hardware issue.

Maybe there still is and I'm not seeing it?

biggie-diagnostics-20260719-1330.zip

I tried search the System Log for errors for the past 5000 lines and didn't find anything, so I'm hoping you folks could help.

Attaching diags below.

Thanks.

bigdaddy-diagnostics-20260719-1102.zip

Kind regards

Jens

tower-02-hobby-diagnostics-20260719-1030.zip

5 disks plus 2 parity on one, and 7 disks plus 1 parity on the other.

At first I ran Parity-Checks every 30 to 60 days. More recently I seem to remember to do it at 120 or more day intervals. It takes in the neighborhood of 25 to 30 hours to run the parity-check on each system.

No errors ever found on either system.

Any input on how often to run parity checks?

I am looking for some advice on whether anyone in the Unraid community is already doing something similar to this, or whether there are any Docker containers/plugins/projects I should be looking at.

Background

I work in finance and recently started a new role at a smaller business that is very proactive with AI and software adoption.

The company is currently moving from ChatGPT to Claude, mainly because of Claude’s connectors and the way it can interact with business systems. For context, I currently have Claude connected to Slack, OneDrive, Google Workspace (Gmail, Calendar, Google Drive), etc.

From a security/data perspective, my understanding is that Claude Team / Claude for Work data is not used for model training by default, unlike some consumer/default AI products:

https://privacy.claude.com/en/articles/7996868-is-my-data-used-for-model-training

Over the last few weeks, the way I carry out my finance role has changed significantly. For example:

• Document review — I no longer need junior members of the finance team to summarise large documents such as contracts, lease agreements, finance agreements, etc. Claude can produce the first draft and I review/check the output.

• Context gathering — Claude often has more context than a new junior team member, because it can pull relevant information from Gmail, Slack, Google Drive and OneDrive.

• Excel work — I no longer have to build every complex workbook manually. I can tell Claude where the month-end data is, which template to roll forward, and what outputs I want. When working directly in Excel, I can ask it to make changes across multiple tabs while considering the wider workbook context.
  

I have only recently started this role, but I can see that a large amount of data entry, month-end processing and reporting could be automated over the next few months - this isn't AI hype, it genuinely is the case where you work with data sets and routine tasks that computers are better at than humans.

The main finance role left is likely to be business partnering, review, judgement, and being the human interface with the rest of the business.

Important caveat: I do not think this removes the need for qualified finance professionals. In my view, it only works properly if the person prompting/reviewing Claude understands accounting standards, finance systems, controls, reporting and process design.

Personal Unraid Use Case

This brings me to how I would like to use Claude, particularly Claude Cowork, in my personal/home setup.

My Unraid server already contains a lot of structured files and datasets. In effect, these shares are the datasets I would like Claude to interact with. At the moment, Anthropic’s Cowork GUI seems to be aimed at Windows and macOS desktop use. Ideally, I would like something closer to the following:

Unraid server
└── Docker container / Web UI / MCP server
    └── Controlled access to specific shares only
        ├── AI_Workspace
        ├── Project folders
        └── Output folders

The ideal setup would be:

• Claude accessible through a browser-based Web UI.

• Claude able to access only specific Unraid shares, not the whole server.

• A dedicated “working area” share for AI tasks.

• Potential use of local or remote MCP servers so Claude can interact with other services/containers in a controlled way.

• Ideally something containerised, auditable and easier to control than giving a desktop app broad access to mapped network drives.
  

For context, MCP is the Model Context Protocol, which is intended to let AI applications connect to external systems, tools, files and workflows in a standardised way. Claude also supports custom connectors using remote MCP across Claude, Cowork and Claude Desktop, although that feature is still described as beta.

Example Use Cases

Some examples of what I would like to do:

1. Process files dropped into a specific Unraid folder and turn them into a spreadsheet or report.

2. Summarise new documents added to a project folder.

3. Produce a daily digest of Docker container errors/warnings.

4. Check the status of selected Docker apps and provide a plain-English update.

5. Search a defined project share and answer questions using only the files in that share.

6. Potentially interact with other containers through MCP/API wrappers, rather than giving Claude direct shell or Docker socket access.

Security Boundaries Required

I would not want Claude to have access to the whole server. Ideally it would only have access to its own share/project workspace:

/mnt/user/AI_Workspace

Rather than:

/mnt/user/appdata
/mnt/user/system
/mnt/user/domains
/mnt/user/backups
/boot
/var/run/docker.sock

I am also conscious that a generic filesystem tool may be too broad. A safer approach may be a purpose-built MCP server exposing only specific tools such as:

list files
read file
write output file
search workspace
summarise logs
get docker status

Rather than giving it unrestricted shell access.

Questions

Has anyone here implemented anything similar on Unraid?

Specifically:

1. Is there already a Docker container that provides a Claude/Cowork-like Web UI with access to mounted Unraid shares?

2. Has anyone set up a remote MCP server on Unraid for Claude?

3. Are there any Community Apps, plugins or GitHub projects I should be looking at?

4. Is the better approach simply to run Claude Desktop/Cowork inside a Windows VM and map a single Unraid share into that VM?

5. Has anyone safely exposed Docker/container status to an AI assistant without giving it direct Docker socket access?

6. Are there any obvious security pitfalls I should be thinking about before experimenting with this?

At the moment, my fallback idea is:

Windows VM on Unraid
→ Claude Desktop / Cowork
→ Mapped network drive to one dedicated Unraid share only
→ No access to appdata/system/backups

But I would prefer a cleaner Docker/MCP/Web UI approach if one exists.

Interested to hear whether anyone has already gone down this route.

Thanks!

Geefle

First of all, thanks for all the help so far

I have a disk, now that I am back from holidays, thats made an error, or more.

I have the smart and dia here:
ST20000NM007D-3DJ103_ZVT5ZA0F-20260713-1127.txttdk-diagnostics-20260713-1121.zip

I hope they will help.

I have swapped the cable, and from what I see, the disk is fine? :) I am NOT the best at this, so I am very sorry if I have missed something or can seam a bit slow.

Could I just run a new config and see how it goes?

Thanks agian guys :)

I restarted the parity check and when it reached 12gb the parity drive started showing UDMA CRC errors and froze the check.

I installed a new parity drive due to the old one having sync errors being reported and now during the parity rebuild, it has been extremely slow and is now at 0.3% and has not changed in at least 10 hours.

Here is a screen grab of the Array Devices

And here is the Array Operation

While typing this up, the array is now showing read errors on drive 4 so I have attached the diagnostics from just before I started typing this post and another one from just now after the read error was reported.

I do still have the old parity drive that I have not touched and I have a spare 4TB drive in the unassigned disks if I need to connect either one of those for testing.

The only thing I use the server for is as a video server (Jellyfin & Emby) and a few backup documents. My end goal is to get things back to normal and then offload the videos to a stack of bluray discs incase this happens again.

And shrink the array to maybe only 12 - 16tb saving the other discs as emergency replacements.

tower-diagnostics-20260714-1917.zip tower-diagnostics-20260714-1956.zip

So what I am wondering now is what, if anything, will happen when I swap out my CPU from AMD Ryzen 5 3600 to a AMD Ryzen 7 5700G? I'm not swapping out the motherboard or anything else, and I will free up a pci express port since the new CPU also have a GPU.

Most of my User shares are missing and this is causing issues with several of my docker containers. I think the error above is simply because something couldn't see those shares. No drive/SMART errors are shown.

Posting diagnostics. Any help is appreciated.

media-server-diagnostics-20260716-0739.zip

EDIT: Just stopped array and attempts to restart have failed (array configuration is valid). Going to reboot now that logs were supplied

The system has run fine for several years. The boot drive is a Samsung flash drive that is attached to the USB header on the motherboard. I have not touched anything to do with the boot drive in a long time.

I believe the system is running Unraid 7.2.2

I Googled and there doesn't seem to be much on this topic. I am guess that the issue is that my flash drive is not working.

I've purchased a domain name for accessing unraid, and personal/internal docker containers.

I've successfully used another domain name of mine, with SWAG and Tailscale for accessing other certain containers, but I'm looking to see how it might be possible to use my domain name:port for containers, as a generic config; as opposed to configuring a SWAG Proxy for each one, every time I add a new container.

Also - accessing my domain name as opposed to the Tailscale Magic DNS address for my Unraid Server would be cool.

There must be a way to achieve this? Both for Tailnet-only & Internet access.

Thanks!

Kev

I have not been able though to install Nextcloud AIO directly on unraid with docker and Tailscale with a Tailscale domain so the site is only available on my local Tailscale network.

I have looked but not found a way to do  Unraid docker, Tailscale, nextcloud AIO using Tailscale domain on local network only without exposing to internet.

Can anybody point me in the right direction?

I tried to install Unraid from a USB drive to an SSD, just as the wizard instructed.

Now, after booting, I keep getting this message:

error: lookup:2159:file “bzimage” not found

error: loader...

I only did this because my USB drive went into read-only mode after the update.

How can I fix this problem, and where can I find my backup on the site?

Best regards and thanks