LinHES Forums
http://forum.linhes.org/

Log files fill-up: hdb: drive not ready for command
http://forum.linhes.org/viewtopic.php?f=6&t=18812		 Page 1 of 1
Author:  BluesBrian [ Sun Aug 17, 2008 8:59 pm ]
Post subject:  Log files fill-up: hdb: drive not ready for command
I can't seem to locate the config file for the program that's causing this.. (I'm not sure what program is doing thing .. but I have a hint.)

Here are some log entries:

Note that the KM machine that has this problem has a SATA drive as /dev/sda (no PATA drives)

/var/log/kern.log
Code:
Aug 17 19:32:44 mythbox kernel: ide: failed opcode was: unknown
Aug 17 19:32:44 mythbox kernel: hdb: drive not ready for command
Aug 17 19:32:44 mythbox kernel: hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }


/var/log/syslog
Code:
Aug 17 19:36:09 mythbox kernel: ide: failed opcode was: unknown
Aug 17 19:36:09 mythbox kernel: hdb: drive not ready for command
Aug 17 19:36:09 mythbox kernel: hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }


/var/log/messages
Code:
Aug 17 19:36:57 mythbox kernel: ide: failed opcode was: unknown
Aug 17 19:36:57 mythbox kernel: hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }


Code:
ps -ef |grep hdb


Code:
root      3547  3522  0 Aug03 ?        00:02:35 hald-addon-storage: polling /dev/hdb (every 2 sec)


My other KM Machine: has a PATA drive as /dev/hda (no problem shows in the log, except there is no /dev/hdc on this machine)
Code:
ps -ef |grep hald

Code:
... hald-addon-storage: polling /dev/hdc (every 2 sec)


