dj13990

Thanks, everyone. It looks like it was the ZFS Unraid 6 plugin. Once I removed that, everything seemed to work normally.

Dumb question. How do I access the plugins in Safemode to rename the .plg file?

Hello all, I followed the instructions to upgrade my parity drives, and everything was working fine. However, after the second parity was completed and I rebooted, I noticed that the array would not start; it just hangs on the "starting" screen. I tried safe boot, and everything worked fine there. When attempting to obtain diagnostics during normal boot, the system hangs again. I ran the diagnostic terminal command and checked the USB drive, but I couldn’t open the diagnostic file that I copied. I am attaching the diagnostic file from safe boot, along with the current one and a syslog file. Any help would be greatly appreciated. unraid-diagnostics-20250219-0447.zip unraid-diagnostics-20250219-0535.zip unraid-syslog-20250219-1021.zip

So you are correct and the NVME failed. Getting a warranty replacement now. Thank you

I will try it in a new slot and keep you posted. Thank you

I had a bad drive in my array and I finally replaced it. After powering on, my NVME drive is now showing Unsupported or no file system. I was using this as a drive for my docker containers. I didn't notice this until after I started the array and it started to rebuild the bad disk. Its not apart of the array so I have not stopped it. Any thoughts on how I may be able to fix this? unraid-diagnostics-20230715-1638.zip

I get the same error: Something really wrong went on during get_content Post the ENTIRE contents of this message in the Community Applications Support Thread OS: 6.12.0-rc2 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Language: No data was returned. It is probable that another browser session has rebooted your server. Reloading this browser tab will probably fix this error

+1