Bonjour,

Voila quelques temps déja que j'utilise Fedora (5 puis 6) sans avoir rencontré de difficulté mageure dont je n'ai trouvé la sollution sur le forum. Mais aujourd'hui je me tourne vers vous pour m'aider à decripter un log : (désolé pour la longueur ) :

################### Logwatch 7.3 (03/24/06) ####################
Processing Initiated: Tue Feb 27 04:32:14 2007
Date Range Processed: yesterday
( 2007-Feb-26 )
Period is day.
Detail Level of Output: 0
Type of Output: unformatted
Logfiles for Host: salon.mi2p.com
##################################################################

--------------------- Automount Begin ------------------------

**Unmatched Entries**
create_udp_client: hostname lookup failed: No such process: 3 Time(s)
lookup_mount: exports lookup failed for .directory: 3 Time(s)
create_tcp_client: hostname lookup failed: No such process: 3 Time(s)

---------------------- Automount End -------------------------


--------------------- Kernel Begin ------------------------


WARNING: Kernel Errors Present
hda: drive_cmd: error=0x04 { DriveStat ...: 2 Time(s)
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } ...: 2 Time(s)
hdc: drive_cmd: error=0x04 { DriveStat ...: 2 Time(s)
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } ...: 2 Time(s)

---------------------- Kernel End -------------------------


--------------------- pam_unix Begin ------------------------

runuser:
Unknown Entries:
session closed for user beaglidx: 2 Time(s)
session opened for user beaglidx by (uid=0): 2 Time(s)

su:
Sessions Opened:
(uid=500) -> root: 4 Time(s)

system-config-network:
Unknown Entries:
authentication failure; logname= uid=500 euid=0 tty= ruser=Stirner rhost= user=root: 2 Time(s)


---------------------- pam_unix End -------------------------


--------------------- samba Begin ------------------------


WARNING!!!!!!
Errors when creating subnets:
No local interfaces : 1 Time(s)
No subnets to listen to. Shutting down. : 1 Time(s)

**Unmatched Entries**
nmbd/nmbd_subnetdb.c:create_subnets(189) create_subnets: Waiting for an interface to appear ... : 1 Time(s)

---------------------- samba End -------------------------


--------------------- Connections (secure-log) Begin ------------------------


Userhelper executed applications:
Stirner -> system-config-network as root: 8 Time(s)
Stirner -> system-config-securitylevel.py as root: 1 Time(s)
Stirner -> pirut as root: 2 Time(s)

---------------------- Connections (secure-log) End -------------------------


--------------------- Smartd Begin ------------------------


Offline uncorrectable sectors detected:
/dev/hdc - 19 Time(s)
1463 offline uncorrectable sectors detected

Warnings:
Warning via mail to root: successful - 2 Time(s)
Sending warning via mail to root ... - 2 Time(s)

---------------------- Smartd End -------------------------


--------------------- SSHD Begin ------------------------


SSHD Killed: 1 Time(s)

SSHD Started: 3 Time(s)

---------------------- SSHD End -------------------------


--------------------- yum Begin ------------------------


Packages Installed:
klamav.i386 0.38-4.fc6
libfwbuilder.i386 2.0.12-3.fc6
zlib-devel.i386 1.2.3-3
clamav-devel.i386 0.88.7-1.fc6
firestarter.i386 1.0.3-14.fc6
clamav-update.i386 0.88.7-1.fc6
fwbuilder.i386 2.0.12-2.fc6

---------------------- yum End -------------------------


--------------------- Disk Space Begin ------------------------

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
147G 27G 113G 20% /
/dev/hda1 99M 28M 67M 29% /boot
/dev/hdc1 151G 112G 32G 79% /home/Stirner/docs


---------------------- Disk Space End -------------------------


###################### Logwatch End #########################
Par avance merci de votre aide.
hum...

Avoir en soi des warning et des erreurs dans le fichier de log est "normal" dans la vie d'un systeme Linux...
Maintenant, sur l'analyse des traces, seules celles concernant ton DD sont genantes. Au debut des traces, tu as eu des echecs sur des commandes IDE :
WARNING: Kernel Errors Present
hda: drive_cmd: error=0x04 { DriveStat ...: 2 Time(s)
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } ...: 2 Time(s)
hdc: drive_cmd: error=0x04 { DriveStat ...: 2 Time(s)
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } ...: 2 Time(s)
Ensuite, le demon smartd qui gere l'interface SMART a detecte des secteurs defectueux sur ton 2eme DD :
Offline uncorrectable sectors detected:
/dev/hdc - 19 Time(s)
1463 offline uncorrectable sectors detected
Dans le premier cas, verifie que tes 2 nappes IDE sont bien enfoncees et connectees...

Ensuite dans le 2eme cas, sauvegarde deja tes donnees perso...Ensuite utilise les samrtmontools pour voir la sante de ton DD (/dev/hdc) : http://valaurea.free.fr/documents/sig11_smart.html : 
# smartctl -a /dev/hdc
++
Bonjour,

Sans être alarmiste, j'ai déjà eu ce genre d'erreur et 1 semaine plus tard mon disque dur était mort...
Donc, prudence et sauvegardes sont de rigueur.
7 jours plus tard
Salut,


Merci de vos réponse, toutes mes excuses pour le délais mais j'ai était pas mal débordé et en déplacement. J'ai essayé la commande smartctl en root
mais cela me retourne que la commande n'existe pas j'ai pourtant smartmontolls est bien installé.. Je vais tenté de régler ce souci et vous transmer le résultat.

@+
su -

Pas su pour se mettre en root si ça dit que la commande n'existe pas.

Je crois qu'il va falloir ajouter cette ligne quelque part d'autre pour que ça soit lisible...
Salut,

J'ai passablement honte. On est plein de certitude ce qui avec le temps nous pousse à comettre des erreurs un petit mann m'a permit de me rendre compte que l'apli ce trouve dans /usr/sbin d'ou :

en root :
./smartctl -a /dev/hdc

Et voici le résultat de la commande (désolé pour la longueur :
=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 9 family
Device Model: Maxtor 6Y160P0
Serial Number: Y46JQMNE
Firmware Version: YAR41BW0
User Capacity: 163,928,604,672 bytes
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: Tue Mar 6 09:36:15 2007 CET
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: ( 302) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 72) 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
3 Spin_Up_Time 0x0027 206 204 063 Pre-fail Always - 18086
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 94
5 Reallocated_Sector_Ct 0x0033 234 210 063 Pre-fail Always - 192
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0
8 Seek_Time_Performance 0x0027 253 240 187 Pre-fail Always - 36038
9 Power_On_Minutes 0x0032 211 211 000 Old_age Always - 353h+11m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 711
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 29
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 1994
196 Reallocated_Event_Count 0x0008 001 001 000 Old_age Offline - 314
197 Current_Pending_Sector 0x0008 253 229 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 001 001 000 Old_age Offline - 1463
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 0
202 TA_Increase_Count 0x000a 253 034 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 0
204 Shock_Count_Write_Opern 0x000a 253 241 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 194 191 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 286 inconsistent with error log pointer 5

ATA Error Count: 286 (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 286 occurred at disk power-on lifetime: 9539 hours (397 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 67 9f 8a e0 Error: UNC 7 sectors at LBA = 0x008a9f67 = 9084775

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 08 67 9f 8a e0 00 2d+07:13:55.296 READ DMA EXT
25 00 08 3f 00 60 e0 00 2d+07:13:55.296 READ DMA EXT
25 00 08 3f 00 00 e0 00 2d+07:13:55.280 READ DMA EXT
25 00 01 00 00 00 e0 00 2d+07:13:55.280 READ DMA EXT
25 00 04 7f 00 00 e0 00 2d+07:13:55.280 READ DMA EXT

Error 285 occurred at disk power-on lifetime: 9539 hours (397 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 67 9f 8a e0 Error: UNC 7 sectors at LBA = 0x008a9f67 = 9084775

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 08 67 9f 8a e0 00 2d+07:13:54.256 READ DMA EXT
25 00 08 3f 00 60 e0 00 2d+07:13:54.256 READ DMA EXT
25 00 08 3f 00 00 e0 00 2d+07:13:54.240 READ DMA EXT
25 00 04 7f 00 00 e0 00 2d+07:13:54.240 READ DMA EXT
25 00 01 00 00 00 e0 00 2d+07:13:54.240 READ DMA EXT

Error 284 occurred at disk power-on lifetime: 9539 hours (397 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 67 9f 8a e0 Error: UNC 7 sectors at LBA = 0x008a9f67 = 9084775

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 08 67 9f 8a e0 00 2d+07:13:53.200 READ DMA EXT
25 00 08 3f 00 60 e0 00 2d+07:13:53.200 READ DMA EXT
25 00 08 3f 00 00 e0 00 2d+07:13:53.184 READ DMA EXT
25 00 01 00 00 00 e0 00 2d+07:13:53.184 READ DMA EXT
25 00 04 7f 00 00 e0 00 2d+07:13:53.184 READ DMA EXT

Error 283 occurred at disk power-on lifetime: 9539 hours (397 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 67 9f 8a e0 Error: UNC 7 sectors at LBA = 0x008a9f67 = 9084775

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 08 67 9f 8a e0 00 2d+07:13:52.144 READ DMA EXT
25 00 08 3f 00 60 e0 00 2d+07:13:52.144 READ DMA EXT
25 00 08 3f 00 00 e0 00 2d+07:13:52.128 READ DMA EXT
25 00 04 7f 00 00 e0 00 2d+07:13:52.128 READ DMA EXT
25 00 01 00 00 00 e0 00 2d+07:13:52.128 READ DMA EXT

Error 282 occurred at disk power-on lifetime: 9539 hours (397 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 67 9f 8a e0 Error: UNC 7 sectors at LBA = 0x008a9f67 = 9084775

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 08 67 9f 8a e0 00 2d+07:13:51.104 READ DMA EXT
25 00 08 3f 00 60 e0 00 2d+07:13:51.104 READ DMA EXT
25 00 08 3f 00 00 e0 00 2d+07:13:51.088 READ DMA EXT
25 00 01 00 00 00 e0 00 2d+07:13:51.088 READ DMA EXT
25 00 04 7f 00 00 e0 00 2d+07:13:51.088 READ DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


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 span
s, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Encore merci de votre aide
hum...
je ne suis pas un specialiste mais ttu as des erreurs de lecture par DMA...

Verifie tes nappes IDE pour voir si elles sont bien enfichees...

++
Il semble que tu as une erreur sur le secteur at LBA = 0x008a9f67 = 9084775

Si je me rappelle bien il existe un utilitaire pour marquer les blocs défectueux et empêcher leur utilisation.

badblock, peut-être ? essaie un

#locate badblock
Salut,

encore merci de votre soutient. Je tente les manips et vous tiens au jus
11 jours plus tard
Que signifient les logs suivants dans mon mail logwatch:
Received disconnect:
    11: Bye Bye
       139.223.200.45 : 680 Time(s)
A+ 🙂