On Thu, Dec 30, 2004 at 02:10:07PM +0100, Piotr Marczak wrote:
> Package: scsitools
> Version: 0.8-1
> Severity: normal
> 
> 
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: sparc (sparc64)
> Kernel: Linux 2.4.27
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> 
> Versions of packages scsitools depends on:
> ii  debconf                     1.4.30.11    Debian configuration management 
> sy
> ii  libc6                       2.3.2.ds1-18 GNU C Library: Shared libraries 
> an
> ii  util-linux                  2.12-10      Miscellaneous system utilities
> 
> -- debconf information:
> * scsitools/info:
> 
> I'm trying to disable write cache in two SCSI drives with tools scsiinfo
> and scsi-config. Unfortunatelly I'm always getting such result:
> 
> # scsiinfo -c -R -X /dev/sda 0 1 0 0 0 65535 0 65535 65535
> Unable to store Caching Page 08h
> 00 00 00 20 00 00 00 20 00 00 00 00 00 00 00 00 
> 00 00 00 00 00 00 00 00 02 00 08 12 14 00 ff ff 
> 00 00 ff ff ff ff 00 20 00 00 00 00 00 00 00 00 
> 
> #
> 
> The same with scsi-config tool.
> Replacing options (i.e. 0 to 1) in command line gives nothing new.
> 
> Some info:
> Drives are Seagate Cheetah ST336607LC, brand-new.
> 
> Data from Caching Page
> ----------------------
> Write Cache                        1
> Read Cache                         1
> Prefetch units                     0
> Demand Read Retention Priority     0
> Demand Write Retention Priority    0
> Disable Pre-fetch Transfer Length  65535
> Minimum Pre-fetch                  0
> Maximum Pre-fetch                  65535
> Maximum Pre-fetch Ceiling          65535
> 
> # scsiinfo -cX /dev/sda
> 1 1 0 0 0 65535 0 65535 65535 
> 
> Info from dmesg:
> 
> SCSI subsystem driver Revision: 1.00
> sym.0.3.0: setting PCI_COMMAND_INVALIDATE.
> sym.0.3.1: setting PCI_COMMAND_PARITY...
> sym.0.3.1: setting PCI_COMMAND_INVALIDATE.
> sym0: <875> rev 0x14 on pci bus 0 device 3 function 0 irq 4,7e0
> sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym0: SCSI BUS has been reset.
> sym1: <875> rev 0x14 on pci bus 0 device 3 function 1 irq 4,7e6
> sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym1: SCSI BUS has been reset.
> scsi0 : sym-2.1.17a
> scsi1 : sym-2.1.17a
> Vendor: SEAGATE   Model: ST336607LC        Rev: 0007
> Type:   Direct-Access                      ANSI SCSI revision: 03
> Vendor: SEAGATE   Model: ST336607LC        Rev: 0007
> Type:   Direct-Access                      ANSI SCSI revision: 03
> Vendor: TOSHIBA   Model: XM6201TASUN32XCD  Rev: 1103
> Type:   CD-ROM                             ANSI SCSI revision: 02
> sym0:0:0: tagged command queuing enabled, command queue depth 16.
> sym0:1:0: tagged command queuing enabled, command queue depth 16.
> Vendor: HP        Model: C1537A            Rev: L706
> Type:   Sequential-Access                  ANSI SCSI revision: 02
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> sym0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
> SCSI device sda: 71687372 512-byte hdwr sectors (36704 MB)
> Partition check:
> sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
> sym0:1: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
> SCSI device sdb: 71687372 512-byte hdwr sectors (36704 MB)
> sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8
> 
> System is Debian 3.1 on Sparc.
> 
> I have the same disk in other machine (IBM RS6000) and the same error
> occurs.
> 
> 
> Happy New Year.
> Peter

Hello Peter,
  sorry for the late reply. I was too busy last weeks.
Unfortunately, scsiinfo is not maintained for years and I even don't
have access to scsi disks anymore to do extensive tests.
Btw, a new tool named sginfo, which is somehow a derivative work from
scsiinfo, is available in sg3-utils Debian package. Can you try it and
see if it works better for you?

Best regards.
Eric.

-- 
 Eric Delaunay       | Quand on ne sait pas oł l'on va, il faut y aller !
 [EMAIL PROTECTED] | ... et le plus vite possible.       Devise Shadok.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to