Opinions on Western Digital SN840 vs Intel P4510 - Firmware updates available for WD?

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

bleomycin

Member
Nov 22, 2014
54
6
8
40
I need a large ssd as a super overkill storage drive for an NVR system. Scrubbing high resolution footage lags if it's not on some type of SSD. This is for my personal use and it'll take a lifetime for my cameras to write enough data to wear out one of these things so that isn't a concern.

The 7.68TB Ultrastar DC SN840 and the 8TB Intel DC P4510 are both available new in the ~$400 range. On paper the WD drive slightly edges out the intel drive but I don't think that's going to matter much for my intended use case. The thing that concerns me is a quick google search has returned absolutely nothing as far as firmware or even documentation regarding firmware updates for these western digital drives. Intel firmware and general management seems much better. They both use similar amounts of power on paper.

I'd be fine with a Sata drive but I can't find any as cheap as these U.2 variants. Should I just grab an intel drive or is there a better option I'm missing?
 
I use SATA S3700 \ S3710 for my cameras and it's amazingly fast, any enterprise NVME in the 2TB+ capacity should be sufficient and really really overkill :D
 
  • Like
Reactions: nexox
WD has a dashboard app that you use for firmware at least for the sn770/850 drives. Not sure what they would do for the U options. On Linux fwupd doesn't do it and you'd need to boot to windows to update the FW if needed.

Micron provides updates you can apply but they run hot and I didn't have luck with two of them not being usable in under a week. Most of the enterprise drives won't provide updates without a contract though.

FW updates aren't really an issue though unless you have a problem in the first place.
 
@napalm_atx
I have this fw for Ultrastar DC SN840 ftp://atxlab.ddns.net/hdd/fw/hgst/SSD/malibux_qs2_GD_R2210010.zip
Thank you!
Tried to unzip it under recent Fedora (fc38) and got this:
Code:
# unzip malibux_qs2_GD_R2210010.zip
Archive:  malibux_qs2_GD_R2210010.zip
   skipping: malibux_qs2_GD_R2210010.vpkg  need PK compat. v6.3 (can do v4.6)
So I used 7za 'x'.
Do you have any Odyssey firmwares? (SN260 HHHL) I believe rev122 was the last one for them

I had managed to download and extract R2210002 from Cisco ISO images but alas the resulting payload was too short and nvme had refused to apply it.
 
So the Cisco (CC) file would not upload to my drive but yours did:

Code:
# nvme fw-download -f malibux_qs2_CC_R2210002.vpkg /dev/nvme0
Invalid size:3420446 for f/w image

# nvme fw-download -f malibux_qs2_GD_R2210010.vpkg /dev/nvme0
Firmware download success

But when I tried to commit it, I got:
Code:
#  nvme fw-commit -s 2 /dev/nvme0
NVMe status: Invalid Firmware Image: The firmware image specified for activation is invalid and not loaded by the controller(0x4107)
Multiple Update Detected (MUD) Value: 0

#  nvme fw-commit -s 2 -a 0 /dev/nvme0
NVMe status: Invalid Firmware Image: The firmware image specified for activation is invalid and not loaded by the controller(0x4107)
Multiple Update Detected (MUD) Value: 0
 
Last edited:
So I've got some good news..
After more than a week of multiple cases, issuesm rejections, redirections WDC finally found someone who:
1) emailed me a firmware image for the drive.
2) provided some tools made by WDC that work under Linux:

# nvme fw-download -f malibux_qs2_GN_R2210010.vpkg /dev/nvme0 Firmware download success # nvme fw-commit -s 2 /dev/nvme0 Success committing firmware action:0 slot:2 Multiple Update Detected (MUD) Value: 0 # nvme fw-log /dev/nvme0 Firmware Log for device:nvme0 afi : 0x24 frs1 : 0x3030303031323252 (R2210000) frs2 : 0x3031303031323252 (R2210010) frs3 : 0x3030303031323252 (R2210000) frs4 : 0x3030303031323252 (R2210000)

The only difference between your @napalm_atx is that your firmware is 'GD' while the one shared by HGST support is 'GN'. These point to different OEMs, I think.

Do you want a copy of the GN file?

# ls -l malibux_qs2_G* -rwxr-xr-x. 1 core core 3530752 May 19 06:05 malibux_qs2_GD_R2210010.vpkg -rwxr-xr-x. 1 core core 3530752 May 22 22:31 malibux_qs2_GN_R2210010.vpkg
 
Shared here:
Please let me know if you can access it:


$ sha256sum malibux_qs2_GN_R2210010.vpkg a22c99353f8f34fb6c508c1f31ad5b26130205d019f3d1f3ab14fb8b173710d0 malibux_qs2_GN_R2210010.vpkg