What the bot is referring to, I think, is that your disk seems to be
failing. So the disk probably needs replacing before proceeding
further...

[  345.930284] ata1.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 0x0
[  345.930287] ata1.00: irq_stat 0x40000008
[  345.930290] ata1.00: failed command: READ FPDMA QUEUED
[  345.930295] ata1.00: cmd 60/40:68:d8:aa:c5/00:00:6f:00:00/40 tag 13 ncq dma 
32768 in
                        res 41/40:00:d8:aa:c5/00:00:6f:00:00/40 Emask 0x409 
(media error) <F>
[  345.930297] ata1.00: status: { DRDY ERR }
[  345.930299] ata1.00: error: { UNC }
[  345.942704] ata1.00: configured for UDMA/133
[  345.942714] sd 0:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[  345.942717] sd 0:0:0:0: [sda] tag#13 Sense Key : Medium Error [current] 
[  345.942718] sd 0:0:0:0: [sda] tag#13 Add. Sense: Unrecovered read error - 
auto reallocate failed
[  345.942721] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 6f c5 aa d8 00 00 
40 00
[  345.942722] print_req_error: I/O error, dev sda, sector 1875225304
[  345.942742] ata1: EH complete
[  378.838106] ata1.00: exception Emask 0x0 SAct 0x4000003f SErr 0x0 action 0x6 
frozen
[  378.838111] ata1.00: failed command: READ FPDMA QUEUED
[  378.838116] ata1.00: cmd 60/08:00:b8:dd:b8/00:00:64:00:00/40 tag 0 ncq dma 
4096 in
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  378.838118] ata1.00: status: { DRDY }
[  378.838120] ata1.00: failed command: WRITE FPDMA QUEUED
[  378.838124] ata1.00: cmd 61/08:08:68:f0:3a/00:00:62:00:00/40 tag 1 ncq dma 
4096 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  378.838126] ata1.00: status: { DRDY }
[  378.838128] ata1.00: failed command: WRITE FPDMA QUEUED
[  378.838132] ata1.00: cmd 61/08:10:80:f0:3a/00:00:62:00:00/40 tag 2 ncq dma 
4096 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  378.838134] ata1.00: status: { DRDY }
[  378.838135] ata1.00: failed command: WRITE FPDMA QUEUED
[  378.838140] ata1.00: cmd 61/08:18:b0:f0:3a/00:00:62:00:00/40 tag 3 ncq dma 
4096 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  378.838141] ata1.00: status: { DRDY }
[  378.838143] ata1.00: failed command: WRITE FPDMA QUEUED
[  378.838147] ata1.00: cmd 61/08:20:28:f1:3a/00:00:62:00:00/40 tag 4 ncq dma 
4096 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  378.838149] ata1.00: status: { DRDY }
[  378.838151] ata1.00: failed command: READ FPDMA QUEUED
[  378.838155] ata1.00: cmd 60/20:28:00:26:ca/00:00:64:00:00/40 tag 5 ncq dma 
16384 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  378.838157] ata1.00: status: { DRDY }
[  378.838159] ata1.00: failed command: READ FPDMA QUEUED
[  378.838163] ata1.00: cmd 60/08:f0:d8:aa:c5/00:00:6f:00:00/40 tag 30 ncq dma 
4096 in
                        res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4 
(timeout)
[  378.838165] ata1.00: status: { DRDY }

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782145

Title:
  package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed
  gdm3 package pre-removal script subprocess returned error exit status
  10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to