fsck errors prevent F17 install?

[mps2006]

Hi,

I can't install F17 from the livecd as part way through it fails with an fsck error and forces a reboot. I reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=823140

Wondering if anyone else has the same issue? F16 installs fine on the same computer.

There are a couple of threads with similar issues with F16 but there doesn't seem to have been a clear resolution.

Any ideas?

thanks
M.

[gurutech]

Have you tried installing F16, then following up with a "yum install preupgrade" to upgrade to F17?

[Fenrin]

this also happens when BIOS time is far different from OS time. Make sure the time of both is correct.

[george_toolan]

Please e2fsck your file systems before you try to install

kernel: [ 524.074407] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended

Verify the F17 image and then try to burn it to a real cd or dvd or at least use a different usb drive, because there are a lot of read errors on the livecd (loop3) device

[ 605.747819] SQUASHFS error: xz_dec_run error, data probably corrupt
[ 605.747828] SQUASHFS error: squashfs_read_data failed to read block 0x12ce04e0
[ 605.747868] Buffer I/O error on device loop3, logical block 332992

Installation fails, because the journal has suddenly disappeared

[ 608.543182] JBD2: no valid journal superblock found
[ 608.543186] EXT4-fs (dm-3): error loading journal

Btw is this an encrypted file system or why does it keep saying... ?

udisksd[1182]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4)

Maybe you should check your memory with Memtest86+?

[mps2006]

Thanks for the hints. A combination of fsck-ing the data disk and using a different usb key did the trick.