T42 Randomly Ejects Multiburner Tray?

[Milintellect]

I've had my T42 (2734-3VU) for over a year now and in the past few months it has picked up a bad habit. It ejects the multiburner tray whenever it pleases. It is the Matshita UJ-812 that came stock with the machine. Noteably, it seems to do it most frequently after being woken up from a suspended state or after there has been considerable movement to the machine (i.e. passing the machine to another person, Active Protection suspends the HD, etc...)

To answer the obvious question first, I am sure that I am not accidentally pressing the eject button. I thought that for the first month but I am now certain that is not the case. Also, it may be important to note that I had a system board failure a few months back which required the replacement of the whole board. This problem existed before the swap and, obviously, exists afterward.

Any ideas folks? Do I need to take it to a shaman?

[draco2527]

There is a mechanical latch inside the drive, some of the drives are know to fail and it will cause it to eject on its own.

Removed it from the laptop and move the drive around (up, down, left, right). If the drive opens up, then the lath is defective.

[Milintellect]

Thanks for the reply, but unfortunately that's not it. The drive typically spins up a few times like it is trying to read a disk (I also get a spinning CD image next to my cursor on the screen) and then it ejects itself. Any thoughts?

[afd]

Did you check to see if you have the latest firmware?

http://www-307.ibm.com/pc/support/site. ... MIGR-57083

[meeotch]

I just re-formatted & clean installed XP on my t42p, and I've been getting the "random eject" thing as well. It seems to happen when it wakes up from a hibernate state, primarily.

mitch

[bontistic]

As afd said, you should check if you have the latest firmware. Or you could check if you have background applications (like Record Now) that is trying to make you burn a disc (or backup to a disc). Or you could try another ultrabay drive to check if the problem persists with that drive as well (hopefully same model as yours but not neccessarily)

[meeotch]

Firmware is up to date, nothing running in the background (this is a fresh OS install). I don't remember noticing the problem before I did the fresh install, in fact. Also, it's present with both k104 and k105 firmware.

It definitely seems to be related to resume-from-hibernate, or possibly changes in the state/number of USB peripherals.