Hi Mike, 1) You didn't actually demonstrate e2label/dumpe2fs etc. crashing after you reinstalled e2fslibs. Did it?
2) Looks like hdd has serious hardware errors; look at dmesg. So that could very easily be causing your problems: [ 2696.303287] hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } [ 2696.303302] hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=31533912, sector=31533759 [ 2696.303316] ide: failed opcode was: unknown [ 2696.303325] end_request: I/O error, dev hdd, sector 31533759 [ 3505.083582] hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } [ 3505.083597] hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=27509655, sector=27509647 [ 3505.083611] ide: failed opcode was: unknown [ 3505.083620] end_request: I/O error, dev hdd, sector 27509647 These hardware errors could have corrupted the e2fslibs binary causing the FPE failures, or the hardware errors could have caused ext2fs_open to fail, etc. So you rather desparately need to get your hard drive backed up ASAP, and get a new hard drive. In general hard drive errors get worse over time, often on an very quickly exponentially growing number of blocks going bad. -- e2label crashed with SIGFPE in ext2fs_open2() https://bugs.launchpad.net/bugs/177478 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs