hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }

[Vidar]

System: Hardy Heron LTS
Affected cdrom drive: Philips DVD1648P1

Hardy Heron LTS is unable to boot from Philips dvd burner. When booting from another drive, the Philips drive is locked, and appear on the desktop with Blank disk icon, although the drive is empty.

These problems are reported under Bug #182996, where I was requested to file a new bug.
The fix suggested under Bug #182996, using sudo hdparm -w /dev/hdc and sudo hdparm -d1 /dev/hdc, makes the drive available for reading, but the drive can not be found by any burner programs.

Here is the output to /var/log/messages:

Apr 28 17:35:29 ubuntu kernel: [ 1219.166220] ide: failed opcode was: unknown
Apr 28 17:35:29 ubuntu kernel: [ 1219.166265] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
Apr 28 17:35:29 ubuntu kernel: [ 1219.166272] hdc: status error: error=0x00 { }
Apr 28 17:35:29 ubuntu kernel: [ 1219.166276] ide: failed opcode was: unknown
Apr 28 17:35:29 ubuntu kernel: [ 1219.166309] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
Apr 28 17:35:29 ubuntu kernel: [ 1219.166316] hdc: status error: error=0x00 { }
Apr 28 17:35:29 ubuntu kernel: [ 1219.166319] ide: failed opcode was: unknown
Apr 28 17:35:29 ubuntu kernel: [ 1219.166367] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
Apr 28 17:35:29 ubuntu kernel: [ 1219.166374] hdc: status error: error=0x00 { }
Apr 28 17:35:29 ubuntu kernel: [ 1219.166377] ide: failed opcode was: unknown

After running sudo hdparm -w /dev/hdc and sudo hdparm -d1 /dev/hdc:

Apr 28 17:36:39 ubuntu kernel: [ 1303.129931] hdc: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
Apr 28 17:36:39 ubuntu kernel: [ 1303.129947] hdc: status error: error=0x00 { }
Apr 28 17:36:39 ubuntu kernel: [ 1303.129951] ide: failed opcode was: unknown
Apr 28 17:36:39 ubuntu kernel: [ 1303.130969] hdc: DMA disabled
Apr 28 17:36:39 ubuntu kernel: [ 1303.178860] hdc: ATAPI reset complete
Apr 28 17:36:48 ubuntu kernel: [ 1314.675700] hdc: UDMA/33 mode selected

I have ran the following commands to inform about the system:

uname -a > uname-a.log
cat /proc/version_signature > version.log
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log

The resulting files are attached to this bug report.

[Vidar (vidarjb)]

When trying to boot from the Ubuntu 8.04 LTS cdrom in the Philips drive, the grub menu is shown. Shortly after, the boot process stops in a BusyBox shell.

[B-Flash-D (webmaster-feuerwehr-bobstadt)]

I've got exactly the same Problem with the same drive an the same Kernel Version!
The only difference is, that I have a 64 Bit Ubuntu.

[guggi (guggi)]

I confirm this bug, same situation with Plextor PX-740A and Linux 2.6.24-16-rt #1 SMP PREEMPT RT Thu Apr 10 15:15:40 UTC 2008 i686 GNU/Linux

[Fraser Doerksen (fraser-fraserjohn)]

I have the same problem, it's been present since the first Hardy alpha all the way through to 8.04 LTS. Drive worked normally under Gutsy.
The only drive on my single IDE channel is a BenQ EW-164B (same as DW-1640), the drive is visible in /dev/disk/by-id as ata-BENQ_DVD_DD_EW164B_J95B1U053C25049780PS
All SATA drives work normally. I've tried with the SATA controller in native-IDE, SATA-AHCI and RAID mode.
fstab gives an entry for scd0:
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
However, there's no device called scd0 in /dev
I replaced the scd0 entry with this:
/dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
with no good results.
In /dev I can see that hda does exist.
I'm getting random crashes, along with the messages about hda: drive not ready for command.
The fix suggested at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182996 will allow my DVD to eject and nothing further. No mounting of an inserted disc, nothing visible in Brasero.
dmesg gives identical output to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182996
If anybody can help please send an email and I'll send any logs you need.

