Micron 5200 firmware bug

[EffrafaxOfWug]

Not sure how you want to do the update but I used Micron's Storage Executive software using windows and a USB to SATA adapter. That needs the entire zip file I shared with the drop box link as it does not work with the individual .bin files

I've almost always used msecil to do this since it works with the individual .bin files and (last time I looked at storage executive anyway) isn't a massively bloated GUI app.
From bumping one of my 5200's up to x30:

root@wug:~/firmware/micron 5200 eco# msecli -F -U 5200_fw830.bin -n /dev/sda

Trying to update current firmware for /dev/sda.
Are you sure you want to continue(Y|N):y

Firmware update for /dev/sda will take a few minutes to complete.
Please wait
................
Device Name  : /dev/sda
Firmware update operation completed successfully.

CMD_STATUS   : Success
STATUS_CODE  : 0

Copyright (C) 2020 Micron Technology, Inc

Edit: And as if by magic; two drives now updated to x40, one under windows (the oldest)...

C:\Windows\system32>msecli -F -U q:\5200_fw440.bin -n Drive1

Trying to update current firmware for Drive1.
Are you sure you want to continue(Y|N):y

Firmware update for Drive1 will take a few minutes to complete.
Please wait
................
Device Name  : Drive1
Firmware update operation completed successfully.

CMD_STATUS   : Success
STATUS_CODE  : 0

Copyright (C) 2020 Micron Technology, Inc.

