2
3
Купил новый SSD, и при каждом ребуте он прибавляет ровно 1 ошибку
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 11 0 0x100f 0x4004 - 0 0 -полный лог
sudo smartctl -a /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.18.0-3-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZVLB256HBHQ-00000
Serial Number: S4GGNX0RC91284
Firmware Version: EXH7201Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 256,060,514,304 [256 GB]
Unallocated NVM Capacity: 0
Controller ID: 4
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 256,060,514,304 [256 GB]
Namespace 1 Utilization: 88,786,948,096 [88.7 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 8c11c5d479
Local Time is: Wed Aug 3 16:59:34 2022 MSK
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x03): S/H_per_NS Cmd_Eff_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.00W - - 0 0 0 0 0 0
1 + 6.30W - - 1 1 1 1 0 0
2 + 3.50W - - 2 2 2 2 0 0
3 - 0.0760W - - 3 3 3 3 210 1200
4 - 0.0050W - - 4 4 4 4 2000 8000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 34 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 425,685 [217 GB]
Data Units Written: 279,397 [143 GB]
Host Read Commands: 13,091,553
Host Write Commands: 1,869,139
Controller Busy Time: 11
Power Cycles: 3
Power On Hours: 3
Unsafe Shutdowns: 1
Media and Data Integrity Errors: 0
Error Information Log Entries: 11
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 34 Celsius
Temperature Sensor 2: 41 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 11 0 0x100f 0x4004 - 0 0 -
Погуглил, нашёл похожие темы, но не нашёл решение. Как исправить, кто знает? Говорят это что-то то ли с прошивкой SSD, то ли с версией kernel, то ли ещё что…
Recently I installed Xubuntu 22.04.1 on a system that contains a Micron MTFDHBA512QFD NVMe disk.
The last line on the smartctl -a report is the following:
Error Information (NVMe Log 0x01, 16 of 256 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 17 0 0x700c 0x4005 - 0 1 -
The error counter increases by 1 every time the system starts.
Is there any way for me to read that log and find out what those errors are and what causes them every time I start the system?
NotTheDr01ds
11.8k2 gold badges42 silver badges68 bronze badges
asked Nov 12, 2022 at 17:53
From what I’ve found so far, it seems that there is no actual error. Other brands are facing the same issue and the most official answer to that was by Transcend.
Their answer was that some platforms are sending commands unknown to SSD drives during system startup. This results in a corresponding response by the drive saying that it doesn’t support those specific commands, and this is recorded in the SMART Error Logs. That’s all. Drive usage is not affected at all by this issue.
Nevertheless, if anyone else knows something different, please post it.
NotTheDr01ds
11.8k2 gold badges42 silver badges68 bronze badges
answered Nov 13, 2022 at 19:53
StormlordStormlord
5,6392 gold badges24 silver badges38 bronze badges
1
Have you tried downloading and installing Storage Executive Software for Linux Systems?
It might offer more information on the health of the SSD drive, and a firmware upgrade, if available.
answered Nov 15, 2022 at 16:42
GeorgeGeorge
1628 bronze badges
Доброго
LM 20.2 cinamon x64
на буке стоит один ссд
Диск /dev/loop0: 4 KiB, 4096 байт, 8 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop1: 61,79 MiB, 64770048 байт, 126504 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop2: 61,85 MiB, 64835584 байт, 126632 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop3: 32,32 MiB, 33878016 байт, 66168 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop4: 65,22 MiB, 68378624 байт, 133552 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop5: 307,46 MiB, 322387968 байт, 629664 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop6: 308,35 MiB, 323321856 байт, 631488 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop7: 32,42 MiB, 33980416 байт, 66368 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/nvme0n1: 238,49 GiB, 256060514304 байт, 500118192 секторов
Disk model: KINGSTON RBUSNS8154P3256GJ1
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Тип метки диска: gpt
Идентификатор диска: 2DE22DAF-3520-4534-9B00-040167D620FC
Устр-во начало Конец Секторы Размер Тип
/dev/nvme0n1p1 2048 1050875 1048828 512,1M EFI
/dev/nvme0n1p2 1052672 197382143 196329472 93,6G Файловая система Linux
/dev/nvme0n1p3 197382144 201381887 3999744 1,9G Linux своп
/dev/nvme0n1p4 201381888 500117503 298735616 142,5G Файловая система Linux
Диск /dev/sda: 28,9 GiB, 31004295168 байт, 60555264 секторов
Disk model: DataTraveler 3.0
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Тип метки диска: dos
Идентификатор диска: 0x2af71e68
Устр-во Загрузочный начало Конец Секторы Размер Идентификатор Тип
/dev/sda1 2048 60555263 60553216 28,9G c W95 FAT32 (
Диск /dev/loop8: 55,45 MiB, 58130432 байт, 113536 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop9: 450,25 MiB, 472117248 байт, 922104 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Диск /dev/loop10: 450,25 MiB, 472113152 байт, 922096 секторов
Единицы: секторов по 1 * 512 = 512 байт
Размер сектора (логический/физический): 512 байт / 512 байт
Размер I/O (минимальный/оптимальный): 512 байт / 512 байт
Не счего начала появляться эта ошибка Device: /dev/nvme0, number of Error Log entries increased from 1344 to 1345
Что это и как исправить подскжите.
вот еще smartctl -a /dev/nvme0 :
martctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-88-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke,
www.smartmontools.org
Smartctl open device: /dev/nvme0 failed: Permission denied
seregka@MyAcer ~ [0:55:22]
> $ sudo smartctl -a /dev/nvme0
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-88-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke,
www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: KINGSTON RBUSNS8154P3256GJ1
Serial Number: 50026B76842E424A
Firmware Version: E8FK12.3
PCI Vendor/Subsystem ID: 0x2646
IEEE OUI Identifier: 0x0026b7
Total NVM Capacity: 256 060 514 304 [256 GB]
Unallocated NVM Capacity: 0
Controller ID: 0
Number of Namespaces: 1
Namespace 1 Size/Capacity: 256 060 514 304 [256 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 0026b7 6842e424a5
Local Time is: Fri Oct 15 00:55:32 2021 +05
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0007): Security Format Frmw_DL
Optional NVM Commands (0x001e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.90W 0.0790W — 0 0 0 0 600 600
1 + 7.90W 0.0790W — 0 0 0 0 600 600
2 + 7.90W 0.0790W — 0 0 0 0 600 600
3 — 0.1000W 0.0790W — 3 3 3 3 1000 1000
4 — 0.0050W 0.0790W — 4 4 4 4 400000 90000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 1
1 — 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 32 Celsius
Available Spare: 100%
Available Spare Threshold: 100%
Percentage Used: 1%
Data Units Read: 6 776 670 [3,46 TB]
Data Units Written: 8 127 362 [4,16 TB]
Host Read Commands: 96 096 107
Host Write Commands: 71 074 113
Controller Busy Time: 124
Power Cycles: 1 628
Power On Hours: 277
Unsafe Shutdowns: 40
Media and Data Integrity Errors: 0
Error Information Log Entries: 1 345
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 2: 32 Celsius
Error Information (NVMe Log 0x01, max 16 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 1345 0 0x000a 0x0004 — 4009754624 1 —
1 1344 0 0x000a 0x0004 — 4009754624 1 —
2 1343 0 0x000a 0x0004 — 4009754624 1 —
3 1342 0 0x000a 0x0004 — 4009754624 1 —
4 1341 0 0x000a 0x0004 — 4009754624 1 —
5 1340 0 0x000a 0x0004 — 4009754624 1 —
6 1339 0 0x000a 0x0004 — 4009754624 1 —
7 1338 0 0x000a 0x0004 — 4009754624 1 —
8 1337 0 0x000a 0x0004 — 4009754624 1 —
9 1336 0 0x000a 0x0004 — 4009754624 1 —
10 1335 0 0x000a 0x0004 — 4009754624 1 —
11 1334 0 0x000a 0x0004 — 4009754624 1 —
12 1333 0 0x000a 0x0004 — 4009754624 1 —
13 1332 0 0x000a 0x0004 — 4009754624 1 —
14 1331 0 0x000a 0x0004 — 4009754624 1 —
15 1330 0 0x000a 0x0004 — 4009754624 1 —
Последний раз редактировалось пользователем 1 seregka; всего редактировалось раз: 14
Будьте добрее к этому миру, даже если мир не добр к вам.
-
#1
Hello. I was wondering if anyone can tell me what these mean. From most people posting about them, there is no more than double digits. However, I have 1051556645921812989870080 Media and Data Integrity Errors on my SK hynix PC711 on my new HP dev one. Thanks!
Here’s my entire smartctl output
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.0.7-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, smart mon tools
=== START OF INFORMATION SECTION ===
Model Number: SK hynix PC711 HFS001TDE9X073N
Serial Number: KDB3N511010503A37
Firmware Version: HPS0
PCI Vendor/Subsystem ID: 0x1c5c
IEEE OUI Identifier: 0xace42e
Total NVM Capacity: 1,024,209,543,168 [1.02 TB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1,024,209,543,168 [1.02 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: ace42e 00254f98f1
Local Time is: Wed Nov 9 13:58:37 2022 EST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x001f): Security Format Frmw_DL NS_Mngmt Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Namespace 1 Features (0x02): NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.3000W — — 0 0 0 0 5 5
1 + 2.4000W — — 1 1 1 1 30 30
2 + 1.9000W — — 2 2 2 2 100 100
3 — 0.0500W — — 3 3 3 3 1000 1000
4 — 0.0040W — — 3 3 3 3 1000 9000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
1 — 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 34 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 0%
Data Units Read: 13,162,025 [6.73 TB]
Data Units Written: 3,846,954 [1.96 TB]
Host Read Commands: 156,458,059
Host Write Commands: 128,658,566
Controller Busy Time: 116
Power Cycles: 273
Power On Hours: 126
Unsafe Shutdowns: 15
Media and Data Integrity Errors: 1051556645921812989870080
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 34 Celsius
Temperature Sensor 2: 36 Celsius
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
Last edited by a moderator: Nov 10, 2022
-
#2
Hello!
I am totally relieved…
I have the exactly same media and data integrity errors on my brand new HP laptop:
(there must be some bug somewhere)
smartctl -a /dev/nvme0n1
smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.14.21-150400.24.38-default] (SUSE RPM)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: SK hynix BC711 HFM512GD3JX013N
Serial Number: FYB5N027811905M2M
Firmware Version: HPS1
PCI Vendor/Subsystem ID: 0x1c5c
IEEE OUI Identifier: 0xace42e
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: ace42e 002a741846
Local Time is: Thu Jan 12 23:24:35 2023 EET
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x001f): Security Format Frmw_DL NS_Mngmt Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Namespace 1 Features (0x02): NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.3000W — — 0 0 0 0 5 5
1 + 2.4000W — — 1 1 1 1 30 30
2 + 1.9000W — — 2 2 2 2 100 100
3 — 0.0500W — — 3 3 3 3 1000 1000
4 — 0.0040W — — 3 3 3 3 1000 9000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
1 — 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 20 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 0%
Data Units Read: 1,343,349 [687 GB]
Data Units Written: 1,101,021 [563 GB]
Host Read Commands: 8,284,919
Host Write Commands: 4,079,672
Controller Busy Time: 11
Power Cycles: 22
Power On Hours: 63
Unsafe Shutdowns: 1
Media and Data Integrity Errors: 1051556645921812989870080
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 20 Celsius
Temperature Sensor 2: 24 Celsius
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
-
#3
That looks like an error in Smartctl. It looks like it’s misinterpreting the value that the drive is providing. Funny fact, the value that the drive is reporting in binary is 11011110101011010000000000000000000000000000000000000000000000000000000000000000 which translates into hexidecimal DEAD0000000000000000
kernel: [48206.099238] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48215.664426] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48215.801820] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48226.432077] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48226.552193] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48236.231765] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48236.343529] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48245.843013] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48245.962491] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48255.573382] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48255.689129] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48266.318625] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 18 prio class 0
kernel: [48266.458434] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 17 prio class 0
kernel: [48276.030256] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48276.151809] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48285.788769] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48285.919040] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48295.677259] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48295.814393] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48306.432219] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48306.558280] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48316.167333] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48316.301746] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48325.808063] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48325.937518] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48335.475759] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48335.585588] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48346.174478] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48346.282133] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48355.826348] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
kernel: [48355.933182] blk_update_request: I/O error, dev nvme2n1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 20 prio class 0Hi everyone,
I recently had a spare Oracle F320 (MS1PC2DD3ORA3.2T) that I had plugged into a U.2 to PCI-E adapter, intending to use on my workstation PC. Currently using one that’s at 100% health with no issues whatsoever.
Upon boot with it plugged in, the BIOS detects an «imminent failure» to the hardware. I decided to use smartmontools/smartctl to look at the SMART data of the drive. It displays the following:
Code:
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- volatile memory backup device has failed
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x10
Temperature: 38 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 667,382,716 [341 TB]
Data Units Written: 3,256,546 [1.66 TB]
Host Read Commands: 5,398,930,997
Host Write Commands: 25,679,853
Controller Busy Time: 4,371
Power Cycles: 545
Power On Hours: 705
Unsafe Shutdowns: 518
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors LoggedDoing a bit of Googling around doesn’t really elaborate much on that particular critical warning error. As you can see, the drive does have quite a bit of data units read/written, but the usage and spare percentages are pristine. For reference, my other current working drive is as follows:
Code:
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 42 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 55,427,535 [28.3 TB]
Data Units Written: 42,616,373 [21.8 TB]
Host Read Commands: 360,804,605
Host Write Commands: 232,288,622
Controller Busy Time: 672
Power Cycles: 2,189
Power On Hours: 11,639
Unsafe Shutdowns: 359
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors LoggedBoth drives have been updated to the newest firmware that was found on here, and the new drive has already been through a full format and trim. Has anybody encountered this issue before? I will obviously not pursue using the drive on a daily basis because of this, but would love an opinion or two.
Теперь другой сегодня купил Samsung 970Pro на 512GB отформатировал в EXT4
При запуске iostat -xm -t 5 %util доходит до 100% это нормально строку жирным выделил?
напоминаю там крутится mysql с больим онлайном
3.10.2020 22:59:40
avg-cpu: %user %nice %system %iowait %steal %idle
3,48 0,00 2,73 1,38 0,00 92,42
Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
nvme1n1 29,00 0,00 8,00 1,00 0,16 0,00 37,33 0,00 0,11 0,12 0,00 0,67 0,60
nvme0n1 0,00 72,00 2825,00 218,00 44,14 2,50 31,39 0,53 0,15 0,09 0,94 0,32 98,40
sdb 127,00 0,00 21,00 0,00 0,68 0,00 66,29 0,00 0,24 0,24 0,00 0,67 1,40
sda 0,00 0,00 1,00 0,00 0,00 0,00 0,00 0,00 1,00 1,00 0,00 2,00 0,20
sdc 0,00 0,00 1,00 0,00 0,00 0,00 0,00 0,00 1,00 1,00 0,00 1,00 0,10