[Bug 160656] Similar, without AbortedCommand

[J.O.L.]

Mine is very similar, but I get error code 40 instead of 44:

[  229.744000] hda: status error: error=0x40 { LastFailedSense=0x04 }
[  229.744000] ide: failed opcode was: unknown
[  229.744000] hda: drive not ready for command
[  231.744000] hda: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[  231.744000] hda: status error: error=0x40 { LastFailedSense=0x04 }
[  231.744000] ide: failed opcode was: unknown
[  231.744000] hda: drive not ready for command
[  231.744000] hda: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[  231.744000] hda: status error: error=0x40 { LastFailedSense=0x04 }
[  231.744000] ide: failed opcode was: unknown
[  231.744000] hda: drive not ready for command
[  231.744000] hda: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
...repeats many times...

I get the "drive not ready for command" message on the screen many times consecutively just before the login window appears.  The above appears in dmesg after I log in.
I am running Linux Mint based on Gutsy, and I have what I believe to be a Matshita DVD/CD-RW drive.  The Audio Disc icon appears on the Desktop, but the tracks have negative times.  When I try to unmount, says it is not mounted.  When I try to mount, it gives the following output:

jol at jol-laptop:~$ mount /dev/hda
mount: block device /dev/hda is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hda,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

My fstab has the following as the last line:
/dev/hda        /media/cdrom0   udf,iso9660    rw,user,noauto,exec   0           0

The rmmod didn't work either:
jol at jol-laptop:~$ sudo rmmod cdrom ide_cd
[sudo] password for jol:
ERROR: Module cdrom is in use by ide_cd

Any ideas?

-- 
K3B can't find CD/DVD Writer
https://bugs.launchpad.net/bugs/160656
You received this bug notification because you are a member of Ubuntu
Burning Team, which is a bug contact for k3b in ubuntu.