Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: BTRFS <linux-btrfs@vger.kernel.org>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: SSD overheating during scrub in laptop (SOLVED: no overheating but firmware issue)
Date: Sat, 14 Nov 2026 11:29:30 +0100	[thread overview]
Message-ID: <-8JrlgE5SLizPVsfOSFaOg@lichtvoll.de> (raw)
In-Reply-To: <967be80b-f683-4611-a473-0ad02897c451@gmx.com>

Greetings Qu, greetings.

Qu Wenruo - 16.09.25, 23:17:18 CET:
> >>> I have hit similar situation, but the symptom is very different, the
> >>> death come silently at boot, the drive is no longer recognized by
> >>> the
> >>> BIOS thus no longer bootable, and Linux kernel from liveUSB will not
> >>> recognize it either.
> > 
> > Hmm, did you capture any logs?
> 
> Nothing suspicious at all, except no PCIE device detected at all.
> 
> So in my case it's really toasted so that it can not even be detected
> anymore.

I think I finally got this sorted.

You have been right, Qu: It was no overheating issue.

Just completed a scrub of 2 TiB data. Twice in a row, first on TTY without 
loaded desktop with about 3 GiB/s, then on desktop with power-profiles-
daemon set to performance mode with about 3,8 GiB/s.

Sensor 2 of SSD temp went up to 101 degree Celsius and it was no issue.

What did I change? I upgraded firmware from 4B2QJXD7 to 8B2QJXD7 after in 
a dialog with AI I was hinted about issues that users lost their device at 
least temporarily after unsafe shutdown. Or even needed to send them in 
for repair. Luckily I never had one of these.

However they also wrote something interesting about read-operation 
stability:

-----------------------------------------------------------------------

* (8B2QJXD7) To improve read-operation stability. (Release : December 
2025)

* (7B2QJXD7) To address the intermittent non-recognition and blue screen 
issue. (Release: September 2025)

* (4B2QJXD7) To address reports of high temperatures logged on Samsung 
Magician. (Release: December 2024)

*990 PRO I 990 PRO with Heatsink will be manufactured using a mixed 
production between the V7 and V8 process starting September 2023.

-----------------------------------------------------------------------

https://semiconductor.samsung.com/consumer-storage/support/tools/

What can I say?

With 4B2QJXD7 a scrub of more than 1 TiB data was always interrupted with 
SSD being gone until forced restart of the machine, unless I paused and 
resumed it myself quite an amount of times.

With 8B2QJXD7 two scrubs of 2 TiB in a row completed without any issue.

Happy to have this sorted. Thanks for firmware update to Samsung!

So make a backup and update your firmware!


What a mess, really: Just took some years until I finally seem to have a 
fully working product. And it has not been the first firmware issue I have 
seen. Not even the first issue regarding this SSD model. Also I still 
remember "no operating system found" with Intel SSD 320 after unsafe 
shutdown with a firmware that should even fix this issue and despite this 
SSD even having some sort of Power Loss Protection (PLP) unlike the 
Samsung 990 Pro.

Another note to Samsung: Pretty please update the way you create your 
firmware ISOs. Kernel 4.5.3 and it does not even boot on my laptop? You 
gotta be kidding me. Sure I can extract the update tool from initrd and 
run it manually, but really? How about just going with Linux Vendor 
Firmware Service via fwupd? Then I would have seen this update much 
earlier.

Best,
-- 
Martin



  reply	other threads:[~2026-11-14 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14 11:57 SSD overheating during scrub in laptop Martin Steigerwald
2025-09-14 21:28 ` Qu Wenruo
2025-09-14 21:33   ` Qu Wenruo
2025-09-16 11:36     ` Martin Steigerwald
2025-09-16 21:17       ` Qu Wenruo
2026-11-14 10:29         ` Martin Steigerwald [this message]
2026-11-14 11:05           ` SSD overheating during scrub in laptop (SOLVED: no overheating but firmware issue) Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=-8JrlgE5SLizPVsfOSFaOg@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox