Comment 11 for bug 103006

I have the same problem and it seems to be related to adding a drive to a table. I disabled the splash screen at booting and followed the text on screen to see where the boot process times-out. It waits approx 10 minutes at the position below (excerpt from var/log/messages)

jul 20 21:37:20 max-linux kernel: [ 47.937520] input: ImPS/2 Logitech Wheel Mouse as /class/input/input3
Jul 20 21:37:20 max-linux kernel: [ 47.964425] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 19
Jul 20 21:37:20 max-linux kernel: [ 47.964488] ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKD] -> GSI 19 (level, high) -> IRQ 20
Jul 20 21:37:20 max-linux kernel: [ 48.278784] device-mapper: table: device /dev/mapper/1ATA_WDC_WD2000JD-00GBB0_WD-WMAEP1588874p1 too small for target
Jul 20 21:37:20 max-linux kernel: [ 48.278924] device-mapper: ioctl: error adding target to table
Jul 20 21:37:20 max-linux kernel: [ 48.279721] device-mapper: table: device /dev/mapper/1ATA_WDC_WD2000JD-00GBB0_WD-WMAEP1588874p1 too small for target
Jul 20 21:37:20 max-linux kernel: [ 48.279852] device-mapper: ioctl: error adding target to table
Jul 20 21:37:20 max-linux kernel: [ 227.781290] device-mapper: table: device /dev/mapper/1ATA_WDC_WD2000JD-00GBB0_WD-WMAEP1588874p1 too small for target
Jul 20 21:37:20 max-linux kernel: [ 227.781432] device-mapper: ioctl: error adding target to table
Jul 20 21:37:20 max-linux kernel: [ 227.805638] device-mapper: table: device /dev/mapper/1ATA_WDC_WD2000JD-00GBB0_WD-WMAEP1588874p1 too small for target
Jul 20 21:37:20 max-linux kernel: [ 227.805769] device-mapper: ioctl: error adding target to table
Jul 20 21:37:20 max-linux kernel: [ 246.366164] lp0: using parport0 (interrupt-driven).

the curious thing is that when i boot dapper LTS it does not have a problem. Is there a way to re-initiate the hardware table?