rx2660 IR volume status

[kirkkak]

Hi!
by sasmgr is RAID OK
Device Special File : /dev/rdsk/c0t0d0
Raid State : OPTIMAL
Raid Status Flag : ENABLED

by sfmconfig is RAID NOK
SCSI Disk 0/1/1/0.0.0.0.0 DEGRADED

What could be reason for that kind of behavior?
TIA

[Steven E. Protter]

Shalom,

One of the disks in a raid set has been pulled or failed.

Looks like hardware raid in this case.

Look for bad disks.

SEP

[Olivier Masse]

I think have the exact same problem here, if you're running 11.31.

I opened a call last month and it's been escalated to the lab. I can only suggest that you do the same so that it gets more noticed.

As for the details, it's a bug in the way SFM handles agile DSFs of IR volumes with 11.31. By looking through /var/sam/log/samlog I noticed that SFM is referring to a non-existent dsf (/dev/disk/disk5s2 while it should be /dev/disk/disk5_p2).

As a workaround it could be possible to use mksf and create a disk5s2 but I didn't try it.

Thanks

[kirkkak]

Shouldnt it be seen as status change through sasmgr? Full output:
sasmgr get_info -D /dev/sasd0 -q raid
---------- LOGICAL DRIVE 1 ----------

Raid Level : RAID 1
Volume sas address : 0xd05ba239c0c433b
Device Special File : /dev/rdsk/c0t0d0
Raid State : OPTIMAL
Raid Status Flag : ENABLED
Raid Size : 69618
Rebuild Rate : 0.00 %
Rebuild Progress : 100.00 %

Participating Physical Drive(s) :

SAS Address Enc Bay Size(MB) Type State

0x500000e013bdf992 1 8 70007 SECONDARY ONLINE
0x500000e013bd5362 1 7 70007 PRIMARY ONLINE


Nothing suspicios can be seen from drvcfg RAID menu (fw is not latest)

[Olivier Masse · Accepted solution]

If it's the bug I'm having here, then sasmgr is right but SFM is wrong. You have to be on 11.31, if you're on 11.23 please disregard my posts.

Look up in /var/sam/log/samlog what device files it's referring to, then check if they actually exist.

If you see error messages like this:
stderr = pvdisplay: /dev/disk/disk5s2: No such file or directory

Then chances are it's the same bug that I have and I suggest you open a tech support call to have it documented. You can refer my ticket number which is #3603775057 (don't do this if it's not the same problem!!).

Thanks

[Steven E. Protter]

Shalom again,

Do take the time to check the hardware, but it seems you have.

There are known bugs in 11.31 that can cause this behavior.

The unresolved question is whether or not the most recent bi-annual patch set fixes it or not.

SMH has not impressed me. sam was better.

SEP

[Olivier Masse]

Steven, I share your concerns. :)

[kirkkak]

Correct it's 11v3 Sept08 release with latest SFM/SMH versions, but samlog is clean. I'll make a case to HP. Thanks for your input

[Sebastian.Koehler]

Same issue here on two BL860c running September 2008 release of 11.31.

# sasmgr get_info -D /dev/sasd0 -q raid

Fri Feb 6 09:35:17 2009

---------- LOGICAL DRIVE 1 ----------

Raid Level : RAID 1
Volume sas address : 0x7790bfbd66f24c1
Device Special File : /dev/rdsk/c0t0d0
Raid State : OPTIMAL
Raid Status Flag : ENABLED
Raid Size : 139236
Rebuild Rate : 0.00 %
Rebuild Progress : 100.00 %

Participating Physical Drive(s) :

SAS Address Enc Bay Size(MB) Type State

0x5000c5000ee0a9fd 1 2 140014 SECONDARY ONLINE
0x5000c5000ee87449 1 1 140014 PRIMARY ONLINE