Ubiquity crashed downgrading from 11.10 to 11.04

[Hugo Melo]

As the interface didn't show me a place to attach the files I am pasting syslog here and attaching the partman..
It seems to be easy to solve. The if not os.path.isdir(targetpath) returns True. It would verify for os.path.exists(targetpath).

Nov 1 00:08:30 ubuntu ubiquity: mkdir: cannot create directory `/target/var/lock'
Nov 1 00:08:30 ubuntu ubiquity: : File exists
Nov 1 00:08:30 ubuntu ubiquity:
Nov 1 00:08:30 ubuntu ubiquity: mkdir: cannot create directory `/target/var/run'
Nov 1 00:08:30 ubuntu ubiquity: : File exists
Nov 1 00:08:30 ubuntu kernel: [ 517.321974] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
Nov 1 00:08:31 ubuntu ubiquity[4725]: debconffilter_done: ubiquity.components.partman_commit (current: None)
Nov 1 00:08:31 ubuntu install.py: keeping packages due to preseeding: icedtea6-plugin openoffice.org
Nov 1 00:08:31 ubuntu install.py: keeping language packs for: en
Nov 1 00:08:33 ubuntu ubiquity: /usr/lib/python2.7/dist-packages/apt/deprecation.py:96: UserWarning: Deprecated parameter 'autoFix'
Nov 1 00:08:33 ubuntu ubiquity: warnings.warn("Deprecated parameter %r" % key)
Nov 1 00:12:25 ubuntu install.py: Exception during installation:
Nov 1 00:12:25 ubuntu install.py: Traceback (most recent call last):
Nov 1 00:12:25 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 610, in <module>
Nov 1 00:12:25 ubuntu install.py: install.run()
Nov 1 00:12:25 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 124, in run
Nov 1 00:12:25 ubuntu install.py: self.copy_all()
Nov 1 00:12:25 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 362, in copy_all
Nov 1 00:12:25 ubuntu install.py: os.mkdir(targetpath, mode)
Nov 1 00:12:25 ubuntu install.py: OSError: [Errno 17] File exists: '/target/var/lock'
Nov 1 00:12:25 ubuntu install.py:
Nov 1 00:17:03 ubuntu CRON[24344]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

[Hugo Melo (hugo-melo)]

Now the full syslog file.

[Brian Murray (brian-murray)]

I'm marking this as a duplicate of bug 891711 which has some detailed information regarding the issue. We are currently looking into ways to recover your system from this scenario so keep an eye on bug 891711 for those steps.