Tools: CachyOS Wouldn't Install and My NVMe Was the Problem (Corrupted GPT + chwd Fix)

Tools: CachyOS Wouldn't Install and My NVMe Was the Problem (Corrupted GPT + chwd Fix)

CachyOS Wouldn't Install and My NVMe Was the Problem (Corrupted GPT + chwd Fix)

Problem 1: The NVMe with an Identity Crisis

Problem 2: chwd Killed the Install Mid-Way

muzasio #til #devlog #techexperiment #linux #cachyos #nvme #archlinux I was setting up CachyOS on a secondary laptop — i7 11th Gen, NVIDIA mobile GPU, Micron 2210 NVMe. Should've been a clean install. It wasn't. Two specific things broke and both of them looked like my fault until they weren't. The CachyOS installer (Calamares) failed to create a partition table on the Micron 2210 NVMe. No useful error, just a failure. I dropped into the terminal and ran gdisk: Three warnings. Then this: The drive had a corrupted GPT and ghost MBR headers from a previous install. The Calamares installer couldn't write a clean partition table because it was fighting old metadata it couldn't fully read or overwrite. The fix is a full zap from inside gdisk: Drive came out completely clean. Re-ran the installer, partition table created without issue. If gdisk can't get there, hit it with wipefs first: Intel VMD note: If you're on an 11th Gen Intel laptop, check your BIOS for Intel VMD (Volume Management Device). If it's enabled, Linux can see the NVMe drive but can't write to it properly. Disable VMD or switch from RAID to AHCI/NVMe mode before trying any of the above. After getting past the NVMe issue, the installer failed again — this time at chwd, the CachyOS hardware detection tool. The online installer couldn't pull the driver profiles, likely a mirror timeout. The fix: switch to the offline installer. It installs a default desktop from the USB without pulling anything from the network. Once booted into the system, run hardware detection manually: That scans your hardware and applies the right driver profiles — in my case, the Intel + NVIDIA hybrid (Optimus) setup for the laptop. Old partition metadata is silent until it isn't. Before installing anything on a drive that's been used before, zap it manually — don't trust the installer to do it cleanly. Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse

Command

Copy

$ -weight: 600;">sudo gdisk /dev/nvme0n1 -weight: 600;">sudo gdisk /dev/nvme0n1 -weight: 600;">sudo gdisk /dev/nvme0n1 MBR: not present BSD: not present APM: not present GPT: damaged Found invalid MBR and corrupt GPT. MBR: not present BSD: not present APM: not present GPT: damaged Found invalid MBR and corrupt GPT. MBR: not present BSD: not present APM: not present GPT: damaged Found invalid MBR and corrupt GPT. -weight: 600;">sudo gdisk /dev/nvme0n1 # at the prompt: x # enter expert mode z # zap GPT data — confirm with y # then zap MBR — confirm with y -weight: 600;">sudo gdisk /dev/nvme0n1 # at the prompt: x # enter expert mode z # zap GPT data — confirm with y # then zap MBR — confirm with y -weight: 600;">sudo gdisk /dev/nvme0n1 # at the prompt: x # enter expert mode z # zap GPT data — confirm with y # then zap MBR — confirm with y -weight: 600;">sudo wipefs -a /dev/nvme0n1 -weight: 600;">sudo wipefs -a /dev/nvme0n1 -weight: 600;">sudo wipefs -a /dev/nvme0n1 -weight: 600;">sudo chwd -a -weight: 600;">sudo chwd -a -weight: 600;">sudo chwd -a