PS5 Says Your M.2 SSD Needs Formatting. Don't Format It.

Written and maintained by the Desert Data Recovery lab team. · Updated September 17, 2026

We already wrote about the format prompt on an SD card, Windows Initialize Disk, Unraid's Format checkbox, and a handheld M.2 that vanished after sleep. This is the PlayStation 5 screen: an NVMe in the expansion bay, and Format sitting there like a repair. The words are about storage. The write is the same class of mistake.

The prompt is a filesystem write, not a health check

The PS5 M.2 bay is expansion storage. The console does not treat that stick as a Windows volume, an exFAT USB drive, or a Steam library. When you install a compatible NVMe — or when the console later cannot mount one it already used — Settings / the first-boot expansion wizard offers to format it for M.2 SSD storage. The wording varies: storage needs to be formatted, format this M.2 SSD, Initialize Storage. The action is the same. The console writes its own expansion layout onto the drive so it can install PS5 games there.

That layout is console-specific. We are not going to invent partition names, Sony filesystem internals, or an encryption story we cannot verify from what is already public on this site. What we can say, because it is the same fact as every other “needs formatting” dialog we already cover: the host is telling you it does not have a volume it is willing to mount. The button is permission to replace that volume, not permission to inspect it.

Format does not run SMART. It does not re-seat the heatsink. It does not re-detect a drop-out. It does not copy your games to the internal SSD first. It writes. Downloaded games, extra game data, captures, and any saved data that lived on that expansion stick are then sitting under a new empty console filesystem — or they are gone from the map the PS5 will read. The internal console SSD is a different store. Formatting the expansion drive does not, by itself, wipe the internal drive. People still lose the only copy of a 200 GB install because that copy was on the M.2.

The public case log does not have a PlayStation 5 or PS5 M.2 job. We will not invent a case ID or an outcome. The closest published M.2 write-up is a Steam Deck 2230 that died after sleep. Different host, different layout. Same rule: a format prompt is not a diagnosis.

When Format is expected — and when it is a trap

Brand-new empty drive. A stick that has never held your games, still in the retail package, going into a PS5 for the first time: Format is the setup step. The console has to write its expansion filesystem before it will install titles there. This post is not telling you to skip setup on a blank SSD you just bought.

A drive that already had data. That is the trap. The stick was working last week. You powered down, moved the console, updated the system software, came out of Rest Mode, or the expansion bay lost the drive after heat or a loose heatsink. The PS5 no longer mounts the volume, so it offers Format as if the bay were empty. It is not empty. The games are still on the NAND until something overwrites them.

The usual ways we see that prompt come back on a used expansion SSD:

• The console cannot mount an existing expansion volume. Same sentence as a NAS that will not import and an SD card that “needs to be formatted.” The host gave up on the layout. The files did not volunteer to leave.
• Rest Mode, a power cut, or a yank mid-copy. Sleep / resume is a common way an NVMe drops — we already described that on the Deck 2230. A PS5 expansion stick lives in a tight, warm bay behind a required heatsink. A transfer that did not finish, a hard power-off, or Rest Mode that did not come back clean can leave the console unable to mount what is still on the drive.
• Seating, heatsink, or adapter trouble. The M.2 not fully in the slot, a third-party heatsink that shorted or lifted the module, a 2230/2242 adapter that worked until it did not. The console then treats the next successful enumerate as a new disk and offers Format. Reseating until it “sees” the drive is not a recovery method. Two or three looks tell you it is intermittent. After that you are power-cycling a dropping NVMe — same rule as SSD not detected.
• Heat. A PS5 expansion SSD that does not meet the console's cooling or speed requirements will throttle, drop, or throw storage errors. The next screen is often Format. Heat is a failure sign, not a cue to wipe the only copy so the temperature warning goes away.

If the stick never enumerated — no M.2 in the storage list, no serial, nothing to format — you do not have a format problem yet. You have a detection problem. Do not keep power-cycling it hoping the wizard appears.

Format writes. It does not “re-detect.”

This is the same class of mistake as Initialize Disk, the camera's Format Disk, and Unraid / TrueNAS Format / destroy-and-recreate. The UI copy says the storage cannot be used until it is formatted. That is true in the setup sense: the PS5 will not install games onto a volume it does not own. It is false in the recovery sense: formatting is how you replace the volume, not how you inspect it.

After Format, the console has a fresh expansion filesystem. It will happily start downloading the same titles again. That is not proof the old files were unhealthy. It is proof the map that pointed at them was replaced. A lab cannot put back a console filesystem the PS5 already overwrote, and TRIM / garbage collection on an NVMe can make that overwrite permanent faster than people expect on a hard drive.

The buttons and follow-ups that make it worse

Format / Format this M.2 SSD. Writes the new console expansion filesystem. Not a scan. Not “make it show up again.”

