SGI: Hardware

LSI SAS/SATA HBA's and the Fuel (or other IP35 Systems) - Page 2

As a follow up to the removable media drive portion of this topic, I attached an externally mounted Samsung SH-S203 SATA DVD-RW to an Onyx300 equipped with an LSI SAS3442X. The DVD drive is installed in an enclosure with a SAS/SATA SFF8470 multilane adapter/connector - it connects to the external multilane connector on the Onyx300/SAS3442X via an SFF8470 cable.

The drive appeared in an hinv -vm

Code: Select all

Integral SCSI controller 3: Version SAS/SATA LS1068
CDROM: unit 7 on SCSI controller 3
a CDROM icon appeared on the desktop, and when I inserted a DVD the desktop icon changed to read 'DVD'.

Unfortunately I was unable to access the contents of either the DVD or an OEM IRIX CD-ROM. The syslog reports:

Code: Select all

mediad: DIOCSELECT failed on CD-ROM /dev/rdsk/dks3d7vol: I/O error
[Alert] Illegal request: Invalid command code (asc=0x20, asq=0x0)  CDB: 1a 0 3f 0 fe 0
- so no joy.

IRIX reports the firmware on the SAS3442 as

Code: Select all

1068 SAS/SATA firmware version 0.6.9.0
which would be fairly ancient - so a firmware update is probably the next step.
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
^^ Pretty much the same as what I got.
Today I removed the LSI SAS3442X from the Onyx300 and installed it in an Intel box with PCI-X slots <running XP>. I connected the PC installed SAS3442X to the same external enclosure/Samsung SATA DVD-RW <with the same cabling>. After the system booted the new hardware wizard asked to be pointed at the driver and immediately afterwards the SATA DVD-RW appeared in my device tree <no reboot needed>. Tried several different CDs and DVDs - no problems :roll: So the LSI SAS3442X *will* allow the use of optical drives. I didn't make any changes to the firmware settings in the controller, I wonder what it is that IRIX doesn't like? <although every CD-RW or DVD-RW I've tried have generated a syslog message or two when a disk was inserted and/or read>

While the controller is in the intel box I'll reflash the firmware to see what effect that will have once it's back in the Onyx300.

EDIT: Looks like a firmware update will not be possible. The SAS3442X I have has the 1068(A0) chipset. The DOS boot disk version of the firmware updater for SAS3442X only has images for LSI 1068 chipsets version A3 through B3 - regardless if the updater is run in IR (Integrated RAID) or IT (Initiator Target) mode. <there is apparently a relatively new windows based flash installer tool, but as I write this, the download page for the SAS3442X omits the link to access the associated firmware/BIOS images>. I emailed LSI support and got a very prompt response; unfortunately it appears a firmware update for my A0 chipset SAS3442X will never be a possibility:
Please accept my apologies, but there is no firmware available for boards with the A0 chipset. This is a prototype board, so new later revisions were made.

Best Regards,
LSI Support
Global Support Service
I also mentioned the missing firmware images on the 3442X web page, and they fixed that within the hour.
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
My guess is that this *isn't* directly a controller or SATA issue. Both seem to have done what's expected of them - the LSI controller and the attached DVD-RW appear to IRIX when and where they should.

I'm starting to wonder if the underlying issue is IRIX's inability to correctly interpret/implement the use of <at least some> DVD-RW drives. The syslog error message complaining about an invalid command code is familiar - I got command code error messages when I connected a DVD-RW via one of the Yamaha SCSI>IDE adapters <and, as I recall, even with certain SCSI CD-RW drives>. I don't know enough about SCSI command codes to interpret how the implications of the command code error message < [Alert] Illegal request: Invalid command code (asc=0x20, asq=0x0) CDB: 1a 0 3f 0 fe 0 >.

The nekochan membership spans quite a bit of knowledge - anyone have any thoughts?
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
recondas wrote: My guess is that this *isn't* directly a controller or SATA issue. Both seem to have done what's expected of them - the LSI controller and the attached DVD-RW appear to IRIX when and where they should.

I'm starting to wonder if the underlying issue is IRIX's inability to correctly interpret/implement the use of <at least some> DVD-RW drives. The syslog error message complaining about an invalid command code is familiar - I got command code error messages when I connected a DVD-RW via one of the Yamaha SCSI>IDE adapters <and, as I recall, even with certain SCSI CD-RW drives>. I don't know enough about SCSI command codes to interpret how the implications of the command code error message < [Alert] Illegal request: Invalid command code (asc=0x20, asq=0x0) CDB: 1a 0 3f 0 fe 0 >.

The nekochan membership spans quite a bit of knowledge - anyone have any thoughts?

Its a mode sense command.
http://en.wikipedia.org/wiki/SCSI_Mode_Sense_Command

Was a SCSI device driver developer 10 years ago.
Its asking: "send me all your mode pages".. no more than 254 (0xfe) bytes.
The optical drive doesn't have SCSI mode pages... its SATA.
This error is usually not a show stopper.
It shouldn't fail because the device its talking to is not sharing its mode pages.



Regan
死の神はりんごだけ食べる

開いた括弧は必ず閉じる -- あるプログラマー

:Tezro: :Tezro: :Onyx2R: :Onyx2RE: :Onyx2: :O3x04R: :O3x0: :O200: :Octane: :Octane2: :O2: :O2: :Indigo2IMP: :PI: :PI: :1600SW: :1600SW: :Indy: :Indy: :Indy: :Indy: :Indy:
:hpserv: J5600, 2 x Mac, 3 x SUN, Alpha DS20E, Alpha 800 5/550, 3 x RS/6000, Amiga 4000 VideoToaster, Amiga4000 -030, 733MHz Sam440 AmigaOS 4.1 update 1.

Sold: :Indy: :Indy: :Indy: :Indigo: Tandem Himalaya S-Series Nonstop S72000 ServerNet.

@PymbleSoftware
Current Apps -> https://itunes.apple.com/au/artist/pymb ... d553990081
Cortex ---> http://www.facebook.com/pages/Cortex-th ... 11?sk=info
Minnie ---> http://www.facebook.com/pages/Minnie-th ... 02?sk=info
Github ---> https://github.com/pymblesoftware
Visit http://www.pymblesoftware.com
Search for "Pymble", "InstaElf", "CryWhy" or "Cricket Score Sheet" in the iPad App store or search for "Pymble" or "CryWhy" in the iPhone App store.
PymbleSoftware wrote:
recondas wrote: My guess is that this *isn't* directly a controller or SATA issue. Both seem to have done what's expected of them - the LSI controller and the attached DVD-RW appear to IRIX when and where they should.

I'm starting to wonder if the underlying issue is IRIX's inability to correctly interpret/implement the use of <at least some> DVD-RW drives. The syslog error message complaining about an invalid command code is familiar - I got command code error messages when I connected a DVD-RW via one of the Yamaha SCSI>IDE adapters <and, as I recall, even with certain SCSI CD-RW drives>. I don't know enough about SCSI command codes to interpret how the implications of the command code error message < [Alert] Illegal request: Invalid command code (asc=0x20, asq=0x0) CDB: 1a 0 3f 0 fe 0 >.

Its a mode sense command.
http://en.wikipedia.org/wiki/SCSI_Mode_Sense_Command

Its asking: "send me all your mode pages".. no more than 254 (0xfe) bytes.
The optical drive doesn't have SCSI mode pages... its SATA.
This error is usually not a show stopper.
It shouldn't fail because the device its talking to is not sharing its mode pages.


While I was back inside the Fool I re-attached the Pioneer DVD-Writer.

1) Yes, get that mesage with a small variation :

Code: Select all

dksc2d2vol: [Alert] Illegal request: Invalid command code (asc=0x20, asq=0x0)  CDB: 15 10 0 0 c 0


2) oddly, the desktop message when you double-click the icon is

Code: Select all

DVD disk type is still being identified.
Double-click again when icon shows DVD type above drive.

Except the icon does show the DVD type above the drive and it does change properly when you go from DVD to CD. Or it oes this about as reliably as the normal SCSI DVD-ROM does, which ain't all that great.

3) Off we go to cdrecord. Mmm, good

Code: Select all

fewel 10# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (mips-sgi-irix6.5) Copyright (C) 1995-2007 Jörg Schilling
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0     0) *
0,1,0     1) 'SEAGATE ' 'ST336706LW      ' '0108' Disk
0,2,0     2) *
0,3,0     3) *
0,4,0     4) *
0,5,0     5) *
0,6,0     6) *
0,7,0     7) *
scsibus1:
1,0,0   100) *
1,1,0   101) *
1,2,0   102) *
1,3,0   103) *
1,4,0   104) *
1,5,0   105) *
1,6,0   106) 'HL-DT-ST' 'DVDRAM GSA-4167B' 'DL11' Removable CD-ROM
1,7,0   107) *
scsibus2:
2,0,0   200) 'ATA     ' 'Hitachi HDP72505' 'A5CA' Disk
2,1,0   201) *
2,2,0   202) 'PIONEER ' 'DVD-RW  DVR-216 ' '1.09' Removable CD-ROM
2,3,0   203) *
2,4,0   204) *
2,5,0   205) *
2,6,0   206) *
2,7,0   207) *

That's encouraging ...

Code: Select all

fewel 15# cdrecord dev=2,2,0 -prcap
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (mips-sgi-irix6.5) Copyright (C) 1995-2007 Jörg Schilling
scsidev: '2,2,0'
scsibus: 2 target: 2 lun: 0
Using libscg version 'schily-0.9'.
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'PIONEER '
Identifikation : 'DVD-RW  DVR-216 '
Revision       : '1.09'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.

