|
Home > Archive > Red Hat Topics > February 2005 > Why is Redhat's EXT3 incompatible with Mandrake?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why is Redhat's EXT3 incompatible with Mandrake?
|
|
| General Schvantzkoph 2005-02-06, 5:45 pm |
| I have a number of multiboot machines. I've noticed that an EXT3 partition
that is formated by Disk Druid can't be read by Mandrake. I first noticed
it when I put Fedora Core 3 on a system that already had Mandrake 10.1 on
it, Mandrake wouldn't boot unless I removed the FC3 partition from it's
/etc/fstab. I've since seen the same problem with Whitebox (RHEL 3.0) and
Vitalinux (which uses Anaconda to install Gentoo). Fedora has no problem
reading partitions that were created with Mandrake's disk utility, it's
just the partitions that were created with disk druid. What did Redhat do
to make their EXT3 partitions incompatible?
| |
| Rincewind 2005-02-06, 5:45 pm |
| On Sun, 06 Feb 2005 15:10:52 -0500, General Schvantzkoph mumbled something
like this:
> I have a number of multiboot machines. I've noticed that an EXT3 partition
> that is formated by Disk Druid can't be read by Mandrake. I first noticed
> it when I put Fedora Core 3 on a system that already had Mandrake 10.1 on
> it, Mandrake wouldn't boot unless I removed the FC3 partition from it's
> /etc/fstab. I've since seen the same problem with Whitebox (RHEL 3.0) and
> Vitalinux (which uses Anaconda to install Gentoo). Fedora has no problem
> reading partitions that were created with Mandrake's disk utility, it's
> just the partitions that were created with disk druid. What did Redhat do
> to make their EXT3 partitions incompatible?
I'm not sure about Redhat EXT3 and Mandrake being incompatible, but
Mandrake definitely seem to do things slightly differently.
I recently tried to install Mandrake 10.1 official on a multi-boot machine
which had been running RH9 as one of the OS's. The Mandrake install was
able to see the RH9 EXT3 partitions and to mount them, but *it
mis-identified the drives!*
The machine in question has three drives and a DVD/CD rewriter on the 2
motherboard IDE channels and 2 drives on the 2 channels of a PCI Promise
TX2 100 RAID controller. Redhat identifies the drives attached to the M/B
as hda, hdb, hdc and hdd and recognises the drives on the RAID controller
as hde and hdg. Every install I have done has ordered the drives in this
way.
Mandrake's install recognised the drives on the RAID controllers *before*
the ones attached to the M/B, resulting in the M/B attached disks being
identified as hde, hdf,hdg and hdh and the drives attached to the PCI
controller being recognised as hda and hdc! At this point, I abandoned the
install, having no confidence that Mandrake would be able to create a
working grub configuration...
Rinso
--
/\
/ \
/wizz\
~~~~~~~~~~~~
| |
| Michael Heiming 2005-02-06, 5:45 pm |
| In comp.os.linux.misc General Schvantzkoph <schvantzkoph@yahoo.com>:
> I have a number of multiboot machines. I've noticed that an EXT3 partition
> that is formated by Disk Druid can't be read by Mandrake. I first noticed
> it when I put Fedora Core 3 on a system that already had Mandrake 10.1 on
> it, Mandrake wouldn't boot unless I removed the FC3 partition from it's
> /etc/fstab. I've since seen the same problem with Whitebox (RHEL 3.0) and
Would you mind showing us the line /etc/fstab and the error
message you get if boot fails? Can you mount the partition later,
if set to "noauto"?
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | PERL -pe 'y/a-z/n-za-m/'
#bofh excuse 97: Small animal kamikaze attack on power supplies
| |
| General Schvantzkoph 2005-02-06, 5:45 pm |
| On Sun, 06 Feb 2005 22:06:42 +0100, Michael Heiming wrote:
> In comp.os.linux.misc General Schvantzkoph <schvantzkoph@yahoo.com>:
>
> Would you mind showing us the line /etc/fstab and the error
> message you get if boot fails? Can you mount the partition later,
> if set to "noauto"?
I just put the Vitalinux partition back into /etc/fstab and I was able to
mount it from the command line. I'm going to try a reboot and see what
happens.
| |
| General Schvantzkoph 2005-02-06, 5:45 pm |
| On Sun, 06 Feb 2005 16:28:55 -0500, General Schvantzkoph wrote:
> On Sun, 06 Feb 2005 22:06:42 +0100, Michael Heiming wrote:
>
>
> I just put the Vitalinux partition back into /etc/fstab and I was able to
> mount it from the command line. I'm going to try a reboot and see what
> happens.
Just did a reboot. The problem is with fsck.ext3, it's out of date. The
error message is "filesystem has unsupported features, update fsck.ext3".
| |
| John Reiser 2005-02-06, 8:45 pm |
| > Just did a reboot. The problem is with fsck.ext3, it's out of date. The
> error message is "filesystem has unsupported features, update fsck.ext3".
$ /sbin/tune2fs -l /dev/... | grep features # Fedora Core 3 root
Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
$ /sbin/tune2fs -l /dev/... | grep features # Fedora Core 2 root
Filesystem features: has_journal ext_attr dir_index filetype sparse_super
e2fsck will complain if it does not recognize _all_ features that are present.
This prevents old e2fsck from destroying new on-disk layouts.
--
|
|
|
|
|