[Waldgeist_dI (noway)]

Same problem for me with a BENQ DW-1620/Plextor 24/10/40A. I was not able to install a clean 8.04 with the standard live cd (32 bit). the text-based installer worked, with some funny messages concerning the drive. now 8.04 is up and running, albeit with the following glitches:

Switching to the terminals with Strg-Alt-1...6 brings the well-known error "hda: drive not ready for command". Login is impossible.

A blank cd is mounted (although the drive is empty).

Brasero won't start, not even giving error messages when invoked from the terminal. The still resulting process "brasero" is not killable, at least not by means of the system monitor.

The drive's eject button doesn't yield a result.

If I follow the above-mentioned suggestions about resetting the drive, all of these symptoms vanish, BUT: brasero won't offer the drive for recording. I took the Plextor out of my box, exchanged it for the BENQ and so forth, to no avail. After posting the requested logs I'm gonna take the Plextor out again and connect the BENQ as slave. I seem to remember such a suggestion.

[Waldgeist_dI (noway)]

version.log shows:

Ubuntu 2.6.24-17.31-generic.

PS
Sorry about the double post. FF hung.

[Waldgeist_dI (noway)]

I have to correct myself:

It's a BenQ DW1650, the Plextor's real name is PX-W2410TA.

It seems to me as if my box was affected by both Bug #182996 and this one here, because the Plextor drive is now working. To summarize my findings:

Plextor alone either as SLave or MAster: ok.
BenQ alone as MA: problem.
BenQ alone as SL: ok.

I hope that means something to someone ;)! Just for good measure I'll throw in the same logs as last time (from the boot with BenQ as SL).

[Waldgeist_dI (noway)]

The final test was to connect both drives again, but this time with the Plextor as MA and the BenQ as SL on the same cable. Guess what---it works! No error messages, both drives available for recording in Brasero.

[Waldgeist_dI (noway)]

I am rather confused. Turned on my ubuntu box yersterday to be told there are some 92 update available. After starting the automatic update there was a message "Couldn't update all packages, this may due to a pre-release version ... bla bla bla". I was offered a partial update/upgrade, that didn't work out at all. There was a problem with the calculation of the available packages. The message stated that this is possibly a transitory problem, please try again later. Later I tried again without the partial update/upgrade. This time i wanted to update only these packages that WERE available.

After that the drive problem reappered!!! Now, however, it's the Plextor (now connected as master) that won't be shown in Brasero and which is unavailable!!!

[Bill Gjestvang (bgjestvang)]

I also have a BENQ DW1620 that doesn't work under 2.6.24-17-generic or 2.6.24-17-server, which works fine under gutsy's 2.6.22-14-* kernels.

[Cesare Falco (c.falco)]

OK, just to report I have the same problem with a Philips DVDR1640P, which worked until I upgraded my HD to a SATA one, putting the dvd burner as Master on channel 0 (i.e. it was /dev/hdb, now it's /dev/hda).

[innominate (natenate)]

I also have the same problem. Drive is a ATAPI DVD DD 8X16X8X16
sudo hdparm -w /dev/hdc
sudo hdparm -d1 /dev/hdc
stops the errors but the drive will not show up in Brasero

[Andrew Ainsworth (andrew-ainsworth)]

I have had exactly the same problem with a BENQ DVD DD DW1620 drive and haven't been able to find a proper fix, however based on what Waldgeist_dl said I just set the drive to slave (it's the only ide device in my computer) and everything is now working fine. No mounted blank disc with no media present, writing discs and blanking dvd-rw discs is working fine with Brasero and the eject button works :).

sudo hdparm -w /dev/hda
sudo hdparm -d1 /dev/hda

Those commands worked in as much as I could read discs, but not writing, the same as everyone else here I guess.

[Vidar (vidarjb)]

I have succeeded in installing Ubuntu 8.04 on the affected computer, and it has detected the dvd burner correctly. This is what I did:

