Fórum Root.cz
Hlavní témata => Hardware => Téma založeno: e3k 10. 02. 2024, 18:31:37
-
ja jen ze mi to hlasi orphaned inodes v EXT4 po soft rebootoch.
ad Unsafe Shutdowns: to bolo vtedy ked som updatoval FW pomocou vybornej Samsung utility ktora zial nepodporuje UEFI :facepalm:
ad Smart: Invalid Field in Command
ad FW: 2B2QEXM7 way too old
ako neriesil by som to ale ked mi odchadza FS...
# smartctl --all /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.7.4-artix1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 970 EVO Plus 2TB
Serial Number: S4J4NM0W609377M
Firmware Version: 2B2QEXM7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 4
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization: 198,313,590,784 [198 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 56319173a9
Local Time is: Fri Feb 9 22:21:57 2024 CET
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: 85 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.50W - - 0 0 0 0 0 0
1 + 5.90W - - 1 1 1 1 0 0
2 + 3.60W - - 2 2 2 2 0 0
3 - 0.0700W - - 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: 155,454 [79.5 GB]
Data Units Written: 2,361,653 [1.20 TB]
Host Read Commands: 1,500,387
Host Write Commands: 31,692,814
Controller Busy Time: 103
Power Cycles: 12
Power On Hours: 88
Unsafe Shutdowns: 6
Media and Data Integrity Errors: 0
Error Information Log Entries: 23
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 34 Celsius
Temperature Sensor 2: 29 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 23 0 0x000c 0x4004 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Extended Completed without error 86 - - - - -
1 Short Completed without error 86 - - - - -
nexus:[root]:/home/erik# smartctl --all /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.7.4-artix1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 970 EVO Plus 2TB
Serial Number: S4J4NM0W609377M
Firmware Version: 2B2QEXM7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 4
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization: 198,580,367,360 [198 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 56319173a9
Local Time is: Sat Feb 10 11:46:56 2024 CET
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: 85 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.50W - - 0 0 0 0 0 0
1 + 5.90W - - 1 1 1 1 0 0
2 + 3.60W - - 2 2 2 2 0 0
3 - 0.0700W - - 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: 35 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 155,472 [79.6 GB]
Data Units Written: 2,368,377 [1.21 TB]
Host Read Commands: 1,500,769
Host Write Commands: 31,835,232
Controller Busy Time: 104
Power Cycles: 12
Power On Hours: 89
Unsafe Shutdowns: 6
Media and Data Integrity Errors: 0
Error Information Log Entries: 23
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 35 Celsius
Temperature Sensor 2: 31 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 23 0 0x000c 0x4004 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Extended Completed without error 86 - - - - -
1 Short Completed without error 86 - - - - -
nexus:[root]:/home/erik# smartctl --all /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.7.4-artix1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 970 EVO Plus 2TB
Serial Number: S4J4NM0W609377M
Firmware Version: 2B2QEXM7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 4
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization: 198,860,980,224 [198 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 56319173a9
Local Time is: Sat Feb 10 15:05:01 2024 CET
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: 85 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.50W - - 0 0 0 0 0 0
1 + 5.90W - - 1 1 1 1 0 0
2 + 3.60W - - 2 2 2 2 0 0
3 - 0.0700W - - 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: 35 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 155,474 [79.6 GB]
Data Units Written: 2,370,175 [1.21 TB]
Host Read Commands: 1,500,796
Host Write Commands: 31,869,869
Controller Busy Time: 104
Power Cycles: 12
Power On Hours: 89
Unsafe Shutdowns: 6
Media and Data Integrity Errors: 0
Error Information Log Entries: 23
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 35 Celsius
Temperature Sensor 2: 31 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 23 0 0x000c 0x4004 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Extended Completed without error 86 - - - - -
1 Short Completed without error 86 - - - - -
# fwupdmgr get-devices
├─SSD 970 EVO Plus 2TB:
│ Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be
│ Summary: NVM Express solid state drive
│ Current version: 2B2QEXM7
│ Vendor: Samsung (NVME:0x144D)
│ Serial Number: S4J4NM0W609377M
│ GUIDs: 47335265-a509-51f7-841e-1c94911af66b ← NVME\VEN_144D&DEV_A808
│ c9d531ea-ee7d-5562-8def-c64d0d144813 ← NVME\VEN_144D&DEV_A808&SUBSYS_144DA801
│ 66cc31b5-6dc4-55da-9008-bf73c91a0826 ← Samsung SSD 970 EVO Plus 2TB
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
-
Mel bys bootnout usb-distro a provest poradne FSCK.. on ten ext4 se blbe opravuje kdyz je to systemovej disk.
Jinak tam nevidim zadny duvod k chybe (media/integrity errors: 0, spare 100% usage 0%)
A podivny je akorat ze zapis mas 1.2 TB a cteni jen 80 GB ... pri cca 200G datech na disku.
ad firmware update: to jde na NVMe delat za chodu, by me ani nenapadlo pozadovat uefi updater - fw se nahraje do disku novej, pak se mu rekne ze pouzivej tenhle ten, a bud se disk rebootne sam - behem beziciho systemu, anebo musis udelat power cycle (mene caste na modernich radicich).
-
ad mel bys: touchnoul sem ten fsck check na /
este aj fstrim -all
ano ten zapis navyse mi prijde divni ale takisto aj runtime ked ten disk mam uz 3+mesiace a bezi 24x7
ad fw update: fwupdmgr to nespravil. nahral som iso od vyrobcu na usb snazil sa to pustit na fujistu ktore nepodporuje legacy boot takze nevyslo. nahodil to do destopu kde mam 3 roky staru dosku tak tam to uz nabootovalo. pustil ten fw update aby som sa dozvedel ze no valid target found a nasledne pisal na samsung support.
this article is a stub!
-
Nejspis mas specifickou variantu 970EVO... viz
https://www.techpowerup.com/forums/threads/different-ssd-versions-on-the-market-available-from-samsung.314218/
... ne vsechny maj moznost/potrebu fw upgrade nad 2B2QEXM7
-
Nejspis mas specifickou variantu 970EVO... viz
https://www.techpowerup.com/forums/threads/different-ssd-versions-on-the-market-available-from-samsung.314218/
... ne vsechny maj moznost/potrebu fw upgrade nad 2B2QEXM7
zhodne jak na techpowerup.com tak i na: https://semiconductor.samsung.com/consumer-storage/support/tools/#
je vidno ze mozem ist na 4B2QEXM7. v teorii teda. v praxy ne...
-
Pokud to má jako systémový disk tak ten zápis je celkem předpokládaný, protože třeba např. Chrome zapisuje data na disk každou sekundu kvůli tomu aby bylo možné obnovit otevřené taby po pádu, atd... Já jsem si nastavil commit time asi 30 sekund právě kvůli tomu, aby ten zápis nebyl pořád.
-
Pokud to má jako systémový disk tak ten zápis je celkem předpokládaný, protože třeba např. Chrome zapisuje data na disk každou sekundu kvůli tomu aby bylo možné obnovit otevřené taby po pádu, atd... Já jsem si nastavil commit time asi 30 sekund právě kvůli tomu, aby ten zápis nebyl pořád.
ad zapis > citanie: no bezi mi to 24x7 a je tam 32GB ram takze je mozne ze to je vsetko nacashovane v RAM a preto necita.
-
Don't panic and call your doctor.
-
dostal som sa k tomu zasa po nejakej dobe. zda sa podla tohoto clanku ze FW na mojom neupdatnem:
https://github.com/fwupd/fwupd/discussions/4141
fw update z 2B2QEXM7 -> 4B2QEXM7 je mozny len pri SN konciacich sa na "BLU" "BLB"
dalej som nasiel vela clankov kde sa ludia stazovali na to ze disk odisiel do RO modu (tu mi neni jasne ci celkovo SSD alebo iba v ramci FS)
-
dalej som nasiel vela clankov kde sa ludia stazovali na to ze disk odisiel do RO modu (tu mi neni jasne ci celkovo SSD alebo iba v ramci FS)
To je safety featura FW, ktera kdyz zafunguje, tak mas zpekla-stesti. Vlastne to je normalni stav, pote co dojdou nahradni bloky - disk zustane nezapisovatelny, a muzes z nej jenom cist.
Pak je dobry udelat kopii na jinej disk.
Jinak FS muze mit problem s tim, ze nenabehne z RO disku (napr. namountovanej fs, neco v zurnalu.. reset.. a zurnal by to chtelo zapsat zpet na disk a ono to nejde.. ). Takze muze z toho byt pripadna docasna panika, dokud to nezkusis mountnout az tu kopii na RW disku.
-
to RO sa ma netyka. ja mam "len" orphaned inodes na EXT4 hlasene skoro po kazdom soft reboote PC. ale da sa to vzdy dokopy.
-
To musí být báječné. ::)
-
to RO sa ma netyka. ja mam "len" orphaned inodes na EXT4 hlasene skoro po kazdom soft reboote PC. ale da sa to vzdy dokopy.
Nevim tedy jestli bych chtel pouzivat takovej disk.. nemohl bys alespon premigrovat z EXT4 na filesystem ktery ma block level checksum? Tj. ZFS nebo BTRFS? A i v tom pripade bych uvazoval treba o konfiguraci jako RAID1 s writemostly na hdd, ale cteni bude ze ssd.. do doby pokud budou sedet checksumy.
-
ne nebudem riesit workaroundy. ta sracka musi ist prec. kupim si 1 WD s dufam ze tou istou kapacitou a prehodim si to SSD zmazem a vyreklamujem. RAID neprichadza do uvahy nakolko ten laptop ma 1 slot na ssd/nvme a nic ine. zfs som mal pred 10 rokmi a nebol som spokojny s degradaciou vykonu po 1,5r. brtfs mi raz lahlo. ziadne experimenty. musim to reklamovat a samsung si uz nekupim.
-
jiz velky v.i.lenin rikal:
zalohujte se, zalohujte se, zalohujte se!!!
-
to RO sa ma netyka. ja mam "len" orphaned inodes na EXT4 hlasene skoro po kazdom soft reboote PC. ale da sa to vzdy dokopy.
... což znamená, že máte solidní pravděpodobnost poškození dat v souborech bez toho, aby jste si toho všiml.
-
Power Cycles: 12
Power On Hours: 88
Unsafe Shutdowns: 6
A nemůže tomu disku trochu vadit, že na celkových 12 zapnutí bylo 6 "Unsafe Shutdowns"?
-
Ty unsafe shutdowns mohou znamenat:
a. Něco (vadný zdroj, výpadek proudu, tvrdé vypnutí…) způsobilo unsafe shutdown. IIRC tlačítko reset mi toto počítadlo nenavyšuje.
b. SSD má nějaký problém (studený spoj?), který způsobuje unsafe shutdowns. Zažil jsem. Mimochodem, různé self-testy vycházely OK, asi protože flash paměť apod. fungovaly dobře, „jenom“ se mi SSD samo odpojovalo.
Pokud zároveň dochází k poškození dat, čekal bych, že to bude spíše varianta B.
-
tie unsafe shutdowns som vynutil ja stlacenim a podrzanim power tlacitka na laptope ked som bootoval fw upgrade utilitu ktora ale vyzaduje legacy BIOS co uz to fujitsu nepodporuje takze som to musel na tvrdo vypnut.
orphaned inodes som nachadzal po soft rebootoch.
-
Power Cycles: 12
Power On Hours: 88
Unsafe Shutdowns: 6
A nemůže tomu disku trochu vadit, že na celkových 12 zapnutí bylo 6 "Unsafe Shutdowns"?
tych power cycles bolo ovela viac. takisto power on hours = 88 je blbost kedze mi ten disk uz bezi skoro 24/7 rok.
-
Ale stěžovat sis začal, když měl disk natočeno 88 hodin...
-
Ale stěžovat sis začal, když měl disk natočeno 88 hodin...
ne stezoval som si po 2-3 mesiacoch pouzivania a uz vtedy to ukazovalo iba 86hodin aj ked som ho pouzival dlhsie. tie smart hodnoty nesedia.