MowMdown

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

Just hit "skip onboarding" at the bottom

It has to be after a crash/reboot, this is the same diags

You will just need to post the diagnostics again, it already anonymizes the info as long as you check the box.

Also, please go and enable the syslog server and where it says "remote IP" just put in localhost and enable it and have it save to any of your shares. Typically hardware crashes are likely due to hardware like a failing PSU or bad RAM. If you want to test ram you can boot MemTest86 from the unraid boot menu and let that run for a period not less than 24 hours. This is necessary to try and rule out hard to find faults. Next time if it happens and the syslog server will save the log so we can better see what might have happened right before it crashed.

This is a plex issue, you will want to take this to the plex forums. In all reality it's likely the web browser client.

Please post diagnostics

I didnt see any mkfs/wipefs 'es logged? what leads to you suspect disk2 was possibly unmountable/formatted? also his shares files says F----------h shareUseCache="prefer" # Share exists on nvme_unten_immich M-------k shareUseCache="yes" # Share exists on disk1, disk2, disk4, disk5 The 2nd of the two being the external libarary mapped via /mnt/user/Mediathek/<users> Which I assume are the two shares containing the immich photos However my advice still stands, Update immich to v3 which will do a comparison to photos on disk vs what the database thinks exists to know for sure if any are missing. Otherwise assume they were user deleted.