Re: [ILUG] strange fdisk problem...

From: John McCormac (jmcc at domain hackwatch.com)
Date: Thu 11 Apr 2002 - 09:59:49 IST


"John P. Looney" wrote:
>
> On Wed, Apr 10, 2002 at 08:11:08PM +0100, John McCormac mentioned:
> > Reordered according to start and end:
>
> Nicely done...I've been doing a lot of chopping & changing on this box
> over the last eighteen months.
>
> > > /dev/hda4 1 4 32098+ 83 Linux [pri/ext]
> > > /dev/hda1 * 5 1275 10209307+ c Win95 FAT32 (LBA) [pri/ext]
> > > /dev/hda3 1276 2982 13711477+ f Win95 Ext'd (LBA) [pri/ext]
> > > /dev/hda7 1276 1762 3911796 83 Linux [logical]
> > > /dev/hda6 1763 1827 522081 82 Linux swap [logical]
> > > /dev/hda5 1926 2982 8490321 83 Linux [logical]
> > > /dev/hda2 2983 4865 15125197+ 83 Linux [pri/ext but is logical here]
> >
> > There seems to be a jump between hda6 and hda5.
>
> Oooh. More unallocated space I'd forgotten about...
>
> > I'm not sure if the order of the partitions should matter. However
> > hda1/2/3/4 are normally selectable as either pimary or extended. The
> > structure here has hda2 as a logical drive in the extended partition.
>
> Yeah. No idea how *that* happened...

Hang on - I was wrong about that. The hda2 is primary but is way up at
the back of the hd. Does fdisk expect the last pri partition to be an
extended one?
 
> > I think I ran across something similar while formatting and partitioning
> > a large drive. The fix, if I remember correctly was to start with the
> > extended partition as being just extended and then redesignate the
> > partition as being Win95 Extd after creating the Linux drives. I think
> > it may have more to do with how fdisk expects the pri/extended drives.
>
> Woah. Are you telling me I've to wipe the partitions & re-make them. That
> makes me really uneasy. I've done some very dodgy stuff with partition
> tables, and it usually means losing data...

Not necessarily. (Just awake so this may not make sense and may be
dangerous in reality.) The missing space may be the problem. Fdisk
should try to create a logical drive starting at the first free space -
which in this case is about 99 blocks. It may be very *dangerous* to try
this but if you have backups and can afford to scrub the installation,
see if you can use free space as a logical drive before going on to
create more. One of the byproducts of partitions out of synch that I
have seen is the W95 Extd partition being rewritten as W95 Hidden. I've
partitioned disks with as many as 17 partitions (mixed W95/Linux) and
never run across the file space error problem.

Regards...jmcc

-- 
********************************************
John McCormac            * Hack Watch News
jmcc at domain hackwatch.com       * 22 Viewmount, 
Voice:   +353-51-873640  * Waterford,
BBS&Fax: +353-51-850143  * Ireland
http://www.hackwatch.com/~kooltek
********************************************
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6
mQCNAzAYPNsAAAEEAPGTHaNyitUTNAwF8BU6mF5PcbLQXdeuHf3xT6UOL+/Od+z+
ZOCAx8Ka9LJBjuQYw8hlqvTV5kceLlrP2HPqmk7YPOw1fQWlpTJof+ZMCxEVd1Qz
TRet2vS/kiRQRYvKOaxoJhqIzUr1g3ovBnIdpKeo4KKULz9XKuxCgZsuLKkVAAUX
tCJKb2huIE1jQ29ybWFjIDxqbWNjQGhhY2t3YXRjaC5jb20+tBJqbWNjQGhhY2t3
YXRjaC5jb20=
=sTfy
-----END PGP PUBLIC KEY BLOCK-----


This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:15:59 GMT