Drive capabilities, per MMC-3 page 2A:

Does read CD-R media
Does write CD-R media
Does read CD-RW media
Does write CD-RW media
Does read DVD-ROM media
Does read DVD-R media
Does write DVD-R media
Does read DVD-RAM media
Does write DVD-RAM media
Does support test writing

Does read Mode 2 Form 1 blocks
Does read Mode 2 Form 2 blocks
Does read digital audio blocks
Does restart non-streamed digital audio reads accurately
Does support Buffer-Underrun-Free recording
Does read multi-session CDs
Does read fixed-packet CD media using Method 2
Does not read CD bar code
Does not read R-W subcode information
Does read raw P-W subcode data from lead in
Does return CD media catalog number
Does return CD ISRC information
Does support C2 error pointers
Does not deliver composite A/V data

Does play audio CDs
Number of volume control levels: 256
Does support individual volume control setting for each channel
Does support independent mute setting for each channel
Does not support digital output on port 1
Does not support digital output on port 2

Loading mechanism type: tray
Does support ejection of CD via START/STOP command
Does not lock media on power up via prevent jumper
Does allow media to be locked in the drive via PREVENT/ALLOW command
Is not currently in a media-locked state
Does not support changing side of disk
Does not have load-empty-slot-in-changer feature
Does not support Individual Disk Present feature

Maximum read  speed:  7056 kB/s (CD  40x, DVD  5x, BD  1x)
Current read  speed:  7056 kB/s (CD  40x, DVD  5x, BD  1x)
Maximum write speed:  7056 kB/s (CD  40x, DVD  5x, BD  1x)
Current write speed:  5644 kB/s (CD  32x, DVD  4x, BD  1x)
Rotational control selected: CLV/PCAV
Buffer size in KB: 2000
Copy management revision supported: 1
Number of supported write speeds: 8
Write speed # 0:  8467 kB/s CLV/PCAV (CD  48x, DVD  6x, BD  1x)
Write speed # 1:  7056 kB/s CLV/PCAV (CD  40x, DVD  5x, BD  1x)
Write speed # 2:  5644 kB/s CLV/PCAV (CD  32x, DVD  4x, BD  1x)
Write speed # 3:  4233 kB/s CLV/PCAV (CD  24x, DVD  3x, BD  0x)
Write speed # 4:  3528 kB/s CLV/PCAV (CD  20x, DVD  2x, BD  0x)
Write speed # 5:  2822 kB/s CLV/PCAV (CD  16x, DVD  2x, BD  0x)
Write speed # 6:  1764 kB/s CLV/PCAV (CD  10x, DVD  1x, BD  0x)
Write speed # 7:   705 kB/s CLV/PCAV (CD   4x, DVD  0x, BD  0x)

Current performance according to MMC get performance:

Maximum performance according to MMC get performance:
End LBA:      281335
Read Speed:     8468 == 48x CD
Write Speed:    8468 == 48x CD

End LBA:      281335
Read Speed:     7056 == 40x CD
Write Speed:    7056 == 40x CD

End LBA:      281335
Read Speed:     5645 == 32x CD
Write Speed:    5645 == 32x CD

End LBA:      281335
Read Speed:     4234 == 24x CD
Write Speed:    4234 == 24x CD

End LBA:      281335
Read Speed:     3528 == 20x CD
Write Speed:    3528 == 20x CD

End LBA:      281335
Read Speed:     2823 == 16x CD
Write Speed:    2823 == 16x CD

End LBA:      281335
Read Speed:     1764 == 10x CD
Write Speed:    1764 == 10x CD

End LBA:      281335
Read Speed:      706 == 4x CD
Write Speed:     706 == 4x CD


Supported CD-RW media types according to MMC-4 feature 0x37:
Does write multi speed       CD-RW media
Does write high  speed       CD-RW media
Does write ultra high speed  CD-RW media
Does write ultra high speed+ CD-RW media

Supported profiles according to MMC-4 feature list:
Current: CD-ROM
Profile: DVD+R/DL
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-R/DL layer jump recording
Profile: DVD-R/DL sequential recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD-RAM
Profile: Removable Disk
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM (current)

Supported features according to MMC-4 feature list:
Feature: 'Profile List' (current) (persistent)
Feature: 'Core' (current) (persistent)
Feature: 'Morphing' (current) (persistent)
Feature: 'Removable Medium' (current) (persistent)
Feature: 'Write Protect'
Feature: 'Random Readable' (current)
Feature: 'Multi Read' (current)
Feature: 'CD Read' (current)
Feature: 'DVD Read'
Feature: 'Random Writable'
Feature: 'Incremental Streaming Writable'
Feature: 'Formattable'
Feature: 'Defect Management'
Feature: 'Restricted Overwrite'
Feature: 'DVD+RW'
Feature: 'DVD+R'
Feature: 'Rigid Restricted Overwrite'
Feature: 'CD Track at Once'
Feature: 'CD Mastering'
Feature: 'DVD-R/-RW Write'
Feature: 'Layer Jump Recording'
Feature: 'CD-RW Write'
Feature: 'DVD+R/DL Read'
Feature: 'Power Management' (current) (persistent)
Feature: 'S.M.A.R.T.'
Feature: 'CD Audio analog play'
Feature: 'Microcode Upgrade'
Feature: 'Time-out' (current) (persistent)
Feature: 'DVD-CSS'
Feature: 'Real Time Streaming' (current)
Feature: 'Logical Unit Serial Number' (current) (persistent)    Serial: 'HLDL081621CN'
Feature: 'Disk Control Blocks'
Feature: 'DVD CPRM'

even more encouraging ...

Code: Select all

fewel 17# cdrecord dev=2,2,0 -minfo
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (mips-sgi-irix6.5) Copyright (C) 1995-2007 Jörg Schilling
scsidev: '2,2,0'
scsibus: 2 target: 2 lun: 0
Using libscg version 'schily-0.9'.
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'PIONEER '
Identifikation : 'DVD-RW  DVR-216 '
Revision       : '1.09'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE
Supported modes: PACKET SAO LAYER_JUMP
WARNING: Phys disk size 2314080 differs from rzone size 2236704! Prerecorded disk?
WARNING: Phys start: 200704 Phys end 2514783
Mounted media class:      DVD
Mounted media type:       DVD-RAM
Disk Is erasable
data type:                standard
disk status:              illegal
session status:           complete
BG format status:         none
first track:              1
number of sessions:       1
first track in last sess: 1
last track in last sess:  1
Disk Is not unrestricted
Disk type: DVD, HD-DVD or BD

Track  Sess Type   Start Addr End Addr   Size
==============================================
1     1 Data   0          2236703    2236704

Last session start address:         0
Last session leadout start address: 2236704

Here's an interesting thing ...

Code: Select all

fewel 20# cdrecord dev=1,6,0 -minfo
Cdrecord-ProDVD-ProBD-Clone 2.01.01a35 (mips-sgi-irix6.5) Copyright (C) 1995-2007 Jörg Schilling
scsidev: '1,6,0'
scsibus: 1 target: 6 lun: 0
Using libscg version 'schily-0.9'.
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   :
Vendor_info    : 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-4167B'
Revision       : 'DL11'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
cdrecord: I/O error. get performance: scsi sendcmd: retryable error
CDB:  AC 00 00 00 00 00 00 00 00 01 03 00
status: 0xff 0x0 (Reserved)
Sense Bytes:
Sense Key: 0xFFFFFFFF [], Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.015s timeout 40s
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE
Supported modes: PACKET SAO
WARNING: Phys disk size 2314080 differs from rzone size 2236704! Prerecorded disk?
WARNING: Phys start: 200704 Phys end 2514783
Mounted media class:      DVD
Mounted media type:       DVD-RAM
Disk Is erasable
data type:                standard
disk status:              illegal
session status:           complete
BG format status:         none
first track:              1
number of sessions:       1
first track in last sess: 1
last track in last sess:  1
Disk Is not unrestricted
Disk type: DVD, HD-DVD or BD

Track  Sess Type   Start Addr End Addr   Size
==============================================
1     1 Data   0          2236703    2236704

Last session start address:         0
Last session leadout start address: 2236704


That's from the LG IDE DVD-Writer via a Yamaha adapter. That one is a total pain in the ass to use for DVD-writing but I have been successful with it.

So next time I get a moment I'll try writing to the SATA drive with cdrecord. It seems to be talking nicely to the drive, even better than the yamadapted drive.

Seems likely there's something goofed up in the graphical desktop rather than the underlying system. Damned graphical methods totally screw up formatting a DVD-RAM, too.

One question for people with two CD-ROM drives - do you have a /CDROM2 entry in the file system ? I do not .... altho hinv shows :

Code: Select all

Integral SCSI controller 3: Version IEEE1394 SBP2
Disk drive / removable media: unit 2 on SCSI controller 3
Integral SCSI controller 2: Version SAS/SATA LS1064
Disk drive: unit 0 on SCSI controller 2 (unit 0)
CDROM: unit 2 on SCSI controller 2
Integral SCSI controller 0: Version QL12160, low voltage differential
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version QL12160, single ended
CDROM: unit 6 on SCSI controller 1


definitely recognized ...

Code: Select all