C:\Program Files\smartmontools\bin>smartctl -a /dev/sdb
smartctl 7.5 2025-04-30 r5714 [x86_64-w64-mingw32-win7-sp1] (AppVeyor)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Micron 5100 / 52x0 / 5300 / 5400 SSDs
Device Model:     Micron_5200_MTFDDAK3T8TDC
Serial Number:    
LU WWN Device Id: 
Firmware Version: D1MU440
User Capacity:    3,840,755,982,336 bytes [3.84 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

...and one under linux (everything else):

root@wug:~/firmware/micron 5200 eco# msecli -F -U 5200_fw840.bin -n /dev/sda

Trying to update current firmware for /dev/sda.
Are you sure you want to continue(Y|N):y

Firmware update for /dev/sda will take a few minutes to complete.
Please wait
................
Device Name  : /dev/sda
Firmware update operation completed successfully.

CMD_STATUS   : Success
STATUS_CODE  : 0

Copyright (C) 2020 Micron Technology, Inc.

root@wug:~# smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.deb10.16-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Micron_5200_MTFDDAK7T6TDC
Serial Number:    
LU WWN Device Id: 
Firmware Version: D1MU840
User Capacity:    7,681,501,126,656 bytes [7.68 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

SMART short and long self-tests both happy, zero problems observed with the drives themselves so far, touch wood.

Incidentally, I poked around a few other crucial/micron drives I have kicking around to see what their power-on-hours stats looked like. I've got a trusty aged MX300 in a laptop that's clearly overflowed past 65k hours already (been in that computer since ~2016) and currently showing at a mere 7500 hour (~310 days) uptime. So clearly not a problem with certain strands of crucial firmware.

 

[UhClem]

...
Incidentally, I poked around a few other crucial/micron drives I have kicking around to see what their power-on-hours stats looked like. I've got a trusty aged MX300 in a laptop that's clearly overflowed past 65k hours already (been in that computer since ~2016)

(implying[?]) that laptop has been powered ON 24/7 for ~9 years!!
Is that true?
Because

and currently showing at a mere 7500 hour (~310 days) uptime. So clearly not a problem with certain strands of crucial firmware.

the (Crucial) MX300 and the (Micron) 5200 both use a Marvell 88SS1074 controller.

 

[EffrafaxOfWug]

(implying[?]) that laptop has been powered ON 24/7 for ~9 years!!
Is that true?
Because

the (Crucial) MX300 and the (Micron) 5200 both use a Marvell 88SS1074 controller.

It's at this point I have to claim ignorance as to how the SMART counters behave when the laptop is in S3 or S4, which is probably at least 50% of that time - but it has indeed been getting used daily for around a decade.

IIRC the Marvell 88SS1074 was also used in the Micron 5100's and at least one of the SanDisk "Ultra" models.

 

[tinfoil3d]

Thank you so much guys. I have

Firmware Version: D1MU820
Micron_5200_MTFDDAK7T6TDC

Guess this applies. I did download the zip, still have 32k hours on mine. Bought it for 1k new from amazon in 2020-21 or so.
Thanks for raising awareness frens

 

[wallacebrf]

Just saw this https://www.reddit.com/r/DataHoarder/comments/1sly734
Curious if other models are impacted. Has anyone exceeded 65k hours on 5100, 5200 or 5300?

I would suggest editing your initial post with the links to the files so others do not need to dig as much through all the posts??

 

[EffrafaxOfWug]

Given the potential severity of the issue - mostly RAID arrays becoming toast - along with Micron's apparently inability to admit to regular users that there is a firmware fix available for this, I did wonder if it was worth pinging Patrick about this in terms of raising awareness...?

Micron might no longer care about individual users, but clearly cared enough about Hetzner to provide them with the files (albeit under NDA), and I suspect there's a large contingent of StHers and SMEs out there using 5200's that haven't had the good fortune to run in to this thread or the Reddit post (or the bad fortune to hit their 65k hours) yet.

I'm still clinging on to the forlorn hope that Micron's still just doing QA on this, but the apparent fact they're still telling users opening support tickets about this issue that the drives are obsolete and unsupported - despite the fixed firmware already existing for at least a month, and possibly since January - is leaving a very sour taste in the mouth, especially since their firmware support's generally been very good from a homelabber's perspective in the past.

 

[ketiljo]

I have a couple of these, HPE branded, vk001920gwsxk. I assume the Micron FW doesn't work on these? HPE seems to a version HPE3(E) from sep 20. 2024, not sure it this is new enough?

https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-75bc856a96a1425a&tab=revisionHistory

 

[TrevorH]

As far as I know the bug was discovered in mid-2025 and the patch only came to public light a few months ago so I think it very unlikely that HP had a fix in 2024.

 

[EffrafaxOfWug]

I think that's basically going to be down to how different from the official firmware the HPE-specific models are; given that on the face of it this looks like it's only going wrong on a 16bit overflow on a certain SMART attr, and that HPE and other OEMs often have custom SMART attrs and counters, it's not out of the realms of possibility that the HPE drives are unaffected.

Certainly I'd have expected a fix or at least an advisory from HPE by now if this problem started rearing its head in mid-2025.

 

[wallacebrf]

Given the potential severity of the issue - mostly RAID arrays becoming toast - along with Micron's apparently inability to admit to regular users that there is a firmware fix available for this, I did wonder if it was worth pinging Patrick about this in terms of raising awareness...?

Micron might no longer care about individual users, but clearly cared enough about Hetzner to provide them with the files (albeit under NDA), and I suspect there's a large contingent of StHers and SMEs out there using 5200's that haven't had the good fortune to run in to this thread or the Reddit post (or the bad fortune to hit their 65k hours) yet.

I'm still clinging on to the forlorn hope that Micron's still just doing QA on this, but the apparent fact they're still telling users opening support tickets about this issue that the drives are obsolete and unsupported - despite the fixed firmware already existing for at least a month, and possibly since January - is leaving a very sour taste in the mouth, especially since their firmware support's generally been very good from a homelabber's perspective in the past.

I have debated about responding to my support tickets with something along the lines of

Hey, guess what, that firmware you said does not exist, well here it is,how about that?

But I do not want to make this too public to micron in case they either get the OP in trouble somehow or make the files disappear from the Internet....

 

[TrevorH]

if this problem started rearing its head in mid-2025.

I should clarify my mid-2025 date. I don't know if that's when it was first discovered but that is around the time that the first shipped drives would have experienced the problem if they'd been on 24/7.

 

[EffrafaxOfWug]

Mid-2025 sounds about right - my oldest is from october 2025, and it was usually a good few of months after release before they'd filter in to the UK retail channels (usually much longer these days), and I usually don't buy anything until it's been out for at least a couple of months.

The press release and the first review were both in January 2018.

65535 hours is just under 7.5 years so assuming it wasn't caught beforehand mid-2025 is the very earliest you could have expected to see this in the wild.

 

[wallacebrf]

Mid-2025 sounds about right - my oldest is from october 2025, and it was usually a good few of months after release before they'd filter in to the UK retail channels (usually much longer these days), and I usually don't buy anything until it's been out for at least a couple of months.

The press release and the first review were both in January 2018.

65535 hours is just under 7.5 years so assuming it wasn't caught beforehand mid-2025 is the very earliest you could have expected to see this in the wild.

I read this exact article and it was one of the reasons why I got the eco 1.92 TB drives to begin with