I got my drive to work thanks to the archives and those of you who went
through it before me, but now I see this in the xconsole, or the window under
the login screen. It's also in the warn log...
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
64
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
66
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
68
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
70
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
72
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
74
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
76
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request
queue (0)
Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector
78
Any idea what's happening?
Did I set the drive up wrong?
I added ide-scsi(and cdrom, and ide-cd) to /etc/sysconfig/kernel, ran
mkinitrd. Added hdd=ide-scsi(andhdc=ide-cd) to grub.
Fixed the links, and now this message repeats about 50 - 75 times when i log
in.
--
Franklin Maurer
On Monday 30 December 2002 16:14, Franklin Maurer wrote:
I got my drive to work thanks to the archives and those of you who went through it before me, but now I see this in the xconsole, or the window under the login screen. It's also in the warn log...
Dec 30 11:04:12 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 30 11:04:12 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 64
<snip> similar messages </snip>
Any idea what's happening? Did I set the drive up wrong? I added ide-scsi(and cdrom, and ide-cd) to /etc/sysconfig/kernel, ran mkinitrd. Added hdd=ide-scsi(andhdc=ide-cd) to grub. Fixed the links, and now this message repeats about 50 - 75 times when i log in.
I have just set up a vanilla SuSE 8.1 distro - everything worked 'out of the box' with my CDRW detected and set up automatically. I also get these messages on boot up (although only about a dozen or so, not 50 - 75 of them!). I have no idea what causes them, but everything works fine, so I am ignoring them. I was hoping for a reply to your question as I am getting the same thing - but as there are none I thought I would just let you know that you are not the only one getting the same symptoms. Sorry I cannot be of any help! In my naivite I had assumed it is just to do with the fact that the CD-ROM is not a hard disk drive, and does not (during the boot) have a disk in. If you do work out what is going on do let us know! Yours -- Ray
On Tuesday 31 December 2002 8:57 am, Ray Poynter wrote:
On Monday 30 December 2002 16:14, Franklin Maurer wrote:
big snip
. I have no idea what causes them, but everything works fine, so I am ignoring them.
I was hoping for a reply to your question as I am getting the same thing - but as there are none I thought I would just let you know that you are not the only one getting the same symptoms. Sorry I cannot be of any help!
Thanks, I was beginning to take it personally. :-)
In my naivite I had assumed it is just to do with the fact that the CD-ROM is not a hard disk drive, and does not (during the boot) have a disk in. If you do work out what is going on do let us know!
That ran through my mind as well. It happens on my dvd drive if I leave an
audio cd in the night before. I thought maybe linux didn't care fore the
grateful dead... but
yesterday, or 2 days ago, 29th?,("Drive errors", by mike, I think), there was
a similar post, with the same messages. It seemed that the via chipset was
the culprit.
Is that was you use as well?
Of course right after that someone said it wasn't via, it must be a hardware
problem. So i guess i'll just ignore the messages..
Have a happy new year.
--
Franklin Maurer
On Tuesday 31 December 2002 20:58, Franklin Maurer wrote:
On Tuesday 31 December 2002 8:57 am, Ray Poynter wrote:
On Monday 30 December 2002 16:14, Franklin Maurer wrote:
snip
That ran through my mind as well. It happens on my dvd drive if I leave an audio cd in the night before. I thought maybe linux didn't care fore the grateful dead... but
yesterday, or 2 days ago, 29th?,("Drive errors", by mike, I think), there was a similar post, with the same messages. It seemed that the via chipset was the culprit.
Is that was you use as well?
Of course right after that someone said it wasn't via, it must be a hardware problem. So i guess i'll just ignore the messages..
Have a happy new year.
Yes, I have a VIA chipset on the motherboard - the one that has a `southbridge bug' . The only problems I have had with this (new) system was some horrible crashes that I tracked down to a kinked and trapped IDE cable leading to the main hard drive. It might be interesting to see if these problems go away when/if I upgrade the kernal (I am on 2.4.19 at the moment) as according to a post in the kernal developers list (sorry can't find the reference now) a fix for this VIA problem might be included in the 2.4.20 kernal - there is a patch for it but as I do not seem to be having problems I am loathe to patch a working kernal. Happy new year to you too! -- Ray
The 02.12.31 at 15:58, Franklin Maurer wrote:
In my naivite I had assumed it is just to do with the fact that the CD-ROM is not a hard disk drive, and does not (during the boot) have a disk in. If you do work out what is going on do let us know!
That ran through my mind as well. It happens on my dvd drive if I leave an audio cd in the night before. I thought maybe linux didn't care fore the grateful dead... but
Well, an audio CD can not be mounted; so if you try you will get error messages. I think that some software is trying to see if there is something in your drives when you log in (probably KDE), trying to mount them, and failing. Nothing to worry about, unless you get errors when trying to mount data CDs and it fails. -- Cheers, Carlos Robinson
On Sunday 05 January 2003 9:57 pm, Carlos E. R. wrote:
Well, an audio CD can not be mounted; so if you try you will get error messages. I think that some software is trying to see if there is something in your drives when you log in (probably KDE), trying to mount them, and failing. Nothing to worry about, unless you get errors when trying to mount data CDs and it fails.
It happens with an audio cd, without an audio cd, with a windows data cd, and
with a SuSE disk. Basically it happens every time I boot, but they function
fine. It's the number of these messages i get, and the amount of space they
take up that won't let me get over it. I'm not exaggerating by saying i get
50 of these when I boot the computer, and i tend to do that often.
The first time I noticed the messages i had left an audio cd in the drive and
was guessing / hoping this would be the problem / solution.
Just as i'll do now ...
Searching through my logs, i found that my ide-scsi cdrw has dma enabled.
Could this be part of the problem?
I ask because in yast2 it lists the dma devices but only lists ide not the
scsi enabled. Is there a command line way to turn this off for that drive?
or do i have to remove the scsi from the kernel turn off dma for that drive
and then add ide-scsi back?
I also checked man hdparm, it was mentioned in a different thread, there was
an option for emptying the queue. It was -f sync and flush the buffer cache
on exit. The error was about
I/O error, dev 16:40 (hdd), sector 68
ide-scsi: hdd: unsupported command in request queue (0)
Thanks
--
Franklin Maurer
The 03.01.06 at 11:47, Franklin Maurer wrote:
It happens with an audio cd, without an audio cd, with a windows data cd, and with a SuSE disk.
Ah... then, I would start to worry a bit :-}
Basically it happens every time I boot, but they function fine.
Well, if it works, then ignore it O:-)
It's the number of these messages i get, and the amount of space they take up that won't let me get over it. I'm not exaggerating by saying i get 50 of these when I boot the computer, and i tend to do that often.
Well, that is a nuissance. But don't complain too much, I once got several megabytes of error logs by the kernel, in something like an hour, with something similar. The kernel felt talkative, that's all ;-) I mean, if it works, then it should be ok.
Searching through my logs, i found that my ide-scsi cdrw has dma enabled. Could this be part of the problem?
Not really... well, you could disable it and see what happens.
I ask because in yast2 it lists the dma devices but only lists ide not the scsi enabled.
True.
Is there a command line way to turn this off for that drive? or do i have to remove the scsi from the kernel turn off dma for that drive and then add ide-scsi back?
No, if it is ide-scsi emulation you are using, for disabling dma just use "hdparm -d0 /dev/hdx", where x is the actual drive the ide-scsi emulates. It "normally" works.
I also checked man hdparm, it was mentioned in a different thread, there was an option for emptying the queue. It was -f sync and flush the buffer cache on exit. The error was about I/O error, dev 16:40 (hdd), sector 68 ide-scsi: hdd: unsupported command in request queue (0)
But it is a different queue, I guess. -- Cheers, Carlos Robinson
On Tuesday 07 January 2003 10:51 am, Carlos E. R. wrote:
Well, that is a nuissance. But don't complain too much, I once got several megabytes of error logs by the kernel, in something like an hour, with something similar. The kernel felt talkative, that's all ;-)
It makes me think my partitioning scheme wasn't correct. guess I'll just have to keep an eye on it. Even better I can burn stuff to cd and repartition instead of reinstalling, if it ever gets that bad. :-).
Searching through my logs, i found that my ide-scsi cdrw has dma enabled. Could this be part of the problem?
Not really... well, you could disable it and see what happens.
No, if it is ide-scsi emulation you are using, for disabling dma just use "hdparm -d0 /dev/hdx", where x is the actual drive the ide-scsi emulates. It "normally" works.
I disabled it. I'll see what happens. Probably the same errors ... :-{ .
But at least it functions. :-)
Thanks for your help.
--
Franklin Maurer
The 03.01.07 at 11:41, Franklin Maurer wrote:
On Tuesday 07 January 2003 10:51 am, Carlos E. R. wrote:
Well, that is a nuissance. But don't complain too much, I once got several megabytes of error logs by the kernel, in something like an hour, with something similar. The kernel felt talkative, that's all ;-)
It makes me think my partitioning scheme wasn't correct. guess I'll just have to keep an eye on it. Even better I can burn stuff to cd and repartition instead of reinstalling, if it ever gets that bad. :-).
What's the problem, your /var/log is filling up too fast? Then I understand. Well... instead of repartition, you can simply create a bigger partition for /var/log - I'm not sure if /var/log is needed during boot, before the rest of partitions are mounted. -- Cheers, Carlos Robinson
On Thursday 09 January 2003 9:47 pm, Carlos E. R. wrote:
The 03.01.07 at 11:41, Franklin Maurer wrote:
It makes me think my partitioning scheme wasn't correct. guess I'll just have to keep an eye on it. Even better I can burn stuff to cd and repartition instead of reinstalling, if it ever gets that bad. :-).
What's the problem, your /var/log is filling up too fast? Then I understand.
Well... instead of repartition, you can simply create a bigger partition for /var/log - I'm not sure if /var/log is needed during boot, before the rest of partitions are mounted.
Actually it turns out it was the apt part of /var/cache that was gobbling up
the space. So I repartitoned my windows disk, and added a mount point of
/var/cache/apt so it should be good. It was the repetition of the errors that
made me realize it. Guess it turned out to be a good thing.
I'd still like to make the errors go away, but I've learned to live with them.
:-)
--
Franklin Maurer
The 03.01.09 at 23:03, Franklin Maurer wrote:
Well... instead of repartition, you can simply create a bigger partition for /var/log - I'm not sure if /var/log is needed during boot, before the rest of partitions are mounted.
Actually it turns out it was the apt part of /var/cache that was gobbling up the space. So I repartitoned my windows disk, and added a mount point of /var/cache/apt so it should be good.
I like to leave free space, non partitioned, on disks, to be added later when and where needed :-)
It was the repetition of the errors that made me realize it. Guess it turned out to be a good thing. I'd still like to make the errors go away, but I've learned to live with them. :-)
Sounds familiar :-) -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
Franklin Maurer
-
Ray Poynter