> Sean Farley wrote:
<snip>
> > Come to think about it, before I went to bed, I was unable to start qps
> > (Qt process utility) to view the running process. I thought about looking
> > at it in the morning when I woke up. I don't know if the SCSI errors
> > caused the problem or something else did. The first SCSI error was well
> > after I had gone to bed and had had trouble with qps.
> Unfortunately, if you are using something like badblocks to find the bad
> sectors, then I've found it to be somewhat arbitrary about what sectors
> actually get found fom run to run depending on whether or not the drive is
> able to successfully retry the operation before it runs out of retries. I
> would suggest using the Adaptec SCSI BIOS disk utilities and doing a Verify
> Media operation. This tends to be more reliable about mapping out bad
> sectors and they are less likely to come back and haunt you in the future,
> which is exactly what has happened in this case.
I'll give it a whirl. I just need to move the files off of the drive.
Why would a bad block make the whole system unstable? The drive in
question is merely a data drive. When I tried to run qps, it failed to
load three hours before the first SCSI error showed up. qps is on a
different drive. At that time qps would not run, but I was able to start
an xterm.
If I do have a bad block, something in the kernel seemed to have
overreacted. At least IMHO. :)
Thanks,
Sean
---------------
sean@farley.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu