Another update:
The drive is currently working fine:
-----
Mar 8 19:59:44 Halef kernel: pd: pd version 1.05, major 45, cluster 64, nice 0
Mar 8 19:59:44 Halef kernel: pda: Sharing parport0 at 0x378
Mar 8 19:59:44 Halef kernel: pda: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 5 (EPP-32), delay 1
Mar 8 19:59:44 Halef kernel: pda: SyQuest SparQ, master, 1960560 blocks [957M], (1945/16/63), removable media
Mar 8 19:59:44 Halef kernel: pda: pda1
(i.e. it was able to read sector 0)
-----
I left the drive go idle for a while, then:
rmmod pd
modprobe pd
-----
Mar 8 20:23:59 Halef kernel: pd: pd version 1.05, major 45, cluster 64, nice 0
Mar 8 20:23:59 Halef kernel: pda: Sharing parport0 at 0x378
Mar 8 20:23:59 Halef kernel: pda: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 5 (EPP-32), delay 1
Mar 8 20:23:59 Halef kernel: pda: SyQuest SparQ, master, 1960560 blocks [957M], (1945/16/63), removable media
Mar 8 20:24:00 Halef kernel: pda:pda: do_pd_read_drq: status = 0x10451 = ERR SEEK READY ABRT TMO
Mar 8 20:24:00 Halef kernel: pda: do_pd_read: status = 0x451 = ERR SEEK READY ABRT
Mar 8 20:24:00 Halef last message repeated 4 times
Mar 8 20:24:00 Halef kernel: end_request: I/O error, dev 2d:00 (PD), sector 0
Mar 8 20:24:01 Halef kernel: unable to read partition table
-----
While the system is attempting to read the partition table, it accepts no
keyboard input at all on the console, then, a few seconds later, all the
error messages appear on the scrren.
Reloading pd doesn't help in getting the drive up again in this scenario.
I have to power cycle the SparQ drive in order to get it back up. Once I
have done that, it works fine again.
Help! :(
Johannes
On Thu, 9 Mar 2000, Johannes Martin wrote:
> On Wed, 8 Mar 2000 grant@torque.net wrote:
> > > pda: do_pd_read: status = 0x4051 = ERR SEEK READY UNC
> >
> > UNC is an uncorrectable ECC error (reported by the hardware). Most likely
> > the media is bad.
> Thanks for the info. Indeed it seems like one of the media is bad, I can
> now reproduce this error by running e2fsck on that disk, the error occurs
> at the same block every time.
>
> This still leaves one problem open: why does the sparq drive refuse to do
> anything at all (except for ejecting the cartridge) once such an error has
> been encountered?
>
> With the disk I am currently using (the one that fails the e2fsck), the
> first error message usually looks like:
> pda: do_pd_read_drq: status = 0x14051 = ERR SEEK READY UNC TMO
> The drive keeps making noises as if it was seeking, until I remove and
> reload the pd module. Interestingly the pd modules seems to be able to
> reset the drive, so I can use it again (previously, I had to power down
> the drive before it would work again).
>
> Any help would be appreciated
> Johannes
>
>
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Thu Mar 09 2000 - 05:20:25 EST