From: Kai M. <Kai...@ko...> - 2004-07-14 06:58:25
|
> Date: Tue, 13 Jul 2004 11:26:16 +0200 (CEST) > From: Hugo Monteiro Cacote <hc...@ma...> > To: sma...@li... > Subject: [smartmontools-support]smart and tape drivers monitoring > > Dear all, > > I'm trying to use the smartmontools package to monitor tape drivers. I'm > currently doing the first tests on a STK tape driver (running GNU-Linux). > > I have some questions after my first experience monitoring these > devices: > > - what are the different messages that we can get from the Tape alert (OK > , .... ). > The standard defines about 50 different conditions that can be reported. However, reporting any error is optional and it depends on the drive what it can actually report. This is documented in the SCSI manual of the drive. Most drives report need for cleaning and some information about read and write errors. Some report too high temperature. The messages are self-explanatory. The list is in the source file scsicmds.c (TapeAlertsMessageTable). > - My device is outputing "Temperature Warning Disabled or Not Supported" > how can I enable the temperature warning ? > This is what you should see with a tape drive. It does not explicitly report a temperature warning but it is included in the tape alert data if the drive can measure the temperature. > - Can I have selftests on tape drives? And does it make sense to have them > scheduled with smartd. > This depends on the drive. All drives do self-tests at power up but whether it can be done programmatically depends on the firmware. I don't recommend usings smartd for anything with tapes. Polling the tape alert messages and performing self tests should be synchronized with using the tapes. I don't think a self test in the middle of a backup would be very good ;-) > - Which smartctl parameters can we use with a tape drive device? > You can use the parameters that request information. What is the best combination for you depends on what you want to see and what your drive reports. The man page gives you some indication about what to expect. You can try the self test parameters that do tests. Don't try to schedule any automatic tests unless you really know what you are doing. -- Kai |
From: Hugo C. <hc...@ma...> - 2004-07-15 09:22:02
|
Dear all, I'm using the smartctl (version 5.30) and particular to monitor the Tape Alerts. I'm getting the following situation even if the Tape driver is idle : # smartctl -a /dev/st0 smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: STK T9940B Version: 1.34 Serial number: 479000002323 Device type: tape Transport protocol: Fibre channel (FCP-2) Local Time is: Wed Jul 14 20:30:20 2004 CEST device is NOT READY (e.g. spun down, busy) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Afterwards I do what the tool says and I add the -T flag to the command # smartctl -a -T permissive /dev/st0 smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: STK T9940B Version: 1.34 Serial number: 479000002323 Device type: tape Transport protocol: Fibre channel (FCP-2) Local Time is: Thu Jul 15 11:17:04 2004 CEST device is NOT READY (e.g. spun down, busy) Temperature Warning Disabled or Not Supported TapeAlert Supported TapeAlert: OK Error counter log: Errors Corrected Total Total Correction Gigabytes Total delay: [rereads/ errors algorithm processed uncorrected minor | major rewrites] corrected invocations [10^9 bytes] errors read: 0 0 0 0 0 1.280 0 write: 0 0 0 0 0 0.000 0 Non-medium error count: 0 Device does not support Self Test logging Is there any way to know what SMART mandatory command is failing? And is there any possibility that by adding this flad I might be doing something wrong or at least not recommended ?? Thanks, -- Hugo Caçote |
From: Kai M. <Kai...@ko...> - 2004-07-15 18:42:26
|
On Thu, 15 Jul 2004, Hugo CACOTE wrote: > Dear all, > > I'm using the smartctl (version 5.30) and particular to monitor the Tape > Alerts. > > I'm getting the following situation even if the Tape driver is idle : > > # smartctl -a /dev/st0 You might want to use /dev/nst0 (closing /dev/st0 automatically rewinds the tape). This is not related to the problem below. > smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > Device: STK T9940B Version: 1.34 > Serial number: 479000002323 > Device type: tape > Transport protocol: Fibre channel (FCP-2) > Local Time is: Wed Jul 14 20:30:20 2004 CEST > device is NOT READY (e.g. spun down, busy) > A mandatory SMART command failed: exiting. To continue, add one or more > '-T permissive' options. > I can reproduce this in my system. The reason is that smartctl does not like a device that is not ready when you use the -a option. If you use -H to just get the TapeAlert data, no error is shown. One can argue that the device ready requirement should be relaxed for tapes. I don't have any firm opinion on this. A SCSI device is not required to do much (respond to inquiry and test unit ready) unless it is ready. It may provide incomplete statistics. In this case allowing the not ready condition may mislead the user. This is one more case where you should see how your drive reacts and then decide how you use the command. My decision is to use '-a' only when there is a tape in the drive. > > Afterwards I do what the tool says and I add the -T flag to the command > > # smartctl -a -T permissive /dev/st0 > smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ ... > Is there any way to know what SMART mandatory command is failing? And is > there any possibility that by adding this flad I might be doing something > wrong or at least not recommended ?? > If you use the option "-r ioctl,2", smartctl prints the commands sent to the device and the responses from the device. This revealed the last command sent to the drive before the error was reported. However, the code should be consulted to be sure that it was the last command that caused the complaint. Using '-T permissive' tells smartctl to continue after it receives a response it thinks is wrong. In this case continuing is harmless. In general, a SCSI device should reject a command it does not implement. In practice, some devices tend to lock up in these cases. If accepting an unexpected response leads to writing something, it may not be harmless. In this case nothing is written. As you can see, it is diffcult to give a definite answer to this question :-) -- Kai |
From: Bruce A. <ba...@gr...> - 2004-07-15 20:47:16
|
On Thu, 15 Jul 2004, Hugo CACOTE wrote: > Dear all, > > I'm using the smartctl (version 5.30) and particular to monitor the Tape > Alerts. > > I'm getting the following situation even if the Tape driver is idle : > > # smartctl -a /dev/st0 > smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > Device: STK T9940B Version: 1.34 > Serial number: 479000002323 > Device type: tape > Transport protocol: Fibre channel (FCP-2) > Local Time is: Wed Jul 14 20:30:20 2004 CEST > device is NOT READY (e.g. spun down, busy) Doug, Kai, would it make sense to change this message to read: "(e.g. spun down, busy, no tape)" Cheers, Bruce |
From: Kai M. <Kai...@ko...> - 2004-07-15 21:12:30
|
On Thu, 15 Jul 2004, Bruce Allen wrote: > > > On Thu, 15 Jul 2004, Hugo CACOTE wrote: > > > Dear all, > > > > I'm using the smartctl (version 5.30) and particular to monitor the Tape > > Alerts. > > > > I'm getting the following situation even if the Tape driver is idle : > > > > # smartctl -a /dev/st0 > > smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen > > Home page is http://smartmontools.sourceforge.net/ > > Device: STK T9940B Version: 1.34 > > Serial number: 479000002323 > > Device type: tape > > Transport protocol: Fibre channel (FCP-2) > > Local Time is: Wed Jul 14 20:30:20 2004 CEST > > device is NOT READY (e.g. spun down, busy) > > Doug, Kai, would it make sense to change this message to read: "(e.g. spun > down, busy, no tape)" > With most tape drives, the message is 'NO MEDIUM present on device'. For some reason, this Storagetek firmware does not report the no tape condition and so scsiprint.c just tells that the device is not ready. Might be less confusing if disks and tapes would have different messages so that people testing disks would not wonder about no tape. The following patch compiles but has not been tested (my drives report no medium): --- smartmontools-5.32/scsiprint.c.org 2004-07-15 23:58:53.000000000 +0300 +++ smartmontools-5.32/scsiprint.c 2004-07-15 23:59:42.000000000 +0300 @@ -732,7 +732,10 @@ if ((err = scsiTestUnitReady(device))) { if (SIMPLE_ERR_NOT_READY == err) { PRINT_ON(con); - pout("device is NOT READY (e.g. spun down, busy)\n"); + if (!is_tape) + pout("device is NOT READY (e.g. spun down, busy)\n"); + else + pout("device is NOT READY (e.g. no tape)\n"); PRINT_OFF(con); } else if (SIMPLE_ERR_NO_MEDIUM == err) { PRINT_ON(con); -- Kai |
From: Bruce A. <ba...@gr...> - 2004-07-15 21:23:33
|
> > Doug, Kai, would it make sense to change this message to read: "(e.g. spun > > down, busy, no tape)" > > > With most tape drives, the message is 'NO MEDIUM present on device'. For > some reason, this Storagetek firmware does not report the no tape > condition and so scsiprint.c just tells that the device is not ready. > > Might be less confusing if disks and tapes would have different messages > so that people testing disks would not wonder about no tape. The following > patch compiles but has not been tested (my drives report no medium): To me this looks better than what I suggested and than what we currently have. Cheers, Bruce > --- smartmontools-5.32/scsiprint.c.org 2004-07-15 23:58:53.000000000 +0300 > +++ smartmontools-5.32/scsiprint.c 2004-07-15 23:59:42.000000000 +0300 > @@ -732,7 +732,10 @@ > if ((err = scsiTestUnitReady(device))) { > if (SIMPLE_ERR_NOT_READY == err) { > PRINT_ON(con); > - pout("device is NOT READY (e.g. spun down, busy)\n"); > + if (!is_tape) > + pout("device is NOT READY (e.g. spun down, busy)\n"); > + else > + pout("device is NOT READY (e.g. no tape)\n"); > PRINT_OFF(con); > } else if (SIMPLE_ERR_NO_MEDIUM == err) { > PRINT_ON(con); > > -- > Kai > > |
From: Douglas G. <do...@to...> - 2004-07-16 14:33:47
|
Kai, The patch looks fine. Who should check it in to cvs? Doug Gilbert Kai Makisara wrote: > On Thu, 15 Jul 2004, Bruce Allen wrote: > > >> >>On Thu, 15 Jul 2004, Hugo CACOTE wrote: >> >> >>>Dear all, >>> >>>I'm using the smartctl (version 5.30) and particular to monitor the Tape >>>Alerts. >>> >>>I'm getting the following situation even if the Tape driver is idle : >>> >>># smartctl -a /dev/st0 >>>smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen >>>Home page is http://smartmontools.sourceforge.net/ >>>Device: STK T9940B Version: 1.34 >>>Serial number: 479000002323 >>>Device type: tape >>>Transport protocol: Fibre channel (FCP-2) >>>Local Time is: Wed Jul 14 20:30:20 2004 CEST >>>device is NOT READY (e.g. spun down, busy) >> >>Doug, Kai, would it make sense to change this message to read: "(e.g. spun >>down, busy, no tape)" >> > > With most tape drives, the message is 'NO MEDIUM present on device'. For > some reason, this Storagetek firmware does not report the no tape > condition and so scsiprint.c just tells that the device is not ready. > > Might be less confusing if disks and tapes would have different messages > so that people testing disks would not wonder about no tape. The following > patch compiles but has not been tested (my drives report no medium): > > --- smartmontools-5.32/scsiprint.c.org 2004-07-15 23:58:53.000000000 +0300 > +++ smartmontools-5.32/scsiprint.c 2004-07-15 23:59:42.000000000 +0300 > @@ -732,7 +732,10 @@ > if ((err = scsiTestUnitReady(device))) { > if (SIMPLE_ERR_NOT_READY == err) { > PRINT_ON(con); > - pout("device is NOT READY (e.g. spun down, busy)\n"); > + if (!is_tape) > + pout("device is NOT READY (e.g. spun down, busy)\n"); > + else > + pout("device is NOT READY (e.g. no tape)\n"); > PRINT_OFF(con); > } else if (SIMPLE_ERR_NO_MEDIUM == err) { > PRINT_ON(con); > |
From: Hugo C. <hc...@ma...> - 2004-08-26 16:16:25
|
Dear all, I'm using smartctl to monitor STK T9940B tape drives. In my first experiences I'm getting the following behaviour: after reading one tape the first smartctl issued will return a Tape Alert warning and all the following will return Tape Alert OK. 1) First smartctl command after reading tape # smartctl -a -T permissive /dev/st0 smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: STK T9940B Version: 1.34 Serial number: 479000010876 Device type: tape Transport protocol: Fibre channel (FCP-2) Local Time is: Thu Aug 26 17:52:53 2004 CEST device is NOT READY (e.g. spun down, busy) Temperature Warning Disabled or Not Supported TapeAlert Supported TapeAlert Errors (C=Critical, W=Warning, I=Informational): [0x27] W: The tape drive may have a hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the tape drive users manual for device specific instructions on running extended diagnostic tests. Error counter log: Errors Corrected Total Total Correction Gigabytes Total delay: [rereads/ errors algorithm processed uncorrected minor | major rewrites] corrected invocations [10^9 bytes] errors read: 0 0 0 0 0 0.181 0 write: 0 0 0 0 1 0.000 0 Non-medium error count: 0 Device does not support Self Test logging 2) Second smartctl commnand after reading tape # smartctl -a -T permissive /dev/st0 smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: STK T9940B Version: 1.34 Serial number: 479000010876 Device type: tape Transport protocol: Fibre channel (FCP-2) Local Time is: Thu Aug 26 17:52:59 2004 CEST device is NOT READY (e.g. spun down, busy) Temperature Warning Disabled or Not Supported TapeAlert Supported TapeAlert: OK Error counter log: Errors Corrected Total Total Correction Gigabytes Total delay: [rereads/ errors algorithm processed uncorrected minor | major rewrites] corrected invocations [10^9 bytes] errors read: 0 0 0 0 0 0.181 0 write: 0 0 0 0 1 0.000 0 Non-medium error count: 0 Can someone provide me some explanation for this behaviour?? Thank you, -- Hugo Caçote @ CERN IT |
From: Kai M. <Kai...@ko...> - 2004-08-27 17:04:34
|
On Thu, 26 Aug 2004, Hugo CACOTE wrote: > Dear all, > > I'm using smartctl to monitor STK T9940B tape drives. In my first > experiences I'm getting the following behaviour: after reading one tape > the first smartctl issued will return a Tape Alert warning and all the > following will return Tape Alert OK. > ... > Can someone provide me some explanation for this behaviour?? > Could you provide the output of 'smartctl -r ioctl,2 ...' when the error message occurs so that we can check that the report is correct. -- Kai |
From: Hugo C. <hc...@ma...> - 2004-08-30 09:04:54
|
Dear Kai, > > > Could you provide the output of 'smartctl -r ioctl,2 ...' when the error > message occurs so that we can check that the report is correct. > # smartctl -r ioctl,2 -a -T permissive /dev/st0 smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ [inquiry: 12 00 00 00 24 00 ] status=0 Incoming data, len=36: 00 01 80 03 02 33 00 10 00 53 54 4b 20 20 20 20 20 10 54 39 39 34 30 42 20 20 20 20 20 20 20 20 20 20 20 31 2e 33 34 Device: STK T9940B Version: 1.34 [mode sense: 1a 00 1c 00 40 00 ] status=0 Incoming data, len=64: 00 17 00 90 08 44 00 00 00 00 00 00 00 1c 0a 08 03 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [mode sense: 1a 00 5c 00 40 00 ] status=0 Incoming data, len=64: 00 17 00 90 08 44 00 00 00 00 00 00 00 1c 0a 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [inquiry: 12 01 80 00 40 00 ] status=0 Incoming data, len=64: 00 01 80 00 0c 34 37 39 30 30 30 30 31 30 38 37 36 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Serial number: 479000010876 Device type: tape [mode sense: 1a 00 19 00 40 00 ] status=0 Incoming data, len=64: 00 13 00 90 08 44 00 00 00 00 00 00 00 19 06 00 00 10 00 00 05 1e 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Transport protocol: Fibre channel (FCP-2) Local Time is: Mon Aug 30 10:46:33 2004 CEST [test unit ready: 00 00 00 00 00 00 ] >>> Sense buffer, len=16: 00 70 00 02 00 00 00 00 12 00 00 00 00 04 00 00 00 status=2: sense_key=2 asc=4 ascq=0 device is NOT READY (e.g. spun down, busy) Temperature Warning Disabled or Not Supported [log sense: 4d 00 40 00 00 00 00 00 04 00 ] status=0 Incoming data, len=4: 00 00 00 00 07 [log sense: 4d 00 40 00 00 00 00 00 0c 00 ] status=0 Incoming data, len=12: 00 00 00 00 07 00 02 03 06 0c 2e 30 00 TapeAlert Supported [log sense: 4d 00 6e 00 00 00 00 01 44 00 ] status=0 Incoming data, len=324 [only first 256 bytes shown]: 00 2e 00 01 40 00 01 40 01 00 00 02 40 01 00 00 03 10 40 01 00 00 04 40 01 00 00 05 40 01 00 00 06 40 20 01 00 00 07 40 01 00 00 08 40 01 00 00 09 40 01 30 00 00 0a 40 01 00 00 0b 40 01 00 00 0c 40 01 00 40 00 0d 40 01 00 00 0e 40 01 00 00 0f 40 01 00 00 50 10 40 01 00 00 11 40 01 00 00 12 40 01 00 00 13 60 40 01 00 00 14 40 01 00 00 15 40 01 00 00 16 40 70 01 00 00 17 40 01 00 00 18 40 01 00 00 19 40 01 80 00 00 1a 40 01 00 00 1b 40 01 00 00 1c 40 01 00 90 00 1d 40 01 00 00 1e 40 01 00 00 1f 40 01 00 00 a0 20 40 01 00 00 21 40 01 00 00 22 40 01 00 00 23 b0 40 01 00 00 24 40 01 00 00 25 40 01 00 00 26 40 c0 01 00 00 27 40 01 01 00 28 40 01 00 00 29 40 01 d0 00 00 2a 40 01 00 00 2b 40 01 00 00 2c 40 01 00 e0 00 2d 40 01 00 00 2e 40 01 00 00 2f 40 01 00 00 f0 30 40 01 00 00 31 40 01 00 00 32 40 01 00 00 33 TapeAlert Errors (C=Critical, W=Warning, I=Informational): [0x27] W: The tape drive may have a hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the tape drive users manual for device specific instructions on running extended diagnostic tests. [log sense: 4d 00 43 00 00 00 00 00 04 00 ] status=0 Incoming data, len=4: 00 03 00 00 3c [log sense: 4d 00 43 00 00 00 00 00 40 00 ] status=0 Incoming data, len=64: 00 03 00 00 3c 00 00 74 04 00 00 00 00 00 01 74 04 10 00 00 00 00 00 02 74 04 00 00 00 00 00 03 74 04 20 00 00 00 00 00 04 74 04 00 00 00 00 00 05 74 08 30 00 00 00 00 0a c3 00 f0 00 06 74 04 00 00 00 00 [log sense: 4d 00 42 00 00 00 00 00 04 00 ] status=0 Incoming data, len=4: 00 02 00 00 3c [log sense: 4d 00 42 00 00 00 00 00 40 00 ] status=0 Incoming data, len=64: 00 02 00 00 3c 00 00 74 04 00 00 00 00 00 01 74 04 10 00 00 00 00 00 02 74 04 00 00 00 00 00 03 74 04 20 00 00 00 00 00 04 74 04 00 00 00 02 00 05 74 08 30 00 00 00 00 00 00 00 00 00 06 74 04 00 00 00 00 [log sense: 4d 00 45 00 00 00 00 00 04 00 ] >>> Sense buffer, len=16: 00 70 00 05 00 00 00 00 12 00 00 00 00 24 00 00 c0 status=2: sense_key=5 asc=24 ascq=0 Error counter log: Errors Corrected Total Total Correction Gigabytes Total delay: [rereads/ errors algorithm processed uncorrected minor | major rewrites] corrected invocations [10^9 bytes] errors read: 0 0 0 0 0 0.181 0 write: 0 0 0 0 2 0.000 0 [log sense: 4d 00 46 00 00 00 00 00 04 00 ] status=0 Incoming data, len=4: 00 06 00 00 08 [log sense: 4d 00 46 00 00 00 00 00 0c 00 ] status=0 Incoming data, len=12: 00 06 00 00 08 00 00 74 04 00 00 00 00 Non-medium error count: 0 [mode sense: 1a 00 0a 00 40 00 ] >>> Sense buffer, len=16: 00 70 00 05 00 00 00 00 12 00 00 00 00 24 00 00 c0 status=2: sense_key=5 asc=24 ascq=0 Device does not support Self Test logging Thank you, -- Hugo Caçote @ CERN IT |
From: Kai M. <Kai...@ko...> - 2004-08-30 21:22:04
|
On Mon, 30 Aug 2004, Hugo CACOTE wrote: > Dear Kai, > > > > > > Could you provide the output of 'smartctl -r ioctl,2 ...' when the error > > message occurs so that we can check that the report is correct. > > > > # smartctl -r ioctl,2 -a -T permissive /dev/st0 > smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ ... This is the log sense command returning the TapeAlert data: > [log sense: 4d 00 6e 00 00 00 00 01 44 00 ] > status=0 > Incoming data, len=324 [only first 256 bytes shown]: > 00 2e 00 01 40 00 01 40 01 00 00 02 40 01 00 00 03 > 10 40 01 00 00 04 40 01 00 00 05 40 01 00 00 06 40 > 20 01 00 00 07 40 01 00 00 08 40 01 00 00 09 40 01 > 30 00 00 0a 40 01 00 00 0b 40 01 00 00 0c 40 01 00 > 40 00 0d 40 01 00 00 0e 40 01 00 00 0f 40 01 00 00 > 50 10 40 01 00 00 11 40 01 00 00 12 40 01 00 00 13 > 60 40 01 00 00 14 40 01 00 00 15 40 01 00 00 16 40 > 70 01 00 00 17 40 01 00 00 18 40 01 00 00 19 40 01 > 80 00 00 1a 40 01 00 00 1b 40 01 00 00 1c 40 01 00 > 90 00 1d 40 01 00 00 1e 40 01 00 00 1f 40 01 00 00 > a0 20 40 01 00 00 21 40 01 00 00 22 40 01 00 00 23 > b0 40 01 00 00 24 40 01 00 00 25 40 01 00 00 26 40 > c0 01 00 00 27 40 01 01 00 28 40 01 00 00 29 40 01 ^^^^^^^^^^^^^^ Here the drive is really reporting 1 in the 0x27 flag. TapeAlert works so that each time the log page is read, the flags are cleared. This explains why you see the message only once. I don't have any good guesses why the drive sets the flag. It may be a real problem or the drive firmware interpreting something in a wrong way. Of course, it can be a smartctl bug but I can't see anything suspicuous in the output. -- Kai |
From: Hugo C. <hc...@ma...> - 2004-08-31 07:53:03
|
Dear Kai, > > [log sense: 4d 00 6e 00 00 00 00 01 44 00 ] > > status=0 > > Incoming data, len=324 [only first 256 bytes shown]: > > 00 2e 00 01 40 00 01 40 01 00 00 02 40 01 00 00 03 > > 10 40 01 00 00 04 40 01 00 00 05 40 01 00 00 06 40 > > 20 01 00 00 07 40 01 00 00 08 40 01 00 00 09 40 01 > > 30 00 00 0a 40 01 00 00 0b 40 01 00 00 0c 40 01 00 > > 40 00 0d 40 01 00 00 0e 40 01 00 00 0f 40 01 00 00 > > 50 10 40 01 00 00 11 40 01 00 00 12 40 01 00 00 13 > > 60 40 01 00 00 14 40 01 00 00 15 40 01 00 00 16 40 > > 70 01 00 00 17 40 01 00 00 18 40 01 00 00 19 40 01 > > 80 00 00 1a 40 01 00 00 1b 40 01 00 00 1c 40 01 00 > > 90 00 1d 40 01 00 00 1e 40 01 00 00 1f 40 01 00 00 > > a0 20 40 01 00 00 21 40 01 00 00 22 40 01 00 00 23 > > b0 40 01 00 00 24 40 01 00 00 25 40 01 00 00 26 40 > > c0 01 00 00 27 40 01 01 00 28 40 01 00 00 29 40 01 > ^^^^^^^^^^^^^^ > Here the drive is really reporting 1 in the 0x27 flag. Could you just tell me what (or where can I find this information) are the name of flags been read and in particular the 0x27 flag in order for me to report this to STK support. Thank you very much -- Hugo Caçote @ CERN IT |
From: Hugo C. <hc...@ma...> - 2004-08-31 09:00:37
|
Dear Kai, > > > status=0 > > > Incoming data, len=324 [only first 256 bytes shown]: > > > 00 2e 00 01 40 00 01 40 01 00 00 02 40 01 00 00 03 > > > 10 40 01 00 00 04 40 01 00 00 05 40 01 00 00 06 40 > > > 20 01 00 00 07 40 01 00 00 08 40 01 00 00 09 40 01 > > > 30 00 00 0a 40 01 00 00 0b 40 01 00 00 0c 40 01 00 > > > 40 00 0d 40 01 00 00 0e 40 01 00 00 0f 40 01 00 00 > > > 50 10 40 01 00 00 11 40 01 00 00 12 40 01 00 00 13 > > > 60 40 01 00 00 14 40 01 00 00 15 40 01 00 00 16 40 > > > 70 01 00 00 17 40 01 00 00 18 40 01 00 00 19 40 01 > > > 80 00 00 1a 40 01 00 00 1b 40 01 00 00 1c 40 01 00 > > > 90 00 1d 40 01 00 00 1e 40 01 00 00 1f 40 01 00 00 > > > a0 20 40 01 00 00 21 40 01 00 00 22 40 01 00 00 23 > > > b0 40 01 00 00 24 40 01 00 00 25 40 01 00 00 26 40 > > > c0 01 00 00 27 40 01 01 00 28 40 01 00 00 29 40 01 > > ^^^^^^^^^^^^^^ > > Here the drive is really reporting 1 in the 0x27 flag. > > Could you just tell me what (or where can I find this information) are the > name of flags been read and in particular the 0x27 flag in order for me to > report this to STK support. > In the scsi stream commands draft: flags from 1Ah to 27h Tape Drive Hardware Error. Thank you, -- Hugo Caçote @ CERN IT |