bonsoir à tous, j'ai eut un reboot houleux a l'instant.
Mon log m'apprend que mon disque dur hdb pose des problèmes. je voulais avoir des spécialistes du raid. Faut il que je m'inquète ou pas ??? Merci pour vos réponses. Christophe. ------------------- 06.04.2006 19:59:20 localhost kernel [ 152.593301] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882809 06.04.2006 19:59:20 localhost kernel [ 152.593807] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882810 06.04.2006 19:59:42 localhost kernel [ 173.876507] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882849 06.04.2006 19:59:42 localhost kernel [ 173.877083] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882850 06.04.2006 19:59:42 localhost kernel [ 173.877431] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882851 06.04.2006 19:59:42 localhost kernel [ 173.877774] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882852 06.04.2006 19:59:42 localhost kernel [ 173.878193] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882853 06.04.2006 19:59:42 localhost kernel [ 173.878525] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882854 06.04.2006 19:59:42 localhost kernel [ 173.878843] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882855 06.04.2006 19:59:42 localhost kernel [ 173.879161] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882856 06.04.2006 19:59:42 localhost kernel [ 173.879479] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882857 06.04.2006 19:59:42 localhost kernel [ 173.879810] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882859 06.04.2006 19:59:42 localhost kernel [ 173.880117] EXT2-fs error (device md0): ext2_free_blocks: bit already cleared for block 25882858 06.04.2006 20:00:02 localhost kernel [ 194.330684] hdb: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error } 06.04.2006 20:00:02 localhost kernel [ 194.330695] hdb: status error: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=260013951, sector=240121535 06.04.2006 20:00:02 localhost kernel [ 194.330708] ide: failed opcode was: unknown 06.04.2006 20:00:02 localhost kernel [ 194.330715] hda: DMA disabled 06.04.2006 20:00:02 localhost kernel [ 194.330719] hdb: DMA disabled 06.04.2006 20:00:02 localhost kernel [ 194.330744] hdb: drive not ready for command 06.04.2006 20:00:02 localhost kernel [ 194.480582] ide0: reset: success 06.04.2006 20:00:12 localhost kernel [ 204.330611] hdb: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error } 06.04.2006 20:00:12 localhost kernel [ 204.330622] hdb: status error: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=260013951, sector=240121535 06.04.2006 20:00:12 localhost kernel [ 204.330635] ide: failed opcode was: unknown 06.04.2006 20:00:12 localhost kernel [ 204.330663] hdb: drive not ready for command 06.04.2006 20:00:38 localhost kernel [ 229.837155] ide0: reset: success 06.04.2006 20:00:39 localhost kernel [ 231.153270] hdb: status error: status=0x30 { DeviceFault SeekComplete } 06.04.2006 20:00:39 localhost kernel [ 231.153279] 06.04.2006 20:00:39 localhost kernel [ 231.153280] ide: failed opcode was: unknown 06.04.2006 20:00:39 localhost kernel [ 231.153308] hdb: no DRQ after issuing MULTWRITE 06.04.2006 20:00:44 localhost kernel [ 236.303083] ide0: reset: success -------------------------