Causa qualche problemino di instabilità del sistema, ma forse provocato da me,
sono andato a vedere se era colpa del disco e così ho lanciato smartctl -a /dev/sdd2 (il disco di sistema è sda2):
Codice: Seleziona tutto
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.21] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Verbatim Vi550 S3
Serial Number: 493522184831074
Firmware Version: U1125A0
User Capacity: 512,110,190,592 bytes [512 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: Not in smartctl database 7.3/5528
ATA Version is: ACS-3 T13/2161-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon May 12 13:35:23 2025 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Disabled
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Unavailable
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
[... omissis ...]
SMART Error Log Version: 1
ATA Error Count: 648 (device log contains only the most recent five errors)
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 644 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 at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 20 02 e6 e0 08 00:00:00.000 READ DMA EXT
25 00 00 a0 02 e6 e0 08 00:00:00.000 READ DMA EXT
25 00 68 98 f8 e5 e0 08 00:00:00.000 READ DMA EXT
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Selective Self-tests/Logging not supported
The above only provides legacy SMART information - try 'smartctl -x' for more
"ATA Error Count: 648 (device log contains only the most recent five errors)
...
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 644 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."
Non so cosa voglia dire error 648 e 644,
quello che mi sembra di aver capito è che gli da 0 ore di vita (lifetime)... (??)
ma c'è anche scritto "PASSED", più sopra...
E comunque, se faccio il boot dalle altre partizioni in /sda
(una slackware14 32 bit e l'altra slackware vecchia current kernel 5.19.17),
non ho scherzi... Eppure sono lo stesso disco sda.
Ma non finisce qui.
Cercando sempre per le instabilità che avevo, ho scoperto un file di più di 140 TB in /proc:
Codice: Seleziona tutto
bash-5.2# ls -l /proc/kcore
-r-------- 1 root root 140737471586304 May 12 12:59 /proc/kcore
Codice: Seleziona tutto
bash-5.2# du -h /proc/
du: cannot access '/proc/5853/task/5853/fd/3': No such file or directory
du: cannot access '/proc/5853/task/5853/fdinfo/3': No such file or directory
du: cannot access '/proc/5853/fd/4': No such file or directory
du: cannot access '/proc/5853/fdinfo/4': No such file or directory
0 /proc/
0 total
ma il disco e il kcore.
Posso star tranquillo o devo cominciare a preoccuparmi...?
Attendendo Vostre luminose diagnosi e consigli.
Intanto comincio a ringraziarvi per l'attenzione.
sistema:
Slackware 15 64bit Current - Fri Apr 4 20:30:41 UTC 2025
Codice: Seleziona tutto
bash-5.2# inxi
CPU: dual core Intel Core2 6320 (-MCP-) speed/min/max: 1596/1596/1862 MHz
Kernel: 6.12.21 x86_64 Up: 1h 3m Mem: 677.2 MiB/3.02 GiB (21.9%)
Storage: 3.19 TiB (46.8% used) Procs: 225 Shell: Bash inxi: 3.3.37