Your message dated Sun, 20 Aug 2006 17:02:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-1 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: cryptsetup Version: 1.0.3-3 I'm interested in running an encrypted root partition, specifically where root is a logical volume on dm-crypt on raid1 md. The nightly build of the Debian installer (2006-08-09) is willing to build this setup without complaint. However, when booting into the new system, the cryptroot script fails to properly open the encrypted md partition. Here's the system layout since it's a little confusing: /dev/hda2, /dev/hda3 => /dev/md0 (raid1) (testing only) /dev/md0 => /dev/mapper/crypt0 (dm-crypt) /dev/mapper/crypt0 => ep.root (volume group) /dev/mapper/ep.root-ep.root => / (jfs formatted logical volume) I've read through some of the other bug reports (#371846 and others) and there seems to be some discussion on properly determining device dependencies, but as far as I can tell a general solution hasn't been developed yet. Is this the right answer? Or is it possible to hack md support into cryptroot as was done for lvm? Here's a console dump of the machine attempting to boot for the first time, the bottom four lines repeat indefinitely: Linux version 2.6.17-1-686 (Debian 2.6.17-5) ([EMAIL PROTECTED]) (gcc version 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)) #1 SMP Sat Jul 29 15:32:47 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved) BIOS-e820: 0000000000100000 - 000000001ffae000 (usable) BIOS-e820: 000000001ffae000 - 0000000020000000 (reserved) BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 511MB LOWMEM available. DMI 2.3 present. ACPI: PM-Timer IO Port: 0x808 Allocating PCI resources starting at 30000000 (gap: 20000000:deda0000) Built 1 zonelists Kernel command line: root=/dev/mapper/ep.root-ep.root ro console=ttyS0 Local APIC disabled by BIOS -- you can enable it with "lapic" Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Detected 1295.994 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 511036k/523960k available (1478k kernel code, 12380k reserved, 540k data, 164k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2594.25 BogoMIPS (lpj=5188501) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 1024K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed ACPI: setting ELCR to 0200 (from 0800) CPU0: Intel(R) Pentium(R) M processor 1300MHz stepping 05 SMP motherboard not detected. Local APIC not detected. Using dummy APIC emulation. Brought up 1 CPUs migration_cost=0 checking if image is initramfs... it is Freeing initrd memory: 5337k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfc96e, last bus=2 Setting up standard PCI resources ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 0880-08bf claimed by ICH4 GPIO PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 PCI: Transparent bridge - 0000:00:1e.0 PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') Please report the result to linux-kernel to fix this permanently PCI: Bus #07 (-#0a) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') Please report the result to linux-kernel to fix this permanently ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11 ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 13 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:02: ioport range 0x4d0-0x4d1 has been reserved pnp: 00:02: ioport range 0x800-0x805 could not be reserved pnp: 00:02: ioport range 0x808-0x80f could not be reserved pnp: 00:03: ioport range 0xf400-0xf4fe has been reserved pnp: 00:03: ioport range 0x806-0x807 has been reserved pnp: 00:03: ioport range 0x810-0x85f could not be reserved pnp: 00:03: ioport range 0x860-0x87f has been reserved pnp: 00:03: ioport range 0x880-0x8bf has been reserved pnp: 00:03: ioport range 0x8c0-0x8df has been reserved pnp: 00:08: ioport range 0x900-0x97f has been reserved PCI: Bridge: 0000:00:01.0 IO window: c000-cfff MEM window: fc000000-fdffffff PREFETCH window: e8000000-efffffff PCI: Bus 3, cardbus bridge: 0000:02:01.0 IO window: 0000d000-0000d0ff IO window: 0000d400-0000d4ff PREFETCH window: 30000000-31ffffff MEM window: f6000000-f7ffffff PCI: Bus 7, cardbus bridge: 0000:02:01.1 IO window: 0000d800-0000d8ff IO window: 0000dc00-0000dcff PREFETCH window: 32000000-33ffffff MEM window: f8000000-f9ffffff PCI: Bridge: 0000:00:1e.0 IO window: d000-efff MEM window: f6000000-fbffffff PREFETCH window: 30000000-34ffffff PCI: Enabling device 0000:02:01.0 (0000 -> 0003) ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 PCI: Enabling device 0000:02:01.1 (0000 -> 0003) ACPI: PCI Interrupt 0000:02:01.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered audit: initializing netlink socket (disabled) audit(1155272668.240:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 8 NET: Registered protocol family 20 Using IPI No-Shortcut mode ACPI wakeup devices: LID PBTN PCI0 USB0 USB1 USB2 USB3 MODM PCIE ACPI: (supports S0 S1 S3 S4 S5) Freeing unused kernel memory: 164k freed Loading, please input: AT Translated Set 2 keyboard as /class/input/input0 wait... Begin: Loading edevice-mapper: 4.6.0-ioctl (2006-02-17) initialised: [EMAIL PROTECTED] ssential drivers... ... Done. Begin: Running /scripts/iACPI: CPU0 (power states:nit-premount ... C1[C1] C2[C2] C3[C3] C4[C3]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM] (50 C) tg3.c:v3.59 (June 8, 2006) ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:0b:db:05:62:1d eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth0: dma_rwctrl[763f0000] dma_mask[64-bit] usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 11, io base 0x0000bf80 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 11, io base 0x0000bf40 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.2: irq 11, io base 0x0000bf20 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:1d.7: debug port 1 ehci_hcd 0000:00:1d.7: irq 11, io mem 0xf4fffc00 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected ICH4: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 ICH4: chipset revision 1 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:DMA, hdd:pio hda: HITACHI_DK23EB-40, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: HL-DT-STDVD-ROM GDR8081N, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 78140160 sectors (40007 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100) hda: cache flushes supported hda: hda1 hda2 hda3 hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, DMA Uniform CD-ROM driver Revision: 3.20 Done. Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Begin: Loading Rmd: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 AID modules ...md: bitmap version 4.39 md: raid1 personality registered for level 1 Success: loaded md: md0 stopped. module raid1. Dmd: bind<hda3> one. Begin: Assmd0: WARNING: hda2 appears to be on the same physical disk as hda3. True protection against single-disk failure might be compromised. embling all RAIDmd: bind<hda2> arrays ... raid1: raid set md0 active with 2 out of 2 mirrors mdadm: /dev/md/0 has been started with 2 drives. Success: success Done. Volume group "ep.root" not found /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 147: panic: not found Command failed: Error opening device: No such file or directory /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 196: cannot open /dev/mapper/crypt0: No such file /scripts/local-top/cryptroot: fstype not recognized, bad password or options? Command failed: Error opening device: No such file or directory /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 196: cannot open /dev/mapper/crypt0: No such file /scripts/local-top/cryptroot: fstype not recognized, bad password or options? Command failed: Error opening device: No such file or directory /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 196: cannot open /dev/mapper/crypt0: No such file /scripts/local-top/cryptroot: fstype not recognized, bad password or options?
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 2.5.3.git200608202239-1 We believe that the bug you reported is fixed in the latest version of mdadm, which is due to be installed in the Debian FTP archive: mdadm-udeb_2.5.3.git200608202239-1_i386.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-1_i386.udeb mdadm_2.5.3.git200608202239-1.diff.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.diff.gz mdadm_2.5.3.git200608202239-1.dsc to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.dsc mdadm_2.5.3.git200608202239-1_i386.deb to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1_i386.deb mdadm_2.5.3.git200608202239.orig.tar.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. martin f. krafft <[EMAIL PROTECTED]> (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Mon, 21 Aug 2006 00:25:22 +0100 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source i386 Version: 2.5.3.git200608202239-1 Distribution: unstable Urgency: low Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]> Changed-By: martin f. krafft <[EMAIL PROTECTED]> Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 381057 381303 382263 382389 382450 382480 382876 383688 383806 383891 Changes: mdadm (2.5.3.git200608202239-1) unstable; urgency=low . * Tracking upstream git releases. - now the --run switch behaves as stated in the manpage. This properly fixes #287415 - new version-1 partitionable arrays are now named X instead of _dX (e.g. 0 instead of _d0) for device names like md_dX. I actually think this is a bug and hope upstream will use dX (e.g. d0) instead in a future version. - we specify --symlink=no and thus disable the new feature to create /dev/mdX symlinks to /dev/md/X devices until the entire device node mess is cleared up. No need to introduce yet another complicating factor at this stage. * Instead of trying to do a whole lot of magic with respect to detecting RAID devices to start, mdadm from now on requires a valid mdadm.conf file to be installed. It still tries to do what it can, but there are no heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 . * Removed the zero-superblock warning because we require the user to sign off the configuration file anyway. * This also enables us to use mdadm.conf from the initial ramdisk and thus closes: #381303. * In case the user chooses to assemble all arrays from the initial ramdisk, use the new homehost feature of mdadm (closes: #381057). This will start only those arrays belonging to the local system, unless it is the first run on a system, in which case it will start all arrays and mark them as belonging to the local system. * Improved the debconf control script: integrated error messages into the frontends, and made it a bit smarter. Error messages can now be translated, and the script checks whether the user's choice is listed in the configuration file and only proceeds if it is, or the user chooses to ignore that it is not. * mkconf can now take a generate/force-generate parameter to write directly to /etc/mdadm/mdadm.conf. A second parameter specifies an alternate filename. * mkconf now outputs comments for the settings it suggests. * Removed all udev-related stuff. We must coexist with udev because there are setups that assemble arrays without mdadm, so the device nodes must be created by udev, if that is used. (closes: #382263, #382450, #383688, #383891, #383806, #382480) Staying at low urgency since these (RC) bugs only exist in unstable. * Now installs MD modules and mdadm/mdrun into initial ramdisk regardless of whether the hook script thinks there are devices to start. This was done to enable recovery from the initramfs shell. * Now uses 'MD' instead of 'RAID' consistently in all messages. * Now rebuilds initramfs for all installed kernels. * Now breaks the endless config loop only when the user does not see the question (see #381284, #381007). * Don't fail mdadm-raid when /dev is on a read-only filesystem (closes: #382876). * Updated debconf translations: - French by Florentin Duneau (closes: #382389). Files: 4b7ff47f67a0cb0b3e304de701a95d5d 760 admin optional mdadm_2.5.3.git200608202239-1.dsc 8006fce30bdac088dfb396410428377b 176469 admin optional mdadm_2.5.3.git200608202239.orig.tar.gz 11e33373fcaf6439cf70cf4c25d6a7d2 84117 admin optional mdadm_2.5.3.git200608202239-1.diff.gz 40fa2bfdc60770eb1f0e58105bcd6b24 194126 admin optional mdadm_2.5.3.git200608202239-1_i386.deb 1017b063b913f43dbe7e8f23dd427d03 68188 debian-installer optional mdadm-udeb_2.5.3.git200608202239-1_i386.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE6PP5IgvIgzMMSnURAndkAJ0a8BYhN+jfjkGuGtzG/phkZDfczgCgwjvg PhYHYrDEZtB7Y4lLtyLp6Bk= =FDVN -----END PGP SIGNATURE-----
--- End Message ---
