# Problèmes d'accès au disque système lors des bootages à froid

**URL:** <https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945>\
**Category:** Support Debian\
**Tags:** erreur, disk\
**Created:** [Janvier 14, 2026, 6:36 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945 "2026-01-14T18:36:49Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 14, 2026, 6:36 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/1 "2026-01-14T18:36:49Z")

</div>

Bonjour à tous,

J’ai un comportement assez étrange de mon disque système SSD (Corsair Force GT 60GB, acheté en 2011 avec le reste de mon système).

Il marche encore très bien sauf lors des démarrages à froid où le système me renvoie un tas d’erreurs d’entrées/sorties sur le disque :

> libresurf@artic:~$ journalctl -b -1 -g ‹&nbsp;(ata3|sda)&nbsp;›  
> janv. 14 19:03:04 artic kernel: ata3: SATA max UDMA/133 abar m1024@0xfcafe000 port 0xfcafe100 irq 39 lpm-pol 3  
> janv. 14 19:03:04 artic kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)  
> janv. 14 19:03:04 artic kernel: ata3.00: ATA-9: Corsair Force GT, 1.2, max UDMA/133  
> janv. 14 19:03:04 artic kernel: ata3.00: 117231408 sectors, multi 16: LBA48 NCQ (depth 32), AA  
> janv. 14 19:03:04 artic kernel: ata3.00: configured for UDMA/133  
> janv. 14 19:03:04 artic kernel: sd 2:0:0:0: [sda] 117231408 512-byte logical blocks: (60.0 GB/55.9 GiB)  
> janv. 14 19:03:04 artic kernel: sd 2:0:0:0: [sda] Write Protect is off  
> janv. 14 19:03:04 artic kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00  
> janv. 14 19:03:04 artic kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA  
> janv. 14 19:03:04 artic kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 512 bytes  
> janv. 14 19:03:04 artic kernel: sda: sda1 sda2  
> janv. 14 19:03:04 artic kernel: sd 2:0:0:0: [sda] Attached SCSI disk  
> janv. 14 19:03:04 artic kernel: EXT4-fs (sda1): orphan cleanup on readonly fs  
> janv. 14 19:03:04 artic kernel: EXT4-fs (sda1): mounted filesystem 3863bfde-c975-4bc1-bd9f-403d3617e8e8 ro with ordered data mode. Quota mode: none.  
> janv. 14 19:03:04 artic kernel: EXT4-fs (sda1): re-mounted 3863bfde-c975-4bc1-bd9f-403d3617e8e8 r/w.  
> janv. 14 19:03:05 artic kernel: Adding 3926012k swap on /dev/sda2. Priority:-2 extents:1 across:3926012k SS  
> janv. 14 19:03:06 artic smartd[959]: Device: /dev/sda, type changed from ‹&nbsp;scsi&nbsp;› to ‹&nbsp;sat&nbsp;›  
> janv. 14 19:03:06 artic smartd[959]: Device: /dev/sda [SAT], opened  
> janv. 14 19:03:07 artic smartd[959]: Device: /dev/sda [SAT], Corsair Force GT, S/N:1131820100000705005E, WWN:0-000000-000000000, FW:1.2, 60.0 GB  
> janv. 14 19:03:07 artic smartd[959]: Device: /dev/sda [SAT], found in smartd database 7.3/5528: SandForce Driven SSDs  
> janv. 14 19:03:07 artic smartd[959]: Device: /dev/sda [SAT], can’t monitor Current\_Pending\_Sector count - no Attribute 197  
> janv. 14 19:03:07 artic smartd[959]: Device: /dev/sda [SAT], no SMART Self-test Log, ignoring -l selftest (override with -T permissive)  
> janv. 14 19:03:07 artic smartd[959]: Device: /dev/sda [SAT], no SMART Error Log, ignoring -l error (override with -T permissive)  
> janv. 14 19:03:07 artic smartd[959]: Device: /dev/sda [SAT], is SMART capable. Adding to «&nbsp;monitor&nbsp;» list.  
> janv. 14 19:03:08 artic smartd[959]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.Corsair\_Force\_GT-1131820100000705005E.ata.state  
> janv. 14 19:03:41 artic kernel: ata3.00: exception Emask 0x0 SAct 0xfce000 SErr 0xd0000 action 0x6 frozen  
> janv. 14 19:03:41 artic kernel: ata3: SError: { PHYRdyChg CommWake 10B8B }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/00:68:90:4d:b4/01:00:00:00:00/40 tag 13 ncq dma 131072 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/e0:70:20:f8:cd/00:00:02:00:00/40 tag 14 ncq dma 114688 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/c8:78:b0:13:f9/00:00:02:00:00/40 tag 15 ncq dma 102400 in  
> res 40/00:01:e8:7f:d5/00:00:1d:00:00/e0 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/d0:90:00:45:bc/00:00:03:00:00/40 tag 18 ncq dma 106496 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/00:98:00:82:bf/01:00:03:00:00/40 tag 19 ncq dma 131072 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/08:a0:30:12:01/00:00:04:00:00/40 tag 20 ncq dma 4096 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/b0:a8:20:dc:be/00:00:01:00:00/40 tag 21 ncq dma 90112 in  
> res 40/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/08:b0:c0:99:8f/00:00:01:00:00/40 tag 22 ncq dma 4096 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3.00: failed command: READ FPDMA QUEUED  
> janv. 14 19:03:41 artic kernel: ata3.00: cmd 60/08:b8:c8:22:c1/00:00:03:00:00/40 tag 23 ncq dma 4096 in  
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)  
> janv. 14 19:03:41 artic kernel: ata3.00: status: { DRDY }  
> janv. 14 19:03:41 artic kernel: ata3: hard resetting link  
> janv. 14 19:03:41 artic kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)  
> janv. 14 19:03:41 artic kernel: ata3.00: configured for UDMA/133  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=33s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#13 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#13 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 00 b4 4d 90 00 01 00 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 11816336 op 0x0:(READ) flags 0x80700 phys\_seg 32 prio class 3  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=32s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#14 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#14 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 02 cd f8 20 00 00 e0 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 47052832 op 0x0:(READ) flags 0x80700 phys\_seg 2 prio class 2  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=32s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#15 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#15 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 02 f9 13 b0 00 00 c8 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 49877936 op 0x0:(READ) flags 0x80700 phys\_seg 2 prio class 2  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=32s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#18 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#18 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#18 CDB: Read(10) 28 00 03 bc 45 00 00 00 d0 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 62670080 op 0x0:(READ) flags 0x80700 phys\_seg 2 prio class 2  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=32s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#19 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#19 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#19 CDB: Read(10) 28 00 03 bf 82 00 00 01 00 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 62882304 op 0x0:(READ) flags 0x80700 phys\_seg 2 prio class 2  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=32s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#21 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#21 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 01 be dc 20 00 00 b0 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 29285408 op 0x0:(READ) flags 0x80700 phys\_seg 2 prio class 2  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID\_OK driverbyte=DRIVER\_OK cmd\_age=32s  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#22 Sense Key : Aborted Command [current]  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#22 Add. Sense: No additional sense information  
> janv. 14 19:03:41 artic kernel: sd 2:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 01 8f 99 c0 00 00 08 00  
> janv. 14 19:03:41 artic kernel: I/O error, dev sda, sector 26188224 op 0x0:(READ) flags 0x80700 phys\_seg 1 prio class 2  
> janv. 14 19:03:41 artic kernel: ata3: EH complete  
> janv. 14 19:03:42 artic smartd[959]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw\_Read\_Error\_Rate changed from 90 to 120  
> janv. 14 19:03:42 artic smartd[959]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 ECC\_Uncorr\_Error\_Count changed from 120 to 100  
> janv. 14 19:03:42 artic smartd[959]: Device: /dev/sda [SAT], SMART Usage Attribute: 201 Unc\_Soft\_Read\_Err\_Rate changed from 120 to 100  
> janv. 14 19:03:42 artic smartd[959]: Device: /dev/sda [SAT], SMART Usage Attribute: 204 Soft\_ECC\_Correct\_Rate changed from 120 to 100  
> janv. 14 19:03:43 artic smartd[959]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Corsair\_Force\_GT-1131820100000705005E.ata.state  
> janv. 14 19:03:57 artic smartd[959]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Corsair\_Force\_GT-1131820100000705005E.ata.state  
> janv. 14 19:03:58 artic systemd[1]: dev-sda2.swap: Deactivated successfully.  
> janv. 14 19:03:58 artic systemd[1]: Deactivated swap dev-sda2.swap - /dev/sda2.

Or je n’ai plus du tout ces messages d’erreurs d’entrées/sorties après un redémarrage à chaud :

> libresurf@artic:~$ journalctl -b -g ‹&nbsp;(ata3|sda)&nbsp;›  
> janv. 14 19:04:55 artic kernel: ata3: SATA max UDMA/133 abar m1024@0xfcafe000 port 0xfcafe100 irq 46 lpm-pol 3  
> janv. 14 19:04:55 artic kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)  
> janv. 14 19:04:55 artic kernel: ata3.00: ATA-9: Corsair Force GT, 1.2, max UDMA/133  
> janv. 14 19:04:55 artic kernel: ata3.00: 117231408 sectors, multi 16: LBA48 NCQ (depth 32), AA  
> janv. 14 19:04:55 artic kernel: ata3.00: configured for UDMA/133  
> janv. 14 19:04:55 artic kernel: sd 2:0:0:0: [sda] 117231408 512-byte logical blocks: (60.0 GB/55.9 GiB)  
> janv. 14 19:04:55 artic kernel: sd 2:0:0:0: [sda] Write Protect is off  
> janv. 14 19:04:55 artic kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00  
> janv. 14 19:04:55 artic kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA  
> janv. 14 19:04:55 artic kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 512 bytes  
> janv. 14 19:04:55 artic kernel: sda: sda1 sda2  
> janv. 14 19:04:55 artic kernel: sd 2:0:0:0: [sda] Attached SCSI disk  
> janv. 14 19:04:55 artic kernel: EXT4-fs (sda1): orphan cleanup on readonly fs  
> janv. 14 19:04:55 artic kernel: EXT4-fs (sda1): mounted filesystem 3863bfde-c975-4bc1-bd9f-403d3617e8e8 ro with ordered data mode. Quota mode: none.  
> janv. 14 19:04:55 artic kernel: EXT4-fs (sda1): re-mounted 3863bfde-c975-4bc1-bd9f-403d3617e8e8 r/w.  
> janv. 14 19:04:55 artic kernel: Adding 3926012k swap on /dev/sda2. Priority:-2 extents:1 across:3926012k SS  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda, type changed from ‹&nbsp;scsi&nbsp;› to ‹&nbsp;sat&nbsp;›  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], opened  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], Corsair Force GT, S/N:1131820100000705005E, WWN:0-000000-000000000, FW:1.2, 60.0 GB  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], found in smartd database 7.3/5528: SandForce Driven SSDs  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], can’t monitor Current\_Pending\_Sector count - no Attribute 197  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], no SMART Self-test Log, ignoring -l selftest (override with -T permissive)  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], no SMART Error Log, ignoring -l error (override with -T permissive)  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], is SMART capable. Adding to «&nbsp;monitor&nbsp;» list.  
> janv. 14 19:04:56 artic smartd[919]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.Corsair\_Force\_GT-1131820100000705005E.ata.state  
> janv. 14 19:04:57 artic smartd[919]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature\_Celsius changed from 27 to 28  
> janv. 14 19:04:57 artic smartd[919]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Corsair\_Force\_GT-1131820100000705005E.ata.state

À part le fait que mon matériel commence sérieusement à dater, quelqu’un d’entre vous serait-il pourquoi j’ai ce problème lors d’un démarrage à froid ???

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 14, 2026, 6:38 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/2 "2026-01-14T18:38:44Z")

</div>

Désolé, je n’ai pas trouvé comment afficher le résultat sur des lignes entières sans les retours à la ligne lorsque la phrase est trop longue. 😒

---

<div class="post-metadata">

**Author:** ![Necromago](https://www.debian-fr.org/user_avatar/www.debian-fr.org/necromago/32/15111_2.png) [@Necromago](https://www.debian-fr.org/u/Necromago)\
**Post date:** [Janvier 14, 2026, 7:17 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/3 "2026-01-14T19:17:19Z")

</div>

Hello,

Que donne cet outil sur ton SSD ?

[Smartmontools](https://doc.ubuntu-fr.org/smartmontools)

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 14, 2026, 8:18 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/4 "2026-01-14T20:18:39Z")

</div>

Bonjour @Necromago ,  
Voici les informations retournées par _smartctl_ :

```
libresurf@artic:~$ sudo smartctl -s on -a /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.63+deb13-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SandForce Driven SSDs
Device Model: Corsair Force GT
Serial Number: 1131820100000705005E
LU WWN Device Id: 0 000000 000000000
Firmware Version: 1.2
User Capacity: 60 022 480 896 bytes [60,0 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
TRIM Command: Available, deterministic
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Jan 14 21:13:38 2026 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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: ( 0) seconds.
Offline data collection
capabilities: (0x7f) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Abort Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        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.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 48) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x0021) SCT Status supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000f 095 095 050 Pre-fail Always - 223/9423839
  5 Retired_Block_Count 0x0033 100 100 003 Pre-fail Always - 0
  9 Power_On_Hours_and_Msec 0x0032 093 093 000 Old_age Always - 6677h+54m+52.949s
 12 Power_Cycle_Count 0x0032 094 094 000 Old_age Always - 6294
171 Program_Fail_Count 0x0032 000 000 000 Old_age Always - 0
172 Erase_Fail_Count 0x0032 000 000 000 Old_age Always - 0
174 Unexpect_Power_Loss_Ct 0x0030 000 000 000 Old_age Offline - 164
177 Wear_Range_Delta 0x0000 000 000 000 Old_age Offline - 5
181 Program_Fail_Count 0x0032 000 000 000 Old_age Always - 0
182 Erase_Fail_Count 0x0032 000 000 000 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 029 080 000 Old_age Always - 29 (Min/Max 16/80)
195 ECC_Uncorr_Error_Count 0x001c 120 120 000 Old_age Offline - 223/9423839
196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0
201 Unc_Soft_Read_Err_Rate 0x001c 120 120 000 Old_age Offline - 223/9423839
204 Soft_ECC_Correct_Rate 0x001c 120 120 000 Old_age Offline - 223/9423839
230 Life_Curve_Status 0x0013 100 100 000 Pre-fail Always - 429496729700
231 SSD_Life_Left 0x0013 100 100 010 Pre-fail Always - 0
233 SandForce_Internal 0x0000 000 000 000 Old_age Offline - 6942
234 SandForce_Internal 0x0032 000 000 000 Old_age Always - 7735
241 Lifetime_Writes_GiB 0x0032 000 000 000 Old_age Always - 7735
242 Lifetime_Reads_GiB 0x0032 000 000 000 Old_age Always - 31574

SMART Error Log not supported

SMART Self-test Log not supported

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 spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more
```

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 14, 2026, 8:21 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/5 "2026-01-14T20:21:05Z")

</div>

J’ai aussi lancé un test long… Il va falloir attendre un petit peu, environ 48 min.

```
libresurf@artic:~$ sudo smartctl -t long /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.63+deb13-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 48 minutes for test to complete.
Test will complete after Wed Jan 14 22:07:23 2026 CET
Use smartctl -X to abort test.
```

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 14, 2026, 9:51 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/6 "2026-01-14T21:51:28Z")

</div>

Le test long n’a pas fonctionné.

```
libresurf@artic:~$ sudo smartctl -l selftest /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.63+deb13-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test Log not supported
```

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Janvier 14, 2026, 10:00 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/7 "2026-01-14T22:00:11Z")

</div>

> [@libresurf](#):
>
> kernel: ata3.00: failed command: READ FPDMA QUEUED

C’est peut etre du à des problèmes de cable aussi, ou de connection du cable.

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 14, 2026, 10:04 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/8 "2026-01-14T22:04:36Z")

</div>

> [@Zargos](#):
>
> C’est peut etre du à des problèmes de cable aussi, ou de connection du cable.

Ah. Merci @Zargos , je vais regarder ça.

---

<div class="post-metadata">

**Author:** ![droopy191](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/c89c15/32.png) [@droopy191](https://www.debian-fr.org/u/droopy191)\
**Post date:** [Janvier 15, 2026, 5:59 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/9 "2026-01-15T17:59:46Z")

</div>

Salut,

Autre piste:  
Ca fait penser problème de condensateur qq part entre la prise et le ssd.  
Peut etre, un problème d’alimentation du ssd. Si vous etes sur un pc, essayez de brancher le ssd sur une autre nappe d’alimentation electrique, seul sur la nappe. Si ca règle le pb, alim qui flanche.

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Janvier 16, 2026, 8:45 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/10 "2026-01-16T08:45:03Z")

</div>

> [@droopy191](#):
>
> Si ca règle le pb, alim qui flanche

ou le cable d’alim.

Ça peut aussi être le fait qu’il y a trop de charge sur le même câble. delester sur une autre câble peut résoudre le problème.

Les problèmes d’alimentation surchargée peuvent aussi provoquer ce genre de problème.

---

<div class="post-metadata">

**Author:** ![libresurf](https://www.debian-fr.org/user_avatar/www.debian-fr.org/libresurf/32/5259_2.png) [@libresurf](https://www.debian-fr.org/u/libresurf)\
**Post date:** [Janvier 17, 2026, 5:38 UTC](https://www.debian-fr.org/t/problemes-dacces-au-disque-systeme-lors-des-bootages-a-froid/91945/11 "2026-01-17T17:38:50Z")

</div>

Merci @Zargos et @droopy191 pour vos conseils.  
On s’oriente donc bien vers un problème matériel.  
J’espérais que ce soit un problème logiciel avec un driver qui aurait pu mettre trop de temps à s’initialiser dans la séquence de boot.

Il va falloir que je m’équipe un peu car mes câbles d’alimentation et mes câbles SATA sont tous utilisés. Mes autres disques sont montés en RAID et je n’ai pas trop envie d’y toucher pour le moment.  
Quelque part, je préfère que ce soit le disque système qui présente des signaux de faiblesses que les disques de données montés en RAID.