How to Kill a Pi

Ok, I was stupid I admit … lazy as well! But I don’t expect my Pi to die

I have been building custom pi images and I really should have just used a docker container on my arm64 Mac, but as stated I was lazy and was just building direct on a Pi4. Build times were only 17 minutes which wasn’t a massive problem, and I could optimize to less than 3. Now I’m working in a container and a full build from scratch is only 3 minutes though it’s much faster to iterate

anyway, I’d done maybe 5 or 6 builds and then in the middle of a build the ssh session froze and that was it… put it on a monitor and no output … went to reflash the SD and instead of 32GB diskutil in Mac complained, only saw 32mb and Raspberry Pi Imager complained as well

today I put a brand new, flashed SG in and still nothing. There’s power being drawn and the fan is spinning so the 5v rail seems good. But the rest is dead… no green activity light but a solid red LED

I was stupid and lazy, the worst I expected was to kill the SD, not the entire Pi. Rather surprised

Anyone think of debugging step I might have missed?

A little video - I stopped too early just before the green LED went out! Drawing 5W

What’s concerning is, since it was not just the SD that died, having an NVME could have resulted in the same outcome

maybe I need to get a console on it. I see no reason for anything other than the SD to die - if it was overheating it should have throttled back. Given I don’t even see the rainbow splash on power up and the BCM chipset boot starts on the GPU though it doesn’t look good

3.3v rail maybe dead?