From: Juan P C <audioprof2002@hotmail.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Temperature sensing, behaviour modification.
Date: Sat, 27 Apr 2024 22:35:55 +0000 [thread overview]
Message-ID: <BN0PR20MB4088A979B801440FA654F044B2152@BN0PR20MB4088.namprd20.prod.outlook.com> (raw)
long time ago, i purchased an 64GB Lexar 1000x µSD card,
wanted to go faster, and made the mistake to format in a wrong block size...
also made another mistake,
sending several GB of files in 1 copy & paste.
Result:
µSD overheated and got permanently damaged,
Fast forward Yesterday,....
i purchased a 2TB PNY XLR8 CS3140,
formatted to XFS,
sent several GB of files in 1 move & delete.
Result:
CS3140 overheated and got permanently damaged,
New, 1 hour of use.
The problmem is low efficiency,
low MB/s per Watt
Low Efficiency = Heat,
Heat kills NAND modules.
you can blame PNY switching to cheaper 112-Layer Kioxia TLC (BiCS5) in the 2TB model.
instead of the original 176-Layer Micron TLC (B47R) in 1TB model.
you can blame the CS3140 2TB Firmware,
but in the End is Temperature...
Linux OS should monitor PCIe / SSD drive SMART temperature...
and Pause File Transfer Automatically until Temperature return to Normal.
Give a Warning, and countdown clock or cancel transfer button.
There is No point to continue file transfer if drive gets damaged, after transfer is complete.
Rabbit vs. Turtle story.
i was using USB3.1 enclosure with RTL9210-2 / -CG controller... <500MB/s
Drive is Rated for 7000MB/s
Enclosure has No problem using higher efficiency M.2 drives.
https://www.pny.com/company/support/solid-state-drives
https://www.tomshardware.com/reviews/pny-xlr8-cs3140-ssd-review/2
https://www.orico.cc/us/product/detail/8039.html
reply other threads:[~2024-04-27 22:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN0PR20MB4088A979B801440FA654F044B2152@BN0PR20MB4088.namprd20.prod.outlook.com \
--to=audioprof2002@hotmail.com \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.