On Fri Oct 08 1999 at 20:49, Tony Nugent wrote:
> I just tried using tomsrtbt on a box with a brand new redhat 6.1
> installation on it.
>
> $ mount -t ext2 /dev/hda1 /mnt
> EXT@-fs: 0301: couldn't mount RDRW because of unsupported features
> mount: wrong fs type, bad option, bad superblock on /dev/fd0,
> or too many mounted file systems
>
> Can anyone confirm that this is happening to them with rh6.1?
Nobody else has said anything about this here since I posted this
message, but I can confirm that this has happened to me here time and
time again on every rh61 installation that I've done so far (10 or so,
so far). It happens with both SCSI and IDE drives, so it doesn't seem
to be related to the device drivers.
> [If so, then the new rh61 is using an incompatible/extended version
> of the ext2 filesystem, which is likely to make tomsrtbt unusable
> with this and probably other forthcoming distributions.]
I strongly suspect that this could be a kernel / ext2fs / mount issue
with the 2.2.x kernels, but I really have no idea why this is
happening.
But no matter what the cause, the fact is that it is not possible to
mount ext2 filesystems made with a redhat 6.1 installation with a
tomsrtbt disk.
Ouch.
Heh, the other thing is that rh61 doesn't come with a rescue.img
image, and the documentation on the distribution disk is incorrect in
that it refers to the existance of such a beast.
This will probably become an FAQ, so here's one answer (hopefully not
the last!) for those looking for a rescue disk solution for rh61.
Ok, this is the scoop from a recent post into one of the redhat
mailing lists by Jay Turner, the RedHat QA Engineer...
========8<-------- cut --------------
Date: Fri, 8 Oct 1999 08:04:08 -0400 (EDT)
From: Jay Turner <[EMAIL PROTECTED]>
To: "RedHat 6.1 Cartman Mailing List" <[EMAIL PROTECTED]>
Subject: Re: no rescue.img
On Sat, 9 Oct 1999, Tony Nugent wrote:
> What happened to the rescue.img file from the images/ directory?
>
> Also, there's no rescue.txt file like it says there should be
> (according to the html docs).
>
> Oops?
Yes, the docs got a little out of step with the development (translation -
development made a decision and did not tell docs :-() and therefore some stuff
slipped. That having been said, here is the answer to your question.
Rescue mode has been completely rewritten in 6.1 to eliminate the need for a
rescue.img or for a system boot disk (the disk made during the installation, or
one made with the mkbootdisk command . . . not the boot.img and bootnet.img
which boot the installation program) Anyway, you can now start rescue mode in
the following manner:
* boot directly from the cdrom with "linux rescue" at the boot prompt
* boot from the boot.img disk with "linux rescue" at the boot prompt
* boot from the bootnet.img disk with "linux rescue" at the boot prompt
* boot from the pcmcia.img disk with "linux rescue" at the boot prompt
Booting directly from the cdrom will drop you at a shell prompt, at which you
can start performing rescue tasks.
Booting from any of the boot images described above will result in what appears
to be an installation. That is, if you boot with the bootnet.img disk, you
will be prompted to provide the location at which you are retrieving the rescue
image from. This is the same path that you would give for an installation.
So, if you have the distribution being nfs served on porkchop.redhat.com in the
/mnt/dist directory, then you would enter that information in the nfs server
and path prompts. The installer will then run off and retrieve the rescue
image, dropping you at the same shell prompt that you get with the cdrom.
We decided this method made things a lot easier in that people did not need a
dedicated rescue.img. In addition, people did not need system-specific boot
disks. Anyway with the boot images or cdrom can get into rescue mode now.
Hope this helps clarify things a little bit.
- J
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*
Jay Turner, QA Engineer [EMAIL PROTECTED] Red Hat, Inc.
========8<-------- cut --------------
Cheers
Tony
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
Tony Nugent <[EMAIL PROTECTED]> Systems Administrator
GrowZone OnLine (a project of) GrowZone Development Network
POBox 475 Toowoomba Oueensland Australia 4350 Ph: 07 4632 8344
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
