Bug 861812

Created attachment 619511 [details]
File: ifcfg.log

Created attachment 619512 [details]
File: anaconda-tb

Created attachment 619513 [details]
File: product

Created attachment 619514 [details]
File: type

Created attachment 619515 [details]
File: environ

Created attachment 619516 [details]
File: storage.log

Created attachment 619517 [details]
File: version

Created attachment 619518 [details]
File: program.log

Created attachment 619519 [details]
File: anaconda.log

Created attachment 619520 [details]
File: syslog

Created attachment 619521 [details]
File: hashmarkername

Created attachment 619522 [details]
File: packaging.log

Created attachment 619523 [details]
File: cmdline_file

Created attachment 619524 [details]
File: release

Created attachment 619525 [details]
File: description

What steps did take that resulted in this traceback?

Not quite sure, I was at the partition step of Fedora 18 alpha, and when I changed the size of a partition or told it to propose an automatic configuration, this happened. I noticed that it happened more frequently when all space on the harddisk was occupied with partitions.

*** Bug 862109 has been marked as a duplicate of this bug. ***

Hello,

Bug 862109 that I reported (marked as duplicate) shows the same symptoms but may be slightly different, or could help you find the cause.

As trustthesky said, this bug occured when he tried to change the size of a partition. I did not even had the chance to see the partition editor, the bug occured as soon as I chose the language for the installation program.

I can help giving info if needed.

Thanks

trustthesky, you are getting bit by a bug. I should be able to get it fixed in time for the Beta.

yach, your ntfs partition (sdc1) is broken. The partition size (61054MB) is 700MB smaller than the minimum possible size (61783MB) reported by ntfsresize. Basically, it looks like you shrunk the partition too much and now the filesystem is in some inconsistent state. There's nothing the Fedora installer can do to help you with this.

Hi David,

Thanks for the reply.
However, I guess there is another problem than the partition size which is already more than 61783 MB (or I am missing something, which is quite possible) :

[yach@cortina ~]$ sudo ntfsresize /dev/sdc1 
ntfsresize v2012.1.15 (libntfs-3g)
Device name        : /dev/sdc1
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 64020804096 bytes (64021 MB)
Current device size: 64020807680 bytes (64021 MB)
New volume size    : 64020804096 bytes (64021 MB)
Nothing to do: NTFS volume size is already OK.
[yach@cortina ~]$ 

I tried this (running fedora 17) then booted on the USB key (fedora 18 nightly) but had the same :
[yach@cortina ~]$ sudo ntfsfix /dev/sdc1 
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
NTFS partition /dev/sdc1 was processed successfully.
[yach@cortina ~]$

What should I do to give further valuable information ?
Thanks a lot !

(In reply to comment #21)
> Hi David,
> 
> Thanks for the reply.
> However, I guess there is another problem than the partition size which is
> already more than 61783 MB (or I am missing something, which is quite
> possible) :
> 
> [yach@cortina ~]$ sudo ntfsresize /dev/sdc1 
> ntfsresize v2012.1.15 (libntfs-3g)
> Device name        : /dev/sdc1
> NTFS volume version: 3.1
> Cluster size       : 4096 bytes
> Current volume size: 64020804096 bytes (64021 MB)
> Current device size: 64020807680 bytes (64021 MB)
> New volume size    : 64020804096 bytes (64021 MB)
> Nothing to do: NTFS volume size is already OK.
> [yach@cortina ~]$ 

I think I see the problem. ntfsresize is reporting sizes in megabytes, whereas everything else in the installer reports sizes in mebibytes.

anaconda-18.13-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.13-1.fc18

Thanks for the quick bugfix !

I'd like to try it, but as this is in the installer, I guess I should play with kickstart.

I was able to create an ISO with livecd-creator (using the nightly kickstart file), but I don't know how to replace the anaconda version in the repos with the one that you built. Is there some way ?

anaconda-18.14-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.14-1.fc18

Package anaconda-18.14-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.14-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15707/anaconda-18.14-1.fc18
then log in and leave karma (feedback).

yach: the fix should be in all the most recent Beta TCs. could you try with one (the latest is TC7) and let us know? Thanks!

Hi there,

The fix works like a charm :)
This bug can be claused as far as I'm concerned.

Thanks a lot !
Yach

I forgot to add that I tested it with beta TC8.

Thanks! Closing, as something much newer than the fix for this has been pushed.