[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: partition does not end on cylinder boundary error. FIXED



On Wed, 2002-02-20 at 16:01, Sebastiaan wrote:
> Hi,
> 
> On 20 Feb 2002, Shriram Shrikumar wrote:
> 
> > Hi Sebastian,
> >
> > tried booting into win98 again and it worked. LILO was still giving me
> > trouble when running it(NOT when booting) - something along the lines
> > of,
> >
> > Device 0x0300: Invalid partition table, 1st entry
> >   3D address:     32/1/0 (94)
> >   Linear address: 1/1/0 (63)
> >
> > I have partition magic 6 installed and when I ran that - it told me that
> > there were some mismatches between the LBA and CHS values and offered to
> > fix them - I said yes.
> >
> > Back in Linux now (and feeling much better) I checked with fdisk and
> > there doesn't seem to be a problem with that partition anymore and lilo
> > seems to run fine as well.
> >
> So basically you ran partition magic, fixed the problem and now everything
> works fine? Great. I became curious, so could you please send me another
> fdisk -l an fdisk -l -u from your current situation? Let's see how it's
> solved.

fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 2491 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1       158   1269103+   b  Win95 FAT32
/dev/hda2           159       184    208845   83  Linux
/dev/hda4           185      2491  18530977+   f  Win95 Ext'd (LBA)
/dev/hda5           185       312   1028128+  16  Hidden FAT16
/dev/hda6           313       571   2080386    6  FAT16
/dev/hda7           572      1403   6683008+   b  Win95 FAT32
/dev/hda8          1404      1467    514048+  82  Linux swap
/dev/hda9          1468      1589    979933+  83  Linux
/dev/hda10         1590      1640    409626   83  Linux
/dev/hda11         1641      1768   1028128+  83  Linux
/dev/hda12         1769      2151   3076416    b  Win95 FAT32

fdisk -l -u /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 2491 cylinders
Units = sectors of 1 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1            63   2538269   1269103+   b  Win95 FAT32
/dev/hda2       2538270   2955959    208845   83  Linux
/dev/hda4       2955960  40017914  18530977+   f  Win95 Ext'd (LBA)
/dev/hda5       2956023   5012279   1028128+  16  Hidden FAT16
/dev/hda6       5012343   9173114   2080386    6  FAT16
/dev/hda7       9173178  22539194   6683008+   b  Win95 FAT32
/dev/hda8      22539258  23567354    514048+  82  Linux swap
/dev/hda9      23567418  25527284    979933+  83  Linux
/dev/hda10     25527348  26346599    409626   83  Linux
/dev/hda11     26346663  28402919   1028128+  83  Linux
/dev/hda12     28402983  34555814   3076416    b  Win95 FAT32



I dont notice any diff between this and the one before.(v. strange) Then
again, how can I get fdisk to display the CHS / LBA values (like pqmagic
was talking about) ?

Looking at fdisk man,

	In  a DOS type partition table the starting offset and the
	size of each partition is stored in two ways: as an  abso­
	lute  number of sectors (given in 32 bits) and as a Cylin­
	ders/Heads/Sectors triple (given in 10+8+6 bits). The for­
	mer  is  OK - with 512-byte sectors this will work up to 2
	TB. The latter has two different problems. First  of  all,
	these  C/H/S  fields can be filled only when the number of
	heads and the number of sectors per track are known.  Sec­
	ondly,  even  if we know what these numbers should be, the
	24 bits that are available do not suffice.  DOS uses C/H/S
	only, Windows uses both, Linux never uses C/H/S.

I suppose this explains the problem I have been having - I guess fdisk
doesn't need the C/H/S values and therefore maybe doesn't have much
facility to change just there values.

Learn something new EVERY day. The only diff between what you learn
about linux and windoze is that - the more you learn about windoze, the
more you tend to dislike it and the more you learn about linux - the
more you like Linux (and dislike windows)

Regards,




Shr

> > BTW, do you know of any software that would be able to do something
> > similar in Linux ?
> >
> Hmmm, not really. I guess fdisk is all you have and if you know how to
> work with the data and how the disk is constructed, it's all you need. But
> it is pretty bare bone, yes.
> 
> Greetz,
> Sebastiaan
> 
> > Thanks for all your help, much appreciated.
> >
> >
> > Regards,
> >
> >
> >
> > Shri
> >
> 
> 
> 




Reply to: