5th test http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
6th test http://www.asus.com/Motherboards/M2NVM_DVI/ I found the problem: A program tested before ubiquity left cruft in /etc/mtab, which was not seen by df, and not affecting terminal window commands (umount and swapoff), but it was affecting ubiquity. This is a very special case. Running various programs, and checking that /etc/mtab is clean (matching the output of df), makes it possible to install into this same computer (as in tests #1-4) with a USB 3 HDD, as well as installing into another computer's internal HDD. So we can give this bug very low priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373365 Title: Ubiquity got stuck at 'Identifying file system...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1373365/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
