So I have X319_S16437T6ATE (the 7.68 TB drive) running NA53. Anyone know if this will suffer from the 32k or 40k power-on hours death? The drive is listed as eligible for NA54, but I'm having trouble finding that LOD.
Samsung SSD PM1643 3.8TB SAS 12Gb/s MZ-ILT3T8A 2.5" @ $289.98
- Thread starter abq
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Important! Use this link: http://ftp.otenet.gr/linux/netapp/all.zip
This file contains firmware's from 2020 i.e., X670_S164315TATE.NA54.LOD 9/9/2020 over the directory listing file of X670_S164315TATE.NA53.LOD from 2019-06-20.
This file contains firmware's from 2020 i.e., X670_S164315TATE.NA54.LOD 9/9/2020 over the directory listing file of X670_S164315TATE.NA53.LOD from 2019-06-20.
Thank you! I have to use this on a pm1633a drive running NA51. Hopefully I don't screw it up, as those drives are in an Unraid setup
For my PM1633a's:
smartctl lists them as NETAPP x357's with NA51.
I have the NA54.lod (3.98MB) from the all.zip here. Also have the MZ7LM240HCGR-00003_3F3Q.bin (1MB) from the huge firmware list from this forum TFW.zip (MEGA).
Any ideas which to use? Is flashing to NA54 the easiest fix, keeping it within the Netapp line, or flip it to Samsung from the perhaps-unverified-source TFW.zip?
smartctl lists them as NETAPP x357's with NA51.
I have the NA54.lod (3.98MB) from the all.zip here. Also have the MZ7LM240HCGR-00003_3F3Q.bin (1MB) from the huge firmware list from this forum TFW.zip (MEGA).
Any ideas which to use? Is flashing to NA54 the easiest fix, keeping it within the Netapp line, or flip it to Samsung from the perhaps-unverified-source TFW.zip?
If NA51 is working for you, I'd just go with NA54 and call it a day. Cross flashing should work, but there's a small chance it might brick the drive or cause data loss due to the change over.
Hello,
i would like to crossflash my Samsung PM1633 3.84 to NetApp. I think this one suffers from the bug and i can't find firmware from Samsung.
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: MZILS3T8HCJM/003
Revision: GQP2
Compliance: SPC-4
User Capacity: 3,840,755,982,336 bytes [3.84 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538a07397df0
Serial number: S23TNA0J301431
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Jan 28 08:11:41 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Percentage used endurance indicator: 0%
Current Drive Temperature: 43 C
Drive Trip Temperature: 60 C
Accumulated power on time, hours:minutes 36382:15
Manufactured in week 10 of year 2017
Accumulated start-stop cycles: 69
Specified load-unload count over device lifetime: 0
Accumulated load-unload cycles: 0
Elements in grown defect list: 0
Can anyone tell me which is the correct NetApp Firmware version and crossflash with sg_buffer does work?
Thank you very much
Tobias
i would like to crossflash my Samsung PM1633 3.84 to NetApp. I think this one suffers from the bug and i can't find firmware from Samsung.
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: MZILS3T8HCJM/003
Revision: GQP2
Compliance: SPC-4
User Capacity: 3,840,755,982,336 bytes [3.84 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538a07397df0
Serial number: S23TNA0J301431
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Jan 28 08:11:41 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Percentage used endurance indicator: 0%
Current Drive Temperature: 43 C
Drive Trip Temperature: 60 C
Accumulated power on time, hours:minutes 36382:15
Manufactured in week 10 of year 2017
Accumulated start-stop cycles: 69
Specified load-unload count over device lifetime: 0
Accumulated load-unload cycles: 0
Elements in grown defect list: 0
Can anyone tell me which is the correct NetApp Firmware version and crossflash with sg_buffer does work?
Thank you very much
Tobias
Last edited:
From my research the Samsung PM1633 = X356_S16333T8ATE
Tried:
root@tera-ve:/tmp# sg_write_buffer -b 4k -m dmc_offs_save -I /tmp/X356_S16333T8ATE.NA04.LOD /dev/sg2
Write buffer failed: Illegal request
sg_write_buffer failed: Illegal request
And:
root@tera-ve:/tmp# sg_write_buffer --m 5 -vvvvvv --in=/tmp/X356_S16333T8ATE.NA04.LOD /dev/sg2
found sg_bsg_major=243
open /dev/sg2 with flags=0x802
tried to read 8388608 bytes from /tmp/X356_S16333T8ATE.NA04.LOD, got 4177920 bytes
will write 4177920 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=4177920
Write buffer cdb: [3b 05 00 00 00 00 3f c0 00 00]
Write buffer parameter list (first 256 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
check_file_type: file descriptor is sg device
set_pt_file_handle: sg driver version 3.05.36 so choose v3
duration=1052 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Field replaceable unit code: 37
Sense Key Specific: Error in Data parameters: byte 0
Raw sense data (in hex), sb_len=24, embedded_len=24
70 00 05 00 00 00 00 10 00 00 00 00 26 00 25 80
00 00 09 65 26 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode
No success, looks like there are checks :-(
I am to noob to get fixed this myself. Since i have 4 of these and they all have 36.000h runtime i get nervous
Anyone can support original Firmware from Samsung or does have a clue how to crossflash them to NetApp ?
Thank you very much
Tried:
root@tera-ve:/tmp# sg_write_buffer -b 4k -m dmc_offs_save -I /tmp/X356_S16333T8ATE.NA04.LOD /dev/sg2
Write buffer failed: Illegal request
sg_write_buffer failed: Illegal request
And:
root@tera-ve:/tmp# sg_write_buffer --m 5 -vvvvvv --in=/tmp/X356_S16333T8ATE.NA04.LOD /dev/sg2
found sg_bsg_major=243
open /dev/sg2 with flags=0x802
tried to read 8388608 bytes from /tmp/X356_S16333T8ATE.NA04.LOD, got 4177920 bytes
will write 4177920 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=4177920
Write buffer cdb: [3b 05 00 00 00 00 3f c0 00 00]
Write buffer parameter list (first 256 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
check_file_type: file descriptor is sg device
set_pt_file_handle: sg driver version 3.05.36 so choose v3
duration=1052 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Field replaceable unit code: 37
Sense Key Specific: Error in Data parameters: byte 0
Raw sense data (in hex), sb_len=24, embedded_len=24
70 00 05 00 00 00 00 10 00 00 00 00 26 00 25 80
00 00 09 65 26 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode
No success, looks like there are checks :-(
I am to noob to get fixed this myself. Since i have 4 of these and they all have 36.000h runtime i get nervous
Anyone can support original Firmware from Samsung or does have a clue how to crossflash them to NetApp ?
Thank you very much
Last edited:
1. Samsung couldn't give a hoot, unless you take 10.000 units and your name is Dell or HPE.
2. Every morning there is a 5% chance that the break lines of your car were cut over night by some criminal. You must drive to work and you mustn't look. You drive many miles on crowded highways. Do you feel comfortable?
Avoid Samsung...
2. Every morning there is a 5% chance that the break lines of your car were cut over night by some criminal. You must drive to work and you mustn't look. You drive many miles on crowded highways. Do you feel comfortable?
Avoid Samsung...
Excuse the confusion, please forget the analogy. Ment that just because this particular bug will happen at 32K hours that doesn't mean 2-3 other serious ones won't at 40K. Samsung without recent firmware stream is imho no great deal, really no deal at all. More like a ticking time tomb.
Hello,
I recently bought 3@PM1643 3.84TB drives on eBay. They appear to be from a Dell EMC machine... I'v attached a picture. SMART is clean on all 3, and they have 93% life remaining. I have successfully reformatted all to 4096.
I've tried them in both a Supermicro server and a Dell R720. They show up fine, and allow me to format/dd them... I even had Proxmox guests running on them for a couple of days. I had them in a ZFS RaidZ array. Then... I rebooted...
The pool completely disappeared, and I noticed endless entries of these in "dmesg". I am seeing this in both servers.
blk_update_request: critical target error, dev sdh, sector xxxxxx op 0x0
READ) flags xxxxxx phys_seg 1 prio class 0
blk_update_request: critical target error, dev sdi, sector xxxxxx op 0x0READ) flags xxxxxx phys_seg 1 prio class 0
blk_update_request: critical target error, dev sdj, sector xxxxxx op 0x0READ) flags xxxxxx phys_seg 1 prio class 0
SMART information from one of them (they're all the same)
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: P043S3T8 EMC3840
Revision: ESFA
Compliance: SPC-5
User Capacity: 3,840,774,504,448 bytes [3.84 TB]
Logical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538b088b7d80
Serial number: ZWNY0K815723
I've gone through this thread but it seems like everybody is updating NETAPP firmware. I've tried a couple of the downloads but they would not apply. I also have come up empty on Dell's website or elsewhere trying to find what these came from, and if they can be updated... or, if they're just dead.
Any advice would be appreciated.
I recently bought 3@PM1643 3.84TB drives on eBay. They appear to be from a Dell EMC machine... I'v attached a picture. SMART is clean on all 3, and they have 93% life remaining. I have successfully reformatted all to 4096.
I've tried them in both a Supermicro server and a Dell R720. They show up fine, and allow me to format/dd them... I even had Proxmox guests running on them for a couple of days. I had them in a ZFS RaidZ array. Then... I rebooted...
The pool completely disappeared, and I noticed endless entries of these in "dmesg". I am seeing this in both servers.
blk_update_request: critical target error, dev sdh, sector xxxxxx op 0x0
READ) flags xxxxxx phys_seg 1 prio class 0blk_update_request: critical target error, dev sdi, sector xxxxxx op 0x0
READ) flags xxxxxx phys_seg 1 prio class 0blk_update_request: critical target error, dev sdj, sector xxxxxx op 0x0
READ) flags xxxxxx phys_seg 1 prio class 0SMART information from one of them (they're all the same)
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: P043S3T8 EMC3840
Revision: ESFA
Compliance: SPC-5
User Capacity: 3,840,774,504,448 bytes [3.84 TB]
Logical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538b088b7d80
Serial number: ZWNY0K815723
I've gone through this thread but it seems like everybody is updating NETAPP firmware. I've tried a couple of the downloads but they would not apply. I also have come up empty on Dell's website or elsewhere trying to find what these came from, and if they can be updated... or, if they're just dead.
Any advice would be appreciated.
Attachments
try formatting to 512 and see. ive seen weird issues on some drives including 3par 520 drives. 512 has fixedHello,
I recently bought 3@PM1643 3.84TB drives on eBay. They appear to be from a Dell EMC machine... I'v attached a picture. SMART is clean on all 3, and they have 93% life remaining. I have successfully reformatted all to 4096.
I've tried them in both a Supermicro server and a Dell R720. They show up fine, and allow me to format/dd them... I even had Proxmox guests running on them for a couple of days. I had them in a ZFS RaidZ array. Then... I rebooted...
The pool completely disappeared, and I noticed endless entries of these in "dmesg". I am seeing this in both servers.
blk_update_request: critical target error, dev sdh, sector xxxxxx op 0x0
blk_update_request: critical target error, dev sdi, sector xxxxxx op 0x0
blk_update_request: critical target error, dev sdj, sector xxxxxx op 0x0
SMART information from one of them (they're all the same)
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: P043S3T8 EMC3840
Revision: ESFA
Compliance: SPC-5
User Capacity: 3,840,774,504,448 bytes [3.84 TB]
Logical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538b088b7d80
Serial number: ZWNY0K815723
I've gone through this thread but it seems like everybody is updating NETAPP firmware. I've tried a couple of the downloads but they would not apply. I also have come up empty on Dell's website or elsewhere trying to find what these came from, and if they can be updated... or, if they're just dead.
Any advice would be appreciated.
I belive these are EMC drives used in Isilon, and to update those you need a “ Isilon drive support packet”. And to use that, you might have guessed it… a isilon with the right OneFs version.Hello,
I recently bought 3@PM1643 3.84TB drives on eBay. They appear to be from a Dell EMC machine... I'v attached a picture. SMART is clean on all 3, and they have 93% life remaining. I have successfully reformatted all to 4096.
I've tried them in both a Supermicro server and a Dell R720. They show up fine, and allow me to format/dd them... I even had Proxmox guests running on them for a couple of days. I had them in a ZFS RaidZ array. Then... I rebooted...
The pool completely disappeared, and I noticed endless entries of these in "dmesg". I am seeing this in both servers.
blk_update_request: critical target error, dev sdh, sector xxxxxx op 0x0
blk_update_request: critical target error, dev sdi, sector xxxxxx op 0x0
blk_update_request: critical target error, dev sdj, sector xxxxxx op 0x0
SMART information from one of them (they're all the same)
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: P043S3T8 EMC3840
Revision: ESFA
Compliance: SPC-5
User Capacity: 3,840,774,504,448 bytes [3.84 TB]
Logical block size: 4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5002538b088b7d80
Serial number: ZWNY0K815723
I've gone through this thread but it seems like everybody is updating NETAPP firmware. I've tried a couple of the downloads but they would not apply. I also have come up empty on Dell's website or elsewhere trying to find what these came from, and if they can be updated... or, if they're just dead.
Any advice would be appreciated.
Maybe it can also on a xxxBSD system.
Thanks for the replies, I tried 512, and that doesn't appear to have fixed the issue. Sounds like I'll just need to sell them as I definitely don't have an Isilon.