Hide Forgot
Description of problem: Installation from live KDE CD fails with the error message: Ext4 filesystem check failure on /dev/mapper/VolGroup-lv_root File system, errors left uncorrected. Errors like this usually mean there is a problem with the filesystem that will requiere user interaction to repair. Before restarting installation, reboot to rescue mode or another system that allows you to repair the filesystem interactively. Restart installation after you have corrected the problems on the filesystem. Version-Release number of selected component (if applicable): Fedora-15-x86_64-Live-KDE.iso and Fedora-16-Beta-x86_64-Live-KDE.iso Both MD5 sum fine and burn well. How reproducible: Every time with installing from live CD (KDE x86_64) Steps to Reproduce: 1. Installing 2. no matter which FS options choosen 3. INstall stops with above message Actual results: Unable to boot installed system, mount /boot from the Live Image shows no kernel/etc has been installed Expected results: Additional info: Laptop is new HP 625 P360 1GB 320GB HD4200 Linux (XN835EA) - installed 4 GB RAM in addition which are by BIOS detected and by the Fedora live CD. Didn't wanted the preinstalled Suse Enterprise Edition.
We only run the filesystem check if you opt to resize that device/filesystem. You can either fix the filesystem from outside the installer (man e2fsck) or you can choose some action other than to resize that device.
Hello David, I ran from a terminal in the live CD after the installation broke once again with the above error: $ su - # vgscan # vgchange -ay # e2fsck -vvv -f /dev/mapper/VolGroup-lv_root The only error that was detected and corrected was due to a date for filesystem check in the future. I changed the system date to the actual. Still the installation fails with the same error message, If I mount /dev/sda1 (whhich shows zero errors with e2fsck) (should be /boot) afterwards to /mnt, there is just lost+found visible? Thx for the fast message, but this seems not the solution. ;-( Best regards Michael
Installation worked fine now, for whatever reason Anaconda had copied /boot directly on VolGroup-lv_root! Now used the BIOS provided HP Disc Sanitizer to clean the disc from everything and in addition simply under manual FS layout settings resized swap slightly, so a fsck was performed, whatever of both was the issue? Thx for the help and hopefully the entry helps others with the them problem. Best regards Michael
I'm getting exactly this same problem with the Fedora-16-x86_64-Live-KDE.iso The burnt media checks out fine, as do the two hard disks I've tried to install it on (one of these previously had Fedora 15 on it, the other Windows XP.) I've tried using various disk utils to wipe them and format to EXT4 but still get the same error.
Gents, I too have had a failure using F16 KDE live on a USB stick. I don't really think that CLOSED NOTABUG is the correct resolution for this one. Is there a fixed version of anaconda available, please? If so, I could load it having booted the live F16. Cheers.
Well, using a FC13 KDE live USb stick to install seems to work ok. It does all the partitioning and creation of ext4 filing systems without complaint. It is then possible to use preupgrade to go from fc13 to fc15. haven't dared try fc16 yet! So, I think that there genuinely be a problem with the anaconda in fc16. Please can this bug be re-opened?