Pages : 1
#1 Le 27/02/2018, à 13:34
- TomK
[RESOLU] Disque Dur Seagate mort ?
Bonjour,
Depuis quelques temps maintenant, j'ai de gros problème avec mon disque dur Seagate 1To ST1000DM003 Barracuda. Je crois que mon DD a commencer à déconner à partir du moment où j'ai quitté Windows 10 pour retourner définitivement sur Ubuntu. Il est dans l'incapacité total de booter... A chaque fois que je démarre mon pc, j'ai une tonne de ligne qui défile et soit ça bloque, soit ça se termine en erreur ( genre initramfs ou autre... ). A chaque fois je suis obligé de démarrer en LiveUSB Ubuntu 16.04 LTS 64bits ( ce qui est le cas actuellement ).
J'ai pris plusieurs photos des lignes pour vous puissiez voir un petit peu ce que ça donnait :
https://thetomk.tumblr.com/post/171342682543/ubuntu
J'ai lancé un boot-info, si cela peut vous être utile :
http://paste.ubuntu.com/p/FBtzSJrMK3/
J'aimerai pouvoir vous donner le résultat d'un gsmartcontrol... Mais je n'arrive pas à l'installer en LiveUSB alors que Smartmontools j'y arrive...
Pourriez-vous m'aider à analyser mon disque dur, voir s'il est bel et bien mort, histoire d'être sûr que ce ne soit pas une question de configuration du BIOS ou autre avant d'en racheter un !
Merci d'avance si vous pouvez m'aider !!
Dernière modification par TomK (Le 28/02/2018, à 14:24)
Hors ligne
#2 Le 27/02/2018, à 13:45
- ??
Re : [RESOLU] Disque Dur Seagate mort ?
Bonjour
Il est clair que ton disque est en mauvais état.
Pour savoir si c'est le disque lui-même ou la connectique, il faut un rapport smarctl à faire avec ton support d'installation.
Tu choisis "essayer avant d'installer, tu mets le clavier en français " setkkbmap fr"
puis
sudo apt-get install --no-install-recommends smartmontools
sudo smartctl -s on -a /dev/sda
et tu postes le résultat.
Dernière modification par ?? (Le 27/02/2018, à 13:46)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#3 Le 27/02/2018, à 13:49
- TomK
Re : [RESOLU] Disque Dur Seagate mort ?
Bonjour
Il est clair que ton disque est en mauvais état.
Pour savoir si c'est le disque lui-même ou la connectique, il faut un rapport smarctl à faire avec ton support d'installation.
Tu choisis "essayer avant d'installer, tu mets le clavier en français " setkkbmap fr"
puissudo apt-get install --no-install-recommends smartmontools sudo smartctl -s on -a /dev/sda
et tu postes le résultat.
Merci pour votre retour !
Effectivement, je me doutais bien que mon disque dur était dans un sale état... Je l'entend tourner bizarrrement...
Voici le retour de la commande :
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST1000DM003-1ER162
Serial Number: Z4Y5QADX
LU WWN Device Id: 5 000c50 07ac51687
Firmware Version: CC45
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Tue Feb 27 12:47:56 2018 UTC
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: ( 80) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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: ( 105) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1085) SCT Status 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 119 099 006 Pre-fail Always - 234017104
3 Spin_Up_Time 0x0003 099 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 084 084 020 Old_age Always - 16454
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 258124291
9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10484
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1559
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 079 000 Old_age Always - 0 0 28
189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2
190 Airflow_Temperature_Cel 0x0022 074 063 045 Old_age Always - 26 (Min/Max 25/26)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 093 093 000 Old_age Always - 14822
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 24699
194 Temperature_Celsius 0x0022 026 040 000 Old_age Always - 26 (0 15 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 10104h+52m+52.882s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 35656070982
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 735411225044
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 10310 -
# 2 Short offline Interrupted (host reset) 00% 10301 -
# 3 Short offline Completed without error 00% 10276 -
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.
Hors ligne
#4 Le 27/02/2018, à 14:15
- ??
Re : [RESOLU] Disque Dur Seagate mort ?
La qualité du disque n'est pas en cause,
=> 197 Current_Pending_Sector = 0
=> 5 Reallocated_Sector_Ct = 0
=> No Errors Logged
Mais sa mécanique faiblit
=> 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 234017104 ( Ce n'est pas si mauvais)
=> 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 258124291 ( ce n'est pas très bon) par moment cela fonction a 60%
Ce que tu confirme par les bruits entendus
L'ennui est ici
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1
===The count of errors in data transfer via the interface cable as determined by ICRC (Interface Cyclic Redundancy Check).
Cela peut être un faux contact qui se produit à un mauvais moment.
Ce qui me surprend c'est la valeur 1 qui semble correspondre à ton incident actuel "READ FPDMA QUEUED"
D# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 234017104
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 258124291
9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10484
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 074 063 045 Old_age Always - 26 (Min/Max 25/26)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1
SMART Error Log Version: 1
No Errors Logged
Ajout: Je viens de remonter ton historique et j'ai récupérté un ancien rapport smartctl
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 74844328
7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 256777963
9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10276
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1
Il y avait déjà cette valeur à 1 !!!!!!!
Dernière modification par ?? (Le 27/02/2018, à 14:51)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#5 Le 27/02/2018, à 14:18
- inbox
Re : [RESOLU] Disque Dur Seagate mort ?
Salut,
Pour analyser les messages système, il faudrait que tu donnes le retour complet de :
dmesg
A+
Un problème résolu ? Indiquez le en modifiant le titre du sujet.
Hors ligne
#6 Le 27/02/2018, à 14:50
- TomK
Re : [RESOLU] Disque Dur Seagate mort ?
Cela peut être un faux contact qui se produit à un mauvais moment.
Un problème avec mon cable SATA ? Voir, mais je ne l'espère pas, un problème avec la prise SATA sur ma carte mère ( une MSI H97M-G43 ) ?
Ajout: Je viens de remonter ton historique et j'ai récupérté un ancien rapport smartctl
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 74844328 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 256777963 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10276 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1
Il y avait déjà cette valeur à 1 !!!!!!!
Oui, j'ai ce problème depuis un bon moment maintenant !
Salut,
Pour analyser les messages système, il faudrait que tu donnes le retour complet de :
dmesg
A+
Bonjour, voici le pastebin avec le retour complet de la commande :
https://pastebin.ubuntu.com/p/HsqFhSBDR3/
Dernière modification par TomK (Le 27/02/2018, à 14:59)
Hors ligne
#7 Le 27/02/2018, à 15:03
- ??
Re : [RESOLU] Disque Dur Seagate mort ?
Je viens de voir que tu as assemblé ton micro. J'insiste donc sur le câble de connexion lui-même ou avec la connexion à la carte mère.
===> https://askubuntu.com/questions/133946/ … -dangerous
Checking that your SATA cable is securely attached and plugged into the sockets on the motherboard and hard drive.
Replacing your SATA cable. SATA cables are (relatively) inexpensive and you do sometimes get a "bad" one. Often simply replacing the cable is the easiest way to diagnose and solve a problem like this.
==> Une des pistes: Ton disque peut débiter a 6 Mb/s et le câble est seulement certifié pour 3 Mb/s
Dans ta photo, on voit très bien le message répété 3 fois..... "failed command: READ FPDMA QUEUED"
Comme le firwmare du disque ne compte que 1 , La commande de lecture ne lui est pas parvenue.
Un extrait de la trace que tu as fournis
9.220881] ata5.00: irq_stat 0x00400040, connection status changed
[ 9.220884] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 9.220888] ata5.00: failed command: IDENTIFY DEVICE
[ 9.220892] ata5.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 2 pio 512 in
res 40/00:90:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 9.220898] ata5.00: status: { DRDY }
[ 9.220901] ata5: hard resetting link
[ 13.592382] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 13.592889] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 13.592897] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 13.594073] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 13.594081] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 13.594447] ata5.00: configured for UDMA/133
[ 13.594453] ata5: EH complete
[ 13.764385] ata5.00: exception Emask 0x50 SAct 0x1000000 SErr 0x4090800 action 0xe frozen
[ 13.764393] ata5.00: irq_stat 0x00400040, connection status changed
[ 13.764406] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 13.764410] ata5.00: failed command: READ FPDMA QUEUED
[ 13.764414] ata5.00: cmd 60/08:c0:00:10:00/00:00:00:00:00/40 tag 24 ncq dma 4096 in
res 40/00:c0:00:10:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 13.764420] ata5.00: status: { DRDY }
[ 13.764423] ata5: hard resetting link
[ 18.135904] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 18.136410] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 18.136421] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 18.137602] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 18.137610] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 18.137973] ata5.00: configured for UDMA/133
[ 18.137977] ata5: EH complete
[ 18.183926] ata5: limiting SATA link speed to 3.0 Gbps
[ 18.183928] ata5.00: exception Emask 0x50 SAct 0x60000 SErr 0x4890800 action 0xe frozen
[ 18.183944] ata5.00: irq_stat 0x04400040, connection status changed
[ 18.183948] ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
[ 18.183951] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183956] ata5.00: cmd 60/08:88:00:08:00/00:00:00:00:00/40 tag 17 ncq dma 4096 in
res 40/00:88:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 18.183961] ata5.00: status: { DRDY }
[ 18.183964] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183968] ata5.00: cmd 60/08:90:f8:0f:2a/00:00:01:00:00/40 tag 18 ncq dma 4096 in
res 40/00:88:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 18.183973] ata5.00: status: { DRDY }
[ 18.183976] ata5: hard resetting link
[ 22.555438] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 22.555943] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 22.555951] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 22.557124] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 22.557132] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 22.557675] ata5.00: configured for UDMA/133
[ 22.557678] ata5: EH complete
[ 22.615443] ata5.00: exception Emask 0x50 SAct 0x1000 SErr 0x4090800 action 0xe frozen
[ 22.615658] ata5.00: irq_stat 0x00400048, connection status changed
[ 22.616005] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 22.616410] ata5.00: failed command: READ FPDMA QUEUED
[ 22.616820] ata5.00: cmd 60/08:60:00:18:2a/00:00:01:00:00/40 tag 12 ncq dma 4096 in
res 40/00:60:00:18:2a/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
[ 22.617635] ata5.00: status: { DRDY }
[ 22.618075] ata5: hard resetting link
[ 26.986971] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 26.987478] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 26.987674] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 26.989187] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 26.989385] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 26.990106] ata5.00: configured for UDMA/133
[ 26.990110] ata5: EH complete
[ 27.303018] ata5.00: exception Emask 0x50 SAct 0x10 SErr 0x4090800 action 0xe frozen
[ 27.303214] ata5.00: irq_stat 0x00400040, connection status changed
[ 27.303587] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 27.304003] ata5.00: failed command: READ FPDMA QUEUED
[ 27.304417] ata5.00: cmd 60/08:20:00:10:00/00:00:00:00:00/40 tag 4 ncq dma 4096 in
res 40/00:30:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 27.305245] ata5.00: status: { DRDY }
[ 27.305659] ata5: hard resetting link
[ 31.674478] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 31.674984] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 31.675184] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 31.676715] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 31.676919] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 31.677659] ata5.00: configured for UDMA/133
[ 31.677662] ata5: EH complete
[ 31.930506] ata5.00: exception Emask 0x50 SAct 0x8000 SErr 0x4090800 action 0xe frozen
[ 31.930509] ata5.00: irq_stat 0x00400040, connection status changed
[ 31.930510] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 31.930511] ata5.00: failed command: READ FPDMA QUEUED
[ 31.930514] ata5.00: cmd 60/08:78:80:00:00/00:00:00:00:00/40 tag 15 ncq dma 4096 in
res 40/00:78:80:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 31.930515] ata5.00: status: { DRDY }
[ 31.930517] ata5: hard resetting link
[ 36.301989] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 36.302528] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 36.302532] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 36.303696] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 36.303699] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 36.304072] ata5.00: configured for UDMA/133
[ 36.304076] ata5: EH complete
[ 36.513978] ata5: limiting SATA link speed to 1.5 Gbps
[ 36.513979] ata5.00: exception Emask 0x50 SAct 0x4 SErr 0x4090800 action 0xe frozen
[ 36.513981] ata5.00: irq_stat 0x00400040, connection status changed
[ 36.513983] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 36.513984] ata5.00: failed command: READ FPDMA QUEUED
[ 36.513986] ata5.00: cmd 60/08:10:00:18:2a/00:00:01:00:00/40 tag 2 ncq dma 4096 in
res 40/00:10:00:18:2a/00:00:01:00:00/40 Emask 0x50 (ATA bus error)
[ 36.513988] ata5.00: status: { DRDY }
[ 36.513990] ata5: hard resetting link
[ 40.885507] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 40.886049] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 40.886053] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 40.887237] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 40.887241] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 40.887611] ata5.00: configured for UDMA/133
[ 40.887615] ata5: EH complete
[ 40.918199] random: crng init done
[ 40.965897] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[ 41.109882] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 41.570266] aufs 4.x-rcN-20170206
[ 43.521283] ata5.00: exception Emask 0x10 SAct 0x100 SErr 0x4090000 action 0xe frozen
[ 43.521285] ata5.00: irq_stat 0x00400040, connection status changed
[ 43.521286] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 43.521288] ata5.00: failed command: READ FPDMA QUEUED
[ 43.521290] ata5.00: cmd 60/00:40:00:02:00/02:00:00:00:00/40 tag 8 ncq dma 262144 in
res 40/00:40:00:02:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 43.521291] ata5.00: status: { DRDY }
[ 43.521293] ata5: hard resetting link
[ 47.892770] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 47.893307] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 47.893312] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 47.894480] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 47.894484] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 47.894842] ata5.00: configured for UDMA/133
[ 47.894847] ata5: EH complete
[ 47.972782] ata5.00: exception Emask 0x10 SAct 0x8 SErr 0x4090000 action 0xe frozen
[ 47.972784] ata5.00: irq_stat 0x00400040, connection status changed
[ 47.972785] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 47.972787] ata5.00: failed command: READ FPDMA QUEUED
[ 47.972789] ata5.00: cmd 60/08:18:00:10:00/00:00:00:00:00/40 tag 3 ncq dma 4096 in
res 40/00:18:00:10:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 47.972800] ata5.00: status: { DRDY }
[ 47.972802] ata5: hard resetting link
[ 52.344300] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 52.344815] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 52.344818] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 52.346018] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 52.346021] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 52.346395] ata5.00: configured for UDMA/133
[ 52.346398] ata5: EH complete
[ 52.496305] ata5.00: exception Emask 0x10 SAct 0x40000 SErr 0x4090000 action 0xe frozen
[ 52.496307] ata5.00: irq_stat 0x00400040, connection status changed
[ 52.496308] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 52.496309] ata5.00: failed command: READ FPDMA QUEUED
[ 52.496312] ata5.00: cmd 60/00:90:00:02:00/02:00:00:00:00/40 tag 18 ncq dma 262144 in
res 40/00:90:00:02:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 52.496313] ata5.00: status: { DRDY }
[ 52.496324] ata5: hard resetting link
[ 56.867828] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.868378] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 56.868382] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 56.869549] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 56.869553] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 56.869914] ata5.00: configured for UDMA/133
[ 56.869920] ata5: EH complete
[ 56.951838] ata5.00: limiting speed to UDMA/100:PIO4
[ 56.951839] ata5.00: exception Emask 0x10 SAct 0x2000 SErr 0x4090000 action 0xe frozen
[ 56.951841] ata5.00: irq_stat 0x00400040, connection status changed
[ 56.951842] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 56.951844] ata5.00: failed command: READ FPDMA QUEUED
[ 56.951856] ata5.00: cmd 60/08:68:00:10:00/00:00:00:00:00/40 tag 13 ncq dma 4096 in
res 40/00:68:00:10:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 56.951857] ata5.00: status: { DRDY }
[ 56.951859] ata5: hard resetting link
[ 61.323355] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.323865] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 61.323868] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 61.325057] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 61.325061] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 61.325421] ata5.00: configured for UDMA/100
[ 61.325424] ata5: EH complete
[ 61.688672] Adding 9764860k swap on /dev/sda1. Priority:-1 extents:1 across:9764860k FS
[ 63.503139] ata5.00: exception Emask 0x10 SAct 0x2080000 SErr 0x4090000 action 0xe frozen
[ 63.503141] ata5.00: irq_stat 0x00400040, connection status changed
[ 63.503142] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 63.503144] ata5.00: failed command: READ FPDMA QUEUED
[ 63.503146] ata5.00: cmd 60/08:98:f8:66:70/00:00:74:00:00/40 tag 19 ncq dma 4096 in
res 40/00:c8:00:18:2a/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[ 63.503147] ata5.00: status: { DRDY }
[ 63.503148] ata5.00: failed command: READ FPDMA QUEUED
[ 63.503150] ata5.00: cmd 60/08:c8:00:18:2a/00:00:01:00:00/40 tag 25 ncq dma 4096 in
res 40/00:c8:00:18:2a/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[ 63.503151] ata5.00: status: { DRDY }
[ 63.503153] ata5: hard resetting link
[ 67.874664] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 67.875207] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 67.875212] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 67.876377] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 67.876380] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 67.876754] ata5.00: configured for UDMA/100
[ 67.876759] ata5: EH complete
[ 67.922690] ata5.00: exception Emask 0x10 SAct 0x10000040 SErr 0x4090000 action 0xe frozen
[ 67.922692] ata5.00: irq_stat 0x00400040, connection status changed
[ 67.922693] ata5: SError: { PHYRdyChg 10B8B DevExch }
[ 67.922695] ata5.00: failed command: READ FPDMA QUEUED
[ 67.922707] ata5.00: cmd 60/08:30:00:18:00/00:00:00:00:00/40 tag 6 ncq dma 4096 in
res 40/00:30:00:18:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 67.922708] ata5.00: status: { DRDY }
[ 67.922709] ata5.00: failed command: READ FPDMA QUEUED
[ 67.922711] ata5.00: cmd 60/08:e0:f8:66:70/00:00:74:00:00/40 tag 28 ncq dma 4096 in
res 40/00:30:00:18:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 67.922712] ata5.00: status: { DRDY }
[ 67.922713] ata5: hard resetting link
[ 72.294198] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 72.294709] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 72.294713] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 72.295921] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 72.295924] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 72.296304] ata5.00: configured for UDMA/100
[ 72.296308] ata5: EH complete
NOTA: Il est probable que windows sache mieux gérer une connectique disque à 1,5 Mo/s
Dernière modification par ?? (Le 27/02/2018, à 15:31)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#8 Le 27/02/2018, à 15:13
- TomK
Re : [RESOLU] Disque Dur Seagate mort ?
Je viens de voir que tu as assemblé ton micro. J'insiste donc sur le câble de connexion lui-même ou avec la connexion à la carte mère.
===> https://askubuntu.com/questions/133946/ … -dangerousChecking that your SATA cable is securely attached and plugged into the sockets on the motherboard and hard drive.
Replacing your SATA cable. SATA cables are (relatively) inexpensive and you do sometimes get a "bad" one. Often simply replacing the cable is the easiest way to diagnose and solve a problem like this.
==> Une des pistes: Ton disque peut débiter a 6 Mb/s et le câble est seulement certifié pour 3 Mb/s
Dans ta photo, on voit très bien le message répété 3 fois..... "failed command: READ FPDMA QUEUED"
Comme le firwmare du disque ne compte que 1 , La commande de lecture ne lui est pas parvenue.
Quand on m'a livré mon DD, j'avais un cable simple avec. Mais pour ma tour, j'avais besoin d'un câble SATA coudé... Le problème peut-être de là...
Voici le retour de la commande dmesg | grep QUEUED :
ubuntu@ubuntu:~$ dmesg | grep QUEUED
[ 4.773650] ata5.00: failed command: READ FPDMA QUEUED
[ 13.764410] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183951] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183964] ata5.00: failed command: READ FPDMA QUEUED
[ 22.616410] ata5.00: failed command: READ FPDMA QUEUED
[ 27.304003] ata5.00: failed command: READ FPDMA QUEUED
[ 31.930511] ata5.00: failed command: READ FPDMA QUEUED
[ 36.513984] ata5.00: failed command: READ FPDMA QUEUED
[ 43.521288] ata5.00: failed command: READ FPDMA QUEUED
[ 47.972787] ata5.00: failed command: READ FPDMA QUEUED
[ 52.496309] ata5.00: failed command: READ FPDMA QUEUED
[ 56.951844] ata5.00: failed command: READ FPDMA QUEUED
[ 63.503144] ata5.00: failed command: READ FPDMA QUEUED
[ 63.503148] ata5.00: failed command: READ FPDMA QUEUED
[ 67.922695] ata5.00: failed command: READ FPDMA QUEUED
[ 67.922709] ata5.00: failed command: READ FPDMA QUEUED
[ 76.565733] ata5.00: failed command: READ FPDMA QUEUED
Merci pour votre aide en tout cas ! Je ne pourrais répondre que en fin d'après-midi à vos messages.
Bonne après midi à vous.
Dernière modification par TomK (Le 27/02/2018, à 15:15)
Hors ligne
#9 Le 27/02/2018, à 15:17
- inbox
Re : [RESOLU] Disque Dur Seagate mort ?
Il y a donc :
[ 4.773308] ata5.00: exception Emask 0x50 SAct 0x20000000 SErr 0x4090800 action 0xe frozen
[ 4.773445] ata5.00: irq_stat 0x00400040, connection status changed
[ 4.773548] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 4.773650] ata5.00: failed command: READ FPDMA QUEUED
[ 4.773753] ata5.00: cmd 60/08:e8:00:00:00/00:00:00:00:00/40 tag 29 ncq dma 4096 in
res 40/00:e8:00:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 4.773910] ata5.00: status: { DRDY }
[ 4.774010] ata5: hard resetting link
[ 9.220875] ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
[ 9.220881] ata5.00: irq_stat 0x00400040, connection status changed
[ 9.220884] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 9.220888] ata5.00: failed command: IDENTIFY DEVICE
[ 9.220892] ata5.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 2 pio 512 in
res 40/00:90:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 9.220898] ata5.00: status: { DRDY }
[ 9.220901] ata5: hard resetting link
[ 13.592382] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 13.592889] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 13.592897] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 13.594073] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 13.594081] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 13.594447] ata5.00: configured for UDMA/133
[ 13.594453] ata5: EH complete
[ 13.764385] ata5.00: exception Emask 0x50 SAct 0x1000000 SErr 0x4090800 action 0xe frozen
[ 13.764393] ata5.00: irq_stat 0x00400040, connection status changed
[ 13.764406] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 13.764410] ata5.00: failed command: READ FPDMA QUEUED
[ 13.764414] ata5.00: cmd 60/08:c0:00:10:00/00:00:00:00:00/40 tag 24 ncq dma 4096 in
res 40/00:c0:00:10:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 13.764420] ata5.00: status: { DRDY }
[ 13.764423] ata5: hard resetting link
[ 18.135904] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 18.136410] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 18.136421] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 18.137602] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 18.137610] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 18.137973] ata5.00: configured for UDMA/133
[ 18.137977] ata5: EH complete
[ 18.183926] ata5: limiting SATA link speed to 3.0 Gbps
[ 18.183928] ata5.00: exception Emask 0x50 SAct 0x60000 SErr 0x4890800 action 0xe frozen
[ 18.183944] ata5.00: irq_stat 0x04400040, connection status changed
[ 18.183948] ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
[ 18.183951] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183956] ata5.00: cmd 60/08:88:00:08:00/00:00:00:00:00/40 tag 17 ncq dma 4096 in
res 40/00:88:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 18.183961] ata5.00: status: { DRDY }
[ 18.183964] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183968] ata5.00: cmd 60/08:90:f8:0f:2a/00:00:01:00:00/40 tag 18 ncq dma 4096 in
res 40/00:88:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 18.183973] ata5.00: status: { DRDY }
[ 18.183976] ata5: hard resetting link
[ 22.555438] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Pas mal d'erreur de connexion Sata avec reset de lien.
[ 72.294198] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Plus loin, le système passe le lien Sata de 3 à 1,5 Gbps.
Comme l'a suggéré ??, il faut vérifier la connectique de ton disque dur interne. En cas de doute, change de câble Sata.
Tu as aussi une clef USB avec un système de fichiers abimé :
[ 2136.067897] usb 3-3: Product: Cruzer Blade
[ 2136.067898] usb 3-3: Manufacturer: SanDisk
[ 2136.067899] usb 3-3: SerialNumber: 4C530000301226121565
...................................
[ 2137.323504] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Un problème résolu ? Indiquez le en modifiant le titre du sujet.
Hors ligne
#10 Le 27/02/2018, à 20:59
- TomK
Re : [RESOLU] Disque Dur Seagate mort ?
Il y a donc :
[ 4.773308] ata5.00: exception Emask 0x50 SAct 0x20000000 SErr 0x4090800 action 0xe frozen
[ 4.773445] ata5.00: irq_stat 0x00400040, connection status changed
[ 4.773548] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 4.773650] ata5.00: failed command: READ FPDMA QUEUED
[ 4.773753] ata5.00: cmd 60/08:e8:00:00:00/00:00:00:00:00/40 tag 29 ncq dma 4096 in
res 40/00:e8:00:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 4.773910] ata5.00: status: { DRDY }
[ 4.774010] ata5: hard resetting link[ 9.220875] ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
[ 9.220881] ata5.00: irq_stat 0x00400040, connection status changed
[ 9.220884] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 9.220888] ata5.00: failed command: IDENTIFY DEVICE
[ 9.220892] ata5.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 2 pio 512 in
res 40/00:90:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 9.220898] ata5.00: status: { DRDY }
[ 9.220901] ata5: hard resetting link
[ 13.592382] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 13.592889] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 13.592897] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 13.594073] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 13.594081] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 13.594447] ata5.00: configured for UDMA/133
[ 13.594453] ata5: EH complete
[ 13.764385] ata5.00: exception Emask 0x50 SAct 0x1000000 SErr 0x4090800 action 0xe frozen
[ 13.764393] ata5.00: irq_stat 0x00400040, connection status changed
[ 13.764406] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }
[ 13.764410] ata5.00: failed command: READ FPDMA QUEUED
[ 13.764414] ata5.00: cmd 60/08:c0:00:10:00/00:00:00:00:00/40 tag 24 ncq dma 4096 in
res 40/00:c0:00:10:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 13.764420] ata5.00: status: { DRDY }
[ 13.764423] ata5: hard resetting link
[ 18.135904] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 18.136410] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 18.136421] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 18.137602] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 18.137610] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8b21150f35f0), AE_NOT_FOUND (20160930/psparse-543)
[ 18.137973] ata5.00: configured for UDMA/133
[ 18.137977] ata5: EH complete
[ 18.183926] ata5: limiting SATA link speed to 3.0 Gbps
[ 18.183928] ata5.00: exception Emask 0x50 SAct 0x60000 SErr 0x4890800 action 0xe frozen
[ 18.183944] ata5.00: irq_stat 0x04400040, connection status changed
[ 18.183948] ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
[ 18.183951] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183956] ata5.00: cmd 60/08:88:00:08:00/00:00:00:00:00/40 tag 17 ncq dma 4096 in
res 40/00:88:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 18.183961] ata5.00: status: { DRDY }
[ 18.183964] ata5.00: failed command: READ FPDMA QUEUED
[ 18.183968] ata5.00: cmd 60/08:90:f8:0f:2a/00:00:01:00:00/40 tag 18 ncq dma 4096 in
res 40/00:88:00:08:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[ 18.183973] ata5.00: status: { DRDY }
[ 18.183976] ata5: hard resetting link
[ 22.555438] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)Pas mal d'erreur de connexion Sata avec reset de lien.
[ 72.294198] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Plus loin, le système passe le lien Sata de 3 à 1,5 Gbps.
Comme l'a suggéré ??, il faut vérifier la connectique de ton disque dur interne. En cas de doute, change de câble Sata.
Tu as aussi une clef USB avec un système de fichiers abimé :
[ 2136.067897] usb 3-3: Product: Cruzer Blade
[ 2136.067898] usb 3-3: Manufacturer: SanDisk
[ 2136.067899] usb 3-3: SerialNumber: 4C530000301226121565
...................................
[ 2137.323504] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Je vais tester un autre câble SATA dans ce cas. J'espère que ça ira et que mon disque dur va tenir.
Pour la clé USB... C'est ma clé bootable. Mes problèmes peuvent venir de la ?
Hors ligne
#11 Le 27/02/2018, à 21:50
- inbox
Re : [RESOLU] Disque Dur Seagate mort ?
Concernant la clef USB, si tu le peux, il te suffit de la reformater. Tu peux en sauvegarder le contenu, avant , si nécessaire.
Un problème résolu ? Indiquez le en modifiant le titre du sujet.
Hors ligne
#12 Le 28/02/2018, à 14:23
- TomK
Re : [RESOLU] Disque Dur Seagate mort ?
Bonjour,
Je viens de faire la manipulation. J'ai remplacé le câble SATA mais aussi le câble d'alimentation SATA... Au redémarrage de mon pc, Le disque dur ne faisait plus aucuns bruits, mais il n'a pas booté, il y avait un message d'erreur. De ce fait, j'ai reformaté mon disque dur avec Gparted ( pas de bruits à ce moment... Alors qu'avant je l'entendais " sauter " ) et j'ai refais l'installation... Il démarre parfaitement. Aucunes lignes de codes indiquant une quelconque erreur ou autre... C'est niquel ! Et le bureau s'affiche rapidement, alors qu'avant ce n'était pas le cas.
A voir dans la durée maintenant !
Merci à vous pour votre aide, je passe le sujet en résolu !
Dernière modification par TomK (Le 28/02/2018, à 14:24)
Hors ligne
Pages : 1