After upgrading of a working Jaunty to Karmic final, it would not boot into the system and instead hang in the initramdisk. I did NOT yet upgrade to ext4 or grub2.
Booting with safe mode reveals that it could not find my main partition (which contains my now Karmic installation).
Booting into a second karmic system on the sda2 reveals that sda1 is indeed not visible any more:
$ ls -la /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 80 Oct 30 09:22 .
drwxr-xr-x 6 root root 120 Oct 30 09:22 ..
lrwxrwxrwx 1 root root 10 Oct 30 09:22 500a11a1-86bd-4609-96ca-78797dfb772b -> ../../sda5
lrwxrwxrwx 1 root root 10 Oct 30 09:22 b17e1aff-9f02-4fbd-81e5-9b1e6899baad -> ../../sda2
Nevertheless, I can mount my main partition when I directly mount /dev/sda1 from the second installation, so the filesystem is intact.
When I start "Palimpsest", it should my first partition as "54 GB unrecognized", which is a bit startling.
After upgrading of a working Jaunty to Karmic final, it would not boot into the system and instead hang in the initramdisk. I did NOT yet upgrade to ext4 or grub2.
Booting with safe mode reveals that it could not find my main partition (which contains my now Karmic installation).
Booting into a second karmic system on the sda2 reveals that sda1 is indeed not visible any more:
$ ls -la /dev/disk/by-uuid 86bd-4609- 96ca-78797dfb77 2b -> ../../sda5 9f02-4fbd- 81e5-9b1e6899ba ad -> ../../sda2
total 0
drwxr-xr-x 2 root root 80 Oct 30 09:22 .
drwxr-xr-x 6 root root 120 Oct 30 09:22 ..
lrwxrwxrwx 1 root root 10 Oct 30 09:22 500a11a1-
lrwxrwxrwx 1 root root 10 Oct 30 09:22 b17e1aff-
Nevertheless, I can mount my main partition when I directly mount /dev/sda1 from the second installation, so the filesystem is intact.
When I start "Palimpsest", it should my first partition as "54 GB unrecognized", which is a bit startling.