# Probleme HDD - sata link reset

**URL:** <https://www.debian-fr.org/t/probleme-hdd-sata-link-reset/87934>\
**Category:** Support Debian\
**Tags:** raid\
**Created:** [Mars 1, 2023, 3:42 UTC](https://www.debian-fr.org/t/probleme-hdd-sata-link-reset/87934 "2023-03-01T15:42:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![morejered](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/m/5daacb/32.png) [@morejered](https://www.debian-fr.org/u/morejered)\
**Post date:** [Mars 1, 2023, 3:42 UTC](https://www.debian-fr.org/t/probleme-hdd-sata-link-reset/87934/1 "2023-03-01T15:42:41Z")

</div>

Bonjour,  
j’ai un probleme recurrent sur les HDD de ma grappe RAID.  
régulièrement, j’ai un disque qui s’ejecte de la grappe avec ce genre de messages:

```nohighlight
               ata7.00: exception Emask 0x10 SAct 0xffffc00f SErr 0x380000 action 0x6 frozen
[5768.185729] ata7.00: irq_stat 0x08000000, interface fatal error
[5768.185731] ata7: SError: { 10B8B Dispar BadCRC }
[5768.185734] ata7.00: failed command: READ FPDMA QUEUED
[5768.185735] ata7.00: cmd 60/40:00:b8:a3:f0/05:00:3c:00:00/40 tag 0 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185741] ata7.00: status: { DRDY }
[5768.185743] ata7.00: failed command: READ FPDMA QUEUED
[5768.185744] ata7.00: cmd 60/40:08:f8:a8:f0/05:00:3c:00:00/40 tag 1 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185749] ata7.00: status: { DRDY }
[5768.185750] ata7.00: failed command: READ FPDMA QUEUED
[5768.185751] ata7.00: cmd 60/40:10:38:ae:f0/05:00:3c:00:00/40 tag 2 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185755] ata7.00: status: { DRDY }
[5768.185757] ata7.00: failed command: READ FPDMA QUEUED
[5768.185758] ata7.00: cmd 60/40:18:78:b3:f0/05:00:3c:00:00/40 tag 3 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185762] ata7.00: status: { DRDY }
[5768.185763] ata7.00: failed command: READ FPDMA QUEUED
[5768.185764] ata7.00: cmd 60/40:70:f8:69:f0/05:00:3c:00:00/40 tag 14 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185769] ata7.00: status: { DRDY }
[5768.185770] ata7.00: failed command: READ FPDMA QUEUED
[5768.185771] ata7.00: cmd 60/40:78:38:6f:f0/05:00:3c:00:00/40 tag 15 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185775] ata7.00: status: { DRDY }
[5768.185776] ata7.00: failed command: READ FPDMA QUEUED
[5768.185777] ata7.00: cmd 60/40:80:78:74:f0/05:00:3c:00:00/40 tag 16 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185782] ata7.00: status: { DRDY }
[5768.185783] ata7.00: failed command: READ FPDMA QUEUED
[5768.185784] ata7.00: cmd 60/40:88:b8:79:f0/05:00:3c:00:00/40 tag 17 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185788] ata7.00: status: { DRDY }
[5768.185789] ata7.00: failed command: READ FPDMA QUEUED
[5768.185790] ata7.00: cmd 60/40:90:f8:7e:f0/05:00:3c:00:00/40 tag 18 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185794] ata7.00: status: { DRDY }
[5768.185796] ata7.00: failed command: READ FPDMA QUEUED
[5768.185797] ata7.00: cmd 60/40:98:38:84:f0/05:00:3c:00:00/40 tag 19 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185801] ata7.00: status: { DRDY }
[5768.185802] ata7.00: failed command: READ FPDMA QUEUED
[5768.185803] ata7.00: cmd 60/40:a0:78:89:f0/05:00:3c:00:00/40 tag 20 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185807] ata7.00: status: { DRDY }
[5768.185809] ata7.00: failed command: READ FPDMA QUEUED
[5768.185810] ata7.00: cmd 60/40:a8:b8:8e:f0/05:00:3c:00:00/40 tag 21 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185814] ata7.00: status: { DRDY }
[5768.185815] ata7.00: failed command: READ FPDMA QUEUED
[5768.185816] ata7.00: cmd 60/40:b0:f8:93:f0/05:00:3c:00:00/40 tag 22 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185820] ata7.00: status: { DRDY }
[5768.185821] ata7.00: failed command: READ FPDMA QUEUED
[5768.185822] ata7.00: cmd 60/40:b8:38:99:f0/05:00:3c:00:00/40 tag 23 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185826] ata7.00: status: { DRDY }
[5768.185828] ata7.00: failed command: READ FPDMA QUEUED
[5768.185829] ata7.00: cmd 60/40:c0:b8:b8:f0/05:00:3c:00:00/40 tag 24 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185833] ata7.00: status: { DRDY }
[5768.185834] ata7.00: failed command: READ FPDMA QUEUED
[5768.185835] ata7.00: cmd 60/40:c8:f8:bd:f0/05:00:3c:00:00/40 tag 25 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185839] ata7.00: status: { DRDY }
[5768.185841] ata7.00: failed command: READ FPDMA QUEUED
[5768.185842] ata7.00: cmd 60/40:d0:38:c3:f0/05:00:3c:00:00/40 tag 26 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185846] ata7.00: status: { DRDY }
[5768.185847] ata7.00: failed command: READ FPDMA QUEUED
[5768.185848] ata7.00: cmd 60/40:d8:78:c8:f0/05:00:3c:00:00/40 tag 27 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185852] ata7.00: status: { DRDY }
[5768.185854] ata7.00: failed command: READ FPDMA QUEUED
[5768.185855] ata7.00: cmd 60/40:e0:b8:cd:f0/05:00:3c:00:00/40 tag 28 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185859] ata7.00: status: { DRDY }
[5768.185860] ata7.00: failed command: READ FPDMA QUEUED
[5768.185861] ata7.00: cmd 60/40:e8:f8:d2:f0/05:00:3c:00:00/40 tag 29 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185865] ata7.00: status: { DRDY }
[5768.185866] ata7.00: failed command: READ FPDMA QUEUED
[5768.185868] ata7.00: cmd 60/80:f0:38:d8:f0/04:00:3c:00:00/40 tag 30 ncq dma 589824 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185872] ata7.00: status: { DRDY }
[5768.185873] ata7.00: failed command: READ FPDMA QUEUED
[5768.185874] ata7.00: cmd 60/40:f8:78:9e:f0/05:00:3c:00:00/40 tag 31 ncq dma 688128 in
                        res 40/00:f0:38:d8:f0/00:00:3c:00:00/40 Emask 0x10 (ATA bus error)
[5768.185878] ata7.00: status: { DRDY }
[5768.185880] ata7: hard resetting link
[5768.657923] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[5768.662330] ata7.00: configured for UDMA/133
[5768.662423] ata7: EH complete

```

j’ai cru d’abord à des problèmes de HDD… je les ai changés  
ensuite de MB… je l’ai changée. en fait j’ai changé tout le PC  
et je me retrouve encore avec ces erreurs  
je ne sais plus quoi faire pour trouver la cause du problème  
avez vous des idées?

---

<div class="post-metadata">

**Author:** ![Clochette](https://www.debian-fr.org/user_avatar/www.debian-fr.org/clochette/32/8757_2.png) [@Clochette](https://www.debian-fr.org/u/Clochette)\
**Post date:** [Mars 1, 2023, 3:59 UTC](https://www.debian-fr.org/t/probleme-hdd-sata-link-reset/87934/2 "2023-03-01T15:59:17Z")

</div>

> [@morejered](#):
>
> en fait j’ai changé tout le PC

Les câbles sata, en particulier celui du disque en question ?

---

<div class="post-metadata">

**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\
**Post date:** [Mars 1, 2023, 7:29 UTC](https://www.debian-fr.org/t/probleme-hdd-sata-link-reset/87934/3 "2023-03-01T19:29:31Z")

</div>

> [@morejered](#):
>
> régulièrement, j’ai un disque qui s’ejecte de la grappe

Un disque en particulier, ou n’importe lequel ?  
Sur un port SATA particulier ou n’importe lequel ?

> [@Clochette](#):
>
> Les câbles sata

Oui, ou l’alimentation.

---

<div class="post-metadata">

**Author:** ![morejered](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/m/5daacb/32.png) [@morejered](https://www.debian-fr.org/u/morejered)\
**Post date:** [Mars 2, 2023, 6:46 UTC](https://www.debian-fr.org/t/probleme-hdd-sata-link-reset/87934/4 "2023-03-02T06:46:06Z")

</div>

j’ai 8 HDD avec des marques variées (WD, Seagate, Toshiba)  
pendant longtemps, seuls les Toshiba s’ejectaient  
j’ai changé quasi tout le PC excepté le boitier .  
j’ai remplacé les HDD toshiba par des Seagate… le pb a fini par revenir  
aujourd’hui c’est 1 WD qui m a laché , puis 1 seagate (pendant la reconstruction du RAID, mais heureusement je suis en RAID6)  
vous avez raison, la cablerie est peut etre en cause… je suis sur des cables SATA noname recupérés au fil des achats de materiels divers… c est peut etre une piste.  
l’alim est neuve (650 NZXT modulaire)

- je viens de commander un lot de cables SATA neufs
- j’ai aussi remplacé une ligne d’alimentation des HDD en rajoutant un cable modulaire de l’Alim  
je croise les doigts pour que ça soit ça.  
merci pour vos suggestions