You are not logged in.

#1 2009-03-21 17:55:35

Revelation60
Member
From: The Netherlands
Registered: 2009-03-19
Posts: 158
Website

FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

I am trying to install Arch on my second computer, but I get this error in cfdisk:

FATAL ERROR: Bad logical partition 6: enlarged logical partitions overlap.

This is the output of fdisk -l:

$ sudo fdisk /dev/sda -l
Schijf /dev/sda: 500.1 GB, 500107862016 bytes
255 koppen, 63 sectoren/spoor, 60801 cilinders
Eenheid = cilinders van 16065 * 512 = 8225280 bytes
Schijf-ID: 0xeaca5f2c

Apparaat Opstart   Begin       Einde     Blokken   ID  Systeem
/dev/sda1   *           1        8475    68075406    7  HPFS/NTFS
/dev/sda2            8476       56711   387442688+   7  HPFS/NTFS
/dev/sda3           57998       60801    22523130    f  W95 Uitgeb. (LBA)
Partition 3 does not end on a cylinder boundary.
/dev/sda5           58252       60801    20482875   83  Linux
/dev/sda6           57998       58250     2032159+  82  Linux wisselgeheugen

This is the output of parted:

Model: ATA WDC WD5000AAKS-0 (scsi)
Schijf /dev/sda: 500GB
Sectorgrootte (logisch/fysiek): 512B/512B
Partitietabel: msdos

Nummer  Begin   Einde   Grootte  Type      Bestandssysteem  Vlaggen
1      32,3kB  69,7GB  69,7GB   primary   ntfs             opstartbaar
2      69,7GB  466GB   397GB    primary   ntfs
3      477GB   500GB   23,1GB   extended                   lba
6      477GB   479GB   2081MB   logical   linux-swap
5      479GB   500GB   21,0GB   logical   ext4


I actually got the same error on my other system too, but then I deleted all the partitions, which is not really an option on this system. What is causing this problem?

Last edited by Revelation60 (2009-03-21 17:56:44)

Offline

#2 2009-03-22 10:28:18

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

Looks like the extended partition /dev/sda3 was not created correctly.
There is a big gap between sda2 end and the start of sda3 (from 56711 until 57998)
Safest solution would be to delete sda6 , sda5, sda3 and then recreate them.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2009-03-22 11:12:46

Revelation60
Member
From: The Netherlands
Registered: 2009-03-19
Posts: 158
Website

Re: FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

The gap was there because I wanted to create my Arch partition there.  If I delete the partitions, wouldn't I lose all the data?

Offline

#4 2009-03-22 12:33:26

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

The problem is here:

/dev/sda3           57998       60801    22523130    f  W95 Uitgeb. (LBA)
Partition 3 does not end on a cylinder boundary.
/dev/sda5           58252       60801    20482875   83  Linux

sda5 starts before the end of sda3 and thats your problem (sda6 is overlapping sda3 too), the gap you have to install arch will not cause problems. I guess that as it is you have already lost some data, if you can try to create an image of the whole disk. Then try testdisk and see if it can restore the partitions layout to what it was before otherwise just do as Lone_Wolf said. Then create all the partitions at once and don't resize them afterwards as it can go really wrong.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#5 2009-03-22 12:44:04

Revelation60
Member
From: The Netherlands
Registered: 2009-03-19
Posts: 158
Website

Re: FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

W95 Uitgeb. (LBA) means Windows 95 Extended. Isn't it correct that sda5 and sda 6 are contained in the extended partition?

Offline

#6 2009-03-22 14:04:17

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

Yes, sda5 and sda6 are in the extended partition sda3.
The error message from fdisk is likely due to an error in sda3, possibly 'Partition 3 does not end on a cylinder boundary.
Not all programs read the partition table the same, and it is possible fdisk/cfdisk interpret the table incorrect.

First step would be to backup the data on sda6.

After that you can try a bootdisk like gparted if you want to fix the partition table.
If that is successfull you can try to create a primary partition in the available space.

Personally I'd delete , then delete sda6, sda5 en sda3 , reboot and recreate the partitions needed.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#7 2009-03-22 15:09:48

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: FATAL ERROR: Bad logical partition 6: enlarged logical partitions over

Oh, ok then, that makes sense ... I don't know the reason to align partitions to cylinders but there must be a good reason, although even if they are not aligned it shouldn't be a big problem (at least gparted allows you to create unaligned partitions).
Personally gparted is not my first choice when dealing with partitions, it already scared me _big time_ and even if linux doesn't complain about partitions not being in the order they are on disk some programs complain about that (and gparted does make a mess out of that) and even refuse to do anything before they fix that (partition magic for example, and I've never lost any data or even got scared when using it).
Lately I have been doing it like this, create the partitions with cfdisk which leaves everything in a way no program complains, then I format the partitions with mkfs.whatever or I use gparted just to format the partitions, I've never had problems when doing things like that.
The last time I've used gparted to resize partitions things went well but on another occasion it did make a huge mess out of the partition layout (there were ntfs partitions involved when it went wrong, and only ext3 when all went well) leaving me with a problem similar to what you have now, luckily testdisk came to the rescue but I reckon I was just lucky that time.
I've learned my lesson, _always_ make backups or copy things to another disk, besides being probably faster (as gparted does a ton of checks) it is a lot safer and if you have really important stuff on your hard disk you can't afford to be relying on the chance of not loosing it in the process.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

Board footer

Powered by FluxBB