Description of problem: Errors during urpmi --auto-update -v when a kernel update takes place. Probably something to with parted ? ---------snip---------- 14/25: kernel-desktop-2.6.38.2-2.mga ######################################################################################################### Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. Error: Unable to satisfy all constraints on the partition. 15/25: kernel-desktop-latest ######################################################################################################### 16/25: harddrake-ui ######################################################################################################### -----------------snip----------------- Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
CC: (none) => pterjan, tmb
yep, thats parted errors... what does fdisk -l -u /dev/sda say ?
Source RPM: (none) => parted
Mageia is on sdb - I included df at the end. [root@localhost baz]# fdisk -l -u /dev/sda Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 16 heads, 63 sectors/track, 1938021 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x251c251b Device Boot Start End Blocks Id System /dev/sda1 * 63 6143759 3071848+ 83 Linux /dev/sda2 6143760 1953525167 973690704 5 Extended /dev/sda5 6143823 16383023 5119600+ 83 Linux /dev/sda6 16383087 24574031 4095472+ 82 Linux swap / Solaris /dev/sda7 24574095 40957055 8191480+ 83 Linux /dev/sda8 40957119 245756447 102399664+ 83 Linux /dev/sda9 245756511 695566367 224904928+ 83 Linux /dev/sda10 695566368 711952604 8193118+ 83 Linux /dev/sda11 711952668 732435479 10241406 83 Linux /dev/sda12 732436047 756087695 11825824+ 83 Linux /dev/sda13 756087759 779282783 11597512+ 83 Linux /dev/sda14 846165663 862548623 8191480+ 83 Linux /dev/sda15 862548687 1067348015 102399664+ 83 Linux /dev/sda16 779282847 846165599 33441376+ 83 Linux /dev/sda17 1067348079 1083731039 8191480+ 83 Linux /dev/sda18 1083731103 1124690111 20479504+ 83 Linux /dev/sda19 1124690175 1329487487 102398656+ 83 Linux /dev/sda20 1329487551 1390927103 30719776+ 83 Linux /dev/sda21 1390927167 1415504159 12288496+ 83 Linux /dev/sda22 1415504223 1476941759 30718768+ 83 Linux /dev/sda23 1476941823 1497421295 10239736+ 83 Linux /dev/sda24 1497421359 1953525167 228051904+ 83 Linux Partition table entries are not in disk order [root@localhost baz]# fdisk -l -u /dev/sdb Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 * 63 1023983099 511991518+ 83 Linux /dev/sdb2 1023983100 1060996859 18506880 5 Extended /dev/sdb5 1023983163 1040353334 8185086 83 Linux /dev/sdb6 1040353398 1060996859 10321731 83 Linux [root@localhost baz]# df Filesystem Size Used Avail Use% Mounted on /dev/sdb5 7.7G 5.0G 2.4G 68% / /dev/sda24 215G 164G 40G 81% /2010_0_home /dev/sdb1 481G 311G 146G 69% /backup /dev/sdb6 9.7G 1.2G 8.5G 13% /home /dev/sdc1 466G 425G 42G 92% /media/imo /dev/sda9 212G 123G 79G 61% /store [root@localhost baz]#
What distribution(s) and versions have you been using? A drive being accessed using the pata kernel module has a limit of 64 partitions on the drive (hda1 to hda64). A drive using the sata module has the scsi limit of 15 partitions (sda1 to sda15). You'll have to use a distro/version that uses the pata driver, and move things around so that the highest partition number is hda15, before using mageia or any distro using the sata driver. I strongly recommend not using mageia to do anything with sda, until the number of partitions has been reduced. Make sure you backup everything that's critical. I get around the number of partition limit by using lvm.
CC: (none) => davidwhodgins
(In reply to comment #3) > What distribution(s) and versions have you been using? Mandriva mainly 2010 + There was a bug relating to hard drive installs to higher partitions in Mandriva 2010.0 which I reported and was fixed. https://qa.mandriva.com/show_bug.cgi?id=57032 There are no issues that I am aware of with using partitions above 15 with Mandriva 2010.1. I also have PCLOS 2010, Slack and Ubuntu, but the latter two were only for some testing. > A drive using the sata module has the scsi limit of 15 partitions (sda1 to sda15). I understand that used to be the case - are you *sure* that applies to kernels >= 2.6.28 ? see:- https://qa.mandriva.com/show_bug.cgi?id=35482#c5 > You'll have to use a distro/version that uses the pata driver, and move things > around so that the highest partition number is hda15, before using mageia or > any distro using the sata driver. I have been using 25+ partitions since Mandriva 2010.0 with SATA drives. In Mageia all the 15+ partitions appear to be correctly assigned as they are in Mandriva:- [baz@localhost ~]$ ls -l /dev/sd* brw-rw---- 1 root disk 8, 0 Apr 4 13:52 /dev/sda brw-rw---- 1 root disk 8, 1 Apr 4 13:52 /dev/sda1 brw-rw---- 1 root disk 8, 10 Apr 4 13:52 /dev/sda10 brw-rw---- 1 root disk 8, 11 Apr 4 13:52 /dev/sda11 brw-rw---- 1 root disk 8, 12 Apr 4 13:52 /dev/sda12 brw-rw---- 1 root disk 8, 13 Apr 4 13:52 /dev/sda13 brw-rw---- 1 root disk 8, 14 Apr 4 13:52 /dev/sda14 brw-rw---- 1 root disk 8, 15 Apr 4 13:52 /dev/sda15 brw-rw---- 1 root disk 259, 0 Apr 4 13:52 /dev/sda16 brw-rw---- 1 root disk 259, 1 Apr 4 13:52 /dev/sda17 brw-rw---- 1 root disk 259, 2 Apr 4 13:52 /dev/sda18 brw-rw---- 1 root disk 259, 3 Apr 4 13:52 /dev/sda19 brw-rw---- 1 root disk 8, 2 Apr 4 13:52 /dev/sda2 brw-rw---- 1 root disk 259, 4 Apr 4 13:52 /dev/sda20 brw-rw---- 1 root disk 259, 5 Apr 4 13:52 /dev/sda21 brw-rw---- 1 root disk 259, 6 Apr 4 13:52 /dev/sda22 brw-rw---- 1 root disk 259, 7 Apr 4 13:52 /dev/sda23 brw-rw---- 1 root disk 259, 8 Apr 4 13:52 /dev/sda24 brw-rw---- 1 root disk 8, 5 Apr 4 13:52 /dev/sda5 brw-rw---- 1 root disk 8, 6 Apr 4 13:52 /dev/sda6 brw-rw---- 1 root disk 8, 7 Apr 4 13:52 /dev/sda7 brw-rw---- 1 root disk 8, 8 Apr 4 13:52 /dev/sda8 brw-rw---- 1 root disk 8, 9 Apr 4 13:52 /dev/sda9 brw-rw---- 1 root disk 8, 16 Apr 4 13:52 /dev/sdb brw-rw---- 1 root disk 8, 17 Apr 4 13:52 /dev/sdb1 brw-rw---- 1 root disk 8, 18 Apr 4 13:52 /dev/sdb2 brw-rw---- 1 root disk 8, 21 Apr 4 13:52 /dev/sdb5 brw-rw---- 1 root disk 8, 22 Apr 4 13:52 /dev/sdb6 brw-rw---- 1 root disk 8, 32 Apr 4 13:52 /dev/sdc brw-rw---- 1 root disk 8, 33 Apr 4 13:52 /dev/sdc1 [baz@localhost ~]$ > Make sure you backup everything that's critical. I get around the number of > partition limit by using lvm. I have never got involved with LVM (or raid) - always looked unnecessarily complicated to me - but I may have to take another look if it turns out to be essential.
Does parted itself work ? whats the output of parted /dev/sda -s print parted /dev/sdb -s print
And if that does not work, try with parted-2.3-1.1.mga1 from: http://tmb.mine.nu/Mageia/Cauldron/bugs/629/x86_64/
Thanks Thomas - I think :-/ I am now even more confused. I installed parted and libparted from the above link and it still complains:- Error: Unable to satisfy all constraints on the partition. I also ran cfdisk [root@localhost baz]# cfdisk -Ps /dev/sda FATAL ERROR: Bad logical partition 10: enlarged logical partitions overlap However fdisk does not show any overlaps (that I can find) Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 16 heads, 63 sectors/track, 1938021 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x251c251b Device Boot Start End Blocks Id System /dev/sda1 * 63 6143759 3071848+ 83 Linux /dev/sda2 6143760 1953525167 973690704 5 Extended /dev/sda5 6143823 16383023 5119600+ 83 Linux /dev/sda6 16383087 24574031 4095472+ 82 Linux swap / Solaris /dev/sda7 24574095 40957055 8191480+ 83 Linux /dev/sda8 40957119 245756447 102399664+ 83 Linux /dev/sda9 245756511 695566367 224904928+ 83 Linux /dev/sda10 695566368 709902143 7167888 83 Linux /dev/sda11 711952668 732435479 10241406 83 Linux /dev/sda12 732436047 756087695 11825824+ 83 Linux /dev/sda13 756087759 779282783 11597512+ 83 Linux /dev/sda14 846165663 862548623 8191480+ 83 Linux /dev/sda15 862548687 1067348015 102399664+ 83 Linux /dev/sda16 779282847 846165599 33441376+ 83 Linux /dev/sda17 1067348079 1083731039 8191480+ 83 Linux /dev/sda18 1083731103 1124690111 20479504+ 83 Linux /dev/sda19 1124690175 1329487487 102398656+ 83 Linux /dev/sda20 1329487551 1390927103 30719776+ 83 Linux /dev/sda21 1390927167 1415504159 12288496+ 83 Linux /dev/sda22 1415504223 1476941759 30718768+ 83 Linux /dev/sda23 1476941823 1497421295 10239736+ 83 Linux /dev/sda24 1497421359 1953525167 228051904+ 83 Linux Partition table entries are not in disk order I then ran :- #!/bin/bash for i in 1 5 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24;do fsck -fn /dev/sda$i >> fsck.log done ...which threw up a couple of minor errors http://pastebin.com/1A7PANZ6 which I later corrected. Parted still errors the same. I have not, until this error in urpmi had any problems with sda, Diskdrake is perfectly happy and will modify sda partition table without complaint. So, is this a problem with parted and cfdisk, or do I have a problem?
N.B. I actually resized sda10 in diskdrake to be sure that the top of sda10 could not overlap sda11. fdisk -l was showing the same block as start of sda11 as the end of sda10.
was it after you resized sda10 theese problems started to show up ? parted usually dont like anything that has been resized by fdisk. and sda10 is now at a bad alignment: /dev/sda10 695566368 709902143 whereas it really should be: /dev/sda10 695566431 711952604 and then you have the unordered partition table: /dev/sda13 756087759 779282783 11597512+ 83 Linux /dev/sda16 779282847 846165599 33441376+ 83 Linux /dev/sda14 846165663 862548623 8191480+ 83 Linux Now the unordered thing should not be a problem (can happend on ms side too and systems still work)
No I re-sized sda10 as a result of seeing the cfdisk error. It's taken all night, but I sorted it finally by backing up sda10 and then deleting it in diskdrake from Mageia running on sdb. I then re-created the partition as ext4 (it was ext3). Now parted works (albeit from within Mandriva just now as most other systems are screwed grub-wise due to the re-numbering - my Mandriva uses grub2 and only labels, so it still works :-) As you can see the old sda10 is now sda24. Just what upset the partition table I have no idea, but this can be closed as INVALID - sorry for the noise, and thanks for your help - just glad I was made aware and I could sort it. [root@jackodesktop baz]# parted /dev/sda -s print Model: ATA WDC WD10EAVS-32D (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 3146MB 3146MB primary ext2 boot 2 3146MB 1000GB 997GB extended 5 3146MB 8388MB 5242MB logical ext3 6 8388MB 12.6GB 4194MB logical linux-swap(v1) 7 12.6GB 21.0GB 8388MB logical ext3 8 21.0GB 126GB 105GB logical ext3 9 126GB 356GB 230GB logical ext3 24 356GB 365GB 8388MB logical ext4 10 365GB 375GB 10.5GB logical ext3 11 375GB 387GB 12.1GB logical ext3 12 387GB 399GB 11.9GB logical ext4 15 399GB 433GB 34.2GB logical ext4 13 433GB 442GB 8388MB logical ext4 14 442GB 546GB 105GB logical ext4 16 546GB 555GB 8388MB logical ext3 17 555GB 576GB 21.0GB logical ext4 18 576GB 681GB 105GB logical ext4 19 681GB 712GB 31.5GB logical ext4 20 712GB 725GB 12.6GB logical ext4 21 725GB 756GB 31.5GB logical ext4 22 756GB 767GB 10.5GB logical ext4 23 767GB 1000GB 234GB logical ext4 [root@jackodesktop baz]# parted /dev/sdb -s print Model: ATA WDC WD10EARS-00Y (scsi) Disk /dev/sdb: 1000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 524GB 524GB primary ext4 boot 2 524GB 572GB 47.5GB extended 5 524GB 533GB 8382MB logical ext4 6 533GB 543GB 10.6GB logical ext4 7 543GB 556GB 13.0GB logical ext4 8 556GB 565GB 8382MB logical ext4 9 565GB 572GB 7131MB logical ext4 [root@jackodesktop baz]# BTW how did you arrive at those "should be" boundaries for sda10 the new sda24 starts now where you figured it should :- /dev/sda1 * 63 6143759 3071848+ 83 Linux /dev/sda2 6143760 1953525167 973690704 5 Extended /dev/sda5 6143823 16383023 5119600+ 83 Linux /dev/sda6 16383087 24574031 4095472+ 82 Linux swap / Solaris /dev/sda7 24574095 40957055 8191480+ 83 Linux /dev/sda8 40957119 245756447 102399664+ 83 Linux /dev/sda9 245756511 695566367 224904928+ 83 Linux /dev/sda10 711952668 732435479 10241406 83 Linux /dev/sda11 732436047 756087695 11825824+ 83 Linux /dev/sda12 756087759 779282783 11597512+ 83 Linux /dev/sda13 846165663 862548623 8191480+ 83 Linux /dev/sda14 862548687 1067348015 102399664+ 83 Linux /dev/sda15 779282847 846165599 33441376+ 83 Linux /dev/sda16 1067348079 1083731039 8191480+ 83 Linux /dev/sda17 1083731103 1124690111 20479504+ 83 Linux /dev/sda18 1124690175 1329487487 102398656+ 83 Linux /dev/sda19 1329487551 1390927103 30719776+ 83 Linux /dev/sda20 1390927167 1415504159 12288496+ 83 Linux /dev/sda21 1415504223 1476941759 30718768+ 83 Linux /dev/sda22 1476941823 1497421295 10239736+ 83 Linux /dev/sda23 1497421359 1953525167 228051904+ 83 Linux /dev/sda24 695566431 711949391 8191480+ 83 Linux
"Just what upset the partition table I have no idea, but this can be closed as INVALID - sorry for the noise, and thanks for your help - just glad I was made aware and I could sort it." so closing
Status: NEW => RESOLVEDResolution: (none) => INVALID