Dell Compellent SC200 disk shelf (Individual Drive LEDs not working) (how to identify drives in which bay)

[BigJ]

Hello all, first time posting so please forgive some of my transgressions, some feedback on what I could do better would be greatly appreciated.

I have more or less successfully configured a Dell SC200 to work in Truenas. However, I had one sata drive (since replaced with a sas drive) showing errors. The problem is all of the individual drive LED lights (green activity lights + some other led) are not working. Well only one drive LED was working. Additionally, It was pretty hard to figure out which drive is in which slot! (manually checked each serial number when I did the swap) so I would love to see all the Blinky lights working . Note, I have it configured as a DAS connected to the T420 thru a SAS card in IT mode. I am just a tinkerer and this setup is probably non standard. On a side note, it seems weird to me why the backplane lights don't work straight out of the box so to speak. It seems unlikely that many LEDs are dead, and a little perplexing why some lights actually do work.

In an effort to try and understand what was going on I swapped out the SC200 for a second one I had on hand. Same result, except there were two drives that lit up. I can't help but think there is some kind of setting and that maybe thru the serial connection I have partially working I could send some kind of command. However, I have reached a point where I am stuck.

NEED HELP WITH THE FOLLOWING (Goal is to have all Drive LEDs working, with an additional goal to figure out how to associate a drive to a slot)


1) How do I get a command prompt from the SC200 serial connection, I would like to pass commands and see responses. I can confirm that an "echo" command gets thru to the serial port on the SC200 as I can change the fan speeds, but I can't figure out for the life of me how "fohdeesha" (forum post number one listed below) got an interactive command prompt from their Dell MD1200. When I try "Screen /dev/ttyS1 84200" or similar "Tmux" command all I get is an error:

root@truenas[~]# tmux /dev/ttyS1 38400
error connecting to /tmp/tmux-0/default (No such file or directory)
root@truenas[~]#

(note "screen" does not exist in Truenas so I tried "Tmux", but the only instruction I could find used "screen" so I was not 100% sure how to translate that to Tmux). Follow up, according to a post over in truenas site, Tmux does not support serial port connections...

I also tried "agetty", but didn't know how to translate (RS232, 38400-8-n-1) into a usable command. I press enter and then nothing...

root@truenas[~]# agetty
agetty: not enough arguments
root@truenas[~]# agetty /dev/ttyS1
root@truenas[~]# agetty ttyS1 38400 vt100
root@truenas[~]#

Tried minicom,
root@truenas[~]# minicom /dev/ttyS1
minicom: cannot open /dev/modem: No such file or directory

got somewhere with...

root@truenas[~]# minicom -D /dev/ttyS1

Welcome to minicom 2.8

OPTIONS: I18n
Port /dev/ttyS1, 03:48:40

Press CTRL-A Z for help on special keys

but it just hangs there...

Next I tried to see if "cu" will work, arrrg this feels like the closest I have got!

root@truenas[~]# cu -l /dev/ttyS1 -s 38400 -h --nostop --parity=none dir
cu: open (/dev/ttyS1): Permission denied
cu: /dev/ttyS1: Line in use



2) If by some miracle I can get access to a terminal with the SC200, I don't know what command to use and the syntax of it (to turn on the LEDs). Fohdeesha referenced that they could send commands, but I don't know how they did it. For example there are about a dozen "LED" references I found in a dump of commands posted to Pastebin (by Fohdeesha I think see third link in research section below) that look like maybe one of them could turn on the LEDs such as:

1. _ledconfig Show LED Configuration Settings
2. _ledmode Set Mode for led: ledmode <number><direction><state>
3. _ledread Read LED GPIO value: ledread <number>
4. _ledset Set LED GPIO Value: ledset <number><state>
5. _ema_poll Turns on or off the analysis polling. Disables SES & LED update
6. _rdled LED Control Register Read: rdled <offset> <# of 32 bit words>
7. _slotled Control Slot LEDs: slotled <slot><pattern> (slot > MaxDrive = 'all')
8. drive_led Write drive led: <logicaldrive> <data>
9. shelf_led Write shelf led: <data> <0 - Disable; 1 - Enable>

