Trouble trying to boot from live cd

[geekusprimus]

Hi, guys! I'm trying to set up a dual-boot for Windows 10 and Kubuntu 17.10.1 on my computer. However, when I try to boot from my DVD drive, I get the following errors as the live disk tries to load:

[    5.348339] nouveau 0000:01:00.0: bus: MMIO write of 8000012c FAULT at 10eb14 [ IBUS ]
[  37.904884] ata7.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
[  37.904891] ata7: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommMake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[  37.904896] ata7.00: failed command: IDENTIFY PACKET DEVICE
[  37.904900] ata7.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 4 pio 512 in
[  37.904900]           res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
[  37.904905] ata7.00: status: { DRDY }

It looks like it's a drive error of some kind, so if it's any help, here's what I've got:
A 128 GB SSD holding my Windows install in SATA3 port A0
A 512 GB SSD with no partitions (the intended destination for the Kubuntu installation) in SATA3 port A1
A DVD drive in SATA2 port 0
A 2 TB hard disk drive in SATA2 port 1

Thanks for any help you can offer!

EDIT: Some additional information, in case it may be useful. I'm running a 3rd generation Intel Core i5, an NVidia GTX 970, and 16 GB of RAM on an ASRock Z77 Extreme4 motherboard.

[jglen490]

Did you verify the sha256 sum on the ISO downloaded image before burning it?

If the DVD drive otherwise has no other issues, then it may be a download problem.

[geekusprimus]

I just verified the checksum on the downloaded ISO, and I verified the integrity of the DVD when I burned it.

[Bings]

You could try burning the iso to a usb stick/pen drive. It'll be quicker to run, less prone to errors than burning a DVD and also you can just wipe the thing after and reuse it.

[jglen490]

Hi, guys! I'm trying to set up a dual-boot for Windows 10 and Kubuntu 17.10.1 on my computer. However, when I try to boot from my DVD drive, I get the following errors as the live disk tries to load:

[    5.348339] nouveau 0000:01:00.0: bus: MMIO write of 8000012c FAULT at 10eb14 [ IBUS ]
[  37.904884] ata7.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
[  37.904891] ata7: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommMake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[  37.904896] ata7.00: failed command: IDENTIFY PACKET DEVICE
[  37.904900] ata7.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 4 pio 512 in
[  37.904900]           res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
[  37.904905] ata7.00: status: { DRDY }

It looks like it's a drive error of some kind, so if it's any help, here's what I've got:
A 128 GB SSD holding my Windows install in SATA3 port A0
A 512 GB SSD with no partitions (the intended destination for the Kubuntu installation) in SATA3 port A1
A DVD drive in SATA2 port 0
A 2 TB hard disk drive in SATA2 port 1

Thanks for any help you can offer!

EDIT: Some additional information, in case it may be useful. I'm running a 3rd generation Intel Core i5, an NVidia GTX 970, and 16 GB of RAM on an ASRock Z77 Extreme4 motherboard.

What software did you use to burn the ISO?

[geekusprimus]

I burned the ISO to the DVD using the standard Windows burning software. I also tried Rufus to create a bootable USB, but I got the same errors as the DVD.

[jglen490]

I did some research (Google is your friend) about the DRDY statement with respect to ata, and it seems like there may be an error with the kernel's device driver. In this case that would be the Linux kernel on the live DVD and the kernel module for your DVD drive. There may be a way around that by changing some boot parameters when the live DVD presents the main screen where you choose to boot into the installer, or verify the DVD image, and other options.

I don't have a solution, but hang in there and someone with more experience with the live DVD boot parameters may have some recommendations. I'd be throwing jello at the wall ...

[geekusprimus]

I know that 17.10 isn't a long-term support release, so would it be worth it to try 16.04 and see if that is a little more compatible?

[mr_raider]

Can you list your full hardware specs, including mobo.

[geekusprimus]

I listed them above, but I'll be more specific:
Storage and Drives:
Samsung 840 Pro 128 GB SSD on SATA3 port A0
SanDisk Ultra 3D 512 GB SSD on SATA3 port A1
TSSTcorp DVD drive on SATA2 port 0
Western Digital 2 TB 7200 RPM HDD on SATA2 port 1
Memory: 16 GB G.Skill DDR3
Processor: Intel Core i5-3570K
Graphics Card: EVGA NVidia GTX 970
Sound Card: ASUS Xonar DG
Wifi: Realtek RTL8190 802.11n
Motherboard: ASRock Z77 Extreme4, circa 2013

[jglen490]

I*'m thinking it may be related to booting under UEFI, which may require changing some settings in the UEFI configuration screen. And I definitely have zero experience with UEFI mobos, even though the rest of your hardware looks to be non-problematic. You may get a better response by posting this in the 17.10 forum.

[geekusprimus]

I've already checked. My PC is booting under a traditional BIOS.

[Snowhog]

I burned the ISO to the DVD using the standard Windows burning software. I also tried Rufus to create a bootable USB, but I got the same errors as the DVD.

It is always possible that the media; the DVD discs; you are using aren't up to snuff. What brand of DVD Discs are you using?

[geekusprimus]

I don't have the discs on me right now, so I can't say what brand they were. However, I tried to install it with a USB 3.0 Samsung flash drive and got the exact same error message. My research online suggests it might be an issue with how my drives are set up on my motherboard, but it would be nice to get a confirmation of the issue before I start haphazardly moving where everything is plugged in.

[jglen490]

When I was looking at some posts on various forums with problems related to yours, there were indications that moving the DVD drive among different SATA connections SOMETIMES fixed the problem, but who knows what combination might actually work.

How about BIOS updates? (I know it's UEFI, but whatever the correct mobo firmware is called)