file system has an incompatible feature enabled

Bug #37137 reported by UbuPetr
This bug report is a duplicate of:  Bug #59620: can't handle ext2 resize_inode feature. Edit Remove
14
Affects Status Importance Assigned to Milestone
parted (Ubuntu)
New
Medium
Unassigned

Bug Description

I have a lot of troubles with Ubuntu installer in Dapper Drake Flight CD 5. When I want to install system to the hard disk, after partitioning disk I obtained message: "file system has an incompatible feature enabled". I do not really know why! I have 2 SATA-I disks, 2 SATA-II disks, 1 IDE disk + 3 ATAPI drives. sda, sdba, sdc, sdd, hdd + hda, hdb, hdc (DVD+-RW, CD-RW, CD-RW). And 1 SCSI CDRom on AIC7xxx. I using only these FS: NTFS, Ext2, Ext3 and SWAP. In SuSE, Gentoo, Arch everything working right.

After this bug i recieved another something like this: Ext2 partition has unrecoverable system error, do you want to continue or go back and repair problems?

But this Ext2 partition is OK, e2fsck do not report any problems.

My situation:
/dev/sdb1 200 MB Ext2 (mount as /boot and LEAVE EXTISTING DATA, do not format)
/dev/sdb7 16 GB Ext3 (mount as / and format as Ext3)
/dev/sdb9 2 GB swap (format as Swap)

I try watch into tty4 and something messages from UDEV appear like as: can not creat symbolic link do dev hdXN, sdXN (X = {a;b}, N={0;9}) because it exists; creating failed.

If I choose continue without repair changes system install sucessfully rarely. In 90% of tests installations failed with some message: deboostrap error, configuring base packages error, mkinitrd instalation failed, or something similar.

Revision history for this message
Felix Miata (mrmazda) wrote :

I too get 'Ext2 partition has unrecoverable system error, do you want to continue or go back and repair problems?', even though fsck reports clean/OK immediately prior to start of install. This happened in breezy & dapper, as I can't even get the installer to find any partitions in current edgy FTP install.

Revision history for this message
highbury (cobrin) wrote :

I'm getting a similar problem with the official Feisty release, both desktop and alternate install, I'm unable to get past this problem.

I am trying to install ubuntu on a system which already has several other distributions

Disk /dev/hda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/hda1 1 653 5245191 83 Linux
/dev/hda2 654 915 2104515 82 Linux swap / Solaris
/dev/hda3 916 14293 107458785 5 Extended
/dev/hda4 14294 14946 5245222+ 83 Linux
/dev/hda5 916 2873 15727603+ 83 Linux
/dev/hda6 2874 4831 15727601 83 Linux
/dev/hda7 4832 6789 15727602+ 83 Linux
/dev/hda8 6790 8747 15727603+ 83 Linux
/dev/hda9 8748 10705 15727603+ 83 Linux
/dev/hda10 10706 14293 28820575+ 83 Linux

I'm trying to install ubuntu root partition onto /dev/hda8 use the existing swap partition but ignore all the other partitions
when I try and write the partition I get the message "File system has an incompatible feature enabled"

If I continue I get the message "The test of the file system with type ext2 in partition #4 of IDE1 master (hda) found uncorrected errors"

When I manually ran e2fsck on /dev/hda4, the message "Adding dirhash hint to filesystem was added" but when I tried to rewrite the partition table I got the "uncorrected errors" message again

Revision history for this message
kellemes (kellemes) wrote :

Same issue with Ubuntu 7.10 Gutsy.

Installer gives me this message before partitioning:
[CODE]file system has an incompatible feature enabled[/CODE]
After partitioning the messsage is:
[CODE]The test of the file system with type ext2 in partition #1 of SCSI4 (0,0,0) (sdc) found uncorrected errors.
If you do not go back to the partitioning menu and correct these errors, the partition will be used as is.[/CODE]

I can continue the procedure but after rebooting the system it hangs at filesystem-check of this partition.

fdisk -l gives:
[CODE]Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000001

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 9728 78140128+ 7 HPFS/NTFS

Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe6e48204

   Device Boot Start End Blocks Id System
/dev/sdb2 * 2 24321 195350400 f W95 Ext'd (LBA)
/dev/sdb5 2 24321 195350368+ b W95 FAT32

Disk /dev/sdc: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb31ab31a

   Device Boot Start End Blocks Id System
/dev/sdc1 1 67 538146 83 Linux
/dev/sdc2 68 8465 67456935 5 Extended
/dev/sdc5 68 193 1012063+ 82 Linux swap / Solaris
/dev/sdc6 194 718 4217031 83 Linux
/dev/sdc7 719 2023 10482379+ 83 Linux
/dev/sdc8 2024 4592 20635459+ 83 Linux[/CODE]

sdc includes another GNU/Linux install I need to keep, the partition Ubuntu seem has a problem with is sdc1, it's formated ext2 and used as /boot for my other GNU/Linux install. This I don't want to change.

e2fsck/fsck does not report any problems on any of my partitions!

Revision history for this message
Make (mnivala) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

This is almost certainly the same as bug 59620. A workaround is to clear the resize_inode feature using tune2fs, but then you lose online resizing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.