# Pironman 5 Long shutdown Delay after shifting OS to NVMe SSD

**URL:** <https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929>\
**Category:** General\
**Created:** [August 16, 2026, 5:15pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929 "2026-08-16T17:15:46Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 16, 2026, 5:15pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/1 "2026-08-16T17:15:47Z")

</div>

Hi

I recently upgraded from a slow samsung Micro SD card to a fast 128gb NVMe SSD to boot my OS on my Pironman 5 case. I have configured my RaspberryPi 5 to prioritize NVMe boot over sd card. The boot time and overall system speeds increased a lot after forcing my Raspberry pi 5 to gen 3 speeds to properly utilize my SSD, but the shutdown time got painfully slow, taking roughly 30-60 seconds to power off. i did notice one thing. if I have any sd card connected in the sd card extender slot, the shutdown time reach to original 1-3 seconds. but when kept empty, its just slow.

Take it like this:  
SD card present = Fast shutdown time  
SD card not present = Slow shutdown time

Any ideas on how can i make my shutdown time faster while keeping my sd card slot completely empty?

---

<div class="post-metadata">

**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\
**Post date:** [August 17, 2026, 10:12am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/2 "2026-08-17T10:12:51Z")

</div>

Thank you for your post. Since your system is booting from the NVMe SSD, the shutdown process itself does not require the SD card.

From your description, this may be related to how Raspberry Pi OS handles the SD/MMC interface. When an SD card is inserted, the system detects it normally. When the slot is empty, some device or service may be waiting for the SD/MMC interface to respond or time out during shutdown, causing an extra 30–60 second delay.

Please perform a slow shutdown with no SD card inserted, then reboot and run:

```auto
journalctl -b -1 | grep -iE "mmc|sdhci|timeout|stop job|failed"

```

Please send us the output. This will help us identify exactly what the system is waiting for during shutdown, and we can then look for a way to configure the system to shut down quickly even without an SD card inserted.

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 17, 2026, 3:09pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/3 "2026-08-17T15:09:07Z")

</div>

Hi,

Here is the journal output:

Aug 17 20:17:01 RaspberryPi-5 kernel: sdhci-brcmstb 1000fff000.mmc: Got CD GPIO  
Aug 17 20:17:01 RaspberryPi-5 kernel: mmc1: CQHCI version 5.10  
Aug 17 20:17:01 RaspberryPi-5 kernel: mmc0: CQHCI version 5.10  
Aug 17 20:17:01 RaspberryPi-5 kernel: mmc0: SDHCI controller on 1000fff000.mmc [1000fff000.mmc] using ADMA 64-bit  
Aug 17 20:17:01 RaspberryPi-5 kernel: mmc1: SDHCI controller on 1001100000.mmc [1001100000.mmc] using ADMA 64-bit

here is the screenshot of the terminal output:

 ![Screenshot_20260817_20363812](https://canada1.discourse-cdn.com/flex029/uploads/sunfounder/original/2X/4/44f562f9a7d2b6b8dfdc938ef8b48193f47745a7.png)

---

<div class="post-metadata">

**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\
**Post date:** [August 18, 2026, 10:01am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/4 "2026-08-18T10:01:51Z")

</div>

From the logs you provided, we did not find any obvious errors related to the Pironman 5. The mmc0/mmc1 entries are standard kernel initialisation messages for the SD/MMC controller.

Since the shutdown delay only occurs when no SD card is inserted, we would like to check whether the system still has any leftover mount configurations referencing the SD card.

Please run the following command and send us the full output:

```auto
cat /etc/fstab

```

If there are no SD‑card‑related entries in fstab, and all other Pironman 5 functions are working normally, then the 30–60 second shutdown delay is likely caused by the operating system waiting for a device or system service to time out during shutdown – rather than an issue with the Pironman 5 itself.

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 18, 2026, 12:36pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/5 "2026-08-18T12:36:43Z")

</div>

Here is the output of the terminal.

 ![mlto1](https://canada1.discourse-cdn.com/flex029/uploads/sunfounder/original/2X/8/83942e8d7a475a90b6acb64f1d03f5661fcb40c0.png)

i actually did some research and found out that in the line “Aug 17 20:17:01 RaspberryPi-5 kernel: sdhci-brcmstb 1000fff000.mmc: Got CD GPIO”, you can see that it says “Got CD GPIO”, which means that the raspberry pi 5 is actually detecting a physical sd card connected. but there is nothing connected, except the sd card extender.

what i think is the issue is that the sd card extender is actually making the rspberry pi firmware think that there is an sd card connected, as the raspberry pi 5 actually has a switch kind of mechanism in the sd card slot that closes when we insert an sd card. so i guess thats what is causing the issue. it is trying to unmount a sd card that it is falsely detecting during the shutdown, causing a delay. i have attached photos for better understanding.

 ![IMG_20260818_175120](https://canada1.discourse-cdn.com/flex029/uploads/sunfounder/original/2X/1/1f6741d92d473b69813f9476216e13467bdf86aa.jpeg)

 ![IMG_20260818_175214](https://canada1.discourse-cdn.com/flex029/uploads/sunfounder/original/2X/8/8d646f683678cedc760d7a69004c2f1062b4c12b.jpeg)

i guess there is no hardware issue here. everything is working fine. do you have an software/ firmware fix so that i can disable the sd card detect completely and improve boot speeds?

---

<div class="post-metadata">

**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\
**Post date:** [August 20, 2026, 7:51am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/6 "2026-08-20T07:51:36Z")

</div>

We have reproduced the issue and confirmed that the shutdown delay is caused by the SD card extension board being connected, even when no SD card is inserted.  
We also tested the available software configuration options, but they did not resolve the issue. As a temporary workaround, if your system boots entirely from the NVMe SSD and you do not need the SD card slot, please disconnect the SD card extension board. This will restore the normal shutdown time.

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 20, 2026, 10:48am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/7 "2026-08-20T10:48:26Z")

</div>

Thank you for verifying the root cause and clarifying things up.

As a temporary workaround, disconnecting the extension board is unfortunately not physically viable. The Pironman 5 standoffs are slightly shorter to accommodate the exact thickness of the sd card extender. Removing the board causes the Pi 5 to sit un-level, creating a physical flex across the board after tightening the mounting screws. I can get it done by replacing the standoffs or use spacers. Furthermore, i still require the slot for occasional secondary OS testing.

Since a software fix isn’t available yet, i will stick with my current setup and i would either bare with the shutdown time, or insert a cheap sd card into the slot for faster shutdown.

Thanks.

---

<div class="post-metadata">

**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\
**Post date:** [August 21, 2026, 10:43am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/8 "2026-08-21T10:43:02Z")

</div>

Thank you for confirming the root cause with us and for the feedback. A software-side fix is still under evaluation, and we will keep an eye on this issue in future updates. The workaround you mentioned — inserting an SD card into the slot — is indeed a viable temporary solution, and replacing the standoffs or adding spacers would also work.

If anything new comes up or you need further assistance, please feel free to reach out to us on the forum or by email anytime.

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 21, 2026, 6:10pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/9 "2026-08-21T18:10:29Z")

</div>

Thank you for the update and for taking these mechanical workarounds with the engineering team. Eagerly waiting for a software patch to fix the slow boot soon.

Thank you for the continued support and for the highly responsive assistance regarding my issue.

---

<div class="post-metadata">

**Author:** ![gauge\_boson](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gauge\_boson](https://forum.sunfounder.com/u/gauge_boson)\
**Post date:** [August 22, 2026, 1:20pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/10 "2026-08-22T13:20:14Z")

</div>

Good afternoon

I have just returned from Thailand and was catching up with the latest SunFounder news when I spotted this post: this is exactly the same situation I find myself in, and I have been trying for 10 months to understand why there is such a long delay of up to a minute! Thank you for reassuring me that there is nothing wrong with my setup.

Obviously this is a problem that needs to be fixed because, even though a lot of us boot directly from NVMe, we absolutely want the SD card slot available without having to mess around with reconnecting it.

The SunFounder team are amazing, and they have responded extremely quickly and positively to all genuine issues [like this one] where switched-on users provide credible and reproduce-able fault conditions.

@OpenLoop I am also jealous of you being able to get gen 3 speed; being a 5 Max, I am stuck with gen 2, so it was silly of me to not properly read the spec before I bought a dual-port that I will probably never use!

I look forward to a SW fix to this soon.

Best wishes, Nick

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 22, 2026, 3:28pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/11 "2026-08-22T15:28:44Z")

</div>

Hi Nick

@gauge_boson I am glad that this post helped you identify the root cause and reassuring that that your pironman 5 max setup has nothing wrong. I am too eagerly waiting for a software fix for faster shutdown speeds.

Regarding the slow gen 2 speeds on the pironman 5 max, this is indeed due to the dual nvme slot extension board. The splitter chip has to split the bandwidth for two nvme slots, which cannot support gen 3 speeds. I have personally never tested the pironman 5 max, so I genuinely dont know the actual issue, but this one seems to be the most obvious one. This is the exact reason I didnt consider the pironman 5 max. But the max is great when you want more storage or want to use the hailo AI acceleration module. you could try dropping out your ssd brand name and model to check compatibility and see if sunfounder or the community has a workaround for it.

Thanks.

---

<div class="post-metadata">

**Author:** ![gauge\_boson](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gauge\_boson](https://forum.sunfounder.com/u/gauge_boson)\
**Post date:** [August 23, 2026, 1:13am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/12 "2026-08-23T01:13:19Z")

</div>

Thank you for your reply.

I have the 2TB Samsung 990 PRO PCIe 4.0 which I know is well over-specified for this. I was looking to the future, and the price was a lot cheaper when I bought it.

Best regards  
Nick

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 23, 2026, 12:00pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/13 "2026-08-23T12:00:35Z")

</div>

That ssd is completely compatible with pironman 5 series case. I dont think you will be able to get gen 3 speeds, as the pironman 5 max hardware itself is limiting the gen 3 speeds. But yes, much more faster than the sd card.

---

<div class="post-metadata">

**Author:** ![gauge\_boson](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gauge\_boson](https://forum.sunfounder.com/u/gauge_boson)\
**Post date:** [August 23, 2026, 12:52pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/14 "2026-08-23T12:52:19Z")

</div>

In fairness, the latest documentation does emphasise the speed limitation; I mainly use this as my home office machine, so it is plenty fast enough for what I need.

When a fix is found for the empty SD slot causing delays, I will be a very happy man 😊

---

<div class="post-metadata">

**Author:** ![gauge\_boson](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gauge\_boson](https://forum.sunfounder.com/u/gauge_boson)\
**Post date:** [August 24, 2026, 3:20am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/15 "2026-08-24T03:20:25Z")

</div>

I have just read this related post: [https://forum.sunfounder.com/t/extra-delay-to-shutdown-reboot/1235](https://forum.sunfounder.com/t/extra-delay-to-shutdown-reboot/1235)

It looks like a known issue that has been unsolved in over 2 years and numerous updates to the SD extender board.

---

<div class="post-metadata">

**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\
**Post date:** [August 24, 2026, 9:17am UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/16 "2026-08-24T09:17:32Z")

</div>

Thank you for your kind words and trust! We have shared the mechanical workarounds and the software fix request — including feedback from you and other users — with our engineering team, and the software-side fix is currently under evaluation. As soon as there is any progress (an evaluation result or a patch release), we will notify you in the forum thread right away. If you have any other questions, please feel free to reach out to us anytime.

---

<div class="post-metadata">

**Author:** ![OpenLoop](https://avatars.discourse-cdn.com/v4/letter/o/c77e96/32.png) [@OpenLoop](https://forum.sunfounder.com/u/OpenLoop)\
**Post date:** [August 24, 2026, 4:01pm UTC](https://forum.sunfounder.com/t/pironman-5-long-shutdown-delay-after-shifting-os-to-nvme-ssd/4929/17 "2026-08-24T16:01:09Z")

</div>

I did read that before starting this topic, hoping that they would have a fix. they couldnt find a solution to it as the root cause was unknown.
