Subject: Error: Unable to satisfy all constraints on the partition - msg#00059

List: gnu.parted.bugs

Date: Prev Next Index Thread: Prev Next Index

Hi,

Here is a bug i get when running qtparted on Kaella v1.1
(http://kaella.linux-azur.org/), a french version of Knoppix 3.4 .

---8<------8<------8<------8<------8<------8<------8<------8<------8<---

root@ttyp0[knoppix]# qtparted

Warning: Unable to align partition properly. This probably means that another
partitioning tool generated an incorrect partition table, because it didn't have
the correct BIOS geometry. It is safe to ignore,but ignoring may cause
(fixable) problems with some boot loaders.
Error: Unable to satisfy all constraints on the partition.
A bug has been detected in GNU parted. Please email a bug report to
bug-parted@xxxxxxx containing the version (1.6.9) and the following
message:Assertion (disk != NULL) at ../../libparted/disk.c:1037 in function
ped_disk_next_partition() failed.
Warning: Unable to align partition properly. This probably means that another
partitioning tool generated an incorrect partition table, because it didn't have
the correct BIOS geometry. It is safe to ignore,but ignoring may cause
(fixable) problems with some boot loaders.
Error: Unable to satisfy all constraints on the partition.
A bug has been detected in GNU parted. Please email a bug report to
bug-parted@xxxxxxx containing the version (1.6.9) and the following
message:Assertion (disk != NULL) at ../../libparted/disk.c:1037 in function
ped_disk_next_partition() failed.
Error: Unable to satisfy all constraints on the partition.
A bug has been detected in GNU parted. Please email a bug report to
bug-parted@xxxxxxx containing the version (1.6.9) and the following
message:Assertion (disk != NULL) at ../../libparted/disk.c:1037 in function
ped_disk_next_partition() failed.
Error: Unable to satisfy all constraints on the partition.
A bug has been detected in GNU parted. Please email a bug report to
bug-parted@xxxxxxx containing the version (1.6.9) and the following
message:Assertion (disk != NULL) at ../../libparted/disk.c:1037 in function
ped_disk_next_partition() failed.

---8<------8<------8<------8<------8<------8<------8<------8<------8<---

So I can't do anything, I can't even see any partition. My hard drives where
partitioned with Mandrake v10.0 Official (
DiskDrake). Is it a qparted bug or a diskdrake one? My Mandrake system runs
great nevertheless.

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

Symantec AVF detected an unrepairable virus in a message you sent

Subject of the message: Re: Test Recipient of the message: Francisco J. Velazquez Medellin

Next Message by Date: click to view message preview

Re: Restoring HDIO_GETGEO semantics for 2.6 (was: Re: [RFC] Restoring HDIO_GETGEO semantics)

On Mon, Jul 05, 2004 at 09:05:05PM +0200, Bartlomiej Zolnierkiewicz wrote: > Andries, the question was "What should we do with HDIO_GETGEO breakage?" > not "Why does somebody need the BIOS geometry?". :-) > > We can fix HDIO_GETGEO to behave like in 2.4 or remove it (preferable), > current situation is bad. I don't know precisely why. Neither of your two proposed actions appeals to me. Here is an ioctl, and it is used for legitimate purposes (finding the starting offset of a partition). You cannot remove it. We can think again in 2.7. For now, leave the kernel interface constant. Is there any advantage in going back? I don't think so. The old situation was broken. People lost all data. Also "the old situation" is badly defined. The returned value differs for 2.0, 2.2, 2.4, 2.6. No. We must go forward. Now distributions can take care of themselves. They can patch the kernel as they like, or patch parted as they like, or do any number of other things. RedHat and SuSE can take their own decisions. With some luck there is a new parted next week or so that they could offer. So we can go slowly and quietly, investigate precisely what happens, and why and how such things can be fixed. I think I understand rather well what is (was) wrong with parted. Maybe Szaka can teach me about other tools that are broken. I am confident that we can fix them, maybe in hours rather than days. As a side result we will have something valuable, namely standard software that tries to handle BIOS data. Several orders of magnitude more reliable than our old guesses. Andries

Previous Message by Thread: click to view message preview

Symantec AVF detected an unrepairable virus in a message you sent

Subject of the message: Re: Test Recipient of the message: Francisco J. Velazquez Medellin

Next Message by Thread: click to view message preview

basic question about libparted

Hey, How do i find the used and free space on a disk/partition? Say i have a partition of 5 GB and want to know how much of this 5 GB is used and is free. how do i calculate this? is it a solution to loop trough all sectors and check them? grtz, Bart -- www.titanium-it.nl --- Open Minded Open Source www.heavenisopen.com <-----Another Source

Loading Comments...