Comment 1 for bug 903948

Ok, the error message from Ubiquity is still present with a different SSD, so it's probably not that. The error reads:

The installer encountered an error copying files to the hard disk:

[Errno 5] Input/Output error

Syslog shows this:

Dec 13 21:18:02 ubuntu : INFO: Simulating trans: /org/debian/apt/transaction/95d6ad71d8414fbbbcd7b91c8cd23a9b
Dec 13 21:18:03 ubuntu : INFO: Upgrade system with safe mode: 1
Dec 13 21:21:05 ubuntu kernel: [ 325.143313] SQUASHFS error: zlib_inflate error, data probably corrupt
Dec 13 21:21:05 ubuntu kernel: [ 325.143326] SQUASHFS error: squashfs_read_data failed to read block 0x27c34a9d
Dec 13 21:21:05 ubuntu kernel: [ 325.143334] SQUASHFS error: Unable to read fragment cache entry [27c34a9d]
Dec 13 21:21:05 ubuntu kernel: [ 325.143340] SQUASHFS error: Unable to read page, block 27c34a9d, size 8672
Dec 13 21:21:05 ubuntu kernel: [ 325.143356] SQUASHFS error: Unable to read fragment cache entry [27c34a9d]
Dec 13 21:21:05 ubuntu kernel: [ 325.143362] SQUASHFS error: Unable to read page, block 27c34a9d, size 8672
Dec 13 21:21:05 ubuntu kernel: [ 325.143376] SQUASHFS error: Unable to read fragment cache entry [27c34a9d]
Dec 13 21:21:05 ubuntu kernel: [ 325.143381] SQUASHFS error: Unable to read page, block 27c34a9d, size 8672
Dec 13 21:21:05 ubuntu kernel: [ 325.143390] SQUASHFS error: Unable to read fragment cache entry [27c34a9d]
Dec 13 21:21:05 ubuntu kernel: [ 325.143396] SQUASHFS error: Unable to read page, block 27c34a9d, size 8672
Dec 13 21:21:05 ubuntu kernel: [ 325.143410] SQUASHFS error: Unable to read fragment cache entry [27c34a9d]
Dec 13 21:21:05 ubuntu kernel: [ 325.143416] SQUASHFS error: Unable to read page, block 27c34a9d, size 8672
Dec 13 21:21:05 ubuntu kernel: [ 325.143426] SQUASHFS error: Unable to read fragment cache entry [27c34a9d]
Dec 13 21:21:05 ubuntu kernel: [ 325.143432] SQUASHFS error: Unable to read page, block 27c34a9d, size 8672

I have complete logs but it's probably not worth attaching them unless requested, at this point it's either networking or memory corruption. I'll test for both and update further.