Bottom Line: Check Physical Seating and BIOS Detection Before Reinstalling ZimaOS
The original ZimaCube arrived with the M.2 card loose inside the chassis. That immediately changes the troubleshooting order. Before blaming the installer, verify the connector, gold contacts, mounting screw and whether BIOS can see the NVMe device at all.
Step 1: Power Down and Inspect the M.2 Hardware
Disconnect power, remove the top cover, and inspect the M.2 module for a bent edge connector, damaged gold fingers, cracked PCB, missing standoff or debris in the socket. Reseat the module fully and secure it so the card sits flat.
If the system was shipped with a loose board rattling inside, document the physical condition before repeated testing. Shipping damage is a hardware-support case, not something software should be expected to repair.
Step 2: Check BIOS → Advanced → NVMe Configuration
If BIOS does not list the drive, ZimaOS cannot install to it. Swap in a known-good compatible NVMe drive if available. If the second drive appears, the original SSD becomes the primary suspect. If neither appears, investigate the M.2 slot, adapter board, power or firmware.
The ZimaOS installation recovery is the safer software-side reference once BIOS detection is confirmed.
Step 3: Verify Linux Detection From the Installer
lspci | grep -i "Non-Volatile"
lsblk -o NAME,SIZE,MODEL,TRAN
dmesg | grep -i -E 'nvme|pcie|error'The nvme-cli tools provides standard NVMe commands. The Linux NVMe subsystem explains the kernel layer.
Multiple NVMe Drives Can Expose a Different Power Problem
A separate reply in the thread found that two drives were reliable while three or four failed during Linux probing, and external power changed the result. That is useful evidence for a multi-drive sled, but it should not be turned into a universal claim that Linux “draws too much current.” Treat it as a power-budget hypothesis to test with known-good power and fewer drives.
Do Not Keep Reformatting Drives That BIOS Cannot See
Partitioning, filesystem creation and ZimaOS installation all happen after hardware enumeration. If the device is missing at BIOS/PCIe level, formatting another disk does not fix the actual problem.
For current multi-NVMe hardware, the ZimaCube 2 storage provides a cleaner reference architecture.
When to Stop and Request Hardware Service
If the original loose M.2 module shows physical damage, BIOS never detects known-good NVMe media in the slot, or the board behaves inconsistently after reseating, stop destructive testing and contact hardware support with photos, serial details and the BIOS detection result.
Use a Minimal-Hardware Test to Separate Power From PCIe Problems
If several NVMe devices are involved, reduce the system to one known-good drive in one known-good slot. Boot, confirm BIOS detection, then add one device at a time. If the first two drives are stable and failures begin only when additional devices are attached, record whether the symptom is disappearance, PCIe link errors, resets or complete boot failure.
That pattern helps distinguish a damaged individual SSD from a shared resource problem such as power delivery, PCIe switching or an adapter board. Repeating the same full four-drive boot without changing one variable at a time produces very little diagnostic information.
FAQ
How do I know whether the M.2 SSD or slot is bad?
Test a known-good compatible NVMe drive in the same slot and, if possible, test the suspect drive in another known-good system.
Can ZimaOS install if BIOS does not see the NVMe?
No. The installer depends on firmware/kernel enumeration. Solve hardware detection first.
Should I update BIOS before replacing the SSD?
Only after recording the current state and following the hardware vendor's supported firmware process. A physically loose or damaged card still needs inspection first.
Why do several NVMe drives fail together?
Possible causes include power budget, PCIe topology, firmware or controller behavior. Reduce the configuration and test incrementally rather than assuming a single cause.
Will formatting the NVMe make it appear?
No. Formatting only applies after the drive is already detected.
