T61 won't hibernate with SSD in ultrabay

[stkris]

Is it possible that the ultrabay in my T61 is too old for (some of) the new SSD drives?

I used to have a HDD in the ultrabay and hibernate worked just fine. But after updating to a Corsair X256 i get errors stopping the hibernation process.

My laptop runs Debian Squeeze on kernel 2.6.32-5 (also tried older kernels).

After a failed hibernate the machine hangs with this message on screen:

Code: Select all

ata1.00: status: { DRDY ERR }
ata1.00: error: { IDNF }
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: FLUSH CACHE EXT
ata1.00: cmd ea/00:00: bla bla 00/a0 tag 0
res 51/10:00:af:32:cf/00:00:00:00:00/a0 Emask 0x01 (invalid argument)
ata1.00: status: { DRDY ERR }
ata1.00: error: { IDNF }
device_suspend(): scsi_bus_suspend+0x0/0x50 [scsi_mod] returns -5
PM: Device 0:0:0:0: failed to quiesce: error -5
PM: Restore failed, recovering.

And looking in the kern.log I see this:

Code: Select all

Aug 16 18:57:00 lap kernel: [ 175.690230] hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 16 18:57:00 lap kernel: [ 175.690237] hda: task_no_data_intr: error=0x10 { SectorIdNotFound }, LBAsect=1207959552, sector=18446744073709551615
Aug 16 18:57:00 lap kernel: [ 175.690299] PM: Device 0.0 failed to freeze: error -5
Aug 16 19:00:01 lap kernel: [ 1.406988] PM: Error -22 checking image file

[stkris]

I got the opportunity to test this with another SSD. A 240GB Patriot Inferno.

Unfortunately also this disk fails in the ultrabay (extra HD or CD in my laptop). With somewhat different errors:

Code: Select all

Aug 31 12:03:34 a kernel: [17252.910459] sd 3:0:0:0: [sdb] Unhandled error code
Aug 31 12:03:34 a kernel: [17252.910461] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Aug 31 12:03:34 a kernel: [17252.910463] sd 3:0:0:0: [sdb] CDB: Write(10): 2a 00 00 00 08 00 00 00 08 00
Aug 31 12:03:34 a kernel: [17252.910473] lost page write due to I/O error on sdb1
Aug 31 12:03:34 a kernel: [17252.910496] sd 3:0:0:0: [sdb] Unhandled error code
Aug 31 12:03:34 a kernel: [17252.910498] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Aug 31 12:03:34 a kernel: [17252.910500] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0d 68 98 80 00 00 08 00
Aug 31 12:03:34 a kernel: [17252.910527] sd 3:0:0:0: [sdb] Unhandled error code
Aug 31 12:03:34 a kernel: [17252.910529] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Aug 31 12:03:34 a kernel: [17252.910531] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0b 0c 0c 48 00 00 08 00

And when trying to restart the computer I often get a BIOS message something like:

Ultrabay Initialization Error. Press a key to continue.

If I do the drive is not there, and if I reboot it sometimes (one out of ten or so) boot normally with no errors in the logs.


Is there anybody out there who have managed to put a SSD in the ultrabay? On a T61?

[stkris]

I have been swapping the three drives around a bit. Quite interesting.

The Intel X-25M works fine in the ultrabay and the main bay. And hibernate works fine.

The Corsair X256 will not hibernate when in either bay. But other use seems to work fine.

The Patriot Inferno will not work in the ultrabay. Neither hibernate nor anything else. But in the main bay it seems to work fine. Including hibernating. So I think I'll swap my data - using the Patriot as a system disk and put /home on the Intel in the ultrabay.

So the conclusion must be that SSD + UltraBay is wery much up to the individual drive.

Anyone with a newer generation machine who have different results?

[smugiri]

There is a known problem with linux hibernate/suspend if a card is present in the SD card slot.

if you have one in there, try removing it and see if that helps.