I updated to 7.3.1 a month or so ago and the server was running fine. A few days ago I patched it to the 7.3.2, rebooted fine and all worked. Last night, the server seemed to lock up and I was unable to SSH in to reboot it, and had to reset it (unclean shutdown). No idea why. the diag are attached.

Edited Friday at 10:32 AM3 days by plunderisley
Removed diagnostics

Enable the syslog server and post that if it happens again. Also make sure this has been taken care of, even if it wasn't an issue before: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

21 minutes ago, JorgeB said:

Enable the syslog server and post that if it happens again. Also make sure this has been taken care of, even if it wasn't an issue before: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Attached are the syslog for this month. I don't see anything there of any mention of the last night (well would have been around 4am 4th Aug) server lockup. I'm quite sure I did all those c-state changes before but I will double check. Sunday morning the docker containers update. I did the 7.3.2 update sun afternoon or evening time.
It is a 5800x Ryzen 7 and a ASRock X470 mobo.

Edited Friday at 10:31 AM3 days by plunderisley
Removed syslog

You seem to have a docker container in a boot loop, consider addressing as it might be causing issues with the rest of the system

I have an issue with Unraid OS 7.3.2 when I update my Lincstation N2 to several days ago. Liking the idea of being able to boot from internal drives istead of a USB stick drive. So I set the internal boot to work and when it finally stopped, I was informed that the drive I had chosen for the internal boot was "Unmountable: unsupprotable no filesystem. I was also inform that there was an Unassigned Device, which contained Dev1 DUTB42-0x60c35e18 - 125GB (mmcblk0) . In the Array Operation (with array started) It informs that there is an "Unmoutable disk present" and underneath the following, Boot KODAK_SSD_1TB_E332MX14300149(nvme1n1.

I have tried reverting to the Previous OS and following the setup given in a youtube video Space Invader1, I stll getthe same results.

What am I doing wrong. I have tried reformating the problem drive, no change butvall I get is more of the same. Any Idea's would be appreciated.

Attach Diagnostics ZIP to your NEXT post in this thread.

Being a relative newby to Unraid, I am unsure how obtain a "Diagnostics ZIP". I would appreciate pointer in this matter.

Found it

unraid-7.3.2.txt domain.cfg bootpool.cfg pooled.cfg boot.cfg docker.cfg zfs.conf savedpcidata.json editor.cfg super.dat ident.cfg pci_diffs.json network-extra.cfg network.cfg go.txt disk.cfg listen.txt SOLIDIGM_SSDPFKKW020X7_SDC7N458710307D1H-2026-05-27 pooled (nvme0).txt KINGSTON_SNV3S2000G_50026B738398DE87-2026-05-27 pooled3 (nvme2).txt eui.00000000000000000026b738398de875-2026-05-27 pooled3 (nvme2).txt eui.aca32f037500b45d2ee4ac0000000001-2026-05-27 pooled (nvme0).txt CT2000BX500SSD1_2442E98F405D-2026-05-27 pooled2 (sdc).txt KODAK_SSD_X350_1TB_E332MX14300149-2026-05-27 boot (nvme1).txt nvme.126f-453333324d583134333030313439-4b4f44414b20535344205833353020315442-00000001-2026-05-27 boot (nvme1).txt Samsung_SSD_870_QVO_8TB_S5SSNF0W518704K-2026-05-27 pooled4 (sdb).txt SanDisk_Ultra_Fit_050122f234b93a78b82b093a8b4de9d85d23b5714b2b981068c31f373d795819981100000000000000000000971465f3ff101210835581078a276a12-0-0-2026-05-27 flash (sda).txt cmdline.txt btrfs-usage.txt drm.txt plugins.txt motherboard.txt iommu_groups.txt ntp.txt aspm-status.txt ethtool.txt folders.txt sshd.txt lsmod.txt lsscsi.txt loads.txt testparm.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt servers.conf.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt graphql-api.txt syslog-previous.txt syslog.txt appdata.cfg system.cfg shareDisks.txt P--------m.cfg

5 minutes ago, Steve731 said:

Found it

unraid-7.3.2.txt domain.cfg bootpool.cfg pooled.cfg boot.cfg docker.cfg zfs.conf savedpcidata.json editor.cfg super.dat ident.cfg pci_diffs.json network-extra.cfg network.cfg go.txt disk.cfg listen.txt SOLIDIGM_SSDPFKKW020X7_SDC7N458710307D1H-2026-05-27 pooled (nvme0).txt KINGSTON_SNV3S2000G_50026B738398DE87-2026-05-27 pooled3 (nvme2).txt eui.00000000000000000026b738398de875-2026-05-27 pooled3 (nvme2).txt eui.aca32f037500b45d2ee4ac0000000001-2026-05-27 pooled (nvme0).txt CT2000BX500SSD1_2442E98F405D-2026-05-27 pooled2 (sdc).txt KODAK_SSD_X350_1TB_E332MX14300149-2026-05-27 boot (nvme1).txt nvme.126f-453333324d583134333030313439-4b4f44414b20535344205833353020315442-00000001-2026-05-27 boot (nvme1).txt Samsung_SSD_870_QVO_8TB_S5SSNF0W518704K-2026-05-27 pooled4 (sdb).txt SanDisk_Ultra_Fit_050122f234b93a78b82b093a8b4de9d85d23b5714b2b981068c31f373d795819981100000000000000000000971465f3ff101210835581078a276a12-0-0-2026-05-27 flash (sda).txt cmdline.txt btrfs-usage.txt drm.txt plugins.txt motherboard.txt iommu_groups.txt ntp.txt aspm-status.txt ethtool.txt folders.txt sshd.txt lsmod.txt lsscsi.txt loads.txt testparm.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt servers.conf.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt graphql-api.txt syslog-previous.txt syslog.txt appdata.cfg system.cfg shareDisks.txt P--------m.cfg

For future reference, just attach the zip file, no need to extract the contents.

7 minutes ago, Steve731 said:

Found it

Please start your own thread; this one is still active and trying to help multiple users can get confusing, even if the issue appears to be related.

I justvdragged the file to the attachment window and they just opened. I thought I was dragging a zipper file across from the diagnosic folder on my Mac book pro

2 hours ago, plunderisley said:

Attached are the syslog for this month. I don't see anything there of any mention of the last night (well would have been around 4am 4th Aug) server lockup.

Yep, there's nothing relevant logged, suggesting more a hardware issue.

58 minutes ago, JorgeB said:

Yep, there's nothing relevant logged, suggesting more a hardware issue.

I'll update the BIOS to the latest version and go through the c-state fix info again and configure it. I did a memtest86 a few months ago and for about 24hrs of running there were no issues. All the other attached devices seem to be fine. The stuck docker container on a boot loop was before the update.

Just to post an update:

I did a full BIOS update, re-did the settings in the BIOS for the Ryzen CPU (cstate and other recommend changes) and also lowered the max TDP of the CPU. Waited 14+ days and did a parity check (last one was months ago). Finished with 0 errors.

Seems it's stable now. Maybe the BIOS version had issues.