LinuxQuestions.org - Partition 1 has different physical/logical endings

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Partition 1 has different physical/logical endings (https://www.linuxquestions.org/questions/linux-hardware-18/partition-1-has-different-physical-logical-endings-290116/)

Partition 1 has different physical/logical endings

Hello, I have a question. I recently did a fdisk -l the other day on one of our servers, and I got the following output...

Code:

Disk /dev/hda: 255 heads, 63 sectors, 524 cylinders

Units = cylinders of 16065 * 512 bytes



  Device Boot    Start      End    Blocks  Id  System

/dev/hda1            1        37    292824  82  Linux swap

Partition 1 has different physical/logical endings:

    phys=(1023, 8, 63) logical=(36, 116, 63)

Partition 1 does not end on cylinder boundary:

    phys=(1023, 8, 63) should be (1023, 254, 63)

/dev/hda2  *        37      525  3916552+  83  Linux

Partition 2 has different physical/logical beginnings (non-Linux?):

    phys=(1023, 8, 63) logical=(36, 117, 1)

Partition 2 has different physical/logical endings:

    phys=(1023, 8, 63) logical=(524, 11, 63)

Partition 2 does not end on cylinder boundary:

    phys=(1023, 8, 63) should be (1023, 254, 63)

Now it may just be me, but this looks bad. The server is acting normally. It seems to boot fine. There is no windows partitions (I noticed other people with similar similar problems had windows issues). Here's what my fstab file looks like. As you can see there's really nothing special to it.

Code:

# <file system> <mount point>  <type>  <options>              <dump>  <pass>

/dev/hda2      /              ext3    errors=remount-ro      0      1

/dev/hda1      none            swap    sw                      0      0

proc            /proc          proc    defaults                0      0

/dev/fd0        /floppy        auto    user,noauto            0      0

/dev/cdrom      /cdrom          iso9660 ro,user,noauto          0      0

If anyone can help me fix these problems or give me a better understanding of what these errors actually mean that would be very helpful.

If I need to provide more information just ask, this has me real nervous

Thanks.

Did you manage to solve your problem? It is happening to me too and i have a rwindows partition that i want to erase and add that space to my linux system but i cant because of this very same error. I have a thread talking about it too so if you know a solution and can help me please reply...

what does sfdisk -l have to say about your disk organization?

How is the HD set in the bios? Copy/post the details please.

You seem to have a conflict someplace between drive logical definitions. This may or may not place the system at risk, but figuring it out is a really good plan.

Some versions of fdisk are problematic; try sfdisk.

I used cfdisk to remove the windows partition. Then i used it again to create an extended partition and i got my space back. why there are so many "fdisk" tools? Now my system doesnt complain about the logical/physical endings anymore.

Quote:

different physical/logical endings

I see this with my BSD and Solaris partitions. I also see it on one of my USB drives.
Saw it once on an old PC that had a Stoned Monkey MBR virus.