SDA disparu
boot sur sdb mais plus de sda
Système et matériels / Installation et configuration
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
ce soir je démarre mon portable et plus de boot mageia, donc je le réinstalle et redémarre (ma mageia 9 est sur sdb et mes fichiers sur sda) apres une attente assez longue je retrouve ma mageia mais j'ai plus mes fichiers le sda a disparu il n'aparait plus dans Gparted ni dans le centre de control de mageia!
Je joint c'est quelques lignes prise dans le journal qui sont en rouge pour la plupart!
Caché :
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: Read log 0x10 page 0x00 failed, Emask 0x1
janv. 09 17:43:31 Asus-R-900V kernel: fbcon: Taking over console
janv. 09 17:43:31 Asus-R-900V kernel: ata1: failed to read log page 10h (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: exception Emask 0x1 SAct 0x40000 SErr 0x0 action 0x6
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: irq_stat 0x40000001
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed command: READ FPDMA QUEUED
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: cmd 60/08:90:00:00:00/00:00:00:00:00/40 tag 18 ncq dma 4096 in
res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
09 17:43:31 Asus-R-900V kernel: ata1.00: Read log 0x10 page 0x00 failed, Emask 0x1
janv. 09 17:43:31 Asus-R-900V kernel: ata1: failed to read log page 10h (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: NCQ disabled due to excessive errors
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: exception Emask 0x1 SAct 0x1 SErr 0x0 action 0x6
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: irq_stat 0x40000001
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed command: READ FPDMA QUEUED
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq dma 4096 in
res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
09 17:43:31 Asus-R-900V kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: irq_stat 0x40000001
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed command: READ DMA
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 1 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: status: { DRDY ERR }
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: error: { ABRT }
janv. 09 17:43:31 Asus-R-900V kernel: ata1: hard resetting link
janv. 09 17:43:31 Asus-R-900V kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/0003:046D:C534.0002/input/input7
janv. 09 17:43:31 Asus-R-900V kernel: hid-generic 0003:046D:C534.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1.6/input1
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: qc timeout after 5000 msecs (cmd 0xef)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: ACPI cmd ef/90:06:00:00:00:00(SET FEATURES) failed (Emask=0x4 Stat=0x50 Err=0x01)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: revalidation failed (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1: hard resetting link
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: qc timeout after 10000 msecs (cmd 0xef)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: ACPI cmd ef/90:06:00:00:00:00(SET FEATURES) failed (Emask=0x4 Stat=0x50 Err=0x01)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: ACPI: failed the second time, disabled
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: revalidation failed (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1: limiting SATA link speed to 1.5 Gbps
janv. 09 17:43:31 Asus-R-900V kernel: ata1: hard resetting link
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: qc timeout after 15000 msecs (cmd 0xef)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed to set xfermode (err_mask=0x4)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: disable device
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
janv. 09 17:43:31 Asus-R-900V kernel: ata1: EH complete
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=32s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 0, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 1, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 2, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 3, async page read
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#19 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 0, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 1, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 2, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 3, async page read
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 0, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 1, async page read
janv. 09 17:43:31 Asus-R-900V kernel: ldm_validate_partition_table(): Disk read failed.
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 00 00 02 00 00 06 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 2 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 00 00 00 02 00 00 02 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: Read log 0x10 page 0x00 failed, Emask 0x1
janv. 09 17:43:31 Asus-R-900V kernel: fbcon: Taking over console
janv. 09 17:43:31 Asus-R-900V kernel: ata1: failed to read log page 10h (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: exception Emask 0x1 SAct 0x40000 SErr 0x0 action 0x6
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: irq_stat 0x40000001
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed command: READ FPDMA QUEUED
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: cmd 60/08:90:00:00:00/00:00:00:00:00/40 tag 18 ncq dma 4096 in
res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
09 17:43:31 Asus-R-900V kernel: ata1.00: Read log 0x10 page 0x00 failed, Emask 0x1
janv. 09 17:43:31 Asus-R-900V kernel: ata1: failed to read log page 10h (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: NCQ disabled due to excessive errors
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: exception Emask 0x1 SAct 0x1 SErr 0x0 action 0x6
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: irq_stat 0x40000001
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed command: READ FPDMA QUEUED
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq dma 4096 in
res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
09 17:43:31 Asus-R-900V kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: irq_stat 0x40000001
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed command: READ DMA
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 1 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: status: { DRDY ERR }
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: error: { ABRT }
janv. 09 17:43:31 Asus-R-900V kernel: ata1: hard resetting link
janv. 09 17:43:31 Asus-R-900V kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/0003:046D:C534.0002/input/input7
janv. 09 17:43:31 Asus-R-900V kernel: hid-generic 0003:046D:C534.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1.6/input1
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: qc timeout after 5000 msecs (cmd 0xef)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: ACPI cmd ef/90:06:00:00:00:00(SET FEATURES) failed (Emask=0x4 Stat=0x50 Err=0x01)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: revalidation failed (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1: hard resetting link
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: qc timeout after 10000 msecs (cmd 0xef)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: ACPI cmd ef/90:06:00:00:00:00(SET FEATURES) failed (Emask=0x4 Stat=0x50 Err=0x01)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: ACPI: failed the second time, disabled
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: revalidation failed (errno=-5)
janv. 09 17:43:31 Asus-R-900V kernel: ata1: limiting SATA link speed to 1.5 Gbps
janv. 09 17:43:31 Asus-R-900V kernel: ata1: hard resetting link
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: qc timeout after 15000 msecs (cmd 0xef)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: failed to set xfermode (err_mask=0x4)
janv. 09 17:43:31 Asus-R-900V kernel: ata1.00: disable device
janv. 09 17:43:31 Asus-R-900V kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
janv. 09 17:43:31 Asus-R-900V kernel: ata1: EH complete
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=32s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 0, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 1, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 2, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 3, async page read
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#19 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 0, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 1, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 2, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 3, async page read
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 0, async page read
janv. 09 17:43:31 Asus-R-900V kernel: Buffer I/O error on dev sda, logical block 1, async page read
janv. 09 17:43:31 Asus-R-900V kernel: ldm_validate_partition_table(): Disk read failed.
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 00 00 02 00 00 06 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 2 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
janv. 09 17:43:31 Asus-R-900V kernel: sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 00 00 00 02 00 00 02 00
janv. 09 17:43:31 Asus-R-900V kernel: I/O error, dev sda, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Merci
Yuusha Membre non connecté
-
- Voir le profil du membre Yuusha
- Inscrit le : 04/07/2017
- Groupes :
-
Modérateur
-
Administrateur
-
Forgeron
Si le disque n'est plus visible nulle part, je conclurai par : disque mort. Mais tu peux déjà essayer d'ouvrir le portable, de débrancher et rebrancher le disque.
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
kernel: ata1.00: NCQ disabled due to excessive errors
kernel: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
Oui, le disque à l'air mort.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
Il y a t-il un moyen de récupéré des fichiers?
Merci
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
GPE GPE :Merci de vos réponses,
Il y a t-il un moyen de récupéré des fichiers?
Merci
Il y a deux moyen, un logiciel (avec testdisk) et un matériel, chez un professionnel qui grosso-modo rachète le même disque dur neuf, démonte les deux, échange les plateaux, etc.
Si testdisk n'y arrive pas, il faut passer au service professionnel.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
si non quelle entreprise fait çà?
Merci
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
TestDisk is free software, and
comes with ABSOLUTELY NO WARRANTY.
Select a media (use Arrow keys, then press Enter):
>Disk /dev/sdb - 500 GB / 465 GiB - Samsung SSD 860 EVO 500GB
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
pour l'instant je l'ai mis au congel, vu sur un site, il peut redémarrer le temps d'extraire les données.
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
GPE GPE :pour l'instant je l'ai mis au congel, vu sur un site, il peut redémarrer le temps d'extraire les données.
Ah les bonnes vieilles recettes de grand-mère… c'est une excellente mauvaise idée d'un point de vu électronique. En plus si la vapeur a pu s'infiltrerr, elle s'est condensée, gelée. En fonction de où, elle peut exploser des composants, désouder, …
De manière général le gel est destructif.
Sort le du congel.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
je l'ai réessayer branché sur autre ordi mais c'est pareil
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
J'ai contacter l'entreprise Recoveo pour avoir un devis!
J'ai mis un nouveau disque ssd de 2 To Crucial mais le démarrage et très très long, j'ai regarder dans le journal et trouver un paragraphe en rouge mais ça me parle pas!
Caché :
janv. 12 10:39:53 Asus-R-900V systemd-coredump[7354]: [🡕] Process 6253 (DiscoverNotifie) of user 1001 dumped core.
Stack trace of thread 6253:
#0 0x00007f4a020b34bc __pthread_kill_implementation (libc.so.6 + 0x854bc)
#1 0x00007f4a02064932 raise (libc.so.6 + 0x36932)
#2 0x00007f4a03a9b6f0 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x56f0)
#3 0x00007f4a020649e0 __restore_rt (libc.so.6 + 0x369e0)
#4 0x00007f49f5277b84 _ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x19b84)
#5 0x00007f49f534c269 _ZN18PackageKitNotifier15refreshDatabaseEv (DiscoverPackageKitNotifier.so + 0x8269)
#6 0x00007f4a024d7a35 _ZN16QSingleShotTimer10timerEventEP11QTimerEvent (libQt5Core.so.5 + 0x2d7a35)
#7 0x00007f4a024c8bcd _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c8bcd)
#8 0x00007f4a0316240e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16240e)
#9 0x00007f4a0249e8f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29e8f8)
#10 0x00007f4a024f2771 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2f2771)
#11 0x00007f4a024f2f44 _ZL19timerSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5 + 0x2f2f44)
#12 0x00007f4a009b8689 g_main_context_dispatch (libglib-2.0.so.0 + 0x58689)
#13 0x00007f4a009b8a18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58a18)
#14 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#15 0x00007f4a024f3266 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f3266)
#16 0x00007f4a0249d4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d4db)
#17 0x00007f4a024a5056 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2a5056)
#18 0x00000000004071f2 main (DiscoverNotifier + 0x71f2)
#19 0x00007f4a02051737 __libc_start_call_main (libc.so.6 + 0x23737)
#20 0x00007f4a020517f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5)
#21 0x0000000000407341 _start (DiscoverNotifier + 0x7341)
Stack trace of thread 6488:
#0 0x00007f4a021257b9 syscall (libc.so.6 + 0xf77b9)
#1 0x00007f4a00a1006f g_cond_wait (libglib-2.0.so.0 + 0xb006f)
#2 0x00007f4a00983f8b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x23f8b)
#3 0x00007f4a009e4502 g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x84502)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6371:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f4a024f3266 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f3266)
#4 0x00007f4a0249d4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d4db)
#5 0x00007f4a022ca297 _ZN7QThread4execEv (libQt5Core.so.5 + 0xca297)
#6 0x00007f4a022cb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389)
#7 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#8 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6278:
#0 0x00007f4a020ae846 __futex_abstimed_wait_common (libc.so.6 + 0x80846)
#1 0x00007f4a020b0eb8 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x82eb8)
#2 0x00007f49edb70a29 cnd_wait (libgallium-25.0.7.so + 0x570a29)
#3 0x00007f49edb3ee6b util_queue_thread_func (libgallium-25.0.7.so + 0x53ee6b)
#4 0x00007f49edb70967 impl_thrd_routine (libgallium-25.0.7.so + 0x570967)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6506:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f49e66be11d dconf_gdbus_worker_thread (libdconfsettings.so + 0xb11d)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6268:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a018cfcf2 _xcb_conn_wait (libxcb.so.1 + 0xccf2)
#2 0x00007f4a018d1f4a xcb_wait_for_event (libxcb.so.1 + 0xef4a)
#3 0x00007f49ff11bc60 _ZN14QXcbEventQueue3runEv (libQt5XcbQpa.so.5 + 0x65c60)
#4 0x00007f4a022cb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6489:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8cbf g_main_loop_run (libglib-2.0.so.0 + 0x58cbf)
#3 0x00007f49f50a1616 gdbus_shared_thread_func (libgio-2.0.so.0 + 0x116616)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6264:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f4a024f3266 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f3266)
#4 0x00007f4a0249d4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d4db)
#5 0x00007f4a022ca297 _ZN7QThread4execEv (libQt5Core.so.5 + 0xca297)
#6 0x00007f4a02f8a457 _ZN22QDBusConnectionManager3runEv (libQt5DBus.so.5 + 0x17457)
#7 0x00007f4a022cb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389)
#8 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#9 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6374:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f4a009b8ae1 glib_worker_main (libglib-2.0.so.0 + 0x58ae1)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
ELF object binary architecture: AMD x86-64
janv. 12 10:39:53 Asus-R-900V systemd[1]: systemd-coredump@0-7350-0.service: Deactivated successfully.
Stack trace of thread 6253:
#0 0x00007f4a020b34bc __pthread_kill_implementation (libc.so.6 + 0x854bc)
#1 0x00007f4a02064932 raise (libc.so.6 + 0x36932)
#2 0x00007f4a03a9b6f0 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x56f0)
#3 0x00007f4a020649e0 __restore_rt (libc.so.6 + 0x369e0)
#4 0x00007f49f5277b84 _ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x19b84)
#5 0x00007f49f534c269 _ZN18PackageKitNotifier15refreshDatabaseEv (DiscoverPackageKitNotifier.so + 0x8269)
#6 0x00007f4a024d7a35 _ZN16QSingleShotTimer10timerEventEP11QTimerEvent (libQt5Core.so.5 + 0x2d7a35)
#7 0x00007f4a024c8bcd _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c8bcd)
#8 0x00007f4a0316240e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16240e)
#9 0x00007f4a0249e8f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29e8f8)
#10 0x00007f4a024f2771 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2f2771)
#11 0x00007f4a024f2f44 _ZL19timerSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5 + 0x2f2f44)
#12 0x00007f4a009b8689 g_main_context_dispatch (libglib-2.0.so.0 + 0x58689)
#13 0x00007f4a009b8a18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58a18)
#14 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#15 0x00007f4a024f3266 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f3266)
#16 0x00007f4a0249d4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d4db)
#17 0x00007f4a024a5056 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2a5056)
#18 0x00000000004071f2 main (DiscoverNotifier + 0x71f2)
#19 0x00007f4a02051737 __libc_start_call_main (libc.so.6 + 0x23737)
#20 0x00007f4a020517f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5)
#21 0x0000000000407341 _start (DiscoverNotifier + 0x7341)
Stack trace of thread 6488:
#0 0x00007f4a021257b9 syscall (libc.so.6 + 0xf77b9)
#1 0x00007f4a00a1006f g_cond_wait (libglib-2.0.so.0 + 0xb006f)
#2 0x00007f4a00983f8b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x23f8b)
#3 0x00007f4a009e4502 g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x84502)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6371:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f4a024f3266 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f3266)
#4 0x00007f4a0249d4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d4db)
#5 0x00007f4a022ca297 _ZN7QThread4execEv (libQt5Core.so.5 + 0xca297)
#6 0x00007f4a022cb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389)
#7 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#8 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6278:
#0 0x00007f4a020ae846 __futex_abstimed_wait_common (libc.so.6 + 0x80846)
#1 0x00007f4a020b0eb8 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x82eb8)
#2 0x00007f49edb70a29 cnd_wait (libgallium-25.0.7.so + 0x570a29)
#3 0x00007f49edb3ee6b util_queue_thread_func (libgallium-25.0.7.so + 0x53ee6b)
#4 0x00007f49edb70967 impl_thrd_routine (libgallium-25.0.7.so + 0x570967)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6506:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f49e66be11d dconf_gdbus_worker_thread (libdconfsettings.so + 0xb11d)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6268:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a018cfcf2 _xcb_conn_wait (libxcb.so.1 + 0xccf2)
#2 0x00007f4a018d1f4a xcb_wait_for_event (libxcb.so.1 + 0xef4a)
#3 0x00007f49ff11bc60 _ZN14QXcbEventQueue3runEv (libQt5XcbQpa.so.5 + 0x65c60)
#4 0x00007f4a022cb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6489:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8cbf g_main_loop_run (libglib-2.0.so.0 + 0x58cbf)
#3 0x00007f49f50a1616 gdbus_shared_thread_func (libgio-2.0.so.0 + 0x116616)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6264:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f4a024f3266 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f3266)
#4 0x00007f4a0249d4db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d4db)
#5 0x00007f4a022ca297 _ZN7QThread4execEv (libQt5Core.so.5 + 0xca297)
#6 0x00007f4a02f8a457 _ZN22QDBusConnectionManager3runEv (libQt5DBus.so.5 + 0x17457)
#7 0x00007f4a022cb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389)
#8 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#9 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
Stack trace of thread 6374:
#0 0x00007f4a0212064f __poll (libc.so.6 + 0xf264f)
#1 0x00007f4a009b8986 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58986)
#2 0x00007f4a009b8a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c)
#3 0x00007f4a009b8ae1 glib_worker_main (libglib-2.0.so.0 + 0x58ae1)
#4 0x00007f4a009e3ede g_thread_proxy (libglib-2.0.so.0 + 0x83ede)
#5 0x00007f4a020b19ca start_thread (libc.so.6 + 0x839ca)
#6 0x00007f4a0212d64c __clone3 (libc.so.6 + 0xff64c)
ELF object binary architecture: AMD x86-64
janv. 12 10:39:53 Asus-R-900V systemd[1]: systemd-coredump@0-7350-0.service: Deactivated successfully.
Merci
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
Je suppose que Discover est installé sur la machine en question ?
Ici on dirait que le programme DiscoverNotifier plante, mais je serais surpris que ce soit lui qui entraine un démarrage long de la machine.
Attention si l' ancien disque a été enlevé du système ( et que l' installation reste la même ( pas de reinstallation sur le nouveau disque), il y a probablement toujours une entrée liée à celui ci dans le /etc/fstab et le système peut essayer de le monter ce qui peut être une cause de ralentissement.
Après le démarrage, il faudrait lancer la commande systemd-analyze blame pour voir si un service de montage n' est pas long à s' executer.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
systemd-analyze blame
Caché :
[guy-jean@Asus-R-900V ~]$ systemd-analyze blame
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
35ms dmraid-activation.service
34ms systemd-tmpfiles-setup-dev.service
29ms mdmonitor.service
29ms systemd-fsck@dev-disk-by\x2duuid-b2d53723\x2d48bf\x2d4327\x2d8b35\x2dd12010d0e9df.service
29ms systemd-rfkill.service
28ms gssproxy.service
28ms msec.service
lines 1-50/93 47%
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
27.866s network-up.service
1.186s network.service
964ms systemd-binfmt.service
824ms mandriva-everytime.service
716ms shorewall6.service
643ms dkms-autorebuild.service
626ms nfs-server.service
371ms systemd-udev-settle.service
369ms upower.service
362ms dev-sdb9.device
319ms packagekit.service
313ms systemd-udev-trigger.service
285ms udisks2.service
276ms user@1001.service
257ms resolvconf.service
186ms cups.service
178ms proc-fs-nfsd.mount
143ms mga-bg-res.service
132ms accounts-daemon.service
106ms polkit.service
94ms systemd-journal-flush.service
89ms bluetooth.service
89ms avahi-daemon.service
84ms lvm2-monitor.service
82ms power-profiles-daemon.service
81ms systemd-udevd.service
80ms dbus.service
77ms systemd-logind.service
64ms systemd-journald.service
61ms partimaged.service
55ms rtkit-daemon.service
53ms acpid.service
50ms systemd-vconsole-setup.service
47ms systemd-tmpfiles-setup.service
46ms gpm.service
46ms dracut-shutdown.service
43ms plymouth-quit-wait.service
42ms plymouth-start.service
40ms plymouth-quit.service
39ms systemd-fsck-root.service
37ms nfs-mountd.service
36ms colord.service
36ms systemd-remount-fs.service
35ms dmraid-activation.service
34ms systemd-tmpfiles-setup-dev.service
29ms mdmonitor.service
29ms systemd-fsck@dev-disk-by\x2duuid-b2d53723\x2d48bf\x2d4327\x2d8b35\x2dd12010d0e9df.service
29ms systemd-rfkill.service
28ms gssproxy.service
28ms msec.service
lines 1-50/93 47%
le fstab je l'ai contrôlé et rien de l'ancien
Merci
Édité par GPE GPE Le 13/01/2026 à 10h50
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie