http://qa.mandrakesoft.com/show_bug.cgi?id=2472
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2003-02-27 21:27 -------
Someone answered on a forum:
�I have exactly the same problem. Here's the situation:
mdk-9.0 has e2fsprogs-1.27ea
mdk-9.1rc1 has e2fsprogs-1.32
It so happens that v1.32 supports some new features not supported by v1.27ea.
Naturally, a filesystem generated by v1.32 cannot be checked/repaired by v1.27ea. �
So I just do a
mount /dev/hda9 -t ext3 /alt
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
I�m currently double booting to both mdk9.0 and 9.1rc1, and I found that I can�t boot
mdk9.0 with the partition of mdk9.1rc1 in the /etc/fstab; I have to comment that line
out and reboot to get to mdk9.0.
The error it gives me is that fsch couldn�t check that filesystem (/dev/hda9 in this
case).
However, there is no update for fsck for mdk9.0.
I installed mdk9.1 by formatting that partition /dev/hda9 (so it wasn�t an update)
