Samsung SSD 850 EVO

[imac]

Cant access my SSD and Samsung tools cant detect it, is there another way to flash the firmware that probably are corrupt?

[fzabkar]

I would first eliminate the possibility of a hardware problem. If you can upload detailed photos of each side of the PCB, I can show you the voltage test points.

[sourcerer]

The EVO 840 (predecessor of your model) provides a SAFE mode where you can also do a firmware update through SATA.
(The third method is theoretically through the UART interface, but it's too unstable to be usable)
Additionally we developed a firmware update method through JTAG.

You might be interested in trying my SSD diagnostic tool https://github.com/thesourcerer8/SSDdiag , it has not been ported to EVO850 yet, but it might give some insight anyway, since most of the hardware in the controller is still the same.

[imac]

Pictures of both sides.

I read through the EVO 840 PDF and saw that about the SAFE mode, but I didn't found how I update the firmware by the SAFE mode?

[fzabkar]

These appear to be the voltage test points:

850_5V_e-fuse.JPG (57.08 KiB) Viewed 40336 times

[imac]

Voltages seems ok?

VBoost = 12V
V1 = 1,1V
V2 = 1,8V
V3 = 1,2V
V4 = 3V
V5 = 1,8V
V6 = 1,1V
5V Efuse = Ok

[sourcerer]

In SAFE mode (when you shorten the 2 pins next to the 5 pins), the EVO840 provides a 500 MB RAM-disk on the SATA interface, and you can do the normal firmware update (UPLOAD MICROCODE) over SATA. If Samsung Magician does not recognize the SAFE mode SSD, you have to decrypt the firmware and send it with hdparm.

But the biggest question is: Does it come available on SATA when you shorten the SAFE mode pins? (Or is the controller completely dead?)

[imac]

Could this two be for the SAFE mode? One is GND and the other is 1,8V.

[sourcerer]

No, I think it is the 2 pins right below the 5 pins on this photo.

[fzabkar]

The voltages look OK to me.

[imac]

In SAFE mode (when you shorten the 2 pins next to the 5 pins), the EVO840 provides a 500 MB RAM-disk on the SATA interface, and you can do the normal firmware update (UPLOAD MICROCODE) over SATA. If Samsung Magician does not recognize the SAFE mode SSD, you have to decrypt the firmware and send it with hdparm.

But the biggest question is: Does it come available on SATA when you shorten the SAFE mode pins? (Or is the controller completely dead?)

I shorted the two pins (next to the five) and started the PC but no difference, are you shore about the pins?

According to the 840EVO PDF:
The 2 pins right next to the JTAG (0V, 1.8V) pins are activating the “SAFE Mode” when shorted. The other 2 pins (marked 1,815 V and 1,819V) are a UART port, which provides debugging functionality in SAFE Mode.

The two smaller pins (marked) I have 0 and 1,8V and the two pin next to the five, its 1,8 and 1,8V = UART port?

[HaQue]

Probably like this... Serial or JTAG plus safe mode, firmware mode or whatever you want to call it:

[imac]

Notis today that if I wait for a time the disk will show up in windows, but with no info. Is the firmware still the suspected candidate? Anyone ho has the firmware in a hdparm format?

In hdparm:
/dev/hdc:

Model=, FwRev=, SerialNo=
Config={ HardSect SoftSect NotMFM Fixed Removeable }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=no
IORDY=no
PIO modes: pio0
AdvancedPM=no

Samsung Magician:

[sourcerer]

Please provide the relevant "dmesg" output. How long does it take to start the SSD? It's interesting that it actually shows the capacity correctly (it is 120 GB, isn't it?)

[imac]

Is there a "dmesg" for windows? I Think it takes about 5 minutes Before it will show up in windows. The size is correct in magician.

[imac]

It seems that the --fwdownload command in the windows version of hdparm are not working?

I installed Ubuntu on the same PC and the disk is not detected, tried with another disk and it's detected, something that I have missed?

[bital]

