Partition Manager errors while installing Asus EEE series 900

[Manoj Iyer]

Installing Asus EEE 900 with Ubuntu Jaunty Alpha5 from USB disk.

- The installer get to the "Prepare disk Space". I picked the default "Use the entire disk"
- It got to the "Installing System" screen and reported an error "Error informing the kernel about modifications to paritition /dev/sda2 -- Device or Resource busy (see attached screen shot for full message).
- I clicked on *ignore* and it made some progress and reported another error, similar to the one above, about /dev/sda5.
- I clicked on *ignore* and it said "partitions formatting", at this point it was stuck on 5% for a long time, for filesystem /
- Then I got a message "Do you want to resume partitioning ?" The attempt to mount a filesystem with type swap in scsi2, parition #5 at none failed.
- I clicked on continue and it brought me back to Prepare disk space menu.
- I clicked on forward.
- It showed me the 2 errors I saw previously but this time I clicked on *cancel* and the install made progress.
- The installer then was able to install the machine, and reboot to login prompt with no problems.

Please find attached screen shots of the errors reported during install.

[Paul Larson (pwlars)]

Confirmed in Alpha6 and in daily builds as recently as Mar 16, 2009

[Paul Larson (pwlars)]

scratch that, I read this wrong. I'm not seeing this bug at all, but a different one. This one does not reproduce currently, at least on my eee900.

[Colin Watson (cjwatson)]

This is essentially bug 340188, by the looks of things, and we believe that this class of problems has now been entirely cleared up. If you (Manoj) can reproduce this with beta or later, please unduplicate this bug and let me know; anyone else, please file a separate bug as it's very easy to confuse multiple issues here.

(By the way, please don't attach PDFs full of screenshots. Screenshots are occasionally useful, but it's better to have them as separate attachments rather than as a big 10MB blob; and in any case what we really need are logs. Running 'ubuntu-bug -p ubiquity' in the live environment after any installer crash with the desktop CD will give us all the information we need.)