"Karl E. Jorgensen" wrote: > > On Mon, Mar 25, 2002 at 11:49:44AM -0800, Erik Steffl wrote: > > [[ snip ]] > > > > I can copy the whole data CD, no problems (fast, no errors, no > > messages in syslog). However when I run either of the following: > > > > cat /dev/hdc |od > > hdparam -t /dev/hdc > > > > the program (cat or hdparm) runs for awhile (5-10s) but then freezes > > (cannot even be kill-9-ed, which means that it's stuck in system call, I > > guess) and there are following messages in syslog (repeated over and > > over, even after shutdown prints out the Power down message, at that > > time they are displayed on the console): > > > > ... > > Mar 25 01:24:49 localhost kernel: hdc: cdrom_decode_status: status=0x51 > > { DriveReady SeekComplete Error } > > Mar 25 01:24:49 localhost kernel: hdc: cdrom_decode_status: error=0x30 > > Mar 25 01:24:52 localhost kernel: hdc: cdrom_decode_status: status=0x51 > > { DriveReady SeekComplete Error } > > Mar 25 01:24:52 localhost kernel: hdc: cdrom_decode_status: error=0x30 > > Mar 25 01:24:55 localhost kernel: hdc: cdrom_decode_status: status=0x51 > > { DriveReady SeekComplete Error } > > Mar 25 01:24:55 localhost kernel: hdc: cdrom_decode_status: error=0x30 > > Mar 25 01:24:55 localhost kernel: hdc: ATAPI reset complete > > Mar 25 01:24:55 localhost kernel: end_request: I/O error, dev 16:00 > > (hdc), sector 3276 > > ... > > You don't mention which kernel you're running...
2.4.17, it was in original message but got lost in the subsequent messages... > In your kernel config, what is the setting of CONFIG_IDEDISK_MULTI_MODE? > > From 2.4.18's Configure.help: > Use multi-mode by default > CONFIG_IDEDISK_MULTI_MODE > If you get this error, try to say Y here: > > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } > hda: set_multmode: error=0x04 { DriveStatusError } > > If in doubt, say N. thanks a lot, it might be relevant (I'll try that), I have more detials on the problem described above: those particular errors occur only when the certain part of data CD is read (each data CD I tried so far), the 'bad' part is somewhere between 1.6 MB and 200 MB - i.e. I can read beginning of the CD and most of the rest. When I mount data CD it works fine (everything can be read) so the 'bad' part might be simply feature of the file system used (iso9660). Anybody has more insight? TIA, erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]