Content-Type: multipart/alternative; boundary="=====================_97288693==.ALT" --=====================_97288693==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 06:49 AM 2/22/2003, Bruce Allen wrote: > > Since the Seagate tools can run and log the tests, I'm wondering why I > > can't from Linux. > >That's interesting. Could you please post the complete output of the >self-test log as reported by the Seagate DOS tool, and tell us about your >kernel version and build? I've attached those files written to the floppy by the Seagate program (had to find the floppy -- it was still in the drive, duh.). The system is a Debian Linux system running a custom kernel 2.2.19 with (I just remembered) the DI-30 ide tape drive patch (the tape drive is no longer in this system though). I can trying using a 2.2.17 or 2.2.19 kernel from Debian proper and see if the problem goes away, i.e. maybe the ide patch went badly. >Also, are there any IO error messages in /var/log/messages when the error >messages above from Smartctl are printed? If so, please post those as >well. I get messages whenever I try to use the smartmon tools, on either drive. For example, I ran smartctl -a on both drives, and /var/log/messages contained: Feb 22 23:53:32 handcuffs kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Feb 22 23:53:32 handcuffs kernel: hda: drive_cmd: error=0x04 { DriveStatusError } Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: error=0x04 { DriveStatusError } Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: error=0x04 { DriveStatusError } This is the only system I get these messages on. >This is quite strange, and at first glance I'd conclude that something is >either wrong with the disk or with the rest of the IO chain (cabling, >motherboard IO controller). Well it has been running a while, so maybe the cabling is coming loose or something. I started up the smartmon tools because I was seeing times where the drive hdb would shut down completely and fail to start back up, but I think I tracked that to the drive spinning down and then refusing to come back up (so I turned off sleeping and it hasn't done it since). I am going to reinstall the whole system with a 2.4 kernel in the next month or so, and at that time I will open it up and reseat everything and see if that helps (although I suspect switching to the new kernel with make a bigger difference). -W --=====================_97288693==.ALT Content-Type: text/html; charset="us-ascii" At 06:49 AM 2/22/2003, Bruce Allen wrote:
> Since the Seagate tools can run and log the tests, I'm wondering why I
> can't from Linux.

That's interesting.  Could you please post the complete output of the
self-test log as reported by the Seagate DOS tool, and tell us about your
kernel version and build?


I've attached those files written to the floppy by the Seagate program (had to find the floppy -- it was still in the drive, duh.).

The system is a Debian Linux system running a custom kernel 2.2.19 with (I just remembered) the DI-30 ide tape drive patch (the tape drive is no longer in this system though).

I can trying using a 2.2.17 or 2.2.19 kernel from Debian proper and see if the problem goes away, i.e. maybe the ide patch went badly.




Also, are there any IO error messages in /var/log/messages when the error
messages above from Smartctl are printed?  If so, please post those as
well.


I get messages whenever I try to use the smartmon tools, on either drive.  For example, I ran smartctl -a on both drives, and /var/log/messages contained:

Feb 22 23:53:32 handcuffs kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Feb 22 23:53:32 handcuffs kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Feb 22 23:53:40 handcuffs kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }

This is the only system I get these messages on.




This is quite strange, and at first glance I'd conclude that something is
either wrong with the disk or with the rest of the IO chain (cabling,
motherboard IO controller).


Well it has been running a while, so maybe the cabling is coming loose or something.  I started up the smartmon tools because I was seeing times where the drive hdb would shut down completely and fail to start back up, but I think I tracked that to the drive spinning down and then refusing to come back up (so I turned off sleeping and it hasn't done it since).

I am going to reinstall the whole system with a 2.4 kernel in the next month or so, and at that time I will open it up and reseat everything and see if that helps (although I suspect switching to the new kernel with make a bigger difference).

-W
--=====================_97288693==.ALT--