Some of these commands look promising. But these setting have values I don't understand?

3) I did come across something called "sesutil" that looked like it could be used to assign drives to a port # on the enclosure but it is not installed on Truenas scale. Side Note, I don't know how to add a repository to apt-get that would allow me to download the software. So I put it to the side for the time being.



Equipment summary:

Dell PowerEdge T420 with two SAS HBA's flashed to IT mode:

1. LSI SAS Host Bus Adapter 16-Port 6Gbp/s Full Height SAS9200-16e
2. The stock Perc h710p (half hight pcie x8 card) that was populated in the T420

Dell Compellent SC200 populated with the max 12 x 3tb sas drives
(the sc200 is connected to the SA9200-16e card via a SFF-8088 cable)

OS - Truenas Scale from the shell "Linux truenas 5.15.131+truenas #1 SMP"

output from "sas2flash -listall"
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved
Adapter Selected is a LSI SAS: SAS2116_1(B1)
Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr
---------------------------------------------------------------------------
0 SAS2116_1(B1) 05.95.02.00 05.02.00.00 No Image 00:02:00:00
1 SAS2308_2(D1) 20.00.07.00 14.01.00.06 No Image 00:08:00:00
Finished Processing Commands Successfully.
Exiting SAS2Flash.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

output from "lsscsi" (BOLD underlined done by me)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[0:0:0:0] disk SEAGATE ST3000NM0023 GE09 /dev/sda
[0:0:1:0] disk SEAGATE ST33000650SS RS0D /dev/sdb
[0:0:2:0] disk WD WD3001FYYG D1R5 /dev/sdc
[0:0:3:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdd
[0:0:4:0] disk WD WD3001FYYG D1R5 /dev/sdf
[0:0:5:0] disk WD WD3001FYYG D1R5 /dev/sde
[0:0:6:0] disk WD WD3001FYYG D1R5 /dev/sdg
[0:0:7:0] disk WD WD3001FYYG D1R2 /dev/sdh
[0:0:8:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdi
[0:0:9:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdk
[0:0:10:0] disk SEAGATE ST3000NM0023 GS0D /dev/sdj
[0:0:12:0] enclosu DELL SC200 1.03 -
[0:0:13:0] disk SEAGATE ST3000NM0023 0006 /dev/sdo
[5:0:0:0] disk ATA OCZ-VERTEX2 1.37 /dev/sdm
[7:0:0:0] enclosu AHCI SGPIO Enclosure 2.00 -
[9:0:0:0] disk Dell Internal Dual SD 1.: /dev/sdn
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

In my research I have used the following forum posts:

1. https://forums.servethehome.com/index.php?threads/fun-with-an-md1200-md1220-sc200-sc220.27487/
   1. I was able to successfully create the cable to connect to the PS2 port from the T420 serial as in the post
2. https://www.reddit.com/r/unRAID/comments/l5pa2g
   1. I was able to issue the following commands from the shell
      1. stty -F /dev/ttyS1 38400 raw -echoe -echok -echoctl -echoke
      2. echo -e -n 'set_speed 20\r' > /dev/ttyS1
3. Pastebin for all the commands available for the SC200:
   1. SC200 - Pastebin.com
4. Additional info on the cable
   1. Dell part # for MD1000/MD3000 debug/password reset cable? | DELL Technologies

I can confirm the "echo" command works as the SC200 fans spool down. I honestly don't think I actually need the first command as I can issue the "echo" command right after a cold boot without doing the first command. I don't understand what role the"\r" has in the echo command.

 

[jabuzzard]

Are you sure this is not down to the "ready light meaning" which is a setting on the drives? Use the following to change the state

sdparm --set=RLM /dev/sdXX
sdparm --clear=RLM /dev/sdXX

This is only temporary and is lost if the drive is power cycled. You need to add a --save if you want to write the setting to the drive firmware.

 

[BigJ]

Hi thanks for the great feedback, it never even occurred to me it might be an HDD setting. Unfortunately no joy with the setting command, it did help me with more things to research and so I have more information:

If I run "lsscsi"
root@truenas[~]# lsscsi
[0:0:0:0] disk SEAGATE ST3000NM0023 GE09 /dev/sda
[0:0:1:0] disk SEAGATE ST33000650SS RS0D /dev/sdc
[0:0:2:0] disk WD WD3001FYYG D1R5 /dev/sdb
[0:0:3:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdd
[0:0:4:0] disk WD WD3001FYYG D1R5 /dev/sde
[0:0:5:0] disk WD WD3001FYYG D1R5 /dev/sdf
[0:0:6:0] disk WD WD3001FYYG D1R5 /dev/sdg
[0:0:7:0] disk WD WD3001FYYG D1R2 /dev/sdj
[0:0:8:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdh
[0:0:9:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdi
[0:0:10:0] disk SEAGATE ST3000NM0023 GS0D /dev/sdk
[0:0:11:0] disk SEAGATE ST3000NM0023 0006 /dev/sdl
[0:0:12:0] enclosu DELL SC200 1.03 -
[5:0:0:0] disk ATA OCZ-VERTEX2 1.37 /dev/sdm
[7:0:0:0] enclosu AHCI SGPIO Enclosure 2.00 -
[9:0:0:0] disk Dell Internal Dual SD 1.: /dev/sdn

I then found this command suggested by a Reddit post (dd if=/dev/urandom of=dev/sdXX) to help identify a specific drive.
I do have two drives that light up (prior to using the "sdparm" command)
So after running that command one drive at a time, I now know the two drives with the working lights are:
/dev/sda
/dev/sdi
So both Seagate drives, it stands to reason the other Seagate drives should light up right?

is there a way to query those two particular drives to determine their settings? I am still researching how "sdparm" works.

(edit)
To be clear I ran the below commands against all 12 drives in the enclosure:
sdparm --set=RLM /dev/sdXX
sdparm --clear=RLM /dev/sdXX

(Update 1)
With some google foo I found the "--get" parameter, so:
root@truenas[~]# sdparm --get=RLM /dev/sda
/dev/sda: SEAGATE ST3000NM0023 GE09
RLM 0 [cha: y, def: 0, sav: 0]

root@truenas[~]# sdparm --get=RLM /dev/sdc
/dev/sdc: SEAGATE ST33000650SS RS0D
RLM 0 [cha: y, def: 1, sav: 1]

root@truenas[~]# sdparm --get=RLM /dev/sdh
/dev/sdh: SEAGATE ST3000NM0023 GE09
RLM 0 [cha: y, def: 0, sav: 0]

So drive:
/dev/sda has "cha: y, def: 0, sav: 0" (this drive the LED light works)
/dev/sdc has "cha: y, def: 1, sav: 1" (this drive LED light not working)
/dev/sdh has "cha: y, def: 0, sav: 0" (this drive LED light not working)

SDA and SDH same firmware, SDC different model and firmware!

What does this mean?

(Update 2)

Found some great info at these two sites regarding "sdparm"

1. Solid Activity Light on Backplane for SAS Drive | JC-LAN.org
2. SAS drives, Firmware and SCSI mode pages

So I think I found some answers from one of the above links :

*****************************Start Quote************************************
Let's take the original (truncated) output:

PPID 6 [cha: n, def: 6, sav: 6]
The first field,

PPID 6 [cha: n, def: 6, sav: 6]
Indicates the tag name "PPID" and current value "6".

The second filed,

PPID 6 [cha: n, def: 6, sav: 6]
tells us if we can change that value, which in this case is no.

The third field,

PPID 6 [cha: n, def: 6, sav: 6]
indicates the default value.

The fourth field,

PPID 6 [cha: n, def: 6, sav: 6]
indicates the saved value.

So in the case of my RLM bit,

RLM 0 [cha: y, def: 0, sav: 0]
if I issue the command:
"sdparm --set=RLM pd1", the output of the RLM bit will show:

RLM 1 [cha: y, def: 0, sav: 0]
Which indicates that the RLM bit is set to "1" but not yet saved sop a reboot of the system will turn the bit back to the sav value or "0" which means the led will be on.

In order to save it, the same command can be issued with and extra option: "sdparm --set=RLM --save pd1" and the output will now look like this:

RLM 1 [cha: y, def: 0, sav: 1]
Confused yet?
***********************************End Quote*************************************

I cycle through these commands but still can't get the light to work? Is my assumption correct that I don't need to reboot the SC200 for the changes to take?

(Update 3)

Ok so the output for all 12 drives from: sdparm --get=RLM /dev/sdX
(green means drive LED is on) (Note sdparm outputs on multiple lines so the red hash indicates where these are, just wanted to get the output all on one row to help compare.)

root@truenas[~]# sdparm --get=RLM /dev/sda # /dev/sda: SEAGATE ST3000NM0023 GE09 # RLM 0 [cha: y, def: 0, sav: 0]
root@truenas[~]# sdparm --get=RLM /dev/sdb # /dev/sdb: WD WD3001FYYG D1R5 # RLM 0 [cha: y, def: 1, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sdc # /dev/sdc: SEAGATE ST33000650SS RS0D # RLM 0 [cha: y, def: 1, sav: 0]
root@truenas[~]# sdparm --get=RLM /dev/sdd # /dev/sdd: SEAGATE ST3000NM0023 GE09 # RLM 1 [cha: y, def: 0, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sde # /dev/sde: WD WD3001FYYG D1R5 # RLM 1 [cha: y, def: 1, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sdf # /dev/sdf: WD WD3001FYYG D1R5 # RLM 1 [cha: y, def: 1, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sdg # /dev/sdg: WD WD3001FYYG D1R5 # RLM 0 [cha: y, def: 1, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sdh # /dev/sdh: SEAGATE ST3000NM0023 GE09 # RLM 0 [cha: y, def: 0, sav: 0]
root@truenas[~]# sdparm --get=RLM /dev/sdi # /dev/sdi: SEAGATE ST3000NM0023 GE09 # RLM 0 [cha: y, def: 0, sav: 0]
root@truenas[~]# sdparm --get=RLM /dev/sdj # /dev/sdj: WD WD3001FYYG D1R2 # RLM 0 [cha: y, def: 1, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sdk # /dev/sdk: SEAGATE ST3000NM0023 GS0D # RLM 0 [cha: y, def: 1, sav: 1]
root@truenas[~]# sdparm --get=RLM /dev/sdl # /dev/sdl: SEAGATE ST3000NM0023 0006 # RLM 0 [cha: y, def: 0, sav: 0]

Sticking to just the same drives (model and firmware) I am confused as to why some but not all Seagate GE09 drive LEDs are not on? What am I missing!

 

[BigJ]

Are you sure this is not down to the "ready light meaning" which is a setting on the drives? Use the following to change the state

sdparm --set=RLM /dev/sdXX
sdparm --clear=RLM /dev/sdXX

This is only temporary and is lost if the drive is power cycled. You need to add a --save if you want to write the setting to the drive firmware.

This is great information thanks, it allowed me to narrow things down, but I am still having problems. I have posted some more results, when you have some free time could you take a look and see if you can spot something I am doing wrong or not understanding.

many thanks

 

[BigJ]

New update, I was having no luck with using sdparm, even with the drives that did have working lights (e.g. could I turn the LED off), so I did a test. I pulled the drive (after I shutdown the OS) with the working LED and swapping around a drive with not working LED. The result was the working LED slot with the new drive continued to work and the non working slot LED continued to not work. This would indicate that the SC200 chassis would be the source of the problem.

On a side note, after I shuffled the drives around (I did it with the power still on, on the SC200, the server box T420 was off, are you able to do that? or was it bad form and I should have turned the SC200 off as well) this swap seems to have borked my ZFS drive (Raidz2 12 drives), not a big deal I will just create it again.

I feel like I should turn my attention back to figuring out how to get a command prompt from the SC200 serial connection. So the last and most promising avenue looks like this:

******************
Next I tried to see if "cu" will work, arrrg this feels like the closest I have got!

root@truenas[~]# cu -l /dev/ttyS1 -s 38400 -h --nostop --parity=none dir
cu: open (/dev/ttyS1): Permission denied
cu: /dev/ttyS1: Line in use

******************

from my first post.

This is what I am trying to achieve:


Though instead of blueDress which I think is the MD1200, the SC200 I think is 12Pack

 

[BigJ]

I have found some new commands:
lsscsi -g
root@truenas[~]# lsscsi -g
[0:0:0:0] disk SEAGATE ST3000NM0023 GE09 /dev/sda /dev/sg2
[0:0:1:0] disk SEAGATE ST33000650SS RS0D /dev/sdc /dev/sg3
[0:0:2:0] disk WD WD3001FYYG D1R5 /dev/sdd /dev/sg4
[0:0:3:0] disk SEAGATE ST3000NM0023 GE09 /dev/sde /dev/sg5
[0:0:4:0] disk WD WD3001FYYG D1R5 /dev/sdf /dev/sg6
[0:0:5:0] disk WD WD3001FYYG D1R5 /dev/sdg /dev/sg7
[0:0:6:0] disk WD WD3001FYYG D1R5 /dev/sdh /dev/sg8
[0:0:7:0] disk WD WD3001FYYG D1R2 /dev/sdi /dev/sg9
[0:0:8:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdj /dev/sg10
[0:0:9:0] disk SEAGATE ST3000NM0023 GE09 /dev/sdk /dev/sg11
[0:0:10:0] disk SEAGATE ST3000NM0023 GS0D /dev/sdl /dev/sg12
[0:0:11:0] disk SEAGATE ST3000NM0023 0006 /dev/sdm /dev/sg13
[0:0:12:0] enclosu DELL SC200 1.03 - /dev/sg14
[5:0:0:0] disk ATA OCZ-VERTEX2 1.37 /dev/sdb /dev/sg1
[7:0:0:0] enclosu AHCI SGPIO Enclosure 2.00 - /dev/sg0
[9:0:0:0] disk Dell Internal Dual SD 1.: /dev/sdn /dev/sg15

This gives me /dev/sgXX numbers which I can feed to:

command sg_ses
root@truenas[~]# sg_ses /dev/sg14
DELL SC200 1.03
Supported diagnostic pages:
Supported Diagnostic Pages [sdp] [0x0]
Configuration (SES) [cf] [0x1]
Enclosure Status/Control (SES) [ec,es] [0x2]
String In/Out (SES) [str] [0x4]
Threshold In/Out (SES) [th] [0x5]
Additional Element Status (SES-2) [aes] [0xa]
<unknown> [0x80]
<unknown> [0xa0]
<unknown> [0xf7]
<unknown> [0xf8]
root@truenas[~]#

So now what? I want to try and use this command try and blink an LED in one of the slots..... but I don't know the syntax..

 

[BigJ]

Well some small progress...
Continuing on with the sg_ses command I was able to turn on the amber LED (ident LED) lights for each drive which means sg_ses could be the tool for me.
example:
root@truenas[~]# sg_ses --index=0,0 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,1 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,2 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,3 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,4 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,5 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,6 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,7 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,8 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,9 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,10 --set=ident /dev/sg14
root@truenas[~]# sg_ses --index=0,11 --set=ident /dev/sg14

Each line represents each of the 12 slots, yay!!

Problem (1)
These are not the LEDs I'm looking for...
Problem (2) FIXED = root@truenas[~]# sg_ses --index=0,11 --clear=ident /dev/sg14
I now have 12 blinking lights that look like defcon 4 and I don't know how to turn them off, short of a reboot..
Problem (3)
How to actually turn on the LEDs that I need!

Found some great info at these sites for sg_ses commands:

1. The sg_ses utility
2. SAS Controllers and Flashy Lights

 

[BigJ]

Oh man, I did it..... that took me several days... geez let's hope it survives a reboot
So I used Minicom
e.g. minicom -D /dev/ttyS1 -s
I made sure I used Fohdeesha's settings of 38400-8-n-1 plus software flow control

then Taa Daa

Lockfile is stale. Overriding it..
Welcome to minicom 2.8

OPTIONS: I18n
Port /dev/ttyS1, 14:02:16

Press CTRL-A Z for help on special keys


12Pack.Slot0.1.03.000 >_ver
********************* Bench Build **********************
Build Owner : GitHub
Build Number : 000
Build Version : 1.03
Build Date : Fri Jul 10 09:40:58 2015
FPGA Revision : AA
Board Revision : 8
CPLD Revision : 7
**************Firmware Image Information****************
Image Region 0 (Always Boot)
Revision : 0.9.0.0
Dell Version : 1.00
Total Image Size : 0005928c [365196]
Fast Boot : Yes
Image Address : 0x14000000
RegionOffset : 0x00000000
RegionSize : 0x00080000
RegionType : 0x00000000
Active--->Image Region 1
Revision : 0.9.0.0
Dell Version : 1.03
Total Image Size : 00055a3c [350780]
Fast Boot : Yes
Image Address : 0x14080000
RegionOffset : 0x00080000
RegionSize : 0x00080000
RegionType : 0x00000001
Image Region 2
Revision : 0.9.0.0
Dell Version : 1.01
Total Image Size : 00059270 [365168]
Fast Boot : Yes
Image Address : 0x14100000
RegionOffset : 0x00100000
RegionSize : 0x00080000
RegionType : 0x00000002
********************************************************

So then I typed

12Pack.Slot0.1.03.000 >drive_led
slotled <number 0..23><state 0..7>
state:
Slot Empty - 0 Fault LED : OFF
Online LED: OFF
Online - 1 Fault LED : OFF
Online LED: ON
Identify - 2 Fault LED : OFF
Online LED: on 250msec, off 250mses
Rebuilding - 3 Fault LED : OFF
Online LED: on 400msec, off 150msec
Failed - 4 Fault LED : on 150msec, off 150msec
Online LED: OFF
Predicted Fail - 5 Fault LED : off 500msec, on 500msec, off 1000msec
Online LED: on 500msec, off 500msec, on 500msec
Rebuild Abort - 6 Fault LED : off 6000msec, on 3000msec, off 3000msec
Online LED: on 3000msec, off 9000msec
Reserved - 7 Fault LED : OFF
Online LED: OFF

So then I typed

12Pack.Slot0.1.03.000 >drive_led 0 1
org value : 00
set value : 01
new value : 01

After that you just change the first number (0) from 0 > 11 and leave the second number (1) as is.
After you issue the command the light turned on for me right away.

as a side note I was also able to change the fan speed, for me I am trying 15% but 20% seems to be more stable, and to be honest is significantly better than the default for 12 drives anyways. Please note, if you don't have any drives populated the chassis behaves different.

12Pack.Slot0.1.03.000 >set_speed 15

I have not yet figured out how to pull drive temps so that I can check if 15% is too aggressive...

man, all that so that I can have some damn BLINKY LIGHTS!

 

[BigJ]

UPDATE....
So I rebuilt my ZFS drive and wouldn't you know it.... the lights are on but they don't show drive activity....well other than the one drive.... sigh... does this mean I need to look at sdparm now? my head hurts.. so much esoteric information.

UPDATE 2

Sadly, not that it was much use but my turned on lights do not survive a reboot. Also, side note, the shutdown command works, takes a long time and was a pain in the ass to restart. I had to pull the plugs, cycling the back side power switch did nothing.

UPDATE 3

Well I discovered you can get temps from the SC200 with the command _who

12Pack.Slot0.1.03.000 >_who

Host Links UP : 2
Expansion Links UP : 0
Drive(s) : 0 1 2 3 4 5 6 7 8 9 10 11
EMM (I'm primary and active) : 0 1
Power Supplies : 1 2
BP_1[2] = 33c
BP_2[3] = 34c
SIM0[0] = 40c
SIM1[1] = 41c
EXP0[4] = 60c
EXP1[5] = 66c

UPDATE 4

Well, I give up for now, I have gone thru a ton of commands, most of which make no sense to me!!!! (offset, 32 bit word....?) I am staring at one stupid drive out of twelve that works for drive light activity!! for the life of me I can't figure out why that one slot works but the rest do not.

Would love for someone to chime in.