[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: Partition table still leaves me confused.
- From: "Mark Knecht" <mknecht controlnet com>
- To: <redhat-install-list redhat com>
- Subject: RE: Partition table still leaves me confused.
- Date: Sun, 1 Jun 2003 10:21:05 -0700
Albert,
For the information I see this morning, I believe it is not worth trying
to save this Mandrake installation. I'm not sure how dead it was before we
started this process, but I think it looks pretty dead now:
1) vfat is a DOS, if you will, file system, or one of the variants that
Linux recognizes. It supplies the 8.3 filename.filetype names. Look at your
list of file names:
loca.lho
localh.ost
who i.sn'
Right or wrong, Linux now sees this disk as vfat. The problem is these are
not logically correct names. It looks to me like Linux names hosed up since
the drive is misconfigured at this point.
2) Possibly, just one more time, try 'umount /dev/hda3' and then 'mount -t
ext2 /dev/hda3 /mnt/hda3'. If that doesn't work then I really think the
drive partitions are gone.
3) I differ with Otto's assessment on whether you should have let Linux
figure out the file type. man mount, which I suggested you look over,
suggests you don't do this unless you know you're using ext2 or ext3 file
systems. For that reason I wanted you to mount it by hand, with the -t ext2
description first. Since that didn't work, I think it was not right to let
the OS figure this out itself. If it guesses wrong it can make a mistake and
possibly hurt the data on the drive.
4) I do NOT think that you doing what Otto suggested actually caused the
problem. Rather, since your extended partition has been identifying itself
as Win 95 Extended (LBA) I think something else (probably Partition Magic
messed it up. I certainly CANNOT say I know this for sure, but the same sort
of thing has happened to me a couple of times.
5) As an aside, I think you need to learn both the mount and umount
commands, if for no other reason than to just to complete this exercise. You
seem a bit surprised sometimes at the results. I'm here to help you with
that if you'd like.
Now, with that in mind, my input would be to consider deleting these
partitions. That done I'd make a decision about what you want to do with the
drive. Do you want to have multiple Linux installations? If so, let's help
you get that set up with Redhat and Mandrake both working.
I think we gone about as far as we can with these partitions, based on
this morning's data.
- Mark
> -----Original Message-----
> From: redhat-install-list-admin redhat com
> [mailto:redhat-install-list-admin redhat com]On Behalf Of Albert DE WINT
> Sent: Sunday, June 01, 2003 8:28 AM
> To: redhat-install-list redhat com
> Subject: RE: Partition table still leaves me confused.
>
>
>
> Op zo 01-06-2003, om 16:44 schreef Otto Haliburton:
> > There is a problem with the file system type as I remember the earlier
> > emails. It calls it a extended win95 partition try going from there.
> > Second I don't think you have to put the partition type in the command.
> > Let it figure it out itself.
>
> YES! I finally got hda3 mounted?
> Like you said, Otto, without any -t options.
>
> Here's what I got, I suppose Mandrake died peacefully when I installed
> REDHAT, amen..
>
> [root dimension albert]# ls -l /mnt/hda3
> ls: /mnt/hda3/en /etc/.new: unknown file or directory
> ls: /mnt/hda3/open /et.c/n: unknown file or directory
> total 23048020
> -rwxr-xr-x 1 root root 0 dec 31 1979 ???.??
> dr-xr-xr-x 42 root root 4096 nov 14 2035 :01 loca.lho
> -rwxr-xr-x 1 root root 1230315641 mrt 1 2035 0 localh.ost
> drwxr-xr-x 35 root root 4096 mrt 25 1996 0, who i.sn'
> dr-xr-xr-x 57 root root 4096 dec 31 2036 :15 loca.lho
> -rwxr-xr-x 1 root root 980709985 mrt 14 2030 17 19:17.:43
> -r-xr-xr-x 1 root root 544501614 aug 31 2013 2:01:01.loc
> dr-xr-xr-x 58 root root 4096 mrt 12 2032 (9)?may.17
> -rwxr-xr-x 1 root root 2003136032 mrt 19 2035 art: ran. by
> -rwxr-xr-x 1 root root 428 mei 29 14:31 bootex.log
> -rwxr-xr-x 1 root root 741351492 mrt 25 1996 calhost.inn
> dr-xr-xr-x 75 root root 4096 mrt 5 2035 calhost.rne
> -rwxr-xr-x 1 root root 1936681068 nov 12 2035 ews (9)?.may
> -r-xr-xr-x 1 root root 1702065409 nov 15 2035 ?ftp.ot
> dr-xr-xr-x 40 root root 4096 dec 31 2004 ho isn't. ne
> -r-xr-xr-x 1 root root 1869742336 nov 12 2035 ing.ff
> drwxr-xr-x 6 root root 4096 jul 25 1903 inndstar.t:
> -rwxr-xr-x 1 root root 540553274 jan 23 2009 isn't n.ews
> drwxr-xr-x 42 root root 4096 okt 21 2016 lhost in.nds
> -rwxr-xr-x 1 root root 0 dec 31 1979 m??&?
> dr-xr-xr-x 70 root root 4096 mrt 20 1996 may 18 2.3:0
> dr-xr-xr-x 38 root root 4096 mrt 20 1996 may 19 1.9:5
> -r-xr-xr-x 1 root root 1751933283 jan 18 1996 news (9.)?m
> -rwxr-xr-x 1 root root 1936681068 nov 12 2035 nn.conf?.may
> drwxr-xr-x 4 root root 4096 mrt 6 1980 office.pos
> drwxr-xr-x 29 root root 4096 feb 4 1996 ost innd.sta
> -r-xr-xr-x 1 root root 1953460082 mrt 15 2037 ot.de
> -rwxr-xr-x 1 root root 958931059 dec 31 2034 ran by.uid
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> drwxr-xr-x 58 root root 4096 sep 15 2032 s: canno.t o
> -rwxr-xr-x 1 root root 1847620647 aug 31 2032 start: r.an
> -rwxr-xr-x 1 root root 0 dec 31 1979 tdb file.?
> -rwxr-xr-x 1 root root 1650524416 feb 11 1902 urity.oot
> -r-xr-xr-x 1 root root 1952803698 jul 31 1980 use.ff
> dr-xr-xr-x 52 root root 4096 mrt 9 2035 y 17 16:.13:
> -rwxr-xr-x 1 root root 0 dec 31 1979 ??y.??y
> -rwxr-xr-x 1 root root 0 dec 31 1979 z?
> [root dimension albert]#
>
> Sorry for this late reply, I have been spending the afternoon
> reinstalling WinXP from scratch, since that died also a couple of days
> ago. WinXP is for my kidz. They are 8 and 12 years old and very much
> addicted to Windoze. Since I can't run any music under REDHAT, I was
> obliged (yes, under pressure) to get XP back.
>
> BTW I like the installation of RH9 much more; XP did not recognise the
> ethernet card, nor the soundcard. What a mess.
>
> Now I should repair GRUB I suppose; I had to boot RH9 using a rescue
> (boot) floppy, Thanks again for that warning Mark!
>
> > -----Original Message-----
> > From: redhat-install-list-admin redhat com
> > [mailto:redhat-install-list-admin redhat com] On Behalf Of Mark Knecht
> > Sent: Sunday, June 01, 2003 7:42 AM
> > To: redhat-install-list redhat com
> > Subject: Re: Partition table still leaves me confused.
> >
> > On Sun, 2003-06-01 at 02:23, Albert DE WINT wrote:
> >
> > > Here's what I got:
> > >
> > > root DIMENSION albert]# mount -t ext2 /dev/hda3 /mnt/hda3
> > > mount: wrong fs type, bad option, bad superblock on /dev/hda3,
> > > or too many mounted file systems
> > >
> > > Then I replaced ext2 -> ext3
> > >
> > > [root DIMENSION albert]# mount -t ext3 /dev/hda3 /mnt/hda3
> > > mount: wrong fs type, bad option, bad superblock on /dev/hda3,
> > > or too many mounted file systems
> > >
> >
> > OK, I don't see anything wrong with the command, so a couple of
> > possibilities comes to mind:
> >
> > 1) The partition type isn't ext2 or ext3. I think this is unlikely, but
> > you could try some others:
> >
> > mount -t vfat
> > mount -t msdos
> > mount -t fat32
> > mount -t reiserfs
> > mount -t xfs
> >
> > Look at man mount for even more info.
> >
> > 2) Possibly the Mandrake partition is actually damaged? You said you had
> > a hard time with installation. Maybe it got hurt?
> >
> > Assuming that this possible, you could try running e2fsck which is a
> > program that will check a damaged ext2/etx3 file system and repair it.
> > First, you want to make sure that /dev/hda3 is NOT mounted. As root, do:
> >
> > df -T
> >
> > and make very sure /dev/hda3 is not there. If it is not, then try:
> >
> > e2fsch /dev/hda3
> >
> > On my system it just does:
> >
> > Wizard root # e2fsck /dev/hda5
> > e2fsck 1.32 (09-Nov-2002)
> > /dev/hda5: clean, 119786/692128 files, 415023/1381582 blocks
> > Wizard root #
> >
> >
> > I'm interested in what you'll see.
> >
> > - Mark
> >
> >
> > _______________________________________________
> > Redhat-install-list mailing list
> > Redhat-install-list redhat com
> > https://www.redhat.com/mailman/listinfo/redhat-install-list
> > To Unsubscribe Go To ABOVE URL or send a message to:
> > redhat-install-list-request redhat com
> > Subject: unsubscribe
> >
> >
> >
> > _______________________________________________
> > Redhat-install-list mailing list
> > Redhat-install-list redhat com
> > https://www.redhat.com/mailman/listinfo/redhat-install-list
> > To Unsubscribe Go To ABOVE URL or send a message to:
> > redhat-install-list-request redhat com
> > Subject: unsubscribe
> --
>
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://www.redhat.com/mailman/listinfo/redhat-install-list
> To Unsubscribe Go To ABOVE URL or send a message to:
> redhat-install-list-request redhat com
> Subject: unsubscribe
>
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]