Page 1 of 1
Bug In HP Solid State Drive Firmware Kills Drives @3-1/2 Yrs
Posted: Thu 12 Dec 2019, 06:18
by perdido
Some HP SSD drives will die after 32,768 hours of use (3-1/2 years)
Supposed to be a patch available
Original advisory from HP with all pertinent info, drive models, etc
https://support.hpe.com/hpsc/doc/public ... 92491en_us
SUPPORT COMMUNICATION - CUSTOMER BULLETIN
Document ID: a00092491en_us
Version: 3
Bulletin: (Revision) HPE SAS Solid State Drives - Critical Firmware Upgrade Required for Certain HPE SAS Solid State Drive Models to Prevent Drive Failure at 32,768 Hours of Operation
https://hackaday.com/2019/12/10/patch-o ... r-and-die/
https://www.bleepingcomputer.com/news/h ... rs-of-use/
" According to the advisory, the failure is unavoidable unless the new firmware is installed, and SSDs installed at the same time are likely to fail "nearly simultaneously."
.
Posted: Thu 12 Dec 2019, 07:47
by jamesbond
Bug? Or planned obsolence, caught red-handed, Apple-style?
Posted: Thu 12 Dec 2019, 12:25
by mikeb
Lol.... HP wanting you to landfill... unbelieveable!!
Anyway I had two identical Pioneer dvd drives.
One was used nearly daily to burn many CDs , the other sat pretty much idle in another machine. Only thing in common was being powered up each day.
Both started to give write errors after exactly two years...hmmm
I am never cynical or paranoid.... WHO SAID THAT?!!
mike off to reboot himself...
Re: Bug In HP Solid State Drive Firmware Kills Drives @3-1/2 Yrs
Posted: Thu 12 Dec 2019, 12:38
by rcrsn51
.
Posted: Fri 13 Dec 2019, 16:01
by Burn_IT
That is a typical overflow bug that many people who write programs where space is critical fall for.
It is the result of using a fixed binary 15(2 byte) field instead of a fixed binary 31(4 byte) field.
Posted: Fri 13 Dec 2019, 17:12
by Wiz57
Burn_IT wrote:That is a typical overflow bug that many people who write programs where space is critical fall for.
It is the result of using a fixed binary 15(2 byte) field instead of a fixed binary 31(4 byte) field.
Brings back memories of the "Y2K" fiasco...the more things change,
the more they remain the same.
OR...the Y2K bug really DID occur, and we're actually living out "sim lives"
in non-volatile, non-writable RAM somewhere!
Posted: Fri 13 Dec 2019, 20:48
by Burn_IT
The Y2K bug was a huge non event.
I spent a solid 6 month doing nothing but read through the source code of programs to identify and fix those that would suffer from it.
I think I had to alter about 6 programs in total (out of thousands)
I also made a fortune by just remaining on call over the new year period.
I wasn't called out once.
Posted: Fri 13 Dec 2019, 21:32
by perdido
As mikeb pointed out, this could have been going on for a number of years with different components.
I never realised SSD hard drives would require upgradeable flash memory.
Except maybe in case the manufacturers get caught and are shamed into fixing their own sabotage?
Can my USB sticks be ticking time bombs?
I wonder if RAM has upgradeable flash memory.
I wonder if the upgradeable flash memory has upgradeable flash memory?
.
Posted: Sat 14 Dec 2019, 01:57
by cthisbear
" I wasn't called out once. "
Not even for the toasters that stopped working?
::::
I made some money then as well.
Nobody could really predict what would happen.
Chris.
Posted: Sat 14 Dec 2019, 10:57
by mikeb
I made some money then as well.
Someone offered me the 'software' to do this at the time but it seemed like an obvious scam which of course it turned out to be so.
Also the person in question was a high flying business executive apparently that turned out to live on the top floor of a block of flats on one of Hull seediest estates....
Now as for the toasters that will turn on us in 2020 I am prepared by not having one...or a microwave....or a freezer.... i feel safe but un equipped for fast food..
mike