Use the following kernel parameter when booting from the Ubuntu 8.04 cdrom: all_generic_ide

Here is what I did:
1. Boot from the Ubuntu cdrom
2. At the first screen, press "ESC" to leave the menu.
3. You get a warning, stating that you are leaving the graphical boot menu, click OK to do this.
4. At the prompt, enter "live all_generic_ide"

[innominate (natenate)]

Finally got fed up enough with this that i went into the case and switched the master and slave drive around, and its working now.

Of Note: the drive that was causing the problem was missing its jumper. It had three slots one master one slave one cable select, so jumper off was not a valid option. I put the jump for that one on to the slave pins and moved the jumper on the other to be master.

Also I noticed that if i waited a while after starting to do the:

sudo hdparm -w /dev/hda
sudo hdparm -d1 /dev/hda

commands the computer would occasionally lock up when i executed the first command.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[raminaghrobis (raminaghrobis)]

Hi, same problem same symptoms.

I would be grateful if someone could explain what these slave and master drives are, and how to switch them round.

Thanks

[raminaghrobis (raminaghrobis)]

I just tried sudo hdparm -w /dev/hdc, sudo hdparm -d1 /dev/hdc. It works but only for the first CD, strangely. Is there some way of making the changes permanent or something?

[Leann Ogasawara (leannogasawara)]

Hi raminaghrobis,

Can you clarify that you are seeing this same issue with the 2.6.27 kernel? If so, can you attach an your dmesg output for 2.6.27 which captures these errors? Thanks.

[Vidar (vidarjb)]

Testing with Ubuntu 8.10 Alpha 5:

The drive is listed in Nautlus, but can't be mounted. Attempting to mount/umount/eject any IDE drive - HD's or cdrom drives - gives a dialogue box with this error message:

Unable to eject CD-RW/DVD±RW Drive
DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound: The given drive was not found

[Vidar (vidarjb)]

After a reboot, where I passed the "all-generic-ide" as a kernel boot parameter, all drives works perfectly. They can be mounted, accessed and umounted without any problems.

Here are the output from
uname -a > uname-a.log
cat /proc/version_signature > version.log
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log

[Bert Van de Poel (bhack)]

I sometimes have similar problems with my samsung drive but only sporadically, when I type sudo mount /dev/scd0 and then CTRL+C it and then do "sudo eject" it opens again.

[raminaghrobis (raminaghrobis)]

Has anyone upgraded to 8.10? Does it fix the bug?

[Vidar (vidarjb)]

I have upgraded to 8.10. As far as I am concerned, the bug is fixed here :-))

Vidar

[Leann Ogasawara (leannogasawara)]

Thanks Vidar. Since you are the original bug reporter I'm marking this "Fix Released" for Intrepid. Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Peter Schwenke (bluetoad)]

This bug still exists on Hardy. Hardy is LTS so it would be nice if it was fixed. This change
 still remains in the kernel right through to the 2.6.29 kernel. The code has changed significantly for 2.6.30.

Upstream commit f367bed005b06db7067fc378a5f2253fac54e5d9 reverts the commit which causes this bug (b140b99c413ce410197cfcd4014e757cd745226a)

The fix worked for me.

[Stefan Bader (smb)]

I am currently looking how this could apply for SRU. I probably sounds overly cautious but as the patch comment suggest the reversion might have downsides. So maybe we can do the following patch which would leave the default the same but adds an option "ide=masterfirst" for Hardy kernels to get the other identify direction.
I compiled kernels with that patch and placed them at http://people.ubuntu.com/~smb/bug223780/
Can someone check whether this works as intended. So with that kernel but without ide=masterfirst the drive should fail as before but with it, it should be ok. Thanks

[Stefan Bader (smb)]

I build a new set of test kernels against the current Hardy kernel. However, if this really should get fixed, I need someone who is affected by the problem to report how that proposed fix works. See my above post on how to activate the alternate setting and where to get the test kernel. Thanks!

[Stefan Bader (smb)]

Since there was no feedback for a really long time, I am closing this won't fix. If there actually is still need for it, feel free to re-open.