The tomsrtbt kernel has the filetype and sparse patches applied (which
*did* make it into 2.0.39) so that shouldn't be the problem. -TOm
On Mon, 20 Aug 2001, Christopher Maujean wrote:
> Date: Mon, 20 Aug 2001 08:39:24 -0700
> From: Christopher Maujean <[EMAIL PROTECTED]>
> To: Koleman Strumpf <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: [tomsrtbt] Unable to mount ext2
>
> Have you upgraded your redhat kernel past v2.0?
> After 2.0 there were some changes to ext2fs and 2.0 kernels can't read ext2
> filesystems created for use with 2.2 or 2.4 kernels.
>
> --Christopher
>
> On Sun, Aug 19, 2001 at 08:15:26PM -0400, Koleman Strumpf wrote:
> > Hi:
> >
> > I have a dual partition Pentium II with RedHat v5.2, and my lilo recently
> > stopped working (I think due to my win anti-virus) --> goes right into
> > Win now. My rescue disk does not seem to function (the PC just freezes up
> > after spinning the floppy). At this point I am just trying to salvage some
> > files and then re-install if needed.
> >
> > Anyway, I got a hold of tomsrtbt v 1.7.358. When I try and mount my linux
> > partition I have problems. No problem mounting the Win partition (hda) but
> > when I try and mount Linux (hdb) I get:
> > # mount /dev/hda2 /test2
> > /dev/hda2: Unknown error
> > ...
> > Transaction block size = 512
> > VFS: Can't find a valid MSDOS filesystem on dev 3:02.
> > mount: you must specify the filesystem
> >
> > More information on the file system does not seem to help:
> > # mount -t ext2 /dev/hda2 /test2
> > attempted to access beyond end of device
> > 03:02: rw=0, want=2, limit=1
> > EXT2-fs: unable to read superblock
> > mount: wrong fs type, bad option, bad superblock on /dev/hda2,
> > or too many mounted fule systems
> >
> > I am not sure if this is also of use but when I first fdisk I get:
> > # fdisk /dev/hda
> > The number of cylinders for this disk is set to 1025.
> > This is larger than 1024, and may cause problems with:
> > 1) software that runs at boot time (e.g., LILO)
> > ...
> >
> > Also, when I print the partition table I get,
> > Device Boot Start End Blocks Id System
> > /dev/hda1 * 1 262 2096608+6 6 DOS 16-bit >=32M
> > Partition 1 does not end on cylinder boundary:
> > phys=(519, 127, 63) should be (519, 254, 63)
> > /dev/hda2 262 514 2028096 5 Extended
> > Partition 2 does not end on cylinder boundary:
> > phys=(1022, 127, 63) should be (1022, 254, 63)
> >
> >
> > I am pretty much a newbie so I am not sure if this is a salvagable
> > situation or I should just reinstall (and lose what files I had).
> >
> > Thanks in advance for any suggestions,
> > Koleman Strumpf
> >
> >
>
> --
>
> Christopher Maujean
> IT Director
> Premierelink Communications
> www.premierelink.com
> [EMAIL PROTECTED]
>
> PLEASE encrypt all sensitive information using the following:
> GnuPG: 0x5DE74D38
> Fingerprint: 91D4 09FE 18D0 27C1 A857 0E45 F8A4 7858 5DE7 4D38
>
> http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x5DE74D38
>
