Comment 5 for bug 1367064

Short answer: sorry, Christopher, I cannot bissect on this machine. I have a couple of other machines that are misbehaving after the 14.04 "upgrade" and I will probably file a report against them, with the extra steps.

Longer answer: This is a production critical machine (family storage). When I did the "upgrade", I took a necessary risk, exported (ZFS) all the storage pools, carefully disconnected all hard drives in the pool from the machine, imported a non-critical pool into a working 14.04 machine and made sure 14.04 can mount the pool and access the datasets. Then I went about installing and diagnosing 14.04 on this machine. After determining that the NOMODESET workaround works, I reconnected all hard drives, reimported all pools, and closed the box. I will not reopen the box until the next scheduled hard disks replacement or until an accident happens. I made a note in the server's logbook, so in case I reopen the box I will make sure I have a spare harddrive and some time to test.