Forum Ubuntu-it

Il forum della comunità italiana di Ubuntu.
https://forum.ubuntu-it.org/

Controllare l'integrità del disco fisso

https://forum.ubuntu-it.org/viewtopic.php?f=9&t=204930

Pagina 1 di 1

Controllare l'integrità del disco fisso

Inviato: giovedì 17 luglio 2008, 11:31
da genesis
Ciao, voglio controllare il mio disco fisso, ma ricevo strani risultati...

Voglio premettere che forse avrei già dovuto cambiare disco fisso: prima di metterci ubuntu, su questo pc c'era xp ed un bel giorno (-.-) il mio pc era morto, non partiva. Successivamente siamo riusciti a rimetterlo a posto, quanto bastava per recuperare files e farlo funzionare anche abb bene, l'unico problema e che certe zone erano proprio andate.. ossia vari files erano corrotti, altri all'aprirli davano i contenuti di altri! (es: aprendo un video, mi dava pochi secondi di un altro che non c'entrava niente -.-). Alla fine mi sono deciso a salvare i files importanti, formattare tutto e metterci ubuntu.

Ora, attualmente ho visto strani comportamenti anche su ubuntu (es il comando per fare un mount di una iso me lo legge come man mount! e altre piccole stranezze) perciò mi son deciso a contollarlo seguendo le indicazioni di un altro topic trovato in questo forum ma ricevo i seguenti risultati (usando il cd live di ubuntu!):

Codice: Seleziona tutto

ubuntu@ubuntu:~$ sudo umount -a
umount: /tmp: device is busy
umount: /dev/shm: device is busy
umount: /dev: device is busy
umount: /var/run: device is busy
umount: tmpfs: not found
umount: /lib/modules/2.6.24-19-generic/volatile: not mounted



ubuntu@ubuntu:~$ fuser -a /tmp
/tmp:                 9129c  9142c
ubuntu@ubuntu:~$ fuser -k /tmp
/tmp:                 9129c  9142c
ubuntu@ubuntu:~$ fuser -a /tmp
/tmp:
ubuntu@ubuntu:~$ sudo fsck /tmp
fsck 1.40.8 (13-Mar-2008)
fsck: fsck.tmpfs: not found
fsck: Error 2 while executing fsck.tmpfs for tmpfs



ubuntu@ubuntu:~$ fuser -a /dev/shm
/dev/shm:
ubuntu@ubuntu:~$ fuser -k /dev/shm 
ubuntu@ubuntu:~$ sudo umount /dev/shm
umount: /dev/shm: device is busy
umount: /dev/shm: device is busy



ubuntu@ubuntu:~$ fuser -a /dev
/dev:
ubuntu@ubuntu:~$ fuser -k /dev
ubuntu@ubuntu:~$ sudo umount /dev
umount: /dev: device is busy
umount: /dev: device is busy



ubuntu@ubuntu:~$ fuser -a /var/run
/var/run:
ubuntu@ubuntu:~$ fuser -k /var/run
ubuntu@ubuntu:~$ sudo umount /var/run
umount: /var/run: device is busy
umount: /var/run: device is busy
Perchè mi da "device is busy" se poi controllando con fuser vedo che non c'e' nessun processo in corso?
Anche provando a fare fuser -k non cambia niente e continua busy, perchè?

Qualcuno potrebbe anche spiegarmi il risultato ottenuto su /tmp ?

Grazie per le eventuali risposte, ed scusate il post lungo.

Re: Controllare l'integrità del disco fisso

Inviato: giovedì 17 luglio 2008, 12:19
da carver55
per /tmp non lo so, può darsi dipenda dal fatto che stai usando una live. Per gli altri la risposta è normale.Se hai dei dubbi sul disco installa da synptic smartmontools e smart-notifier  fagli analizzare il disco

Re: Controllare l'integrità del disco fisso

Inviato: giovedì 17 luglio 2008, 16:45
da genesis
Allora, ho provato smart-notifier e non è successo nulla, mentre con smartctl ho ottenuto questo

Codice: Seleziona tutto

