Thank you for taking the time to report this issue and helping to make Ubuntu better.
Jan 15 00:53:52 ubuntu kernel: [ 146.529219] ata1.00: NCQ disabled due to excessive errors Jan 15 00:53:52 ubuntu kernel: [ 146.529222] ata1.00: exception Emask 0x0 SAct 0x8000000 SErr 0x50000 action 0x6 frozen Jan 15 00:53:52 ubuntu kernel: [ 146.529225] ata1: SError: { PHYRdyChg CommWake } Jan 15 00:53:52 ubuntu kernel: [ 146.529227] ata1.00: failed command: READ FPDMA QUEUED Jan 15 00:53:52 ubuntu kernel: [ 146.529230] ata1.00: cmd 60/b8:d8:68:c0:e7/00:00:0e:00:00/40 tag 27 ncq dma 94208 in Jan 15 00:53:52 ubuntu kernel: [ 146.529230] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 15 00:53:52 ubuntu kernel: [ 146.529231] ata1.00: status: { DRDY } Jan 15 00:53:52 ubuntu kernel: [ 146.529234] ata1: hard resetting link Jan 15 00:53:52 ubuntu kernel: [ 146.843683] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 15 00:53:52 ubuntu kernel: [ 146.844733] ata1.00: configured for UDMA/133 Jan 15 00:53:52 ubuntu kernel: [ 146.844759] ata1.00: device reported invalid CHS sector 0 Jan 15 00:53:52 ubuntu kernel: [ 146.844767] sd 0:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jan 15 00:53:52 ubuntu kernel: [ 146.844769] sd 0:0:0:0: [sda] tag#27 Sense Key : Illegal Request [current] Jan 15 00:53:52 ubuntu kernel: [ 146.844770] sd 0:0:0:0: [sda] tag#27 Add. Sense: Unaligned write command Jan 15 00:53:52 ubuntu kernel: [ 146.844772] sd 0:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 0e e7 c0 68 00 00 b8 00 Jan 15 00:53:52 ubuntu kernel: [ 146.844773] print_req_error: I/O error, dev sda, sector 250069096 flags 80700 I notice many drive issues, as such I suggest you validate the health of your hardware (esp. disk by checking it's SMART status using `smartctl`, `gnome-disks` or whichever tool you prefer), and possibly the integrity of your partition table. If you're unfamiliar with these, I suggest seeking looking up refer to https://discourse.ubuntu.com/t/finding- help/709 If the device is a SD card, or device without SMART logs & diagnostics thus you'll need to test it using script or other means. I've marked this bug as incomplete (due hardware issues), if you believe I'm in error please leave a comment as to why, and you can return the status to "New". ** Changed in: grub-installer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859735 Title: I am trying to install on a surface pro 3. and it quits about 3/4 away thru. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1859735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs