M.2 Hat and Pi 5 - Worked last night, now won't

Support
1

When I went to sleep last night, my new set up of Home Assistant on my new Pi 5 with the Pimoroni NVMe base was working fine. This morning it was down. I tried to SSH into the pi and nothing. I started to toubleshoot. I can SSH into the Pi if the NVMe base is not hooked up, but for some reason, not when it is. I tried to load the home assistant software again, no job, still can’t SSH into the pi. Tried to load the pi software again. Still can’t SSH into it if the base is installed. Finally, I tried another NVMe just to be sure that was not it, and still no joy. I’m at a loss. I can’t bring the pi up on a monitor (don’t have a cable, I ordered the wrong one, new one coming but not till friday) Any thoughts? I’ve disconnected and reconnected the ribbon cable. It does not look damanged. Everything looks good, it’s just stopped working. Any suggestions? I can’t really troubleshoot too much as it won’t come up with the base connected
Steve

2

BTW, it’s a refused connection on the SSH when the base is installed
Steve

3

and it gets stranger. I formated the drive, put it back in and it works fine. But I then put home assistant and it and it no longer works. I’m at a loss
Steve

4

it does not even look like the pi is booting. There is no activity on the light
Steve

5

I give up. Now I can’t even get the Pi to boot from the SD Card. Sending it back to Amazon
Steve

6

I lied, still playing with it. Got it running. The issues seems to be that the PI is no seeing the drive. fdisk shows:
Device Boot Start End Sectors size IDType
/dev/mmcblk0p1 8192 1056767 1048576 512m c W95 Fat32(LBA)
/dv/mmcblk0p2 1056768 62333951 61277184 29.2g 83 Linux

So it’s no seeing the other drive. So, I finally get things up. Use VNC to look at the drive and use RP imager to write the homeassistant image and do update and upgrade pluse it tells me to do sudo rpi-eeprom-update -a update. I go back and set the pi to boot from the NVMe and boot it up excect it does not boot up. I’m at a complete loss at what is going on
Steve

7

It usually should boot from the SD-card if it cannot detect the NVME. Unless you removed the SD-card from the list of devices to check.

Please reboot from the SD-card and check the system log sudo journalctl -b for messages about the NVME. Maybe this helps to find the root-cause.