old rootvg

[adash]

Hi,
I had a regatta with 8 LPARS, I now have a regatta with 4 LPARS and a bunch of HDDs from the already deleted LPARs.
If I assign the SCSI controller to another LPAR, it works, but I get 10 HDDs instead of three:

hdisk4 Defined 2s-08-00-8,0 Other SCSI Disk Drive
hdisk5 Defined 2s-08-00-8,1 Other SCSI Disk Drive
hdisk6 Defined 2s-08-00-8,2 Other SCSI Disk Drive
hdisk7 Defined 2s-08-00-8,3 Other SCSI Disk Drive
hdisk8 Defined 2s-08-00-8,4 Other SCSI Disk Drive
hdisk9 Defined 2s-08-00-8,5 Other SCSI Disk Drive
hdisk10 Defined 2s-08-00-8,6 Other SCSI Disk Drive
hdisk11 Defined 2s-08-00-8,7 Other SCSI Disk Drive
hdisk12 Defined 2s-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk13 Defined 2s-08-00-10,0 16 Bit LVD SCSI Disk Drive

I try to importvg in SMIT, but I got no success; should I create an LPAR and boot it from CD only in order to erase these old HDDs?
Thanks in advance.
Dimitar

 

[ogniemi]

they are defined not available in the system at the moment.

you can safely remove them using rmdev command...

eg.

for i in `lsdev -Cc disk|grep Defined|awk '{print $1}'`;do rmdev -dl $i;done

 

[adash]

Thanks, ogniemi,
They are now Defined for I removed the controller from this particular LPAR (not DLAPR) and rebooted. If I remove these and attach the controller again, I will get the same; I was asking for a convenient way to fully erase contents and destroy what seems to be the remains of an old rootvg. I just want to use the storage space.

 

[MoreFeo]

Why are you using importvg? Of you have your hdisks Available and want to use them you should make a new VG (mkvg) or add them to an already created VG (extendvg), but not import them.

When you make a new VG it may tell you that these hdisks used to belong to another VG, but you can force the creation (and the same whan adding them to an old VG).

 

[ogniemi]

export the VG which was residing on the Defined disks from the system (if the VG still configured - on "lsvg" output)

it will not import automatically after next reboot.

you can also clear PVIDs from unused disks (chdev -l hdiskN -a pv=clear)

new PVID will be given during a VG creation or when you run 'chdev -l hdiskN -a pv=yes'

 

[khalidaaa]

ogniemi,

adash won't be able to clear the disk if it is in a "Defined" state!?!

Regards,
Khalid

 

[adash]

Thanks, guys,
I will attach the controller now and see if any of these work.
Dimitar

 

[adash]

I got it added to another LPAR:



hdisk0 Available 47-08-02 1814 DS4700 Disk Array Device
hdisk1 Available 47-08-02 1814 DS4700 Disk Array Device
hdisk2 Available 2s-08-00-8,0 Other SCSI Disk Drive
hdisk3 Available 2s-08-00-8,1 Other SCSI Disk Drive
hdisk4 Available 2s-08-00-8,2 Other SCSI Disk Drive
hdisk5 Available 2s-08-00-8,3 Other SCSI Disk Drive
hdisk6 Available 5M-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk7 Available 5M-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk8 Available 5M-08-00-10,0 16 Bit LVD SCSI Disk Drive
hdisk9 Available 2s-08-00-8,4 Other SCSI Disk Drive
hdisk10 Available 2s-08-00-8,5 Other SCSI Disk Drive
hdisk11 Available 2s-08-00-8,6 Other SCSI Disk Drive
hdisk12 Available 2s-08-00-8,7 Other SCSI Disk Drive
hdisk13 Available 2s-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk14 Available 2s-08-00-10,0 16 Bit LVD SCSI Disk Drive


Here is what SMIT returns when I try adding an original VG over hdisk2:
0516-1182 /usr/sbin/mkvg Open Failure on hdisk2.
0516-862 /usr/sbin/mkvg: Unable to create volume group.

and here is ogniemi's proposal:

free: <root> />>chdev -l hdisk2 -a pv=clear
Method error (/etc/methods/chgdisk):
0514-047 Cannot access a device.
pv

free: <root> />>

Any suggestions?

 

[khalidaaa]

What's the output of lspv?

 

[adash]

hdisk6 0036872af893fe25 rootvg active
hdisk7 none None
hdisk8 none None
hdisk0 none None
hdisk1 none None
hdisk2 0036872aa6aa79ff None
hdisk3 none None
hdisk4 none None
hdisk5 none None
hdisk9 none None
hdisk10 none None
hdisk11 none None
hdisk12 none None
hdisk13 0036872a986f8701 test active
hdisk14 none None

As you can see, I was able to create a test vg over one of the disks;
I am now running Diagnostics->Format from WebSM and I guess this is why I have ID on Hdisk 2.

 

[adash]

The whole situation seems quite buggy to me.
See output form WebSM Vital Product Data on Hdisk2 and 3:

hdisk2 U1.9-P1/Z1-A8 Other SCSI Disk Drive

Manufacturer................IBM
Machine Type and Model......ST373454LC
Part Number.................03N6345
ROS Level and ID............43373141
Serial Number...............001775D2
EC Level....................H13979
FRU Number..................26K5531
Device Specific.(Z0)........000004129F00013E
Device Specific.(Z1)........0209C71A
Device Specific.(Z2)........0002
Device Specific.(Z3)........07101
Device Specific.(Z4)........0001
Device Specific.(Z5)........22
Device Specific.(Z6)........H13979


PLATFORM SPECIFIC

Name: sd
Node: sd
Device Type: block

hdisk3 U1.9-P1/Z1-A8.1 Other SCSI Disk Drive

Manufacturer................IBM
Machine Type and Model......ST373454LC
Part Number.................03N6345
ROS Level and ID............43373141
Serial Number...............001775D2
EC Level....................H13979
FRU Number..................26K5531
Device Specific.(Z0)........000004129F00013E
Device Specific.(Z1)........0209C71A
Device Specific.(Z2)........0002
Device Specific.(Z3)........07101
Device Specific.(Z4)........0001
Device Specific.(Z5)........22
Device Specific.(Z6)........H13979


PLATFORM SPECIFIC

Name: sd
Node: sd
Device Type: block

Notice anything similar?
Dimitar

 

[DukeSSD]

All the disks at location 2s-08-00-8,x Other SCSI Disk Drive
are the same disk.

You either need to sort out the zoning and / or you need to install the correct multipath driver for the storage.

 

[adash]

Thanks, DukeSSD, but these are on the local drawers.
As I already said, these used to be directly attached to old LPARs,
with rootvg on a single disk.
Please note that the disks that were not a part of the old rootvg now behave normally.
I guess there is a pretty simple solution, but maybe due to lack of experience I am now stuck with a bunch of disks I can not use.

 

[khalidaaa]

Never used that but have a look at this interesting link:

http://publib.boulder.ibm.com/infoc...x.security/doc/security/hard_disk_erasure.htm

It allows you to format an hdisk!

Regards,
Khalid

 

[ogniemi]

try to upgrade firmware of your scsi adapter and hard drives.

http://www14.software.ibm.com/webapp/set2/firmware/gjsn?mode=9&type=dasd

http://www14.software.ibm.com/webapp/set2/firmware/gjsn?mode=9&type=adapter

 

[p5wizard]

If they're all 3 physically the same type of disks and the one in slot 8 is showing up as 8 different aliases "Other SCSI Disk Drive at addresses 8,0 to 8,7", I'd suspect that one of being broken... If so you won't be able to do anything with that one anymore.

Or maybe the backplane slot number 8 is faulty, can you put it in another slot?


HTH,

p5wizard