elva@elva-desktop:~$ sudo smartctl -a /dev/sda1
[sudo] password for elva: 
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.8 family
Device Model:     ST3200826AS
Serial Number:    4ND0BRYD
Firmware Version: 3.03
User Capacity:    200,049,647,616 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 2
Local Time is:    Thu Jul 17 16:20:34 2008 CEST
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:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
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: 		 ( 423) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  91) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   060   055   006    Pre-fail  Always       -       79585834
  3 Spin_Up_Time            0x0002   099   098   000    Old_age   Always       -       0
  4 Start_Stop_Count        0x0033   099   099   020    Pre-fail  Always       -       1748
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       328129852
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5898
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0033   099   099   020    Pre-fail  Always       -       1740
194 Temperature_Celsius     0x0022   041   046   000    Old_age   Always       -       41 (Lifetime Min/Max 0/11)
195 Hardware_ECC_Recovered  0x001a   060   055   000    Old_age   Always       -       79585834
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 TA_Increase_Count       0x0032   100   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 5492 (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 5492 occurred at disk power-on lifetime: 4931 hours (205 days + 11 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
  -- -- -- -- -- -- --
  40 51 01 13 b3 69 e0  Error: UNC at LBA = 0x0069b313 = 6927123

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 01 13 b3 69 e0 00      00:47:21.792  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:21.770  READ DMA EXT
  42 00 02 15 b3 69 e0 00      00:47:21.750  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:21.726  READ DMA EXT
  42 00 02 13 b3 69 e0 00      00:47:18.488  READ VERIFY SECTOR(S) EXT

Error 5491 occurred at disk power-on lifetime: 4931 hours (205 days + 11 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
  -- -- -- -- -- -- --
  40 51 02 13 b3 69 e0  Error: UNC at LBA = 0x0069b313 = 6927123

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 02 13 b3 69 e0 00      00:47:08.624  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:08.603  READ DMA EXT
  42 00 04 13 b3 69 e0 00      00:47:08.582  READ VERIFY SECTOR(S) EXT
  42 00 04 0f b3 69 e0 00      00:47:08.558  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:18.488  READ DMA EXT

Error 5490 occurred at disk power-on lifetime: 4931 hours (205 days + 11 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
  -- -- -- -- -- -- --
  40 51 04 13 b3 69 e0  Error: UNC at LBA = 0x0069b313 = 6927123

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 04 13 b3 69 e0 00      00:47:08.624  READ VERIFY SECTOR(S) EXT
  42 00 04 0f b3 69 e0 00      00:47:08.603  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:08.582  READ DMA EXT
  42 00 08 17 b3 69 e0 00      00:47:08.558  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:05.320  READ DMA EXT

Error 5489 occurred at disk power-on lifetime: 4931 hours (205 days + 11 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
  -- -- -- -- -- -- --
  40 51 04 13 b3 69 e0  Error: UNC at LBA = 0x0069b313 = 6927123

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 08 0f b3 69 e0 00      00:47:08.624  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:08.603  READ DMA EXT
  42 00 10 0f b3 69 e0 00      00:47:08.582  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:08.558  READ DMA EXT
  42 00 10 ff b2 69 e0 00      00:47:05.320  READ VERIFY SECTOR(S) EXT

Error 5488 occurred at disk power-on lifetime: 4931 hours (205 days + 11 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
  -- -- -- -- -- -- --
  40 51 0c 13 b3 69 e0  Error: UNC at LBA = 0x0069b313 = 6927123

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 10 0f b3 69 e0 00      00:47:08.624  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:08.603  READ DMA EXT
  42 00 10 ff b2 69 e0 00      00:47:08.582  READ VERIFY SECTOR(S) EXT
  25 00 01 00 00 00 e0 00      00:47:08.558  READ DMA EXT
  42 00 20 1f b3 69 e0 00      00:47:05.320  READ VERIFY SECTOR(S) EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Nel complesso mi dice che è ok, ma con tutti questi errori, non sarà che mi conviene cambiarlo? è possibile che alcuni strani problemi che ho avuto con il terminale siano dovuti al disco fisso?

Re: Controllare l'integrità del disco fisso

Inviato: giovedì 17 luglio 2008, 16:50
da carver55
gli errori sembrano essersi verificati tutti all'accensione. Non saprei dirti. Sarebbe meglio facessi un po' di ricerche su google
Tutti gli orari sono UTC+02:00 Europa/Roma
Pagina 1 di 1

Basato su phpBB® Forum Software © phpBB Limited • PostgreSQL© • Megmoticons©