Perte aléatoire de 2/5 de mes DD sur SID !

Support Debian
#1

Bonjour,
Je perd aléatoirement 2 de mes 5 disques aux démarrage de mon pc, les DD concernnés sont mes partitions sdc1 et sdd1 en ext3, un démarrage et sdc est bien monté mais pas sdd,un autre c’est le contraire et enfin un ne mem monte pas les deux !!! et pourtant dans tout les cas, un simple redémarrage me permet de retrouver l’ensemble de mes disques .
:119 .

*-Une infos qui peut être utile, sda,sdb,sdc,sdd sont des DD en SATA et sde est en IDE
*-Dans fstab, /virtual_HDD corespond à sde1 (port IDE)

Les logs de boot ne me fournissent pas d’info sur le montage, dans les messages de log, seul indication et les mêmes infos pour les trois problèmes en changeanbt évidement les lecteurs :

debian kernel: [  474.249011] sd 3:0:0:0: [sdd] Unhandled error code

Dec 28 20:54:12 debian kernel: [37972.000014] ata8: lost interrupt (Status 0x50) Dec 28 20:54:12 debian kernel: [37972.000056] ata8: hard resetting link Dec 28 20:54:13 debian kernel: [37972.880046] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 28 20:54:13 debian kernel: [37972.905137] ata8.00: configured for UDMA/133 Dec 28 20:54:13 debian kernel: [37972.905141] ata8.00: device reported invalid CHS sector 0 Dec 28 20:54:13 debian kernel: [37972.905147] ata8: EH complete Dec 28 21:18:43 debian kernel: [39442.988516] ata8: lost interrupt (Status 0x50) Dec 28 21:18:43 debian kernel: [39442.988560] ata8: hard resetting link Dec 28 21:18:44 debian kernel: [39443.868039] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 28 21:18:44 debian kernel: [39443.893153] ata8.00: configured for UDMA/133 Dec 28 21:18:44 debian kernel: [39443.893157] ata8.00: device reported invalid CHS sector 0 Dec 28 21:18:44 debian kernel: [39443.893163] ata8: EH complete Dec 28 21:20:45 debian kernel: [39564.988018] ata8: lost interrupt (Status 0x50) Dec 28 21:20:45 debian kernel: [39564.988062] ata8: hard resetting link Dec 28 21:20:46 debian kernel: [39565.868539] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 28 21:20:46 debian kernel: [39565.893131] ata8.00: configured for UDMA/133 Dec 28 21:20:46 debian kernel: [39565.893135] ata8.00: device reported invalid CHS sector 0 Dec 28 21:20:46 debian kernel: [39565.893141] ata8: EH complete Dec 28 21:21:16 debian kernel: [39595.988514] ata8: lost interrupt (Status 0x50) Dec 28 21:21:16 debian kernel: [39595.988558] ata8: hard resetting link Dec 28 21:21:17 debian kernel: [39596.868045] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 28 21:21:17 debian kernel: [39596.893153] ata8.00: configured for UDMA/133 Dec 28 21:21:17 debian kernel: [39596.893158] ata8.00: device reported invalid CHS sector 0 Dec 28 21:21:17 debian kernel: [39596.893167] ata8: EH complete Dec 28 21:25:37 debian kernel: [39856.988017] ata8: lost interrupt (Status 0x50) Dec 28 21:25:37 debian kernel: [39856.988035] ata8: limiting SATA link speed to 1.5 Gbps Dec 28 21:25:37 debian kernel: [39856.988064] ata8: hard resetting link Dec 28 21:25:38 debian kernel: [39857.868042] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:25:38 debian kernel: [39857.893159] ata8.00: configured for UDMA/133 Dec 28 21:25:38 debian kernel: [39857.893163] ata8.00: device reported invalid CHS sector 0 Dec 28 21:25:38 debian kernel: [39857.893170] ata8: EH complete Dec 28 21:28:35 debian kernel: [40034.988022] ata8: lost interrupt (Status 0x50) Dec 28 21:28:35 debian kernel: [40034.988065] ata8: hard resetting link Dec 28 21:28:36 debian kernel: [40035.868042] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:28:36 debian kernel: [40035.895971] ata8.00: configured for UDMA/133 Dec 28 21:28:36 debian kernel: [40035.895976] ata8.00: device reported invalid CHS sector 0 Dec 28 21:28:36 debian kernel: [40035.895985] ata8: EH complete Dec 28 21:32:51 debian kernel: [40290.988013] ata8: lost interrupt (Status 0x50) Dec 28 21:32:51 debian kernel: [40290.988057] ata8: hard resetting link Dec 28 21:32:52 debian kernel: [40291.868045] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:32:52 debian kernel: [40291.893145] ata8.00: configured for UDMA/133 Dec 28 21:32:52 debian kernel: [40291.893149] ata8.00: device reported invalid CHS sector 0 Dec 28 21:32:52 debian kernel: [40291.893154] ata8: EH complete Dec 28 21:33:22 debian kernel: [40321.988014] ata8: lost interrupt (Status 0x50) Dec 28 21:33:22 debian kernel: [40321.988057] ata8: hard resetting link Dec 28 21:33:23 debian kernel: [40322.868042] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:33:23 debian kernel: [40322.893140] ata8.00: configured for UDMA/133 Dec 28 21:33:23 debian kernel: [40322.893144] ata8.00: device reported invalid CHS sector 0 Dec 28 21:33:23 debian kernel: [40322.893153] ata8: EH complete Dec 28 21:33:53 debian kernel: [40353.000017] ata8: lost interrupt (Status 0x50) Dec 28 21:33:53 debian kernel: [40353.000035] ata8.00: limiting speed to UDMA/100:PIO4 Dec 28 21:33:53 debian kernel: [40353.000065] ata8: hard resetting link Dec 28 21:33:54 debian kernel: [40353.880539] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:33:54 debian kernel: [40353.905134] ata8.00: configured for UDMA/100 Dec 28 21:33:54 debian kernel: [40353.905137] ata8.00: device reported invalid CHS sector 0 Dec 28 21:33:54 debian kernel: [40353.905147] ata8: EH complete Dec 28 21:34:24 debian kernel: [40383.988514] ata8: lost interrupt (Status 0x50) Dec 28 21:34:24 debian kernel: [40383.988557] ata8: hard resetting link Dec 28 21:34:25 debian kernel: [40384.868044] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:34:25 debian kernel: [40384.893137] ata8.00: configured for UDMA/100 Dec 28 21:34:25 debian kernel: [40384.893141] ata8.00: device reported invalid CHS sector 0 Dec 28 21:34:25 debian kernel: [40384.893150] ata8: EH complete Dec 28 21:36:06 debian kernel: [40485.988018] ata8: lost interrupt (Status 0x50) Dec 28 21:36:06 debian kernel: [40485.988061] ata8: hard resetting link Dec 28 21:36:07 debian kernel: [40486.868541] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:36:07 debian kernel: [40486.893155] ata8.00: configured for UDMA/100 Dec 28 21:36:07 debian kernel: [40486.893159] ata8.00: device reported invalid CHS sector 0 Dec 28 21:36:07 debian kernel: [40486.893165] ata8: EH complete Dec 28 21:36:37 debian kernel: [40517.000059] ata8: hard resetting link Dec 28 21:36:40 debian kernel: [40519.292013] ata8: reset failed (errno=-32), retrying in 8 secs Dec 28 21:36:47 debian kernel: [40527.000016] ata8: hard resetting link Dec 28 21:36:50 debian kernel: [40529.324011] ata8: reset failed (errno=-32), retrying in 8 secs Dec 28 21:36:57 debian kernel: [40537.000017] ata8: hard resetting link Dec 28 21:36:59 debian kernel: [40539.228016] ata8: reset failed (errno=-32), retrying in 33 secs Dec 28 21:37:32 debian kernel: [40572.000022] ata8: hard resetting link Dec 28 21:37:33 debian kernel: [40572.880045] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:37:33 debian kernel: [40572.905139] ata8.00: configured for UDMA/100 Dec 28 21:37:33 debian kernel: [40572.905143] ata8.00: device reported invalid CHS sector 0 Dec 28 21:37:33 debian kernel: [40572.905153] ata8: EH complete Dec 28 21:38:26 debian kernel: [40625.988015] ata8: lost interrupt (Status 0x50) Dec 28 21:38:26 debian kernel: [40625.988033] ata8.00: limiting speed to UDMA/33:PIO4 Dec 28 21:38:26 debian kernel: [40625.988063] ata8: hard resetting link Dec 28 21:38:27 debian kernel: [40626.868043] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 28 21:38:27 debian kernel: [40626.893136] ata8.00: configured for UDMA/33 Dec 28 21:38:27 debian kernel: [40626.893140] ata8.00: device reported invalid CHS sector 0 Dec 28 21:38:27 debian kernel: [40626.893147] ata8: EH complete Dec 28 21:38:57 debian kernel: [40656.988055] ata8: hard resetting link Dec 28 21:39:00 debian kernel: [40659.280511] ata8: reset failed (errno=-32), retrying in 8 secs Dec 28 21:39:07 debian kernel: [40666.988015] ata8: hard resetting link Dec 28 21:39:10 debian kernel: [40669.252011] ata8: reset failed (errno=-32), retrying in 8 secs Dec 28 21:39:17 debian kernel: [40676.988027] ata8: hard resetting link Dec 28 21:39:19 debian kernel: [40679.216015] ata8: reset failed (errno=-32), retrying in 33 secs Dec 28 21:39:52 debian kernel: [40711.988013] ata8: hard resetting link Dec 28 21:39:54 debian kernel: [40714.216014] ata8.00: disabled Dec 28 21:39:54 debian kernel: [40714.216018] ata8.00: device reported invalid CHS sector 0 Dec 28 21:39:54 debian kernel: [40714.216025] ata8: EH complete

