On 27.01.2022 20:49, Roman Tyczka wrote:
> Czy da się z nim coś zrobić?

Po kilku dniach pobytu dysku w serwerze w idlu, wykonywaniu na nim wielu
poleceń typu blkdiscard i hdparm dysk trochę odżył i da się na nim teraz
założyć partycję, choć nadal nie jest bezproblemowy, bo np. polecenie
wymuszające trima na całości, czyli:

i=0; while [ $i -lt 937703088 ]; do echo $i:40000; i=$(((i+40000)));
done | hdparm --please-destroy-my-drive --trim-sector-ranges-stdin /dev/sde

po kilkudziesięciu obrotach pętli się przerywa z błędem:

trimming 16120000 sectors from 403 ranges
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40
00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
succeeded

Obecnie jego smart wygląda tak:

$ sudo smartctl --all /dev/sdd
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.0-30-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron Client SSDs
Device Model: CT480BX500SSD1
Serial Number: 2011E3EF0DF3
LU WWN Device Id: 0 000000 000000000
Firmware Version: M6CR022
User Capacity: 480 103 981 056 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Feb 22 16:07:19 2022 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 000 100 000 Pre-fail Always
- 0
5 Reallocate_NAND_Blk_Cnt 0x0032 100 100 010 Old_age Always
- 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always
- 4163
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
- 2068
171 Program_Fail_Count 0x0032 100 100 000 Old_age Always
- 0
172 Erase_Fail_Count 0x0032 000 000 000 Old_age Always
- 0
173 Ave_Block-Erase_Count 0x0032 007 007 000 Old_age Always
- 152
174 Unexpect_Power_Loss_Ct 0x0032 100 100 000 Old_age Always
- 264
180 Unused_Reserve_NAND_Blk 0x0033 100 100 000 Pre-fail Always
- 224
183 SATA_Interfac_Downshift 0x0032 100 100 000 Old_age Always
- 99
184 Error_Correction_Count 0x0032 100 100 000 Old_age Always
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always
- 0
194 Temperature_Celsius 0x0022 069 021 000 Old_age Always
- 31 (Min/Max 7/79)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always
- 0
197 Current_Pending_ECC_Cnt 0x0032 100 100 000 Old_age Always
- 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always
- 243
202 Percent_Lifetime_Remain 0x0030 093 093 001 Old_age
Offline - 7
206 Write_Error_Rate 0x000e 000 000 000 Old_age Always
- 0
210 Success_RAIN_Recov_Cnt 0x0032 100 100 000 Old_age Always
- 0
246 Total_LBAs_Written 0x0032 100 100 000 Old_age Always
- 29072131182
247 Host_Program_Page_Count 0x0032 100 100 000 Old_age Always
- 908504099
248 FTL_Program_Page_Count 0x0032 100 100 000 Old_age Always
- 1166800416

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 1

ATA Error Count: 0
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error -2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active
or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e5 00 00 00 00 00 00 08 00:00:00.000 CHECK POWER MODE
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
60 08 48 60 18 84 40 08 00:00:00.000 READ FPDMA QUEUED
60 20 30 20 e7 88 40 08 00:00:00.000 READ FPDMA QUEUED
60 20 e0 b0 a8 89 40 08 00:00:00.000 READ FPDMA QUEUED

Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active
or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 00 00 00 40 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE
THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
ec 00 01 00 00 00 00 08 00:00:00.000 IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 4163
-
# 2 Short offline Completed without error 00% 4087
-
# 3 Extended offline Completed without error 00% 3944
-
# 4 Extended offline Completed without error 00% 3743
-
# 5 Extended offline Completed without error 00% 3698
-
# 6 Short offline Completed without error 00% 3695
-
# 7 Extended offline Completed without error 00% 3695
-
# 8 Extended offline Interrupted (host reset) 60% 3632
-
# 9 Short offline Completed without error 00% 3632
-

Jakieś nowe wnioski?


ps. firmware ma najnowszy dostępny.

--
pzdr
Roman

do góry

Wcale nie przypadkiem, dnia Tue, 22 Feb 2022 16:25:31 +0100
doszła do mnie wiadomość <6215006c$0$470$65785112@news.neostrada.pl>
od Roman Tyczka <r...@h...you.spammer> :
>On 27.01.2022 20:49, Roman Tyczka wrote:
>> Czy da się z nim coś zrobić?
>
>Po kilku dniach pobytu dysku w serwerze w idlu, wykonywaniu na nim wielu
>poleceń typu blkdiscard i hdparm dysk trochę odżył i da się na nim teraz
>założyć partycję, choć nadal nie jest bezproblemowy, bo np. polecenie
>wymuszające trima na całości, czyli:
>
>i=0; while [ $i -lt 937703088 ]; do echo $i:40000; i=$(((i+40000)));
>done | hdparm --please-destroy-my-drive --trim-sector-ranges-stdin /dev/sde
>
>po kilkudziesięciu obrotach pętli się przerywa z błędem:
>
>trimming 16120000 sectors from 403 ranges
>SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40
>00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>succeeded

TRIM nie działa, blkdiscard coś zgłaszał? Weryfikowałeś, czy dysk jest
wyzerowany?
Jeśli można spartycjonować, to czy da się coś zapisać? Zapisane dane
zostają po odłączeniu i ponownym podłączeniu zasilania? Może on jest w
trybie read-only?
Reszta mało istotna.
Prawdopodobnie skaszaniony firmware/translator czy coś podobnego w
oprogramowaniu wewnętrznym, można go jeszcze rozebrać i zrobić pomiar
napięć zasilających, może jakieś elementy na płytce wysiadły.

--
Szwambuł Trantiputl
Inter stercus/faeces et urinam nascimur
Rodzimy się między łajnem i uryną

do góry