Esperon

After replacing the ASMedia controller with a 5 sata port JMB585 Chipset controller, 'soft' reboots work fine and all drives show up properly on either full shutdowns or Unraid OS restarts.

I checked my BIOS fast boot setting, it was already disabled. I tried enabling some of the ASPM specific settings, but nothing helped. I'm considering looking for a different SATA controller to swap in.

Tested and found some additional details: After a reboot of my system on 7.1.3, with a full power cycle from me checking my BIOS version, the array came up fine showing all drives. Rebooted once again to be sure using the reboot button on the dashboard, and the drives do not show up properly this time... Shut down system using dashboard power button. Confirmed the system appears off, no lights, etc. (did not toggle the PSU), and hit the physical power button to power the unit back on. I have confirmed I can duplicate this by repeating either step above. Each time I reboot the system through the Unraid dashboard WebUI it fails to see the controller when it comes back up. When I shutdown using the dashboard shutdown button and then physically press the power button again to boot it back up, the drives show up as expected and the controller shows as expected in the ASPM-status log file, and the array appears normal and starts up fine. I've attached both diagnostic zips, one for both scenario: 7.1.3 - Missing drives after WebUI Restart button - servertwr-diagnostics-20250604-1415.zip7.1.3 - OK after shutdown - servertwr-diagnostics-20250604-1411.zip

I have also confirmed I am on the latest (last) version of my motherboards BIOS, 7.40 - Q170M vPro

Moved my SATA controller up one PCIe slot.Confirmed Unraid booted properly, all drives still showing as normal on 7.0.1Updated again, this time to 7.1.3, and still have the same issue, same drives not showing up. I see in the ASPM-status log file the following (from diagnostics zip), no ASMedia controller detected still: 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1) (prog-if 00 [Normal decode]) LnkCap: Port #17, Speed 8GT/s, Width x1, ASPM not supported LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk- 00:1b.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 (rev f1) (prog-if 00 [Normal decode]) LnkCap: Port #19, Speed 8GT/s, Width x1, ASPM not supported LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk- 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) (prog-if 00 [Normal decode]) LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM not supported LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk- 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1) (prog-if 00 [Normal decode]) LnkCap: Port #9, Speed 8GT/s, Width x4, ASPM not supported LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk- servertwr-diagnostics-20250604-1345.zip

servertwr-diagnostics-20250604-1143.zipAttached are diags from 7.0.1, running OK

I own a Silverstone CS382 case, and I am using a 4 Port PCIe SATA Card with 4 SATA Cable, 6Gbps SATA3.0 Expansion Card, ASMedia ASM1064 chip to connect the bottom half of the hot swappable bays. The drives in the bottom half no longer show up, and are missing on the array: Here is a snippet of my layout from 7.0.1, prior to upgrading from disk layout plugin: Here is what I see on the Array following the upgrade. When I click the drop down for these missing disks I can only select the unassigned drive, which is unused due to smart errors: Attached diagnostics, I have confirmed I am able to downgrade back to 7.0.1 and continue normal use without error, so unsure what could be occurring. Any tips appreciated. servertwr-diagnostics-20250603-1859.zip

I ran into a similar problem. Not sure why my Unraid SSH port was open. Specifically, I am running a Gitea container that is utilizing port 22 for SSH. Last night backups were made of my containers and their data, and my backup service automatically starts / stops the containers when the backup tasks are ran. My Gitea container failed to restart after backing up. From what I can see, the SSH port on Unraid itself became active. To validate this, I altered my Gitea containers SSH port from 22 to some random port number. This allowed Gitea to start without issue. When set back to port 22 for SSH it fails with the same error as the original poster. With my Gitea container set back to 22 and NOT running, I checked Under Management settings, I confirmed that SSH was set to NO. This was never altered, and I am the only admin for my server. I ran netstat -napt from the terminal and found: tcp 0 0 10.253.0.1:22 0.0.0.0:* LISTEN 21516/sshd: /usr/sb I set SSH to ON, applied, then turned it back off in Unraid management. Confirmed afterwards that the above port was not present when running netstat. Restarted Gitea without issue. Port 22 is now in use by my Gitea container: tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 5817/docker-proxy Port 22 is not forwarded on my router, and I didn't see any suspicious login attempts in my syslogs... Could this be a bug?