fewel 4# scsicontrol -i /dev/scsi/sc*
/dev/scsi/sc0d1l0:  Disk          SEAGATE ST336706LW      0108
ANSI vers 3, ISO ver: 0, ECMA ver: 0; supports:  16bit synch linkedcmds cmdqueing
Device is  ready
/dev/scsi/sc1d6l0:  CD-ROM        HL-DT-STDVDRAM GSA-4167BDL11
ANSI vers 2, ISO ver: 0, ECMA ver: 0; supports:
Device is  ready
/dev/scsi/sc2d0l0:  Disk          ATA     Hitachi HDP72505A5CA
ANSI vers 5, ISO ver: 0, ECMA ver: 0; supports:  cmdqueing
Device is  ready
/dev/scsi/sc2d2l0:  CD-ROM        PIONEER DVD-RW  DVR-216 1.09
ANSI vers 0, ISO ver: 0, ECMA ver: 0; supports:
Device is  ready

Just doesn't work so far ...
Just mkdir /CDROM2 manually?...

Ian.
mapesdhs wrote: Just mkdir /CDROM2 manually?...

Can. And can forcibly mount it there also (or try, anyhow). Was mostly wondering if that is how Irix normally handles it ?
As in using /CDROM2 as a mount point for a 2nd device? Yes.

One thing though: be careful about using such a 2nd unit for installing software. swmgr gets confused
by /CDROM2, fails to properly track CD sources. Always use the /CDROM device with swmgr.

Ian.
hamei wrote: One question for people with two CD-ROM drives - do you have a /CDROM2 entry in the file system ?
Yep - autocreated when I booted with a second CD drive <tho it my case it's a SCSI attached CDRW drive>. Once created, the directory /CDROM2 is persistent unless manually removed.
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
^^ Okay, thanks guys, that will be the next step.
Just some general info for you all...

T'was my bday on 19th May, so I asked for some dosh from parents/brother, bought myself a 1TB SATA for
my PC (movie archiving), though I'll test it when I can in a Fuel with an LSI card, see how it fares.

Anyway, my PC has a 146GB Maxtor Atlas 15K II as a system disk, same model I use in almost all my
SGIs and the main drive I recommend for those who want the best in an SGI (plenty available if anyone's
interested! ;D). I thought a performance comparison with the SATA might be interesting, the classic
space vs. speed issue so often discussed. How well does the old SCSI drive compare? I like the Maxtor
because of its fast access time (ideal as a system disk, ie. searching files, etc.), but despite its
age (released November 2004) it holds up rather well against the SATA, except for burst read where
presumably the faster/larger cache RAM in the modern SATA has an advantage. The following is from
testing with HDTach, standard read test, in order of max sustained speed:

Code: Select all

Max        Min      Average     Burst    Random Access
(MB/sec)   (MB/sec)   (MB/sec)   (MB/sec)        (ms)

Seagate 146GB 15K ST3146855LC SCA:             135         81      113.9       196.4         5.7
Fujitsu 300GB 15K MBA3300NC                    131         69      107.3       223,2         7.1
Samsung SpinPoint F1 1TB SATA/300 HD103UJ:     115         55       89.8       235.9        16.5
Maxtor Atlas 15K II 146GB 8K147J0 SCA:         105         63       89.3       177.7         5.7
Seagate 18GB 15K ST318452LC SCA:                61         45       55.0       128.8         5.9
Fujitsu 18GB 15K MAM3184MC SCA:                 57         44       53.4       144.2         6.0
Seagate 9GB 15K BF00963643 SCA:                 42         36       38.6       128.1         6.3


