dmesg showed ide: failed opcode was: 0xe for my old PLEXTOR CD-R PX-W1210A burner drive.
Ant
Ever since I swapped hardwares (never had a CD burner drive in Debian)
for my old Debian OS (always updated daily with apt-get commands) about
a month ago. I noticed this in my boot up and dmesg:
...
[ 4.030265] usbhid: v2.6:USB HID core driver
[ 4.702426] hdd: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
[ 4.758393] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 4.758681] hdc: UDMA/33 mode selected
[ 4.759258] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 4.759348] hdd: MWDMA2 mode selected
[ 4.759523] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 4.759523] ide1 at 0x170-0x177,0x376 on irq 15
...
[ 38.742513] lo: Disabled Privacy Extensions
[ 49.571146] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
[ 49.571334] hdd: task_in_intr: error=0x04 { AbortedCommand }
[ 49.571472] ide: failed opcode was: 0xec
[ 51.131667] eth0: no IPv6 routers present
...
# /sbin/hdparm /dev/hdc
/dev/hdc:
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
# /sbin/hdparm /dev/hdd
/dev/hdd:
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
$ uname -a
Linux FooBar 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux
Is hdd something to worry about? I was able to do quick reads and burns
an old CD-RW in k3b as tests.
Here are my detailed computer specifications: AMD Athlon 64 X2 (dual
core) 939 4600+ CPU (using a Thermaltake Silent Boost K8 A1838 model),
MSI K8N NEO4-F (MS-7125; PCB v3.0) motherboard (NVIDIA nForce4), EVGA
GeForce 8800 GT (512 MB; PCIe; NVIDIA), Enlight 7237-ATX mid-tower case;
Fortron FSP650-80GLC PSU (650 watts), two case 80mm case fans, Seagate
Barracuda 7200.7 (ST380011A; 7200 RPM; 80 GB) HDD, an IDE Quantum
Fireball Plus LM 15 GB, Toshiba DVD-ROM SD-M1612 Rev. B 16X/48X
ATAPI/IDE drive, Plextor PX-W1210 PlexWriter (12/10/32A; IDE), 3.5"
floppy disk drive, and an Intel InBusiness 10/100 (82559) NIC. Running
Debian (Linux) OS (Kernel v2.6.26-...-686).
This desktop machine is connected to a Belkin Omni Cube (4-port; PS/2
and VGA) to share a 19" Samsung SyncMaster 931BF LCD TFT monitor (4:3
aspect ratio and 1280x1024 native screen resolution), a Dell 104-key
PS/2 SK-8110 keyboard, and a three-buttons (middle is a wheel) PS/2
eMachines mouse. Both PCs and monitor are connected to APC Back-UPS XS
BX1500's battery outlets.
Thank you in advance. :)
--
"In an ant colony, dew is a flood." --Afghan
/\___/\
/ /\ /\ \ Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please nuke ANT if replying by e-mail.
( )
Ant
...
[3181987.614211] martian destination 0.0.0.0 from 192.168.0.1, dev eth0
[3181987.614211] martian destination 0.0.0.0 from 192.168.0.1, dev eth0
[3181987.614211] martian destination 0.0.0.0 from 192.168.0.1, dev eth0
[3181987.614211] martian destination 0.0.0.0 from 192.168.0.1, dev eth0
[3187755.279127] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
[3187755.279127] hdd: task_in_intr: error=0x04 { AbortedCommand }
[3187755.279127] ide: failed opcode was: 0xec
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 280003 182344 83203 69% /
tmpfs 1558376 0 1558376 0% /lib/init/rw
udev 10240 120 10120 2% /dev
tmpfs 1558376 0 1558376 0% /dev/shm
/dev/hda5 14421344 2043616 11645168 15% /home
/dev/hda6 4807056 3413816 1149056 75% /usr
/dev/hda7 964500 463384 452120 51% /var
/dev/hda8 964500 23628 891876 3% /tmp
/dev/hda9 4807056 189884 4372988 5% /usr/local
/dev/hda11 47383396 37860112 7116348 85% /extra
/dev/hda12 918322 16452 852874 2% /others
/dev/hdb1 14436960 1865872 11837724 14% /storage
# /sbin/hdparm /dev/hdd
/dev/hdd:
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
I wonder if the error is caused by smarttoolsmon package upgrade
(smartmontools_5.38-3_i386) I got this morning via apt-get upgrade.
> # /sbin/hdparm /dev/hdc
> # /sbin/hdparm /dev/hdd
"Cheerios: Hula-hoops for ants." --unknown
Huibert Bol
> Ever since I swapped hardwares (never had a CD burner drive in Debian)
> for my old Debian OS (always updated daily with apt-get commands) about
> a month ago. I noticed this in my boot up and dmesg:
>
> ...
> [ 4.702426] hdd: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
> ...
> [ 49.571146] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
> [ 49.571334] hdd: task_in_intr: error=0x04 { AbortedCommand }
> [ 49.571472] ide: failed opcode was: 0xec
> ...
> Is hdd something to worry about?
No. COMMAND ABORTED is the proper response wrt an IDENTIFY DRIVE (ECh)
command on an ATAPI device.
--
Huibert
"The Commercial Channel! All commercials all the time.
An eternity of useless products to rot your skeevy little mind, forever!"
-- Mike the TV (Reboot)
Ant
> > for my old Debian OS (always updated daily with apt-get commands) about
> > a month ago. I noticed this in my boot up and dmesg:
> >
> > ...
> > [ 4.702426] hdd: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
> > ...
> > [ 49.571146] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
> > [ 49.571334] hdd: task_in_intr: error=0x04 { AbortedCommand }
> > [ 49.571472] ide: failed opcode was: 0xec
> > ...
> > Is hdd something to worry about?
> No. COMMAND ABORTED is the proper response wrt an IDENTIFY DRIVE (ECh)
> command on an ATAPI device.
What is "wrt"? If this is normal, how come my TOSHIBA DVD-ROM SD-M1612
drive (hdc) didn't say the same thing?
--
"Cheerios: Hula-hoops for ants." --unknown
Lew Pitcher
wrote:
>> > Ever since I swapped hardwares (never had a CD burner drive in Debian)
>> > for my old Debian OS (always updated daily with apt-get commands) about
>> > a month ago. I noticed this in my boot up and dmesg:
>> >
>> > ...
>> > [ 4.702426] hdd: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
>> > ...
>> > [ 49.571146] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete
>> > [ Error } 49.571334] hdd: task_in_intr: error=0x04 { AbortedCommand }
>> > [ 49.571472] ide: failed opcode was: 0xec
>> > ...
>> > Is hdd something to worry about?
>
>> No. COMMAND ABORTED is the proper response wrt an IDENTIFY DRIVE (ECh)
>> command on an ATAPI device.
>
> What is "wrt"?
"with respect to"
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------
Huibert Bol
>> > Ever since I swapped hardwares (never had a CD burner drive in Debian)
>> > for my old Debian OS (always updated daily with apt-get commands) about
>> > a month ago. I noticed this in my boot up and dmesg:
>> >
>> > ...
>> > [ 4.702426] hdd: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
>> > ...
>> > [ 49.571146] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
>> > [ 49.571334] hdd: task_in_intr: error=0x04 { AbortedCommand }
>> > [ 49.571472] ide: failed opcode was: 0xec
>> > ...
>> > Is hdd something to worry about?
>
>> No. COMMAND ABORTED is the proper response wrt an IDENTIFY DRIVE (ECh)
>> command on an ATAPI device.
>
> What is "wrt"? If this is normal, how come my TOSHIBA DVD-ROM SD-M1612
> drive (hdc) didn't say the same thing?
Fair question. But without knowing what program is responsible it's
hard to tell.
If it's smartd (as you conjectured in a previous posting), you could
take a look at /etc/smartd.conf and see which drives it is monitoring.
Bottom line, the error is inconsequential. Just ignore it.
Ant
> >> command on an ATAPI device.
> >
> > What is "wrt"? If this is normal, how come my TOSHIBA DVD-ROM SD-M1612
> > drive (hdc) didn't say the same thing?
> Fair question. But without knowing what program is responsible it's
> hard to tell.
> If it's smartd (as you conjectured in a previous posting), you could
> take a look at /etc/smartd.conf and see which drives it is monitoring.
> Bottom line, the error is inconsequential. Just ignore it.
I think I never touched that file:
$ ls -all /etc/smartd*
-rw-r--r-- 1 root root 6810 2008-07-24 10:08 /etc/smartd.conf
$ cat /etc/smartd.conf
# /etc/smartd.conf
# Configuration file for smartd. Use "man smartd.conf" for more information.
# Home page is: http://smartmontools.sourceforge.net
# smartd will re-read the configuration file if it receives a HUP
# signal
# The file gives a list of devices to monitor using smartd, with one
# device per line. Text after a hash (#) is ignored, and you may use
# spaces and tabs for white space. You may use '\' to continue lines.
# You can usually identify which hard disks are on your system by
# looking in /proc/ide and in /proc/scsi.
# The word DEVICESCAN will cause any remaining lines in this
# configuration file to be ignored: it tells smartd to scan for all
# ATA and SCSI devices. DEVICESCAN may be followed by any of the
# Directives listed below, which will be applied to all devices that
# are found. Most users should comment out DEVICESCAN and explicitly
# list the devices that they wish to monitor.
DEVICESCAN -m root -M exec /usr/share/smartmontools/smartd-runner
# Alternative setting to ignore temperature and power-on hours reports
# in syslog.
#DEVICESCAN -I 194 -I 231 -I 9
# Alternative setting to report more useful raw temperature in syslog.
#DEVICESCAN -R 194 -R 231 -I 9
# Alternative setting to report raw temperature changes >= 5 Celsius
# and min/max temperatures.
#DEVICESCAN -I 194 -I 231 -I 9 -W 5
# First (primary) ATA/IDE hard disk. Monitor all attributes, enable
# automatic online data collection, automatic Attribute autosave, and
# start a short self-test every day between 2-3am, and a long self test
# Saturdays between 3-4am.
#/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)
# Monitor SMART status, ATA Error Log, Self-test log, and track
# changes in all attributes except for attribute 194
#/dev/hdb -H -l error -l selftest -t -I 194
# Monitor all attributes except normalized Temperature (usually 194),
# but track Temperature changes >= 4 Celsius, report Temperatures
# >= 45 Celsius and changes in Raw value of Reallocated_Sector_Ct (5).
# Send mail on SMART failures or when Temperature is >= 55 Celsius.
#/dev/hdc -a -I 194 -W 4,45,55 -R 5 -m ad...@example.com
# An ATA disk may appear as a SCSI device to the OS. If a SCSI to
# ATA Translation (SAT) layer is between the OS and the device then
# this can be flagged with the '-d sat' option. This situation may
# become common with SATA disks in SAS and FC environments.
# /dev/sda -a -d sat
# A very silent check. Only report SMART health status if it fails
# But send an email in this case
#/dev/hdc -H -C 0 -U 0 -m ad...@example.com
# First two SCSI disks. This will monitor everything that smartd can
# monitor. Start extended self-tests Wednesdays between 6-7pm and
# Sundays between 1-2 am
#/dev/sda -d scsi -s L/../../3/18
#/dev/sdb -d scsi -s L/../../7/01
# Monitor 4 ATA disks connected to a 3ware 6/7/8000 controller which
uses
# the 3w-xxxx driver. Start long self-tests Sundays between 1-2, 2-3, 3-4,
# and 4-5 am.
# NOTE: starting with the Linux 2.6 kernel series, the /dev/sdX interface
# is DEPRECATED. Use the /dev/tweN character device interface instead.
# For example /dev/twe0, /dev/twe1, and so on.
#/dev/sdc -d 3ware,0 -a -s L/../../7/01
#/dev/sdc -d 3ware,1 -a -s L/../../7/02
#/dev/sdc -d 3ware,2 -a -s L/../../7/03
#/dev/sdc -d 3ware,3 -a -s L/../../7/04
# Monitor 2 ATA disks connected to a 3ware 9000 controller which uses
# the 3w-9xxx driver (Linux, FreeBSD). Start long self-tests Tuesdays
# between 1-2 and 3-4 am.
#/dev/twa0 -d 3ware,0 -a -s L/../../2/01
#/dev/twa0 -d 3ware,1 -a -s L/../../2/03
# Same as above for Windows. Option '-d 3ware,N' is not necessary,
# disk (port) number is specified in device name.
# NOTE: On Windows, DEVICESCAN works also for 3ware controllers.
#/dev/hdc,0 -a -s L/../../2/01
#/dev/hdc,1 -a -s L/../../2/03
#
# Monitor 2 disks connected to the first HP SmartArray controller which
# uses the cciss driver. Start long tests on Sunday nights and short
# self-tests every night and send errors to root
#/dev/cciss/c0d0 -d cciss,0 -a -s (L/../../7/02|S/../.././02) -m root
#/dev/cciss/c0d0 -d cciss,1 -a -s (L/../../7/03|S/../.././03) -m root
# Monitor 3 ATA disks directly connected to a HighPoint RocketRAID. Start long
# self-tests Sundays between 1-2, 2-3, and 3-4 am.
#/dev/sdd -d hpt,1/1 -a -s L/../../7/01
#/dev/sdd -d hpt,1/2 -a -s L/../../7/02
#/dev/sdd -d hpt,1/3 -a -s L/../../7/03
# Monitor 2 ATA disks connected to the same PMPort which connected to the
# HighPoint RocketRAID. Start long self-tests Tuesdays between 1-2 and 3-4 am
#/dev/sdd -d hpt,1/4/1 -a -s L/../../2/01
#/dev/sdd -d hpt,1/4/2 -a -s L/../../2/03
# HERE IS A LIST OF DIRECTIVES FOR THIS CONFIGURATION FILE.
# PLEASE SEE THE smartd.conf MAN PAGE FOR DETAILS
#
# -d TYPE Set the device type: ata, scsi, marvell, removable, 3ware,N, hpt,L/M/N
# -T TYPE set the tolerance to one of: normal, permissive
# -o VAL Enable/disable automatic offline tests (on/off)
# -S VAL Enable/disable attribute autosave (on/off)
# -n MODE No check. MODE is one of: never, sleep, standby, idle
# -H Monitor SMART Health Status, report if failed
# -l TYPE Monitor SMART log. Type is one of: error, selftest
# -f Monitor for failure of any 'Usage' Attributes
# -m ADD Send warning email to ADD for -H, -l error, -l selftest, and -f
# -M TYPE Modify email warning behavior (see man page)
# -s REGE Start self-test when type/date matches regular expression (see man page)
# -p Report changes in 'Prefailure' Normalized Attributes
# -u Report changes in 'Usage' Normalized Attributes
# -t Equivalent to -p and -u Directives
# -r ID Also report Raw values of Attribute ID with -p, -u or -t
# -R ID Track changes in Attribute ID Raw value with -p, -u or -t
# -i ID Ignore Attribute ID for -f Directive
# -I ID Ignore Attribute ID for -p, -u or -t Directive
# -C ID Report if Current Pending Sector count non-zero
# -U ID Report if Offline Uncorrectable count non-zero
# -W D,I,C Monitor Temperature D)ifference, I)nformal limit, C)ritical limit
# -v N,ST Modifies labeling of Attribute N (see man page)
# -a Default: equivalent to -H -f -t -l error -l selftest -C 197 -U 198
# -F TYPE Use firmware bug workaround. Type is one of: none, samsung
# -P TYPE Drive-specific presets: use, ignore, show, showall
# # Comment: text after a hash sign is ignored
# \ Line continuation character
# Attribute ID is a decimal integer 1 <= ID <= 255
# except for -C and -U, where ID = 0 turns them off.
# All but -d, -m and -M Directives are only implemented for ATA devices
#
# If the test string DEVICESCAN is the first uncommented text
# then smartd will scan for devices /dev/hd[a-l] and /dev/sd[a-z]
# DEVICESCAN may be followed by any desired Directives.
Did that help?
Ant
> take a look at /etc/smartd.conf and see which drives it is monitoring.
It is from smartctl:
I ran dmesg first and didn't see the errors at the end of it. Then I
ran:
# smartctl /dev/hdd
And checked my dmesg's ending and found:
[3316203.992053] hdd: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
[3316203.992060] hdd: task_in_intr: error=0x04 { AbortedCommand }
[3316203.992064] ide: failed opcode was: 0xec
Isn't strange for CD drives to be read for SMART? :/