Bug#538369: [wordnet] wordnet fails to install because of unmet wordnet-base dependency
On Monday 03 August 2009 11:02:59 you wrote: On Sun, 26 Jul 2009, Lior Chen wrote: As i understand both packages are from unstable. I also tried removing them (dpkg --purge) and reinstalling again, but it produced the same dependency error. orion:~# apt-cache policy wordnet wordnet-base wordnet: Installed: (none) Candidate: 1:3.0-15 Version table: 1:3.0-15 0 500 http://mirror.hamakor.org.il unstable/main Packages 100 /var/lib/dpkg/status wordnet-base: Installed: 1:3.0-16 Candidate: 1:3.0-16 Version table: *** 1:3.0-16 0 500 http://mirror.hamakor.org.il unstable/main Packages 100 /var/lib/dpkg/status Have you checked your installation? As I told you I suspect a problem on the mirror you are using. If I do not hear any confirmation from you I will close the bug after about 2 weeks. Sorry for the late reply. I get the exact same error with the deb http://ftp.debian.org/ unstable main contrib non-free mirror. orion:~# apt-cache policy wordnet wordnet-base wordnet: Installed: (none) Candidate: 1:3.0-15 Version table: 1:3.0-15 0 500 http://ftp.debian.org unstable/main Packages wordnet-base: Installed: (none) Candidate: 1:3.0-16 Version table: 1:3.0-16 0 500 http://ftp.debian.org unstable/main Packages orion:~# apt-get install wordnet Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: wordnet: Depends: wordnet-base (= 1:3.0-15) but it is not going to be installed E: Broken packages Thanks, Lior. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538369: [wordnet] wordnet fails to install because of unmet wordnet-base dependency
On Saturday 25 July 2009 12:34:40 you wrote: On Sat, Jul 25, 2009 at 12:08:04PM +0300, Lior Chen wrote: Package: wordnet Version: 1:3.0-15 Severity: normal --- Please enter the report below this line. --- wordnet depends on wordnet-base 1:3.0-15, but wordnet-base 1:3.0-16 is installed. orion:~# apt-get install wordnet Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: wordnet: Depends: wordnet-base (= 1:3.0-15) but 1:3.0-16 is to be installed E: Broken packages orion:~# dpkg -l | grep wordnet-base ii wordnet-base 1:3.0-16 electronic lexical database of English langu Could you please send me the output of apt-cache policy wordnet wordnet-base It should look somehow like wordnet: Installiert: 1:3.0-15 Kandidat: 1:3.0-15 Versions-Tabelle: 1:3.0-16 0 50 http://debian.tu-bs.de unstable/main Packages *** 1:3.0-15 0 501 file: testing/main Packages 501 http://debian.tu-bs.de testing/main Packages 100 /var/lib/dpkg/status wordnet-base: Installiert: 1:3.0-15 Kandidat: 1:3.0-15 Versions-Tabelle: 1:3.0-16 0 50 http://debian.tu-bs.de unstable/main Packages *** 1:3.0-15 0 501 file: testing/main Packages 501 http://debian.tu-bs.de testing/main Packages 100 /var/lib/dpkg/status I suspect that you somehow fetched wordnet-base from unstable and now have a version conflict and this is not really a wordnet problem out in itself. Kind regards Andreas. As i understand both packages are from unstable. I also tried removing them (dpkg --purge) and reinstalling again, but it produced the same dependency error. orion:~# apt-cache policy wordnet wordnet-base wordnet: Installed: (none) Candidate: 1:3.0-15 Version table: 1:3.0-15 0 500 http://mirror.hamakor.org.il unstable/main Packages 100 /var/lib/dpkg/status wordnet-base: Installed: 1:3.0-16 Candidate: 1:3.0-16 Version table: *** 1:3.0-16 0 500 http://mirror.hamakor.org.il unstable/main Packages 100 /var/lib/dpkg/status Thanks, Lior. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538369: [wordnet] wordnet fails to install because of unmet wordnet-base dependency
Package: wordnet Version: 1:3.0-15 Severity: normal --- Please enter the report below this line. --- wordnet depends on wordnet-base 1:3.0-15, but wordnet-base 1:3.0-16 is installed. orion:~# apt-get install wordnet Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: wordnet: Depends: wordnet-base (= 1:3.0-15) but 1:3.0-16 is to be installed E: Broken packages orion:~# dpkg -l | grep wordnet-base ii wordnet-base 1:3.0-16 electronic lexical database of English langu Thanks, Lior --- System information. --- Architecture: amd64 Kernel: Linux 2.6.30-1-amd64 Debian Release: squeeze/sid 500 unstablemirror.hamakor.org.il --- Package information. --- Depends (Version) | Installed ===-+-= wordnet-base (= 1:3.0-15) | 1:3.0-16 libc6 (= 2.3) | 2.9-21 libfontconfig1 (= 2.4.0) | 2.6.0-4 libfreetype6 (= 2.2.1) | 2.3.9-5 libx11-6| 2:1.2.2-1 libxext6| 2:1.0.4-1 libxft2 ( 2.1.1) | 2.1.13-3 libxrender1 | 1:0.9.4-2 libxss1 | 1:1.1.3-1 tcl8.5 (= 8.5.0) | 8.5.7-1 tk8.5(= 8.5.0) | 8.5.7-1 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-14 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534274: [mdadm] mdadm fails to assemble raid array on boot with kernel 2.6.26
Hi, On Tuesday 23 June 2009 09:33:45 you wrote: also sprach Lior Chen li...@lirtex.com [2009.06.23.0810 +0200]: With kernels newer than 2.6.26-2 (I have tried both 2.6.29-2 and 2.6.30-1) mdadm fails to assemble raid array on boot: Assembling all MD arrays... md: md0 stopped mdadm: no devices found for /dev/md0 Failure: failed to assemble all arrays. Please look at http://wiki.debian.org/InitramfsDebug#Savingdebuginformation and try to provide as much information as you can about what happens between the boot loader and the initramfs prompt. mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sda2 /dev/sdb2 or mdadm -A /dev/md0 /dev/sda2 /dev/sdb2 it fails saying that /dev/sda2 and /dev/sdb2 are busy (mdadm: Cannot open /dev/sda2: Device or resource busy). It seems like som device mapper thing is getting in the way: in the initramfs shell: ls -l /dev/mapper : control isw_cjhfigcfig_LCRAID isw_cjhfigcfig_LCRAID1 isw_cjhfigcfig_LCRAID2 I have no idea what that is, but a sneaking suspicion that isw_cjhfigcfig_LCRAID2 is /dev/sd[ab]2. Try to disable that. I have managed to fully reproduce this. This situation arose from mistakenly installing the dmraid package along with the mdadm package (or maybe it was installed because of some package-dependency, I can't really tell). Removing the dmraid package is not enough, and removing the mdadm package and reinstalling it again is required in order to update the initramfs. You were right about suspecting the isw_* devices, they were generated by dmraid, and that was the problem. The stranger thing is that this situation happens only with new dmraid versions (1.0.0.rc15*). Maybe the dmraid package should check for this conflict and warn the admin, because the result is an unbootable system. Martin and Giuseppe - Thanks again for helping me solve this. Lior -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534274: [mdadm] mdadm fails to assemble raid array on boot with kernel 2.6.26
Package: mdadm Version: 2.6.9-3 Severity: grave --- Please enter the report below this line. --- Hi, With kernels newer than 2.6.26-2 (I have tried both 2.6.29-2 and 2.6.30-1) mdadm fails to assemble raid array on boot: Assembling all MD arrays... md: md0 stopped mdadm: no devices found for /dev/md0 Failure: failed to assemble all arrays. After the system gives up waiting for the root device, I get an initramfs shell, and then I when I try to build the raid-array myself, using either: mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sda2 /dev/sdb2 or mdadm -A /dev/md0 /dev/sda2 /dev/sdb2 it fails saying that /dev/sda2 and /dev/sdb2 are busy (mdadm: Cannot open /dev/sda2: Device or resource busy). Please tell me if there is any more information I can provide that could be of help. Thank you, Lior --- Some additional information: in the initramfs shell: ls -l /dev/mapper : control isw_cjhfigcfig_LCRAID isw_cjhfigcfig_LCRAID1 isw_cjhfigcfig_LCRAID2 === raid-0 (striping) structure === /dev/sda2 - first raid device /dev/sdb2- second raid device === cat /proc/mdstat === Personalities : [raid0] md0 : active raid0 sda2[0] sdb2[1] 488199040 blocks 64k chunks unused devices: none === /etc/mdadm/mdadm.conf === # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE /dev/sda2 /dev/sdb2 # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST system # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md0 level=raid0 num-devices=2 UUID=b4c9005d:7337b4ba:77fef61e:a74ffb27 # This file was auto-generated on Sun, 21 Jun 2009 00:19:47 +0300 # by mkconf $Id$ === /proc/partitions === major minor #blocks name 8 0 244198584 sda 8 1 96358 sda1 8 2 244099642 sda2 816 244198584 sdb 818 244099642 sdb2 9 0 488199040 md0 253 04194304 dm-0 253 1 484003840 dm-1 --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-2-amd64 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstablemirror.hamakor.org.il --- Package information. --- Depends(Version) | Installed -+- libc6 (= 2.3.3) | 2.9-18 udev | 0.141-1 OR makedev | 2.3.1-88 debconf (= 1.4.72) | 1.5.26 lsb-base (= 3.1-6) | 3.2-22 Recommends(Version) | Installed ===-+-=== default-mta | OR mail-transport-agent| module-init-tools | 3.9-2 Package's Suggests field is empty. --- Output from package bug script --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533848: [dmraid] dmraid fails to assmble software raid array (raid-0) - system fails to boot
Hi, On Sunday 21 June 2009 11:48:58 Giuseppe Iuculano wrote: severity 533848 normal thanks Hi, Lior Chen ha scritto: I have a software raid array (raid 0 type), with lvm partitions built over the raid. Please explain. Why are you mixing software raid with fakeraid/ataraid and LVM? I didn't quite understand. As far as I know, I'm only mixing two types: a software raid (striping), and LVM. Doesn't it make sense to first set up the physical abstraction level (raid), and then build a logical abstraction over it? (LVM). Please paste the output of these commands: cat /proc/mdstat Personalities : [raid0] md0 : active raid0 sda2[0] sdb2[1] 488199040 blocks 64k chunks unused devices: none dmraid -r -vvv WARN: locking /var/lock/dmraid/.lock NOTICE: skipping removable device /dev/sdc NOTICE: skipping removable device /dev/sdd NOTICE: /dev/sdb: asr discovering NOTICE: /dev/sdb: ddf1discovering NOTICE: /dev/sdb: hpt37x discovering NOTICE: /dev/sdb: hpt45x discovering NOTICE: /dev/sdb: isw discovering NOTICE: /dev/sdb: isw metadata discovered NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: pdc discovering NOTICE: /dev/sdb: sil discovering NOTICE: /dev/sdb: via discovering NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering NOTICE: /dev/sda: isw metadata discovered NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering INFO: RAID devices discovered: /dev/sdb: isw, isw_cjhfigcfig, GROUP, ok, 488397166 sectors, data@ 0 /dev/sda: isw, isw_cjhfigcfig, GROUP, ok, 488397166 sectors, data@ 0 WARN: unlocking /var/lock/dmraid/.lock dmraid -s -vv NOTICE: skipping removable device /dev/sdc NOTICE: skipping removable device /dev/sdd NOTICE: /dev/sdb: asr discovering NOTICE: /dev/sdb: ddf1discovering NOTICE: /dev/sdb: hpt37x discovering NOTICE: /dev/sdb: hpt45x discovering NOTICE: /dev/sdb: isw discovering NOTICE: /dev/sdb: isw metadata discovered NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: pdc discovering NOTICE: /dev/sdb: sil discovering NOTICE: /dev/sdb: via discovering NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering NOTICE: /dev/sda: isw metadata discovered NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering NOTICE: added /dev/sdb to RAID set isw_cjhfigcfig NOTICE: added /dev/sda to RAID set isw_cjhfigcfig *** Group superset isw_cjhfigcfig -- Subset name : isw_cjhfigcfig_LCRAID size : 976783872 stride : 256 type : stripe status : ok subsets: 0 devs : 2 spares : 0 cat /proc/partitions major minor #blocks name 8 0 244198584 sda 8 1 96358 sda1 8 2 244099642 sda2 816 244198584 sdb 818 244099642 sdb2 9 0 488199040 md0 253 04194304 dm-0 253 1 484003840 dm-1 lvdisplay --- Logical volume --- LV Name/dev/vg0/swap-lv VG Namevg0 LV UUIDdUFQ6h-Od30-Iklp-oRCY-wUSs-bq1Z-ZobN8s LV Write Accessread/write LV Status available # open 2 LV Size4.00 GB Current LE 1024 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Name/dev/vg0/linux-lv VG Namevg0 LV UUIDplhvTr-ficv-VDmy-LhJP-uWnr-fMVp-H5rvwR LV Write Accessread/write LV Status available # open 1 LV Size461.58 GB Current LE 118165 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 pvdisplay --- Physical volume --- PV Name /dev/md0 VG Name vg0 PV Size 465.58 GB / not usable 896.00 KB Allocatable yes (but full) PE Size (KByte) 4096 Total PE 119189 Free PE 0 Allocated PE 119189 PV UUID W2NzvT-QriA-lite-6AjB-QetX-OjYI-VcwWPz dmsetup table vg0-swap--lv: 0 8388608 linear 9:0 384 vg0-linux--lv: 0 968007680 linear 9:0 8388992 Thank
Bug#533848: [dmraid] dmraid fails to assmble software raid array (raid-0) - system fails to boot
Package: dmraid Version: 1.0.0.rc15-8 Severity: critical --- Please enter the report below this line. --- I have a software raid array (raid 0 type), with lvm partitions built over the raid. My discs have the following structure: /dev/sda1 == /boot /dev/sda2 == first raid device /dev/sdb1 == unused space /dev/sdb2 == second raid device. orion:/home/liorc# dmraid -r /dev/sdb: isw, isw_cjhfigcfig, GROUP, ok, 488397166 sectors, data@ 0 /dev/sda: isw, isw_cjhfigcfig, GROUP, ok, 488397166 sectors, data@ 0 (LVM structure attached in the end of the bug report). With kernel 2.6.26-2, and dmraid 1.0.0.rc13-2, the system boots fine (dmraid builds the raid array successfully): [ 89.648985] md0: setting max_sectors to 128, segment boundary to 32767 [ 89.648985] raid0: looking at sda2 [ 89.648985] raid0: comparing sda2(244099520) with sda2(244099520) [ 89.648985] raid0: END [ 89.648985] raid0: == UNIQUE [ 89.648985] raid0: 1 zones [ 89.648985] raid0: looking at sdb2 [ 89.648985] raid0: comparing sdb2(244099520) with sda2(244099520) [ 89.648985] raid0: EQUAL [ 89.648985] raid0: FINAL 1 zones [ 89.648985] raid0: done. [ 89.648985] raid0 : md_size is 488199040 blocks. [ 89.648985] raid0 : conf-hash_spacing is 488199040 blocks. [ 89.648985] raid0 : nb_zone is 1. [ 89.648985] raid0 : Allocating 8 bytes for hash. However, when I upgrade to dmraid 1.0.0.rc15-8, the system fails to boot. Also, if I don't upgrade dmraid (and still use 1.0.0.rc13-2), but upgrade to any newer kernel (2.6.29-1, 2.6.29-2, 2.6.30-1), boot fails with the following error: Assembling all MD arrays... mdadm: no devices found for /dev/md0 Failure: failed to assemble all arrays. Incorrect metadata area header checksum Volume group vg0 not found. I also noticed that 'dmraid -ay' produces the following kernel error: [ 1711.937067] device-mapper: table: 253:2: striped: Couldn't parse stripe destination [ 1711.937072] device-mapper: ioctl: error adding target to table Please tell me if there is more information I can provide that could be of help. Thanks. Lior. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-2-amd64 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstablemirror.hamakor.org.il --- Package information. --- Depends (Version) | Installed =-+-= libc6(= 2.3.5-1) | 2.9-17 libdevmapper1.02 (= 2:1.02.02-2) | 2:1.02.08-1 libselinux1 (= 1.32) | 2.0.80-1 libsepol1 (= 1.14) | 2.0.36-1 lsb-base | 3.2-22 --- lvm information --- orion:/home/liorc# vgdisplay Incorrect metadata area header checksum --- Volume group --- VG Name vg0 System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 9 VG Access read/write VG Status resizable MAX LV0 Cur LV2 Open LV 2 Max PV0 Cur PV1 Act PV1 VG Size 465.58 GB PE Size 4.00 MB Total PE 119189 Alloc PE / Size 119189 / 465.58 GB Free PE / Size 0 / 0 VG UUID vqRtDp-ItdV-10Ju-VJKb-5WOF-8c2c-hsN92t orion:/home/liorc# lvdisplay Incorrect metadata area header checksum --- Logical volume --- LV Name/dev/vg0/swap-lv VG Namevg0 LV UUIDdUFQ6h-Od30-Iklp-oRCY-wUSs-bq1Z-ZobN8s LV Write Accessread/write LV Status available # open 2 LV Size4.00 GB Current LE 1024 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Name/dev/vg0/linux-lv VG Namevg0 LV UUIDplhvTr-ficv-VDmy-LhJP-uWnr-fMVp-H5rvwR LV Write Accessread/write LV Status available # open 1 LV Size461.58 GB Current LE 118165 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 Package's Recommends field is empty. Package's Suggests field is empty. --
