Bien vu !!!
faut vraiment que j’arrête les intra-veineuses de moutarde !!! c’est trop fort pour moi !
bon je refait le checksum avec le BON volume 
premier essai:
[root@sysrescue ~]# md5sum /dev/mapper/Serveur–VG-Imgs > /mnt/imgsmd5_2.checksum
md5sum: /dev/mapper/Serveur–VG-Imgs: Input/output error
[root@sysrescue ~]#
pas concluant !!
Après combien de temps ?
Il y a quelque chose dans les logs du noyau ?
au bout de 35 mn environ.
pour les logs, quelle commande ? dmesg ?
avec quels paramètres s’il en faut ? 
Oui. Uniquement ceux qui se produisent après le début de la commande.
je comprends pas quelle partie tu veux ?
La partie ajoutée à partir du moment où la commande est lancée. Tu repères le dernier message avant de lancer la commande, et tu prends tout ce qui est après quand la commande se termine. Ou sinon avec la date et l’heure dans /var/log/kern/log.
y en a beaucoup quand même !!
je te mets tout ce qu’il y a ?
Si c’est répétitif, tu mets juste un échantillon.
[root@sysrescue ~]# dmesg
[ 7236.402173] ata4.01: status: { DRDY ERR }
[ 7236.402176] ata4.01: error: { ICRC ABRT }
[ 7236.402186] ata4: soft resetting link
[ 7236.711960] ata4.00: configured for UDMA/133
[ 7236.771942] ata4.01: configured for UDMA/33
[ 7236.771972] ata4: EH complete
[ 7251.902179] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 7251.902183] ata4.01: BMDMA stat 0x66
[ 7251.902187] ata4.01: failed command: READ DMA EXT
[ 7251.902196] ata4.01: cmd 25/00:00:3f:e4:35/00:04:6a:00:00/f0 tag 0 dma 524288 in
res 51/84:bf:3f:e4:35/84:00:00:00:00/f0 Emask 0x30 (host bus error)
[ 7251.902199] ata4.01: status: { DRDY ERR }
[ 7251.902201] ata4.01: error: { ICRC ABRT }
[ 7251.902211] ata4: soft resetting link
[ 7252.191914] ata4.00: configured for UDMA/133
[ 7252.251931] ata4.01: configured for UDMA/33
[ 7252.251959] ata4: EH complete
[ 7279.002194] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 7279.002197] ata4.01: BMDMA stat 0x66
[ 7279.002202] ata4.01: failed command: READ DMA EXT
[ 7279.002211] ata4.01: cmd 25/00:f0:4f:9c:47/00:03:6a:00:00/f0 tag 0 dma 516096 in
res 51/84:af:4f:9c:47/84:00:00:00:00/f0 Emask 0x30 (host bus error)
[ 7279.002214] ata4.01: status: { DRDY ERR }
[ 7279.002217] ata4.01: error: { ICRC ABRT }
[ 7279.002227] ata4: soft resetting link
[ 7279.311934] ata4.00: configured for UDMA/133
[ 7279.371878] ata4.01: configured for UDMA/33
[ 7279.371906] ata4: EH complete
[ 7281.342169] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 7281.342173] ata4.01: BMDMA stat 0x66
[ 7281.342178] ata4.01: failed command: READ DMA EXT
[ 7281.342187] ata4.01: cmd 25/00:00:3f:1c:49/00:04:6a:00:00/f0 tag 0 dma 524288 in
res 51/84:df:3f:1c:49/84:00:00:00:00/f0 Emask 0x30 (host bus error)
[ 7281.342190] ata4.01: status: { DRDY ERR }
[ 7281.342192] ata4.01: error: { ICRC ABRT }
[ 7281.342203] ata4: soft resetting link
[ 7281.651904] ata4.00: configured for UDMA/133
[ 7281.711869] ata4.01: configured for UDMA/33
[ 7281.711896] ata4: EH complete
[ 7297.814372] Buffer I/O error on dev dm-9, logical block 41200139, async page read
[ 7297.814423] Buffer I/O error on dev dm-9, logical block 41200139, async page read
[ 7297.814461] Buffer I/O error on dev dm-9, logical block 41200139, async page read
[ 7797.675149] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=243 TOS=0x00 PREC=0x00 TTL=64 ID=59742 DF PROTO=UDP SPT=138 DPT=138 LEN=223
[ 7797.675343] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=236 TOS=0x00 PREC=0x00 TTL=64 ID=59743 DF PROTO=UDP SPT=138 DPT=138 LEN=216
[ 8518.397379] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=243 TOS=0x00 PREC=0x00 TTL=64 ID=53586 DF PROTO=UDP SPT=138 DPT=138 LEN=223
[ 8518.397553] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=236 TOS=0x00 PREC=0x00 TTL=64 ID=53587 DF PROTO=UDP SPT=138 DPT=138 LEN=216
[ 9239.077275] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=243 TOS=0x00 PREC=0x00 TTL=64 ID=19291 DF PROTO=UDP SPT=138 DPT=138 LEN=223
[ 9239.077450] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=236 TOS=0x00 PREC=0x00 TTL=64 ID=19292 DF PROTO=UDP SPT=138 DPT=138 LEN=216
[ 9959.804624] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=243 TOS=0x00 PREC=0x00 TTL=64 ID=19385 DF PROTO=UDP SPT=138 DPT=138 LEN=223
[ 9959.805077] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=236 TOS=0x00 PREC=0x00 TTL=64 ID=19386 DF PROTO=UDP SPT=138 DPT=138 LEN=216
[10680.487852] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=243 TOS=0x00 PREC=0x00 TTL=64 ID=37180 DF PROTO=UDP SPT=138 DPT=138 LEN=223
[10680.488029] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=236 TOS=0x00 PREC=0x00 TTL=64 ID=37181 DF PROTO=UDP SPT=138 DPT=138 LEN=216
[11401.215241] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=243 TOS=0x00 PREC=0x00 TTL=64 ID=43529 DF PROTO=UDP SPT=138 DPT=138 LEN=223
[11401.215539] iptables-dropped: IN=enp1s0 OUT= MAC=ff:ff:ff:ff:ff:ff:f4:ca:e5:48:39:87:08:00 SRC=192.168.0.254 DST=192.168.0.255 LEN=236 TOS=0x00 PREC=0x00 TTL=64 ID=43530 DF PROTO=UDP SPT=138 DPT=138 LEN=216
[11942.211975] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[11942.211979] ata4.01: BMDMA stat 0x66
[11942.211983] ata4.01: failed command: READ DMA EXT
[11942.211992] ata4.01: cmd 25/00:00:47:a8:d2/00:04:63:00:00/f0 tag 0 dma 524288 in
res 51/84:9f:47:a8:d2/84:00:00:00:00/f0 Emask 0x30 (host bus error)
[11942.211995] ata4.01: status: { DRDY ERR }
[11942.211997] ata4.01: error: { ICRC ABRT }
[11942.212007] ata4: soft resetting link
[11942.521750] ata4.00: configured for UDMA/133
[11942.581676] ata4.01: configured for UDMA/33
[11942.581704] ata4: EH complete
après ça se répète
On peut ignorer les messages d’iptables qui n’ont aucun rapport (paquets NetBios bloqués).
Il y a des erreurs de bus sur un disque (ata4.01) mais on dirait qu’il y a deux disques sur le lien. C’est du PATA/IDE ou SATA ? Est-ce que le disque défaillant est encore présent ?
le disque système est un disque IDE (sda), mais j’ai booté sur une clé USB.
les disques utilisés pour le RAID sont de SATA (4 disques).
et oui le disque défaillant est connecté (sdb)
Du coup je ne sais pas trop comment interpréter les logs. Sur quoi les disques en RAID sont-ils branchés ? Sur des ports SATA de la carte mère, une carte contrôleur SATA additionnelle, un multiplicateur de ports ?
Il faudrait identifier la correspondance entre les disques et les notations « ataX.Y ». Si le tampon de dmesg a encore les messages du démarrage, tu peux utiliser
dmesg | grep ata[0-9]
pour retrouver l’identification des types de ports et des disques.
Sinon il faut chercher dans les fichiers de logs enregistrés (/var/log/kern.log pour Debian, à voir pour ton système live).
les disques sont branchés sur les ports de la carte mère. Je n’ai aucune carte fille dans ce PC
la commande
dmesg | grep ata[0-9]
me donne beaucoup de données en sortie ! tu veux tout ?
voilà le début:
[root@sysrescue ~]# dmesg | grep ata[0-9]
[12708.481972] ata4.01: status: { DRDY ERR }
[12708.481975] ata4.01: error: { ICRC ABRT }
[12708.481985] ata4: soft resetting link
[12708.771758] ata4.00: configured for UDMA/133
[12708.831703] ata4.01: configured for UDMA/33
[12708.831732] ata4: EH complete
[12710.311985] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[12710.311988] ata4.01: BMDMA stat 0x66
[12710.311992] ata4.01: failed command: READ DMA EXT
[12710.311999] ata4.01: cmd 25/00:00:3f:f0:f3/00:01:65:00:00/f0 tag 0 dma 131072 in
[12710.312001] ata4.01: status: { DRDY ERR }
[12710.312003] ata4.01: error: { ICRC ABRT }
[12710.312013] ata4: soft resetting link
[12710.601765] ata4.00: configured for UDMA/133
[12710.661683] ata4.01: configured for UDMA/33
[12710.661710] ata4: EH complete
[12715.831991] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[12715.831995] ata4.01: BMDMA stat 0x66
[12715.831999] ata4.01: failed command: READ DMA EXT
[12715.832008] ata4.01: cmd 25/00:00:3f:38:fa/00:04:65:00:00/f0 tag 0 dma 524288 in
après ça se répète et à la fin il ya ceci:
[17729.281315] ata3.00: device reported invalid CHS sector 0
[17731.044334] ata3.00: device reported invalid CHS sector 0
[17731.113329] ata3.00: device reported invalid CHS sector 0
[17731.171769] ata3.00: device reported invalid CHS sector 0
[17736.322581] ata1: link is slow to respond, please be patient (ready=0)
[17736.332572] ata4: link is slow to respond, please be patient (ready=0)
[17736.332581] ata3: link is slow to respond, please be patient (ready=0)
[17738.753718] ata1.01: ACPI cmd ef/03:22:00:00:00:b0 (SET FEATURES) filtered out
[17738.753723] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[17738.753725] ata1.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[17738.782969] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[17738.782974] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[17738.783124] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[17738.783127] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[17740.352748] ata4.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES) filtered out
[17740.352751] ata4.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[17740.415631] ata4.01: ACPI cmd c6/00:10:00:00:00:b0 (SET MULTIPLE MODE) succeeded
[17740.415636] ata4.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[17740.472540] ata4.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[17740.472559] ata4.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[17740.472911] ata4.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[17740.472916] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[17741.362651] ata3: device not ready (errno=-16), forcing hardreset
[17746.552621] ata3: link is slow to respond, please be patient (ready=0)
[17749.035002] ata3.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES) filtered out
[17749.035008] ata3.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[17749.035279] ata3.01: ACPI cmd c6/00:10:00:00:00:b0 (SET MULTIPLE MODE) succeeded
[17749.035285] ata3.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[17754.042577] ata3.00: qc timeout (cmd 0xec)
[17754.042584] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[17754.042587] ata3.00: revalidation failed (errno=-5)
[17759.102562] ata3: link is slow to respond, please be patient (ready=0)
[17759.777468] ata3.00: ACPI cmd ef/03:01:00:00:00:a0 (SET FEATURES) filtered out
[17759.777645] ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) rejected by device (Stat=0x51 Err=0x04)
[17759.777650] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Non, seulement les lignes d’initialisation du style
[ 1.571512] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x34e0 irq 14
[ 1.571514] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x34e8 irq 15
[ 1.729608] ata3: SATA max UDMA/133 cmd 0x3818 ctl 0x3830 bmdma 0x34f0 irq 19
[ 1.729611] ata4: SATA max UDMA/133 cmd 0x3820 ctl 0x3834 bmdma 0x34f8 irq 19
[ 1.760330] ata1.00: ATAPI: LITE-ON COMBO SOHC-4832K, OQKB, max UDMA/44
[ 1.784209] ata1.00: configured for UDMA/44
[ 1.907153] ata3.00: ATA-7: Maxtor 6E040T0, NAN51680, max UDMA/100
[ 1.907161] ata3.00: 78165360 sectors, multi 16: LBA48
[ 1.911709] ata3.00: configured for UDMA/100j’ai complété ma réponse précedente
Le tampon dmesg a déjà perdu les messages de démarrage, il faut soit chercher dans les fichiers de log, soit redémarrer le système.
donc je redémarre et je lance la commande dmesg tout de suit ? c’est bien ça ?
Oui, si tu ne trouves pas les fichiers logs du noyau.
bon j’ai réussi à trouver des trucs sans rebooter :
Dec 29 13:58:00 sysrescue kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
Dec 29 13:58:00 sysrescue kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
Dec 29 13:58:00 sysrescue kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
Dec 29 13:58:00 sysrescue kernel: scsi host2: ata_piix
Dec 29 13:58:00 sysrescue kernel: scsi host3: ata_piix
Dec 29 13:58:00 sysrescue kernel: ata3: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xc800 irq 23
Dec 29 13:58:00 sysrescue kernel: ata4: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc808 irq 23
Dec 29 13:58:00 sysrescue kernel: pci 0000:00:00.0: Intel G33 Chipset
Dec 29 13:58:00 sysrescue kernel: pci 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Dec 29 13:58:00 sysrescue kernel: pci 0000:00:00.0: detected 8192K stolen memory
Dec 29 13:58:00 sysrescue kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Dec 29 13:58:00 sysrescue kernel: Console: switching to colour dummy device 80x25
Dec 29 13:58:00 sysrescue kernel: ACPI: \_SB_.PCI0.SBRG.ASOC: Device cannot be configured due to a frequency mismatch
Dec 29 13:58:00 sysrescue kernel: ACPI: \_SB_.PCI0.SBRG.ASOC: Device cannot be configured due to a frequency mismatch
Dec 29 13:58:00 sysrescue kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Dec 29 13:58:00 sysrescue kernel: [drm] Driver supports precise vblank timestamp query.
Dec 29 13:58:00 sysrescue kernel: ACPI: \_SB_.PCI0.SBRG.ASOC: Device cannot be configured due to a frequency mismatch
Dec 29 13:58:00 sysrescue kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Dec 29 13:58:00 sysrescue kernel: [drm] RC6 disabled, disabling runtime PM support
Dec 29 13:58:00 sysrescue kernel: [drm] Initialized overlay support.
Dec 29 13:58:00 sysrescue kernel: [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0
Dec 29 13:58:00 sysrescue kernel: fbcon: i915drmfb (fb0) is primary device
Dec 29 13:58:00 sysrescue kernel: ata3.00: failed to read native max address (err_mask=0x1)
Dec 29 13:58:00 sysrescue kernel: ata3.00: HPA support seems broken, skipping HPA handling
Dec 29 13:58:00 sysrescue kernel: ata3.00: ATA-6: ST_M13FQBL, 1117F38E, max UDMA/133
Dec 29 13:58:00 sysrescue kernel: ata3.00: 8089950 sectors, multi 16: LBA48 NCQ (depth 0/32)
Dec 29 13:58:00 sysrescue kernel: ata3.01: ATA-8: ST31000524AS, JC45, max UDMA/133
Dec 29 13:58:00 sysrescue kernel: ata3.01: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Dec 29 13:58:00 sysrescue kernel: ata4.00: ATA-8: ST31000333AS, CC1H, max UDMA/133
Dec 29 13:58:00 sysrescue kernel: ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Dec 29 13:58:00 sysrescue kernel: Console: switching to colour frame buffer device 160x64
Dec 29 13:58:00 sysrescue kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Dec 29 13:58:00 sysrescue kernel: ata4.01: ATA-8: ST31000333AS, CC1F, max UDMA/133
Dec 29 13:58:00 sysrescue kernel: ata4.01: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Dec 29 13:58:00 sysrescue kernel: ata1.00: ATA-6: ST3120022A, 3.04, max UDMA/100
Dec 29 13:58:00 sysrescue kernel: ata1.00: 234441648 sectors, multi 16: LBA48
Dec 29 13:58:00 sysrescue kernel: ata1.01: ATAPI: HL-DT-ST GCE-8160B, 2.01, max MWDMA2
ça te va ça ?
c’est suffisant ?