Comment 2 for bug 139748

I have similar (but worse) experience:
I use feisty on a laptop, I have a Samsung Sata2 drive formatted as ext3 in an external usb/esata box. When connected via usb there are no problems. When connected as esata via Delock Express Card the following happens:
When hotplugging it is not detected at all ('lshal -m' shows nothing related to un-/plugging).
When I cold start with the drive connected I see in '/var/log/dmesg' a lot of lines referring to 'ata1' and 'sda1' they all seem to indicate that the boot process tries to get access to the drive but fails. My internal drive which is normally mounted as sda is now mounted as sdb.
Will posting my dmesg with and without connected drive help? If so I can do that.