Note the average sustained speed is almost identical between the Samsung and the Maxtor (shows how long it's taken
for IDE/SATA to catch up), but check out the average access times! Also rather interesting, I first tested the Samsung
using the PC mbd's onboard Marvell RAID controller, which gave a substantially lower Burst rate (155MB/sec) and a
slightly lower average rate that matched the Maxtor (89.3). Looks like the choice of SATA controller in a PC is important
(the mbd's NVIDIA controller is much better).

For a real world test, I copied a 6.7GB VOB file from the Maxtor to the Samsung, which completed in 80 seconds, avg
speed 84MB/sec.

The Samsung isn't the fastest SATA around, but it's pretty high up the scale and is a decent tradeoff between speed and
price (in UKP, 65 + 6 shipping from CCL Online).


Are there any gotchas I should watch out for though when testing the Samsung with the Fuel?

Ian.
Regarding newer drives, high platter densities mean that the areal transfer rates have gone way up on consumer drives lately - but as your test has noted the access times (and latencies) would still be better on the 15k drives. The 10k SATA drives are likely in the middle.

As for testing gotchas, I'd be concerned that for large contiguous files the SATA drive will post good numbers, but for small file accesses with lots of random seeks, the 15k SCSI drive will likely still win out by a fair margin. As a note, I always try to use a 15k drive as the root drive on any of the later-model SGI's I have - and for the Fuel this combo with a large consumer SATA/IDE drive for bulk storage (ie: homes) seems to be the best of both worlds. The root drive doesn't have to be more than 18GB or so to give you ample room for just about anything you'd want to do if you set it up this way, and 18GB 15k drives are pretty cheap.

So keeping this in mind, probably the two tests I'd try is a huge contiguous file transfer, and maybe a 'find' function across the disk to replicate random seek timing effects, using a SATA drive which has a duplicate filesystem to ensure the tests are equivalent. 'Diskperf' is actually a pretty good tool for easily showing this, though since it uses only the portion of the disk that the temp file is on, the numbers only represent a portion of the transfer curve for the platter.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day
Dr. Dave writes:
> Regarding newer drives, high platter densities mean that the areal transfer rates have gone way up on consumer drives lately
> - but as your test has noted the access times (and latencies) would still be better on the 15k drives. The 10k SATA drives are
> likely in the middle.

Yup, that makes sense.

Btw, an update on the 'best' 15K drive for SGIs. Ok, so I'll admit I'm surprised. Today I received a Fujitsu 300GB 15K SCA SCSI
(which will now be the new system disk in my Fuel), a drive I bought 'cos the price was good and I needed more space in my
Fuel. First, here's the diskperf for a Maxtor 15K II 146GB:

Code: Select all

# req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#  (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#---------------------------------------------------------
16384   54.97   63.18   46.53    4.31    8.07    4.65
32768   75.20   88.89   65.67    9.07   14.60    8.85
65536   89.38   97.03   75.82   20.21   23.55   15.83
131072   89.35   97.11   72.84   26.67   34.56   25.64
262144   89.54   96.84   73.22   45.07   48.67   39.29
524288   89.03   73.91   78.00   53.26   59.15   53.85
1048576   89.38   78.83   80.96   68.68   68.99   66.06
2097152   90.35   77.97   77.15   78.24   75.46   75.88
4194304   89.95   85.12   83.23   85.36   82.89   84.29


Ok, pretty good, but now check the Fujitsu (the model is MBA3300NC):

Code: Select all

# req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#  (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#---------------------------------------------------------
16384   59.87   68.97   30.55   27.13   10.23    5.30
32768   80.08   93.85   34.26   33.87   17.71   10.04
65536   94.37  114.01   56.67   38.45   29.14   18.21
131072   92.95  117.03   43.56   43.48   32.49   31.45
262144  102.52  124.69   44.35   44.50   51.88   48.31
524288  107.48  124.89   66.54   67.23   72.67   67.22
1048576  109.85  124.88   89.21   90.17   91.55   86.17
2097152  112.99  124.93  105.37  102.76  104.32   99.83
4194304  114.38  124.92  110.83  109.11  111.25  109.44


Good grud! This is the first SCSI disk I've come across that can sustain more than 100MB/sec, but it's way over 100! Wow! 8)

So, I guess I'd now have to say this Fujitsu is the best possible SCSI disk for an SGI, but they're hard as hell to find (certainly
for a decent price anyway - I was damn lucky for sure), whereas I have more than 50 of the Maxtors available...

If anyone comes across a drive that beats the above Fujitsu, please let me know! Hmm, before I fit it into the Fuel, I'll connect
it to my PC and run HDTach, see what it comes up with. Should be interesting...


> As for testing gotchas, I'd be concerned that for large contiguous files the SATA drive will post good numbers,
> but for small file accesses with lots of random seeks, the 15k SCSI drive will likely still win out by a fair margin.

Absolutely true, which is why I'm fortunate in this regard since I'll be using the SATA disk to store large files,
typically 500MB to 2GB, so the slower access time isn't an issue.


> As a note, I always try to use a 15k drive as the root drive on any of the later-model SGI's I have ...

Despite the lower sustained max speed, a 15K helps in Octane aswell, boosting file searches, etc. by more than 30%.
Any O3K machine just gets more out of them given the use of an U160 bus, though of course Octane can aswell if
the disk is connected via better SCSI card.


> ... doesn't have to be more than 18GB or so to give you ample room for just about anything you'd want to do if you
> set it up this way, and 18GB 15k drives are pretty cheap.

(I even have a couple of 9GB 15Ks available! Wierd huh? I didn't know anyone made 9GB 15Ks)

An 18GB 15K is certainly cheap, but it's not very fast. Infact an 18GB 15K is typically slower than a reasonable
36GB or 73GB 10K for sustained read/write. For example, here's a typical 18GB 15K Seagate (all these tests were
done with a Fuel/600):

Code: Select all

# req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#  (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#---------------------------------------------------------
16384   41.21   41.36    8.93    4.31    6.45    3.45
32768   41.27   41.45   15.31    9.37   10.94    6.18
65536   41.29   41.45   22.38   11.31   17.01   10.43
131072   41.39   41.46   28.82   20.23   24.82   15.70
262144   41.04   41.44   32.13   25.87   30.34   21.17
524288   40.50   41.42   33.75   32.43   31.06   30.52
1048576   39.70   41.44   37.78   33.61   31.94   33.82
2097152   39.31   41.41   32.26   38.43   32.61   37.38
4194304   38.75   41.38   35.42   38.66   31.80   38.51


