I'm going to have to say no on this. It would be inappropriate to try
and pretend a formatted partition is the same as the existing one.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Similar problem here, I've got a Windows partition that I rarely boot
into, a home partition, a root partition with Gutsy that I've been using
all the time and another root partition that had was Hardy, now
Intrepid. After installing Intrepid, I got the fsck message during boot:
fsck.ext3:
I'm not sure what you mean by compatibility problems with the upcoming
ext4 filesystem. You will get better performance if you remake the
filesystem as ext4 from the beginning as opposed to converting an
existing ext3 filesystem to ext4, but the latter certainly works.
Also, note that that use
Theodore, I stand corrected! I got the impression that converting an
ext3 partition with 128-byte inodes to ext4 would be extremely
challenging if at all possible and the statement reflects that.
Alan
--
[gutsy] Don't change UUID of existing ext3 partition when formatting it for
install
I have this problem too, but i am installing on my three partition Gutsy
only. First partition is in any case all right, but Gutsy on second
partition, after installation Gutsy on third partition, reports fsck
died with exit status 8 (see above).
--
[gutsy] Don't change UUID of existing ext3
I also have this problem.
I have a testing and a stable install of Ubuntu. I have Gutsy installed
on most of my HD. It booted up correctly every time. Last night I
installed Hardy Alpha 2 onto the testing partition and left all of the
Gutsy partitions alone. From then onwards, Gutsy stalls on
If I understand correctly I have a similar but different problem.
I had feisty installed on /dev/sda1. Then I installed gutsy tribe-5 in
/dev/sda5. During the installation I removed the existing swap partition
and made a new (bigger) one. Then I created a new partition for gutsy
and it installed.
Hi again, I just wanted to add that if I can help testing any fix you
come up with, I'll try my best to do it.
For example, if it's needed I can happily erase Gutsy and Feisty in my
machine and reinstall both, to try any fix for the interrupted boot
process in Feisty after a Gutsy install (as I
** Changed in: ubiquity (Ubuntu)
Sourcepackagename: None = ubiquity
--
[gutsy] Don't change UUID of existing ext3 partition when formatting it for
install
https://bugs.launchpad.net/bugs/132762
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
