No that 5100 is generic:Is that Cisco / OEM only
9f586bded1f935bcb82a393cc8c6481e2fd8f34320fec5175fb0b20c4765f2cf M5100_D0MU078.bin
When you search on ebay for Micron 5100 SSDs with Cisco labels, usually they have D0MU. But I guess it depends which hardware had them. Server/SAN might be different from networking. I wouldn't know, this is a Mellanox household.
So a 5200 update came from Hetzner.
5300:
12cd559c751fddfdd1b3d35a4c1e983f94c1a583bc8fb1816a1c3e159dfbb0df M5300_D3CN003.bin
dac5a31a7e17cab1296c973183d31c089aefe88b72352d327e0c18b3316450ea M5300_D3MU005.bin
5400 is supposed to work with D4MU and D4CN, because hardware takes both:
3293c9b6357540c2c22724e1f97dcdc8d826f06a6b3b20f09c6b6d1d25542ded M5400_D4CN005.bin
Fixes are around a year old, from August/September 2025. For 5300 this worked:
hdparm --please-destroy-my-drive --yes-i-know-what-i-am-doing --fwdownload fw.bin /dev/sdX
If you have a C400 mSATA, word on the street is they can hang after 80+ days of uptime. Apparently Micron made a firmware that detects the hang and then... just reboots the mSATA card.
I already checked smartmontools/drivedb/drivedb.h at main · smartmontools/smartmontools but nothing. Could be super cap / plp cap status like with Samsung, unknown. There is no documentation because Micron still busy counting money in basement.You might try running/usr/bin/update-smart-drivedbto see if an updated data file might id those unknown attributes.
Last edited: