K3B can't find CD/DVD Writer

Bug #160656 reported by tai133
28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
k3b (Ubuntu)
Expired
Medium
Unassigned
Nominated for Karmic by joe florez

Bug Description

Binary package hint: k3b

This is similar to #114471 which is now closed. My Plextor 719A DVD burner worked fine in K3B in Edgy. When I upgraded to Feisty this scenario occurred: When the machine is booted, it finds the drive and I can burn exactly one CD or DVD. Then it reports "No CD/DVD writer found." This condition remains until I reboot the computer after which I can again burn one disk.

I was hoping for a fix in Gutsy, but no joy. Exactly the same problem. dmesg output consists of this repeated many times:

[1604360.807844] ide: failed opcode was: unknown
[1604360.807848] hdc: drive not ready for command
[1604360.808382] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1604360.808388] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1604360.808391] ide: failed opcode was: unknown
[1604360.808393] hdc: drive not ready for command
[1604361.338872] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1604361.338883] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1604361.338887] ide: failed opcode was: unknown
[1604361.338891] hdc: drive not ready for command
[1604361.338932] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1604361.338936] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1604361.338939] ide: failed opcode was: unknown
[1604361.338941] hdc: drive not ready for command
[1604361.338968] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1604361.338973] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1604361.338975] ide: failed opcode was: unknown
[1604361.338977] hdc: drive not ready for command
[1604361.339024] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1604361.339028] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1604361.339031] ide: failed opcode was: unknown
[1604361.339033] hdc: drive not ready for command

Revision history for this message
ssus (dennis-miraden) wrote :

confirming the bug with the same dmesg-output. I'm using a Plextor 716A device, connected via pATA.
I'm using NeroLinux in the meanwhile, in which the problem doesn't occur. This also gives me the idea that the problem is strictly in k3b only, and that the bug is not a systemwide problem.

Revision history for this message
tai133 (tsines) wrote :

First of all, my drive is a 716A like that of ssus not a 719A as I originally stated. Second and most important, this problem appears to be FIXED in the latest version of K3b: 1.0.4-2ubuntu1~gutsy1

NeroLinux was starting to look pretty good, but K3b is the best and my application of choice for most burning. I'm currently on my 4th consecutive disk (3 DVDs and one CD) and everything is A-OK. Many thanks to the developers for addressing this issue.

Revision history for this message
tai133 (tsines) wrote :
Download full text (3.4 KiB)

OK - I spoke too soon. After the 4th disk K3b lost touch with the writer again. Here is the dmesg output:

[1167230.405850] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167230.405856] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167230.405859] ide: failed opcode was: unknown
[1167230.405861] hdc: drive not ready for command
[1167231.368552] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167231.368562] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167231.368566] ide: failed opcode was: unknown
[1167231.368570] hdc: drive not ready for command
[1167231.369052] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167231.369057] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167231.369060] ide: failed opcode was: unknown
[1167231.369063] hdc: drive not ready for command
[1167231.935806] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167231.935815] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167231.935819] ide: failed opcode was: unknown
[1167231.935823] hdc: drive not ready for command
[1167232.087240] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167232.087250] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167232.087254] ide: failed opcode was: unknown
[1167232.087258] hdc: drive not ready for command
[1167232.087298] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167232.087303] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167232.087306] ide: failed opcode was: unknown
[1167232.087308] hdc: drive not ready for command
[1167232.087335] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167232.087339] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167232.087342] ide: failed opcode was: unknown
[1167232.087344] hdc: drive not ready for command
[1167232.087389] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167232.087394] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167232.087397] ide: failed opcode was: unknown
[1167232.087399] hdc: drive not ready for command
[1167232.392012] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167232.392022] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167232.392026] ide: failed opcode was: unknown
[1167232.392030] hdc: drive not ready for command
[1167232.392521] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167232.392527] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167232.392530] ide: failed opcode was: unknown
[1167232.392532] hdc: drive not ready for command
[1167233.362902] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
[1167233.362911] hdc: status error: error=0x44 { AbortedCommand LastFailedSense=0x04 }
[1167233.362915] ide: failed opcode was: unknown
[1167233.362919] hdc: drive not ready for command
[1167233.36...

Read more...

Revision history for this message
Jan Schumacher (jansch) wrote :

Got exactly the same problem with latest version of k3b (1.0.4-2) and Plextor px-716A

Changed in k3b:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Florian Jensen (florian.jensen) wrote :

I have exactly the same problem. I am using an Samsung CD writer. My entire machine more or less freezes on the drive not ready for command messages.

Please fix this :)

Revision history for this message
smith (nicolas-dessoye) wrote :

I have exactly the same problem with a plextor DVD Writer. Have you try this ?

sudo rmmod cdrom ide_cd
sudo insmod cdrom ide_cd

Revision history for this message
J.O.L. (juanolopez) wrote : Similar, without AbortedCommand

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@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@jol-laptop:~$ sudo rmmod cdrom ide_cd
[sudo] password for jol:
ERROR: Module cdrom is in use by ide_cd

Any ideas?

Revision history for this message
J.O.L. (juanolopez) wrote : Nevermind

I'm not using the K3B application, so I'll have to post my problem elsewhere... :(

Revision history for this message
tai133 (tsines) wrote :

Actually, I'm starting to think that this is not only a K3B bug but a (K)Ubuntu system bug. I run a WinXP virtual machine on my Kubuntu box and it cannot find the writer either in cases when K3B cannot. This is in conflict with the report from ssus. ssus - are you still having success with NeroLinux?

Revision history for this message
ssus (dennis-miraden) wrote :

Yes i am, i'm running NeroLinux on every computer now, started to like the app :)

The funny thing is that i have this problem only on the computers with the Plextor 716A on board. The other one's, which use LG and Lite-On and even one which has an other Plextor drive (don't know the type) one's don't seem to have any problem. I can use K3B again and againwithout any problems...

Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 160656 and any other logs that are relevant for this particular issue.

Changed in k3b (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for k3b (Ubuntu) because there has been no activity for 60 days.]

Changed in k3b (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.