Initialize Storage. Same job, different label — prepare this device as expansion storage. If the stick already held your library, that is a wipe with a calmer name.

Wiping both internal and expansion. Initialize Console, Reset PS5, or “clear PS5 to factory settings” can offer to wipe console storage, and some flows include USB / extended storage or will not leave the M.2 alone. Formatting the expansion SSD is already enough to destroy the games on that stick. Do not add a console initialize so the whole system “matches.” Saves that still lived on the internal SSD are the copy you have not destroyed yet.

Rebuild Database vs Format. Rebuild Database reconstructs the library index. It is slow and it looks serious. It is not Format. If someone told you to Rebuild Database to fix a missing expansion drive, that is a different click. If the screen in front of you is Format, Rebuild will not do that write — and Format will not “rebuild harder.” Do not chain them.

Yanking the SSD mid-transfer. Pulling the M.2 while a game is copying, while the console is in Rest Mode, or while a format you already started is running is how you add a torn write on top of a bad mount. If you are going to remove the stick, power the console fully off first. One pull. Label it. Do not reseat it ten times.

Testing it in a PC, then initializing or formatting there. Windows and macOS do not speak the PS5 expansion layout. Disk Management offers Initialize. Disk Utility / GParted offer Format. Vendor SSD tools offer Secure Erase. Those are PC writes over a console volume. People do this to “see if the SSD is healthy,” then put it back in the PS5, which now has even more reason to demand Format. If the stick enumerates at its real capacity, the only non-destructive PC step is a read-only look or a clone onto a different drive. Then stop.

Re-downloading onto the same stick to test. A new install is a write. It does not probe the old files. It spends the free space — and on an SSD, often the old blocks — so you can watch a progress bar.

What to do right now

Do not format. Do not initialize. Do not plug it into a PC and accept GPT / MBR. Do not factory-reset the console to “clear the error.”

1. Stop. Leave the Format dialog up or back out of it. If the drive is making unusual noise (rare on an SSD, but the console or fan story still matters), if storage errors are climbing, or if the M.2 keeps disappearing from the list, power the PS5 fully off. Extra uptime on a dropping NVMe is more controller time you do not get back. See SSD not detected.
2. Photograph the screen. The exact wording (needs to be formatted, format this M.2 SSD, Initialize Storage), the drive name or serial if shown, capacity, any temperature or “this SSD cannot be used” text, and whether the prompt is about the expansion bay only or also console storage. Screenshots help. They are not a diagnosis.
3. Power off before you pull it, if you pull it at all. One removal. Do not keep reseating to see if Format goes away.
4. Label the SSD and keep the heatsink, screws, and any 2230/2242 adapter it was mounted in. Proprietary or tight heatsinks are part of how the module sat in the bay. We would rather see the assembly than a bare stick that was pried out of a clip.
5. Write down where the data lived. Games on the M.2 vs console storage. Saves on console storage vs anything you moved. Media / captures. PS Plus cloud saves cover some saves; they do not replace a 100 GB install that only existed on the expansion drive. Note Rest Mode, a recent update, a mid-copy yank, or a PC test you already did.

If you are mailing it, pack the module like any other failed SSD — how to ship a failed drive safely. A padded envelope is how M.2 sticks arrive bent. Do not ship it loose in the console if the only patient is the expansion SSD; the console is heavy and the slot is not a case.

How a lab handles it

We do not tap Format on your PS5. We do not Initialize Storage to “see if the bay works.” We do not run Disk Management against the patient stick.

The module is imaged write-blocked, as much of it as the controller will still give us, including a drive that only enumerates in pieces. Work happens on the copy. A PS5 expansion SSD uses a console-specific layout — not NTFS, not the Steam Deck's disk, not a camera card. We will not invent a Sony on-disk spec or a secret PlayStation tool. If the controller still talks, imaging is standard NVMe work: talk to that controller, preserve what is there, then look at the image for a console volume rather than asking the PS5 to rebuild one. If the controller will not talk, that is the board / firmware path we already describe, not a format wizard. Modern NVMe is often encrypted to its own controller; pulling packages and hoping for a game folder is the same dead end we already flag on chip-off AES NVMe.

What imaging cannot do: undo a Format that finished and then filled the drive with new downloads. Undo a PC initialize plus format. Invent files that TRIM already dropped. We will tell you if the data is not there. There is no PS5 case in the public case log, and we will not invent one. We don't advertise a success rate. The free evaluation is how you find out which failure you have before anyone bills you.

If the stick vanished from every host, start with SSD not detected. If a PC already offered Initialize, that is Initialize Disk. If this is a handheld 2230 that died after sleep, that is the Steam Deck post — do not follow it as a click-by-click script on a PS5 2280. For the work itself, see SSD & NVMe recovery.