root@debian:/home/chris# blkid

/dev/sda1: UUID="84c14eba-554d-4c28-aab5-257a957d01f5" TYPE="ext4" /dev/sda2: UUID="66cabd12-b3bc-4115-b800-b7247a97bbb2" TYPE="swap" /dev/sda3: UUID="e1a437ed-7773-4503-8cba-a0e7dacb15ed" TYPE="ext4" /dev/sdb1: UUID="c29dd20c-cf2c-464c-9dc9-0a0091dacb95" TYPE="ext4" /dev/sdc1: UUID="af024edc-ab3c-442b-848f-b37cab40e4aa" TYPE="ext3" /dev/sdd1: UUID="e01f6de5-b09a-42bf-812a-9a5d6562c5c8" TYPE="ext3" /dev/sde1: UUID="a9ed45c1-3483-4243-81d9-674bee4e791c" TYPE="ext4"

cat /etc/fstab

[code]#
proc /proc proc defaults 0 0

/ was on /dev/sda3 during installation

UUID=e1a437ed-7773-4503-8cba-a0e7dacb15ed / ext4 errors=remount-ro 0 1

/boot was on /dev/sda1 during installation

UUID=84c14eba-554d-4c28-aab5-257a957d01f5 /boot ext4 defaults 0 2

/donnees was on /dev/sdc1 during installation