That's pretty horrible. Would the access time really be all that good? I'm not so sure. Either way, compare the above
to a Fujitsu 73GB 10K:

Code: Select all

# req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#  (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#---------------------------------------------------------
16384   54.35   55.74   22.08   21.95    9.11    3.88
32768   61.80   70.82   25.12   25.99   15.21    7.34
65536   70.20   80.40   42.42   29.54   23.92   13.28
131072   76.87   83.65   29.09   29.08   24.06   21.62
262144   82.66   88.36   31.38   29.07   37.65   32.90
524288   86.61   88.42   48.59   43.52   52.78   45.43
1048576   88.80   88.63   66.71   57.91   66.33   62.12
2097152   88.78   88.55   80.09   69.35   75.50   70.96
4194304   88.69   88.78   84.57   76.97   81.84   78.35


Blows the 18GB 15K away completely.

I'm sure the 18GB 15K was nice when drives were typically no more than 18GB max capacity, but at least for sustained read/write
they've long since been surpassed by newer 10K drives.

If I get a chance, I'll try one of the 18GB 15Ks with HDTach aswell, see what it says about average access time.

(EDIT: tested! Susained 18GB 15K speed isn't that good, but the access time, 6ms, is still way better than the SATA, and not that
much slower than modern 15Ks. See the table in my previous post, ammended with extra results)


> So keeping this in mind, probably the two tests I'd try is a huge contiguous file transfer, and maybe a 'find' function across the
> disk to replicate random seek timing effects, using a SATA drive which has a duplicate filesystem to ensure the tests are

Yes, I already have a 'find' test, consists of searching all of the contents of /usr/share (pre-copied onto a target drive before
a reboot prior to the test), 715MB of data, more than 54000 files, ie. searching for a non-existent file forces the search to
scan the entire archive. System is rebooted before each test of course. I've not tried this test with any newer models such as the
Maxtor mentioned earlier, but here's an example comparison of a 10K vs. a 15K in a Fuel/500:

Code: Select all

Search Time
(seconds)

36GB 15K:     11.08
36GB 10K:     18.32


ie. about 40% faster with a 15K.


> ... though since it uses only the portion of the disk that the temp file is on, the numbers only represent a portion of the
> transfer curve for the platter.

If the disk is blank via a freshly done mkfs, where on the drive will the file be placed when one does a mkfile to create
the test file? On the slowest part of the platters, or the fastest? Do all disks default to writing data in the same place when
they're initially empty?

Either way, I'm slowly building up a collection of diskperfs for various drives. When I have a decent number, I'll add the
info as links from my disks-for-sale page, and keep the entries shown even when I've none in stock (text will be in
italics) so the reference info is still accessible.

EDIT:

Just discovered one of my Seagate 146GB/15Ks is pretty fast too (faster than the Maxtor), ie. the ST3146855LC:

Code: Select all

# req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#  (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#---------------------------------------------------------
16384   61.86   70.91   35.78   13.71   10.10    4.78
32768   81.17   93.59   55.53   17.91   19.06    9.02
65536   95.78  114.09   75.43   29.28   32.90   15.81
131072  105.75  128.86   92.64   42.90   51.67   25.62
262144  112.39  134.28  102.58   43.24   68.36   38.02
524288  115.86  134.05   64.30   48.24   71.51   50.17
1048576  117.45  134.01   85.31   64.54   92.22   59.12
2097152  117.99  133.80  101.38   86.01   94.91   84.19
4194304  118.53  128.88  112.93  108.64  110.52  107.86


Seems to be slightly faster than the Fujitsu.

Dr Dave, I added a few more results to the table in my last post (have a look). It seems you were right; though the
sustained rates with the older 15K drives is much less, the access time remain nice and fast.

Ian.
Quick update...

I've tested a 1TB SATA drive on a Fuel with an LSI SAS3442X-R SAS/SATA card and it works fine!

Check the hinv , and here's the diskperf/df output (the SATA drive is the one mounted on /0):

Code: Select all

#  req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#   (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#----------------------------------------------------------
16384   64.18   65.03   47.89   33.18    4.44    2.27
32768   75.78   99.78   88.04   37.53    8.73    4.42
65536  106.05  111.59  106.76   42.43   16.23    8.48
131072  112.12  114.28  107.58   49.08   27.45   15.77
262144  106.30  113.90  106.95   56.80   41.58   27.56
524288  106.15  113.59  106.60   55.57   57.88   44.60
1048576  112.30  113.14  107.58   79.46   74.57   62.15
2097152  111.39  110.91  106.38   85.67   86.97   80.43
4194304  111.30  109.20  108.82  102.21   98.86   93.09

Filesystem             Type  kbytes     use     avail  %use Mounted on
/dev/root               xfs 71545548 10065788 61479760  15  /
/dev/dsk/dks0d2s7       xfs 143368692 88316288 55052404  62  /i
/dev/dsk/dks4d0s7       xfs 976641304  1058736 975582568   1  /0


