- Home
- Categorie
- Gaming, Hardware e Software
- Software (Windows - Linux - Apple) & Applicazioni
- thunderbird o disco guasto?
-
thunderbird o disco guasto?
Ho una rete mista, i file più importanti la condivisione delle stampanti ecc, le tengo su un pc debian.
Sulla mia macchina debian (senza interfacccia grafica) tengo anche la posta con thunderbird, per capirci: ho installato thunderbird su 2 macchine windows con due profili ciascuno mentre i messsaggi le impostazioni e quantaltro sono su debian.
Il problema è che un giorno si e uno no quando tento di aprire uno o tutti e due i profili non c'è più nulla e thunderbird mi chiede di creare le impostazioni come se si trattasse di profilo nouvo.
Il culmine l'ho toccato questa sera i profili appena sistemati, recuperati i backup, aggiunti i messaggi mancanti hanno durato ben 3 minuti.
(sono sul disperato andante)
Ho fatto un controllo del disco leggendo una guida su smartctl e usando il comando smartctl -a /dev/hda.Vi allego il risultato sperando che voi capiate più di quanto non sia riuscito a fare io.
Grazie in anticipo.debian2:~# smartctl -a /dev/hda
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is [url=http://smartmontools.sourceforge.net/]smartmontools Home Page (last updated $Date: 2006/06/13 12:49:03 $)=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SP0411N
Serial Number: S01JJ40XA89170
Firmware Version: TW100-11
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Wed Jul 19 00:21:46 2006 CEST==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details.
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: PASSEDGeneral SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
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: ( 900) seconds.
Offline data collection
capabilities: (0x1b) 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.
No 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 15) minutes.SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 051 Pre-fail Always - 12
3 Spin_Up_Time 0x0007 075 063 000 Pre-fail Always - 4672
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1242
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 253 253 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0024 253 253 000 Old_age Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 326966
10 Spin_Retry_Count 0x0013 253 253 049 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 769
194 Temperature_Celsius 0x0022 163 130 000 Old_age Always - 25
195 Hardware_ECC_Recovered 0x000a 100 100 000 Old_age Always - 164643746
196 Reallocated_Event_Count 0x0012 253 253 000 Old_age Always - 0
197 Current_Pending_Sector 0x0033 253 253 010 Pre-fail Always - 0
198 Offline_Uncorrectable 0x0031 253 253 010 Pre-fail Offline - 0
199 UDMA_CRC_Error_Count 0x000b 100 092 051 Pre-fail Always - 5438
200 Multi_Zone_Error_Rate 0x000b 100 100 051 Pre-fail Always - 0
201 Soft_Read_Error_Rate 0x000b 100 100 051 Pre-fail Always - 0SMART Error Log Version: 1
ATA Error Count: 16405 (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:mmS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.Error 16405 occurred at disk power-on lifetime: 2722 hours (113 days + 10 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 c2 4f e0 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 da 00 00 c2 4f e0 00 08:21:32.938 SMART RETURN STATUS
ec 00 00 26 00 db e0 00 08:21:32.688 IDENTIFY DEVICE
ef 02 00 00 00 00 e0 00 00:00:58.813 SET FEATURES [Enable write cache]
c6 00 10 00 00 00 e0 00 00:00:58.813 SET MULTIPLE MODE
10 00 ff 00 00 00 e0 00 00:00:58.750 RECALIBRATE [OBS-4]Error 16404 occurred at disk power-on lifetime: 2714 hours (113 days + 2 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 ed c2 4f b0 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 da 00 ed c2 4f b0 00 01:05:25.750 SMART RETURN STATUS
c4 00 01 26 92 43 f4 00 00:33:24.063 READ MULTIPLE
c4 00 01 00 00 00 f0 00 00:33:24.063 READ MULTIPLE
c4 00 01 00 00 00 f0 00 00:33:24.063 READ MULTIPLE
c4 00 01 77 00 01 f0 00 00:33:22.813 READ MULTIPLEError 16403 occurred at disk power-on lifetime: 1105 hours (46 days + 1 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
84 51 00 b8 6f 01 e2 Error: ICRC, ABRT at LBA = 0x02016fb8 = 33648568
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 00 b8 6f 01 e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6f 00 e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e ff e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e fe e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e fd e2 00 01:11:01.125 READ DMAError 16402 occurred at disk power-on lifetime: 1105 hours (46 days + 1 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
84 51 00 b8 6e f7 e2 Error: ICRC, ABRT at LBA = 0x02f76eb8 = 49770168
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 00 b8 6e f7 e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e f6 e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e f5 e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e f4 e2 00 01:11:01.125 READ DMA
c8 00 00 b8 6e f3 e2 00 01:11:01.063 READ DMAError 16401 occurred at disk power-on lifetime: 1105 hours (46 days + 1 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
84 51 00 18 6a ea e2 Error: ICRC, ABRT at LBA = 0x02ea6a18 = 48917016
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 00 18 6a ea e2 00 01:11:01.063 READ DMA
c8 00 00 18 6a e9 e2 00 01:11:01.000 READ DMA
c8 00 00 18 6a e8 e2 00 01:11:01.000 READ DMA
c8 00 00 18 6a e7 e2 00 01:11:01.000 READ DMA
c8 00 00 18 6a e6 e2 00 01:11:01.000 READ DMAWarning! SMART Self-Test Log Structure error: invalid SMART checksum.
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]Device does not support Selective Self Tests/Logging
debian2:~#
-
che filesystem hai montato sul disco?
prova con un e2fsck, ti dovrebbe dare molti più dati che il cechk dello status dello smart...
-
ext3, la prossima volta volta ti garantisco che non lo adopero più.