UUID=af024edc-ab3c-442b-848f-b37cab40e4aa /donnees ext3 defaults 0 2

/home was on /dev/sdb1 during installation

UUID=c29dd20c-cf2c-464c-9dc9-0a0091dacb95 /home ext4 defaults 0 2

/photos was on /dev/sdd1 during installation

UUID=e01f6de5-b09a-42bf-812a-9a5d6562c5c8 /photos ext3 defaults 0 2

swap was on /dev/sda2 during installation

UUID=66cabd12-b3bc-4115-b800-b7247a97bbb2 none swap sw 0 0

HDD EXTERNE

UUID=a9ed45c1-3483-4243-81d9-674bee4e791c /virtual_HDD ext4 defaults 0 2[/code]

Merci

#2

Message d’erreur que je connais: pbm de driver SATA/IDE. Un changement de noyau avait réglé le pbm chez moi.

#3

Pour l’instant je n’ai que le 2.6.32 de dispo …

linux-headers-2.6.37-rc5-486 - Header files for Linux 2.6.37-rc5-486 linux-headers-2.6.37-rc5-686-bigmem - Header files for Linux 2.6.37-rc5-686-bigmem linux-headers-2.6.37-rc5-686 - Header files for Linux 2.6.37-rc5-686 linux-headers-2.6.37-rc5-all-i386 - All header files for Linux 2.6.37 (meta-package) linux-headers-2.6.37-rc5-all - All header files for Linux 2.6.37 (meta-package) linux-headers-2.6.37-rc5-amd64 - Header files for Linux 2.6.37-rc5-amd64 linux-headers-2.6.37-rc5-common - Common header files for Linux 2.6.37-rc5 linux-headers-2.6.37-rc7-486 - Header files for Linux 2.6.37-rc7-486 linux-headers-2.6.37-rc7-686-bigmem - Header files for Linux 2.6.37-rc7-686-bigmem linux-headers-2.6.37-rc7-686 - Header files for Linux 2.6.37-rc7-686 linux-headers-2.6.37-rc7-all-i386 - All header files for Linux 2.6.37 (meta-package) linux-headers-2.6.37-rc7-all - All header files for Linux 2.6.37 (meta-package) linux-headers-2.6.37-rc7-amd64 - Header files for Linux 2.6.37-rc7-amd64 linux-headers-2.6.37-rc7-common - Common header files for Linux 2.6.37-rc7

#4

Bonjour,

A tout hasard en attendant le prochain noyau ?

C’est par le BIOS que se fait la détection des disques durs, et donc le choix du support de démarrage.
On dit qu’avec un disque SATA, la reconnaissance du chipset peut poser problème.

En principe le BIOS permet de passer le contrôleur SATA en mode d’émulation IDE, ce qui permet à Linux de reconnaitre le SATA comme un IDE.
Linux gère parait-il les chipsets SATA compatibles AHCI, standard publique.

Il faut donc aller dans le BIOS et choisir ce nom s’il est proposé, apparaissant parfois semble-t-il en native.

Si çà n’arrange rien il faut tenter le mode combined puis legacy IDE

Pour ce qui concerne le noyau, il est possible qu’un module spécifique permette la correction de ton affaire, mais je ne suis pas assez expert.