The EVO 840 (predecessor of your model) provides a SAFE mode where you can also do a firmware update through SATA.
(The third method is theoretically through the UART interface, but it's too unstable to be usable)
Additionally we developed a firmware update method through JTAG.

You might be interested in trying my SSD diagnostic tool https://github.com/thesourcerer8/SSDdiag , it has not been ported to EVO850 yet, but it might give some insight anyway, since most of the hardware in the controller is still the same.

I'm having:
SAMSUNG SSD 840 EVO 1TB, still able to boot in SAFE MODE with FIRMWARE: UNKNOWN
SAMSUNG SSD 840 EVO 120GB, in good standing with FIRMWARE: EXT0DB6Q

SAMSUNG SSD 840 EVO 120GB, EXT0DB6Q, I was able to upgrade from EXT0BB6Q to EXT0DB6Q by this command in REGULAR MODE

Code:

hdparm --yes-i-know-what-i-am-doing --please-destroy-my-drive --fwdownload EXT0DB6Q /dev/sda

so, the process is kind of working to upgrade the firmware, while I'm trying to move from EXT0DB6Q to EXT0BB6Q back it gives me this kind of error:

Code:

hdparm --yes-i-know-what-i-am-doing --please-destroy-my-drive --fwdownload EXT0BB6Q /dev/sda
/dev/sda:
fwdownload: xfer_mode=3 min=1 max=2048 size=512
...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 e0 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
. Done.

I'm trying to upgrade SAMSUNG SSD 840 EVO 1TB, still able to boot in SAFE MODE with FIRMWARE: UNKNOWN to EXT0BB6Q or EXT0DB6Q with the same result of sda hanging and not answering anymore forcing to shut down by holding power for 5 sec
I have this message and stuck

Code:

/dev/sda:
fwdownload: xfer_mode=3 min=1 max=2048 size=512
...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................


Ordered Altera USB Blaster cable...

Any ideas?

[cpm0088]

Do you need the data off the drive?

[imac]

Why does not Ubuntu detect the disk? In w10 the disk is detected but not readable.

Here is dmesg for the disks.

sudo dmesg | grep sd
[sudo] password for ...
[ 1.329864] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.329906] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 1.329914] sd 0:0:0:0: [sda] Write Protect is off
[ 1.329916] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.329934] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.390306] sda: sda1 sda2 < sda5 > sda3
[ 1.390582] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.406608] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 1.406654] sd 2:0:0:0: [sdb] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[ 1.406667] sd 2:0:0:0: [sdb] Write Protect is off
[ 1.406669] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.406689] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.409893] sdb: sdb1 sdb2 sdb3 sdb4
[ 1.410210] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 2.768352] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 2.768523] sd 6:0:0:1: Attached scsi generic sg4 type 0
[ 2.768678] sd 6:0:0:2: Attached scsi generic sg5 type 0
[ 2.768825] sd 6:0:0:3: Attached scsi generic sg6 type 0
[ 2.768996] sd 6:0:0:4: Attached scsi generic sg7 type 0
[ 2.909807] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[ 2.912305] sd 6:0:0:1: [sdd] Attached SCSI removable disk
[ 2.915025] sd 6:0:0:2: [sde] Attached SCSI removable disk
[ 2.917484] sd 6:0:0:3: [sdf] Attached SCSI removable disk
[ 2.919929] sd 6:0:0:4: [sdg] Attached SCSI removable disk
[ 3.137200] sd 7:0:0:0: Attached scsi generic sg8 type 0
[ 3.137797] sd 7:0:0:0: [sdh] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 3.138793] sd 7:0:0:0: [sdh] Write Protect is off
[ 3.138794] sd 7:0:0:0: [sdh] Mode Sense: 28 00 00 00
[ 3.139794] sd 7:0:0:0: [sdh] No Caching mode page found
[ 3.139797] sd 7:0:0:0: [sdh] Assuming drive cache: write through
[ 3.199661] sdh: sdh1
[ 3.202793] sd 7:0:0:0: [sdh] Attached SCSI disk
[ 117.030332] audit: type=1400 audit(1559411397.647:47): apparmor="DENIED" operation="connect" profile="snap.udisks2.udisksd" name="/run/dbus/system_bus_socket" pid=1198 comm="pool" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

[imac]

Could this be the problem? Is it possible to extend the timeout?

[ 6.400032] ata5: link is slow to respond, please be patient (ready=0)
[ 11.080033] ata5: COMRESET failed (errno=-16)
[ 16.432036] ata5: link is slow to respond, please be patient (ready=0)
[ 21.112034] ata5: COMRESET failed (errno=-16)
[ 26.464032] ata5: link is slow to respond, please be patient (ready=0)
[ 56.164046] ata5: COMRESET failed (errno=-16)
[ 56.164054] ata5: limiting SATA link speed to 1.5 Gbps
[ 61.216034] ata5: COMRESET failed (errno=-16)
[ 61.216042] ata5: reset failed, giving up