So, the 1TB SATA gives 953GB of usable space (via 1MB = 1024KB, etc.). I'm just about to run a speed
test to compare access times to the system disk and Maxtor 15K data disk. More shortly...

Oh, I also tested a SUN SAS drive which worked ok, a Hitachi 146GB 10K, model H101414SCSUN146G. Have
a few more to test this evening...

---

More results from the SAS drives! First, a SUN-badged Hitachi 146GB 10K (H101414SCSUN146GSA23):

Code: Select all

#  req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#   (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#----------------------------------------------------------
16384   66.93   88.90   12.57    2.80    9.13    3.70
32768   88.78   88.77    2.86    5.82   17.25    7.09
65536   88.81   88.81   44.03   12.37   26.42   13.36
131072   88.85   88.91   28.88   28.93   22.73   23.13
262144   88.90   88.81   31.21   31.19   36.29   36.41
524288   88.87   88.81   48.22   43.25   51.17   49.96
1048576   88.87   88.81   71.19   60.99   65.04   64.45
2097152   88.81   88.87   80.43   77.48   74.89   73.86
4194304   88.76   88.77   81.77   81.00   80.67   80.02
8388608   88.70   88.82   85.23   83.58   84.46   83.79



Here's a SUN-badged Seagate 146GB 10K SAS (ST9146802SS):

Code: Select all

#  req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#   (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#----------------------------------------------------------
16384   89.90   90.43   46.32    6.93    8.37    3.60
32768   90.28   91.42   79.54   11.84   15.99    7.06
65536   90.46   91.60   81.42   19.29   27.38   12.87
131072   90.76   91.67   80.76   40.48   42.99   22.81
262144   90.22   91.64   80.61   36.54   57.97   36.35
524288   90.73   91.56   48.78   49.01   51.38   52.39
1048576   90.60   91.07   73.19   73.07   65.98   65.84
2097152   90.60   91.41   82.14   82.87   75.56   76.49
4194304   90.46   91.52   82.47   83.19   82.89   82.68


Nice! Now here's two of the Seagates in an XLV optimised for HD:

Code: Select all

#  req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#   (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#----------------------------------------------------------
8294400  178.27  178.26  165.34  149.33  161.85  144.29
16588800  177.98  178.83  166.97  157.04  167.76  158.16



And now top of the pack, the SAS version of the Seagate 15K mentioned in my earlier post (ST3146855SS):

Code: Select all

#  req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#   (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#----------------------------------------------------------
16384   89.72   90.32   50.68    8.88   10.45    4.90
32768  112.64  131.40   83.82   31.66   19.29    9.42
65536  120.24  131.57  116.86   34.55   34.71   17.76
131072  126.29  131.47  115.22   59.47   56.88   31.54
262144  129.34  131.66  115.01   57.21   76.17   50.46
524288  130.70  131.36   65.12   65.41   72.12   73.24
1048576  130.75  131.41   86.91   87.12   93.33   93.63
2097152  130.81  131.41  103.98  104.46  108.36  107.43
4194304  130.64  131.56  115.35  116.02  118.92  117.31
8388608  130.58  131.56  122.97  122.64  124.81  122.20


The SCSI version of this drive is significantly slower for sequential read/writes of smaller request sizes, but
much the same for larger sizes, though the SAS is more consistent.


Lastly, though not an optimal arrangement since it's using three different models, here's an XLV of four
146GB 10K SAS drives, optimised for HD:

Code: Select all

#  req_size  fwd_wt  fwd_rd  bwd_wt  bwd_rd  rnd_wt  rnd_rd
#   (bytes)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)  (MB/s)
#----------------------------------------------------------
8294400  216.83  312.60  212.35  231.79  212.48  256.24
16588800  217.63  315.13  216.18  273.97  215.73  278.73


Either way, the LSI card works very well!

Ian.
Darn. You beat me to the SAS drive test.
All because my Fuel is still at your warehouse... ;)
:O3200: :Fuel: :Indy: :O3x02L:
ramq wrote: Darn. You beat me to the SAS drive test.
All because my Fuel is still at your warehouse... ;)


Yeah, sorry about that; couldn't post anything last week, spent all my time tidying up the place ready for
a Landlord/property inspection (rented house). Most inconvenient...

Ian.
I've got a couple of Seagate ST973402SS drives I want to evaluate. :D
:O3200: :Fuel: :Indy: :O3x02L:
ramq wrote: I've got a couple of Seagate ST973402SS drives I want to evaluate. :D


They should perform the same as the ST9146802SS mentioned earlier, as it's the same model
range (Savio 10K II), ie. 90MB/sec for one drive, just under 180MB/sec for two in XLV.

Ian.
Most probably, yes.
I've got access to those drives as well, but since you already covered them...
:O3200: :Fuel: :Indy: :O3x02L: