I'm afraid it looks like it was right. The syslog has this kind of stuff in it:
Jan 22 12:59:09 ubuntu kernel: [ 603.807017] ata1.00: exception Emask 0x0 SAct 0xe SErr 0x0 action 0x6 frozen Jan 22 12:59:09 ubuntu kernel: [ 603.807025] ata1.00: failed command: WRITE FPDMA QUEUED Jan 22 12:59:09 ubuntu kernel: [ 603.807033] ata1.00: cmd 61/00:08:00:ad:c5/04:00:2e:00:00/40 tag 1 ncq 524288 out Jan 22 12:59:09 ubuntu kernel: [ 603.807035] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 22 12:59:09 ubuntu kernel: [ 603.807039] ata1.00: status: { DRDY } Jan 22 12:59:09 ubuntu kernel: [ 603.807042] ata1.00: failed command: WRITE FPDMA QUEUED Jan 22 12:59:09 ubuntu kernel: [ 603.807048] ata1.00: cmd 61/00:10:00:b1:c5/04:00:2e:00:00/40 tag 2 ncq 524288 out Jan 22 12:59:09 ubuntu kernel: [ 603.807050] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 22 12:59:09 ubuntu kernel: [ 603.807053] ata1.00: status: { DRDY } Jan 22 12:59:09 ubuntu kernel: [ 603.807056] ata1.00: failed command: WRITE FPDMA QUEUED Jan 22 12:59:09 ubuntu kernel: [ 603.807063] ata1.00: cmd 61/00:18:00:b5:c5/04:00:2e:00:00/40 tag 3 ncq 524288 out Jan 22 12:59:09 ubuntu kernel: [ 603.807065] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 22 12:59:09 ubuntu kernel: [ 603.807068] ata1.00: status: { DRDY } Jan 22 12:59:09 ubuntu kernel: [ 603.807074] ata1: hard resetting link Jan 22 12:59:19 ubuntu kernel: [ 613.813470] ata1: softreset failed (device not ready) Jan 22 12:59:19 ubuntu kernel: [ 613.813477] ata1: hard resetting link Jan 22 12:59:29 ubuntu kernel: [ 623.819943] ata1: softreset failed (device not ready) Jan 22 12:59:29 ubuntu kernel: [ 623.819950] ata1: hard resetting link Jan 22 12:59:39 ubuntu kernel: [ 634.386108] ata1: link is slow to respond, please be patient (ready=0) Jan 22 13:00:04 ubuntu kernel: [ 658.844603] ata1: softreset failed (device not ready) Jan 22 13:00:04 ubuntu kernel: [ 658.844612] ata1: limiting SATA link speed to 1.5 Gbps Jan 22 13:00:04 ubuntu kernel: [ 658.844616] ata1: hard resetting link Jan 22 13:00:07 ubuntu kernel: [ 661.687027] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 22 13:00:07 ubuntu kernel: [ 661.707435] ata1.00: configured for UDMA/133 Jan 22 13:00:07 ubuntu kernel: [ 661.723016] ata1.00: device reported invalid CHS sector 0 Jan 22 13:00:07 ubuntu kernel: [ 661.723024] ata1.00: device reported invalid CHS sector 0 Jan 22 13:00:07 ubuntu kernel: [ 661.723031] ata1.00: device reported invalid CHS sector 0 Jan 22 13:00:07 ubuntu kernel: [ 661.723041] ata1: EH complete Jan 22 13:04:22 ubuntu kernel: [ 916.460873] EXT4-fs error (device sda5): ext4_lookup:1044: inode #2: comm install.py: deleted inode referenced: 6291457 Jan 22 13:04:22 ubuntu kernel: [ 916.460884] Aborting journal on device sda5-8. Jan 22 13:04:22 ubuntu kernel: [ 916.461381] EXT4-fs (sda5): Remounting filesystem read-only ... which is a clear sign of a lower-level problem. It may not be heat; perhaps the hard drive is dying. At any rate, the installer couldn't do any more than notifying you of the problem, and this isn't an installer bug. ** Changed in: ubiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919989 Title: ubunt6u did not install alongside windows correctly, hard drive issue apparently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/919989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs