Last week after a few sudden losses of power from a bad breaker and UPS dying too quickly before shutdown could complete, This log showed up. "emhttpd: error: malloc_share_locations, 8119: Operation not supported (95): getxattr: /mnt/user/Media"

Following this log, all shares dissappeared except for /mnt/user/Media listed in the log. On top of it, my second Parity drive and Disk16 were unavailable. I shut down the server, pulled the 2 problem drives and tested them in another PC. They both passed smart tests and are OK. I put them back into the system, started the array and during the parity sync / data rebuild, I was alerted to some logs of corruption. Stopped the array, started it into maintenance mode and repaired the corruption on Disk9.

Started the array back up without the second parity drive to accelerate the data rebuild process (Unsure if this will help but seems to) and about 1.5 days into the data rebuild, this log shows back up. I have shut down the docker and vm service in the mean time and am thinking to finish the data rebuild before rebooting again.

I have attached the current diagnostics file. Any input on what is causing this issue or suggestions would be greatly appreciated.

prime-diagnostics-20250603-2255.zip

Jun 3 22:27:53 Prime smbd[3936123]: make_connection_snum: canonicalize_connect_path failed for service proxmox, path /mnt/user/proxmox

Problem appears to start with this share, and causing a lot of spam, first reboot and post new diags after array start

Here are the diags after a reboot and array start.

prime-diagnostics-20250604-0818.zip

Looks OK for now, but you need to clean up the shares, click on shares, then clean up, and if new share related errors started being logged try to get the diags right after that.

Thank you for the suggestion. I have just ran the clean up. I will monitor the logs closely for the time being.