MowMdown

fixes can be found in earlier messages in this forum thread. several fixes are listed.

I confused myself but ultimately unraid did the correct thing (which is what I originally suspected would happen). I have two pools /mnt/cache and /mnt/backup and then created a user-share through cli usingmkdir /mnt/user/backup which it correctly put on the cache pool so there was no conflict with my pool named backup. You are correct though, accessing the folder at /mnt/cache/cache and /mnt/user/cache (if settings are correct) would access the same files. FCP just complains about it I guess (I removed FCP long ago)

/mnt/user/cache and /mnt/cache/cache should not conflict. It's probably FCP being FCP (outdated warnings) Edit: As a test I created a user share named backup but also have a pool named backup. Actually it looks like unraid automatically symlinked it to my backup pool rather than keeping it a folder on my cache pool where I originally created it... how strange. Edit2: My mistake, it created it correctly on /mnt/cache (not /mnt/backup) that's my bad, all worked out fine.

I do find it quite odd that device sdb isn't reporting any partitions.

can you post a screenshot of the MAIN page on your nas showing all the disks?

Please post the output of wipefs /dev/sdb

Right because you have a mirrored boot pool with your data partition you would have to remove the now missing device from BOTH filesystems (btrfs and zfs) before the whole 2nd disk can be removed and re-assigned. Can you post the output of zpool status flash Edit: I found it in the diags: pool: flash state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J scan: resilvered 1.19G in 00:00:03 with 0 errors on Mon Aug 17 23:26:59 2026 config: NAME STATE READ WRITE CKSUM flash DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 nvme0n1p3 ONLINE 0 0 0 15148541010099398958 UNAVAIL 0 0 0 was /dev/sdb3 errors: No known data errors

I've deduced it to one of my installed plugins, just not sure which one yet, but I don't have many installed so finding the culprit shouldn't be difficult.. Edit: The problematic plugin is the "Dynamix System Buttons" plugin (probably should blacklist this plugin on 7.4.0)

Neither of my physical servers have a "power button" tab within power settings 😳

Im not sure if it's a related cause or a symptom of something else but one thing I notice in common when your disks are spun down and back up is the unraid flashbackup script runs each time.

create pool, assign disks to slots, click poolname and set fiilesystem and raid type, then start array and hit format checkbox

You will need to mount an external storage location in your current nextcloud instance, then copy all your data you store in NC to the external storage location. Then destroy the docker.img vdisk and re-create it as a folder, then reinstall all your containers. After that you will need to re-import all your NC data back into NC where it will be stored inside the docker filesystem once again. (you will have to setup NC from scratch again) If you had used the standard nextcloud container, you could have just saved your data to a share and it would have been accessible on the nas in a standard folder separate from docker.

Disk is having read/write issues likely due to splitters and/or the SATA cable. SMART on the disabled disk looks ok

can you start the array and post new diagnostics?

Say what now? That is not normal...

Nothing logged in syslog, I would just reboot and monitor for any abnormalities. You could also try updating unraid to a newer version with a different kernel version.

Please post the entire diagnostics zip

You will need to open a support ticket or email unraid support for them to move your license to the new TPM since you are ineligible.

Unraid runs entirely from RAM, if you run out, it crashes.

No telling, either the number stays 2 for a long time or it could rapidly increase and die. All you can do is keep an eye on it. If the reallocated sector number or the offline uncorrectable number goes up, prepare to replace the drive.

All you can do is test it and see the results for yourself.

Yes. Had you told us that in your first post, this all would have been solved right then and there lol. Unless you are in the same room on the same circuit where there is a straight wire between two outlets, you have to remember you are traversing the entire home's electrical system, through the breaker box, etc. powerline is like the last resort if WiFi doesnt work and you dont want to run a several meter long cable and you absolutely need a connection. And I would never use it for a bandwidth heavy task.

To my knowledge it doesn't have one. Just be sure to click the logout button when you're done.

SAS disks dont play nice with spin down known causes of disk spinup are appdata on the wrong disk(s) HomeAssistant unraid integration that polls the disks zfs master reads snapshots from zfs disks. There are no known bugs to my knowledge causing disk spinup Start by disabling all docker containers (stop the entire service) as well as disabling the VM service. If disks still spin up, disable plugins (reboot into safe mode or use the same mode plugin) also make sure you dont have any open SMB/NFS connections. as browsing the shares from another pc will wake them

https://docs.unraid.net/unraid-os/system-administration/secure-your-server/user-management/#reset-your-password The same steps apply. You may need to temporarily boot with another usb to access the drive or pull the drive and plug it into another PC