Skip to contentSkip to conversation

kernel hda errors on dmesg

DISCUSSION Alejandro Bonilla 3 participants 4 messages Mar 19, 2006 – Mar 20, 2006 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi,

I have an Compaq V2000 laptop with Ubuntu Dapper Drake, I'm getting flooded with the messages below:
ON: Linux ubuntu 2.6.15-18-386 #1 PREEMPT Thu Mar 9 14:41:49 UTC 2006 i686 GNU/Linux
/dev/sda: FUJITSU MHV2060BH:

Why am I getting hda errors when I don't even have a hda drive? Mine is sda. The syslog says is the kernel itself, no other application is causing this as I have stopped most services and still happen.

I already wrote to the Ubuntu ML but had no luck.

Any idea?

dmesg

[4295643.338000] ide: failed opcode was: 0xef 
[4295644.283000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295644.295000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295645.963000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295645.966000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } 
[4295645.966000] hda: drive_cmd: error=0x04 { AbortedCommand } 
[4295645.966000] ide: failed opcode was: 0xec 
[4295646.000000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295646.003000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } 
[4295646.003000 ] hda: drive_cmd: error=0x04 { AbortedCommand } 
[4295646.003000] ide: failed opcode was: 0xec 
[4295646.345000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295646.357000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295648.408000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295648.421000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295650.471000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq: 0x00 
[4295650.483000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295652.534000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295652.546000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq: 0x00 
[4295654.601000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295654.612000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00

Thanks,

.Alejandro

#3 lore raw

Hi Alejandro,

Quoted 28 lines · Alejandro Bonilla

Why am I getting hda errors when I don't even have a hda drive? Mine is sda. The syslog says is the kernel itself, no other application is causing this as I have stopped most services and still happen.

dmesg

[4295643.338000] ide: failed opcode was: 0xef 
[4295644.283000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295644.295000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295645.963000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295645.966000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } 
[4295645.966000] hda: drive_cmd: error=0x04 { AbortedCommand } 
[4295645.966000] ide: failed opcode was: 0xec 
[4295646.000000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295646.003000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } 
[4295646.003000 ] hda: drive_cmd: error=0x04 { AbortedCommand } 
[4295646.003000] ide: failed opcode was: 0xec 
[4295646.345000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295646.357000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295648.408000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295648.421000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295650.471000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq: 0x00 
[4295650.483000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295652.534000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
[4295652.546000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq: 0x00 
[4295654.601000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
[4295654.612000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00
Quoted 1 line

Any idea?

Just an idea, but this looks to me like problems reading a CD - if you use ide-cd and a normal parralel ATA / ATAPI CD-ROM drive, you might have /dev/hda and a symlink pointing to that node as well. In this case, you only care for e.g. /dev/cdrom, but in fact are using /dev/hda.

Regards,
Chris

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw

Re: kernel hda errors on dmesg - new VFS messages

After installing 2.6.16, it looks like the hda messages(below) changed to:

[4294840.149000] VFS: busy inodes on changed media.
[4294840.162000] VFS: busy inodes on changed media.
[4294840.251000] VFS: busy inodes on changed media.
[4294840.258000] VFS: busy inodes on changed media.
[4294850.829000] VFS: busy inodes on changed media.
[4294850.830000] VFS: busy inodes on changed media.
[4294850.831000] VFS: busy inodes on changed media.
[4294850.832000] VFS: busy inodes on changed media.
[4294850.837000] VFS: busy inodes on changed media.
[4294852.847000] VFS: busy inodes on changed media.
[4294852.848000] VFS: busy inodes on changed media.
-I inserted a CD and:-
[4294853.924000] UDF-fs: No VRS found
[4294854.199000] UDF-fs: No VRS found
[4294854.517000] ISO 9660 Extensions: Microsoft Joliet Level 3
[4294854.579000] ISO 9660 Extensions: RRIP_1991A

It looks like it was taking /dev/hda as the CDROM before, still I don't see a symlink and still have no idea why this is flooding my dmesg.

It is a LightScribe CDROM in case it matters.

any idea?

Thanks,

Quoted 10 lines
Quoted 10 lines

I have an Compaq V2000 laptop with Ubuntu Dapper Drake, I'm getting flooded with the messages below:
ON: Linux ubuntu 2.6.15-18-386 #1 PREEMPT Thu Mar 9 14:41:49 UTC 2006 i686 GNU/Linux
/dev/sda: FUJITSU MHV2060BH:

Why am I getting hda errors when I don't even have a hda drive? Mine is sda. The syslog says is the kernel itself, no other application is causing this as I have stopped most services and still happen.

Quoted 8 lines
Quoted 8 lines

I already wrote to the Ubuntu ML but had no luck.

Any idea?

dmesg

[4295643.338000] ide: failed opcode was: 0xef 
[4295644.283000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295644.295000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295645.963000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295645.966000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete

Error }

Quoted 3 lines
Quoted 3 lines
[4295645.966000] hda: drive_cmd: error=0x04 { AbortedCommand } 
[4295645.966000] ide: failed opcode was: 0xec 
[4295646.000000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295646.003000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete

Error }

Quoted 3 lines
Quoted 3 lines

[4295646.003000 ] hda: drive_cmd: error=0x04 { AbortedCommand }

[4295646.003000] ide: failed opcode was: 0xec 
[4295646.345000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295646.357000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295648.408000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295648.421000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295650.471000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295650.483000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295652.534000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295652.546000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295654.601000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq:

0x00

Quoted 1 line
Quoted 1 line
[4295654.612000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq:

0x00

Quoted 16 lines
Quoted 11 lines

Thanks,

.Alejandro

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 3 lines
1024D/A6D12F80 print D51D 2633 8DAC 04DB 7265  9BB8 5883 6DAA A6D1 2F80
main(i) { putchar(182623909 >> (i-1) * 5&31|!!(i<7)<<6) && main(++i)
; }

--
Open WebMail Project (http://openwebmail.org)

#6 lore raw

Re: kernel hda errors on dmesg - new VFS messages

Quoted 7 lines · Alejandro Bonilla

-I inserted a CD and:-

[4294853.924000] UDF-fs: No VRS found
[4294854.199000] UDF-fs: No VRS found
[4294854.517000] ISO 9660 Extensions: Microsoft Joliet Level 3
[4294854.579000] ISO 9660 Extensions: RRIP_1991A

any idea?

Do you use KDE? I had a problem once with /dev/hdd being hammered very similar (but this _was_ a CD-ROM).

If you do use KDE look in Control Center->KDE Components->Service Manager. There is a service called 'KDED Media manager' that was causing my problems. I turned it off.

Just an idea.

Nick