Any ideas?
Author:  manicmike [ Sun Aug 17, 2008 11:03 pm ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
BluesBrian wrote:
I can't seem to locate the config file for the program that's causing this.. (I'm not sure what program is doing thing .. but I have a hint.)
Any ideas?


Are you sure you don't have a PATA DVD writer? If you haven't, have you ever had one? This error usually (always) occurs when your IDE DVDRW (yours is connected to the slave of the primary IDE controller from the logs) fails to communicate with the controller.

If instead you have upgraded to a SATA drive, you just need to point the symlinks for /dev/dvd* to the new location for your drive (usually /dev/sdb). Do an ls -l /dev/dvd* and see what it says.

If you do have an IDE optical drive, looks like it's buggered.

To make the symlinking permanent, edit /etc/udev/rules.d/70-persistent-cd.rules

Cheers

Mike

P.S. I was just being polite: I'm almost 100% sure you have an IDE optical drive.
Author:  BluesBrian [ Sun Aug 17, 2008 11:47 pm ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
manicmike wrote:
Are you sure you don't have a PATA DVD writer? If you haven't, have you ever had one? This error usually (always) occurs when your IDE DVDRW (yours is connected to the slave of the primary IDE controller from the logs) fails to communicate with the controller.

If instead you have upgraded to a SATA drive, you just need to point the symlinks for /dev/dvd* to the new location for your drive (usually /dev/sdb). Do an ls -l /dev/dvd* and see what it says.

If you do have an IDE optical drive, looks like it's buggered.

To make the symlinking permanent, edit /etc/udev/rules.d/70-persistent-cd.rules

Thanks Mike.. of course, you're totally right! I've got an IDE/PATA DVD writer..
Code:
ls -l /dev/dvd*
.. Aug 3 12:29 /dev/dvd -> hdb
.. Aug 3 12:29 /dev/dvdrw -> hdb

hmmm.. I don't have a /etc/udev/rules.d/70-persistent-cd.rules file/link.
How do I go about fixing this? (This is just a bit beyond my experience!)

Thanks!

// Brian
Author:  manicmike [ Mon Aug 18, 2008 5:40 am ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
BluesBrian wrote:
Thanks Mike.. of course, you're totally right! I've got an IDE/PATA DVD writer..
Code:
ls -l /dev/dvd*
.. Aug 3 12:29 /dev/dvd -> hdb
.. Aug 3 12:29 /dev/dvdrw -> hdb

hmmm.. I don't have a /etc/udev/rules.d/70-persistent-cd.rules file/link.
How do I go about fixing this? (This is just a bit beyond my experience!)

Thanks!

// Brian


You don't need the udev file, since the symlink is correct. Just replacing your DVD writer will fix the problem, since the DVD writer appears to be broken.

If you replace it with a SATA drive, just check that the symlink points to it after booting.

Mike
Author:  BluesBrian [ Tue Aug 19, 2008 8:00 am ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
manicmike wrote:
You don't need the udev file, since the symlink is correct. Just replacing your DVD writer will fix the problem, since the DVD writer appears to be broken.

If you replace it with a SATA drive, just check that the symlink points to it after booting.

Mike
Seems like the Microsoft solution works again.. rebooting the system seems to have cleared the error. Significantly cheaper than randomly purchasing a new DVD drive :!: (Of course, I will test the drive to make sure it functions.)
Code:
uptime
06:54:51 up  8:42,  1 user,  load average: 1.07, 1.02, 1.00
Author:  manicmike [ Tue Aug 19, 2008 3:38 pm ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
Good luck with that. The error "drive not ready" is a hardware error, so it's very likely that problems will creep back in and slowly get worse as the drive dies. DVD drives seem more susceptible to the law of impermanence than any other component.

Mike
Author:  BluesBrian [ Thu Aug 21, 2008 5:48 pm ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
manicmike wrote:
Good luck with that. The error "drive not ready" is a hardware error, so it's very likely that problems will creep back in and slowly get worse as the drive dies. DVD drives seem more susceptible to the law of impermanence than any other component.
Thanks again, Mike. .. and yeah, I think you're right all around. I was hoping for better. Fortunately, a replacement is only around $25.. except that I actually use the drive someplace between "never" and "seldom". One would hope that "Sony" was built better than "brand x".
I wish there was some diagnostic tool that could determine .. that it's not just a bad cable.. (ok, I'm still dreaming.)
Here's my follow-up:
1. reboot (as I described above)
2. test rip music CD. worked OK.
3. after about a day, the "drive not ready" came back.
4. shutdown system & insert IDE drive (hoping that master with slave would work better.)
5. after about a day, the "drive not ready" came back.

Amusing postscript: googling on "dvd drive not ready" gets a hit on this thread! :D
Author:  manicmike [ Thu Aug 21, 2008 10:44 pm ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
BluesBrian wrote:
I wish there was some diagnostic tool that could determine .. that it's not just a bad cable.. (ok, I'm still dreaming.)


No you aren't. You can test by.... replacing the cable ;-)

Going by your more recent information, it's almost certainly not the cable. Cables don't need to be reset, but drives do.

I'd spend the $25 and save myself the grief. You'll also get a SATA drive, and relieve the CPU of some work.

With the drive brand, I haven't had an ASUS fail yet. I'm allergic to giving Sony money so can't tell you anything there.

Cheers

Mike
Author:  BluesBrian [ Fri Aug 22, 2008 12:17 am ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
manicmike wrote:
Cables don't need to be reset, but drives do.

It took a while for the denial to subside.. but I've come to that conclusion myself. (I have had CD drives belly up before.)
manicmike wrote:
I'd spend the $25 and save myself the grief. You'll also get a SATA drive, and relieve the CPU of some work.

Totally makes sense to go SATA. when I put together this box, I thought that I would/could stick with PATA.. (That's where all my experience was.) but earlier KM would not install on the PATA drive, so it was an "emergency switch" to SATA.. and now, I get it.
manicmike wrote:
With the drive brand, I haven't had an ASUS fail yet.

I have an ASUS P5P800 motherboard that's deader than a mackerel. It won't boot to BIOS. (Not a KM box.) but I'm willing to try an ASUS drive.
manicmike wrote:
I'm allergic to giving Sony money so can't tell you anything there.

I understand that concept. At the time, Sony had the edge on DVD-R, DVD-RW, +R and +RW and Double Layer .. not so anymore.
Author:  BluesBrian [ Sun Aug 31, 2008 12:39 am ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
manicmike wrote:
I'd spend the $25 and save myself the grief. You'll also get a SATA drive, and relieve the CPU of some work.

Got it! .. but all that works is "eject". (Attempts to use either CD or DVD under Myth control jumps back to the menu.)
/etc/fstab wrote:
/dev/cdrom /cdrom auto defaults,ro,user,noexec,noauto 0 0

Should that be updated? .. or is there something else missing?
/var/log/messages wrote:
ata4.00: ATAPI: PIONEER DVD-RW DVR-215D, 1.13, max UDMA/66
ata4.00: configured for UDMA/66
ata4: EH pending after completion, repeating EH (cnt=4)
scsi 3:0:0:0: CD-ROM PIONEER DVD-RW DVR-215D 1.13 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa
/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20

ls -l /dev wrote:
lrwxrwxrwx 1 root root 4 Aug 30 23:04 cdrom1 -> scd0
lrwxrwxrwx 1 root root 4 Aug 30 23:04 cdrw1 -> scd0
lrwxrwxrwx 1 root root 4 Aug 30 23:04 dvd1 -> scd0
lrwxrwxrwx 1 root root 4 Aug 30 23:04 dvdrw1 -> scd0
brw-rw---- 1 root cdrom 11, 0 Aug 30 23:04 scd0
lrwxrwxrwx 1 root root 4 Aug 30 23:04 sr0 -> scd0
Author:  manicmike [ Mon Sep 01, 2008 7:46 am ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
BluesBrian wrote:
/etc/fstab wrote:
/dev/cdrom /cdrom auto defaults,ro,user,noexec,noauto 0 0

Should that be updated? .. or is there something else missing?

Yes, you need to edit the udev rules fine I mentioned earlier. Make sure that /dev/cdrom (and /dev/dvdrw etc.) points to the new drive. Reboot when you're happy that it will work (to test if you did it right), and all the symlinks should be correct when it comes back.

Mike
Author:  BluesBrian [ Mon Sep 01, 2008 11:42 am ]
Post subject:  Re: Log files fill-up: hdb: drive not ready for command
manicmike wrote:
Yes, you need to edit the udev rules fine I mentioned earlier. Make sure that /dev/cdrom (and /dev/dvdrw etc.) points to the new drive. Reboot when you're happy that it will work (to test if you did it right), and all the symlinks should be correct when it comes back.
Mike

It's even easier .. Debian created all of this for me, so the core OS is "Jake":
ls -l /dev/dvd* wrote:
lrwxrwxrwx 1 root root 4 Aug 30 23:04 /dev/dvd1 -> scd0
lrwxrwxrwx 1 root root 4 Aug 30 23:04 /dev/dvdrw1 -> scd0

ls -l /dev/cd* wrote:
lrwxrwxrwx 1 root root 4 Aug 30 23:04 /dev/cdrom1 -> scd0
lrwxrwxrwx 1 root root 4 Aug 30 23:04 /dev/cdrw1 -> scd0

cat /etc/udev/rules.d/z25_persistent-cd.rules wrote:

# This file was automatically generated by the /lib/udev/write_cd_rules
# program, probably run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line
# and set the $GENERATED variable.

# SONY_DVD_RW_DRU-840A (pci-0000:02:00.1-ide-0:1)
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:02:00.1-ide-0:1", SYMLINK+="cdrom", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:02:00.1-ide-0:1", SYMLINK+="cdrw", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:02:00.1-ide-0:1", SYMLINK+="dvd", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:02:00.1-ide-0:1", SYMLINK+="dvdrw", ENV{GENERATED}="1"
# DVD-RW_DVR-215D (pci-0000:00:1f.2-scsi-1:0:0:0)
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="cdrw1", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="dvd1", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="dvdrw1", ENV{GENERATED}="1"

It took a while, but looks like the "persistent-cd.rules" is a different name than your earlier hint.
The other thing that I see is that the device is now:
Code:
/dev/dvd1
/dev/dvdrw1
/dev/cdrom1
/dev/cdrw1

I comment out the old Sony DVD drive and change the device number on the new drive (delete the "1") so the existing references in KM work again. and reboot. Now the dev names are as expected for KM.
ls -l /dev/dvd* wrote:
lrwxrwxrwx 1 root root 4 Sep 1 09:41 /dev/dvd -> scd0
lrwxrwxrwx 1 root root 4 Sep 1 09:41 /dev/dvdrw -> scd0

ls -l /dev/cd* wrote:
lrwxrwxrwx 1 root root 4 Sep 1 09:41 /dev/cdrom -> scd0
lrwxrwxrwx 1 root root 4 Sep 1 09:41 /dev/cdrw -> scd0

Works! :D Thanks Mike :!:
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/