topic Re: Persistant dsf issue from Smart Array Controller to LSI SAS in Operating System - HP-UX

Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 14:45:06 GMT

Recently I changed our RX6600 from Windows to HP-UX. We pulled out our P600 Smart Array because it would not recognize HP-UX and put back in the old LSI SAS card. Now it looks like something is left over from Windows. Disk9 is showing 3 entries, probably left over from previious Windows O/S. Any way to fix it without changing card back? Will this possible cause issues in future? Below are the Disk9_p1 and disk9_p2 I would like to remove.

=> #ioscan -m dsf
Persistent DSF Legacy DSF(s)
========================================
/dev/rdisk/disk6 /dev/rdsk/c0t5d0
/dev/rdisk/disk6_p1 /dev/rdsk/c0t5d0s1
/dev/rdisk/disk6_p2 /dev/rdsk/c0t5d0s2
/dev/rdisk/disk6_p3 /dev/rdsk/c0t5d0s3
/dev/rdisk/disk7 /dev/rdsk/c0t1d0
/dev/rdisk/disk8 /dev/rdsk/c0t4d0
/dev/rdisk/disk9 /dev/rdsk/c0t0d0
/dev/rdisk/disk9_p1 /dev/rdsk/c0t0d0s1
/dev/rdisk/disk9_p2 /dev/rdsk/c0t0d0s2
/dev/rdisk/disk10 /dev/rdsk/c0t3d0
/dev/rdisk/disk11 /dev/rdsk/c0t2d0
/dev/rdisk/disk13 /dev/rdsk/c1t0d0

=> #sasmgr -N get_info -D /dev/sasd1 -q raid

Wed Oct 20 08:46:36 2010

---------- PHYSICAL DRIVES ----------
LUN dsf SAS Address Enclosure Bay Size(MB)

/dev/rdisk/disk10 0x5000c5000596b201 1 7 70007
/dev/rdisk/disk11 0x5000c5000596d01d 1 6 70007
/dev/rdisk/disk7 0x5000c50005965279 1 5 70007
/dev/rdisk/disk8 0x5000c50005969365 1 8 70007
/dev/rdisk/disk9 0x5000c500062d2f75 1 4 70007

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

Raid Level : RAID 1
Volume sas address : 0xce1afbb9c78f283
Device Special File : /dev/rdisk/disk6
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

0x5000c500062d3659 1 2 70007 SECONDARY ONLINE
0x5000c500062d1cbd 1 1 70007 PRIMARY ONLINE

---------- GLOBAL SPARE DRIVES ----------
SAS Address Enc Bay Size(MB) Pool State

0x5000c500062d1fad 1 3 70007 0 ACTIVE

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

Steven E. Protter — Wed, 20 Oct 2010 15:31:02 GMT

Shalom,

/dev/rdisk/disk9 /dev/rdsk/c0t0d0
/dev/rdisk/disk9_p1 /dev/rdsk/c0t0d0s1
/dev/rdisk/disk9_p2 /dev/rdsk/c0t0d0s2

That is normal. HP-UX boot drives need three partitions. One for EFI, one for the boot loader(term may not be exact) one for the OS itself.

disk6 might be leftover from windows.

You might have replaced a hardware raid card with one that is not or operates differently and need to repartition, or do a hardware mirror of the HP-UX boot disk.

SEP

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 15:45:28 GMT

Hi Steve, so I had it backwards? I thought disk6 is my HPUX system, because on this command c5t5d0 shos it to be IR,

Yes the other one is Windows O.S. from the other card. Can you double check and tell me which one is my HP-UX and if I can get the other one to only show one not 3....or 4 entries? thanks again

=> #ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 5 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DH072ABAA6
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0s1
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
disk 0 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DH072ABAA6
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 1 0/4/1/0.0.0.2.0 sdisk CLAIMED DEVICE HP DH072ABAA6
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 3 0/4/1/0.0.0.3.0 sdisk CLAIMED DEVICE HP DH072ABAA6
/dev/dsk/c0t3d0 /dev/rdsk/c0t3d0
disk 4 0/4/1/0.0.0.4.0 sdisk CLAIMED DEVICE HP DH072ABAA6
/dev/dsk/c0t4d0 /dev/rdsk/c0t4d0
disk 2 0/4/1/0.0.0.5.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c0t5d0 /dev/dsk/c0t5d0s2 /dev/rdsk/c0t5d0 /dev/rdsk/c0t5d0s2
/dev/dsk/c0t5d0s1 /dev/dsk/c0t5d0s3 /dev/rdsk/c0t5d0s1 /dev/rdsk/c0t5d0s3
disk 12 255/1/0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 16:03:47 GMT

When I went into E.F.I., I had planed to use all eight disks. But then EFI allowed me to mirror the first two and the only allowed me to use the 3rd one as a mirror. I have five 72 gig disks left over. So I was going to create a new vg01, but I see that only 4 look right. And now I do not even know for sure which is the 5th disk I need. I thought it was disk 9 I needed, but is disk9 or disk6 my O.S.? and can I use the other one just the way it is? or do I need to clean it up? If how can I clean it up?

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 16:04:30 GMT

3rd one as a hot spare not mirror

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 16:56:50 GMT

I think I found answer on page 34 of this page. I missed a step and will need to do this all over again.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02017117/c02017117.pdf

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

S. Ney — Wed, 20 Oct 2010 17:03:00 GMT

what is the output of:
vgdisplay -v vg00
lvlnboot -v
strings /etc/lvmtab

Those commands will tell you which disks are your boot disks and belong to vg00

After you find out which disks were the windows disks you can try and remove the information with:
idisk -wR /dev/rdsk/(device)
then an rmsf -a or rmsf -H

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 17:07:58 GMT

thanks yes disk6 is vg00 and disk9 is the stuff with windows.

--- Physical volumes ---
PV Name /dev/disk/disk6_p2
PV Status available
Total PE 4294
Free PE 503
Autoswitch On
Proactive Polling On

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 17:14:04 GMT

Hi S. So when I do the idisk command (never heard of it but looking at man commands) I am going to do it to

/dev/rdisk/disk9_p1
/dev/rdisk/disk9_p1

But not
/dev/rdisk/disk9. Is that correct?

thanks again

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 18:00:09 GMT

I am new to 11.31 and am confused on weather to use persistent or legacy names. Here is what I want to clean up and only show one not three

/dev/rdisk/disk9 /dev/rdsk/c0t0d0
/dev/rdisk/disk9_p1 /dev/rdsk/c0t0d0s1
/dev/rdisk/disk9_p2 /dev/rdsk/c0t0d0s2

In some threads I see they are using legacy not percistant so to get rid of all 3 do I use use the

rdisk -R /dev/rdsk/c0t0d0
or
rdisk -R /dev/rdsk/disk9

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

Steven E. Protter — Wed, 20 Oct 2010 18:18:01 GMT

Shalom,

You can use either legacy or persistent names.

Either will work.

It is a good idea however to migrate to persistent names. That is the new thing and that is what HP wants you to do. So says my crystal ball.

SEP

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

Earl_Crowder — Wed, 20 Oct 2010 18:27:13 GMT

John,

Wipe the partition table off the disk:
#idisk -wR /dev/rdisk/disk9

Remove special files:
#rmsf /dev/rdisk/disk9_p?
#rmsf /dev/disk/disk9_p?
#rmsf /dev/dsk/c0t0d0s?
#rmsf /dev/rdsk/c0t0d0s?

Earl

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 18:53:34 GMT

Thanks SEP. Great I can use either. Yes I will remember to always use persistent.

Thanks Earl.
I just remove the persistent one.
=> #idisk -wR /dev/rdisk/disk9
idisk: Write mode requires description file
idisk version: 1.44
********************** WARNING ***********************
If you continue you will destroy all partition data on this disk.
Do you wish to continue(yes/no)? yes

And will remove those 2 persistant special files and 2 legacy special files.

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 19:05:40 GMT

finished removing from /dev/rdsk and /dev/dsk.

ioscan now looks good and I can not create vg01 with these 5 disks.....

=> #ioscan -m dsf
Persistent DSF Legacy DSF(s)
========================================
/dev/rdisk/disk6 /dev/rdsk/c0t5d0
/dev/rdisk/disk6_p1 /dev/rdsk/c0t5d0s1
/dev/rdisk/disk6_p2 /dev/rdsk/c0t5d0s2
/dev/rdisk/disk6_p3 /dev/rdsk/c0t5d0s3
/dev/rdisk/disk7 /dev/rdsk/c0t1d0
/dev/rdisk/disk8 /dev/rdsk/c0t4d0
/dev/rdisk/disk9 /dev/rdsk/c0t0d0
/dev/rdisk/disk10 /dev/rdsk/c0t3d0
/dev/rdisk/disk11 /dev/rdsk/c0t2d0
/dev/rdisk/disk13 /dev/rdsk/c1t0d0

One last questions. I created a hot spare for my mirrored O/S with EFI. is that hot spare only for my mirrored O/S? If I create vg01 with these remaining 5 disks, will that hot spare replace one of these disks? I assume that it will only hot spare my mirror, but was not 100% sure. If it does not I better not put anything importance on these 5 JBOD's.

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

Earl_Crowder — Wed, 20 Oct 2010 19:24:14 GMT

I see 8 drives in the sasmgr output.

From the sasmgr output, i see that bay 1 and 2 are mirrored, and 3 is the hotspare. bay 4 thru 8 (5 disks) are available to configure however you like. The hotspare isn't visible to the OS as a disk device.

So you should see 6 disk devices (assuming no other storage attached).

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 19:38:51 GMT

Yes that sounds 100% correct, and I guess first guess is correct, and If I make a new vg01 with the remaining 5 that that hot spare will not spare, because the O.S. does not even know its there.
The O.S. does not even know about the spare or the mirror, becuause the E.F.I. created the mirror and spare.... I wonder if crating a mirror and spare was over kill....
I guess I better not put anything important on these other 5 internal drives, because if one fails we have no raid or hot spares.

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

Steven E. Protter — Wed, 20 Oct 2010 20:09:10 GMT

With this set up, going with hardware based raid and spares, saves you CPU cycles.

It is the way to go.

An OS based solution is normally not going to perform as well.

Much as I love mirror/ux

SEP

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 20:40:13 GMT

Okay thats good to know. But the last 8 years I have ran PA RISC servers with "only" two internal drives and the reset on a SAN. just wondering if there was a way to make thse other 5 disks Now I have 8 internal drives, and just hoping that I could make these 5 disks more fault tollerant.

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

Earl_Crowder — Wed, 20 Oct 2010 20:41:20 GMT

You could bind the remaining 5 drives in a raid-5 set, which will give you redundancy, and the hot-spare will be available to replace either a failed mirror from the OS or a failed drive from the raid-5 set.

It will give you capacity of 280GB (roughly) with redundancy.

Performance will be meh on writes, so don't use it for anything performance-critical (oracle database, etc).

Re: Persistant dsf issue from Smart Array Controller to LSI SAS

John Jimenez — Wed, 20 Oct 2010 20:45:15 GMT

Oh.....So that disk will fail over, if one of these drives goes down. Awesome, good to know.