We recently went through the same thing and had problems. It turned out
to be a problem with FastWrite Cache on older SSA adapters. When we
imported the VG's on the new system we could not see the Raid Arrays. We
had to recable them to the old adapters and turn off Cache. Then vary off
and export the VG's. Then we could move them to the new system, and newer
SSA adapters, and import the VGs. IBM is still looking into our problem.
A word of warning, we also had problems with the lastest SSA adapter
microcode when we moved to the new system and had to downlevel the
microcode on the SSA adapters.
Registered Linux User #169330 ( http://counter.li.org )
Pure Linux (SUSE) User
GnuPGP key available on request
AF36 E256 D9DA 8CB2 64DD 199B 9373 F605 1314 083B
> This is the standard procedure for moving volume groups from one
> system to another, however it does not address the problem reported by
> the original poster.
> > We do this with some regularity.... here's how...
> > 1) Unmount /data file systems. If the system refuses to unmount a file
> > system, use the lsof utility to determine which process has a file
> > handle on that file system and stop that process. If there doesn't
> > appear to be any, edit the /etc/filesystems file and change the mount
> > = true to mount = false for all moving file systems and reboot.
> > 2) De-activate the data volume groups. In smit, select System Storage
> > Management:Logical Volume Manager:Volume Groups:Deactivate a Volume
> > Group (fastpath "varyoffvg") and specify the volume group(s) to be
> > de-activated.
> > 3) Export the data volume groups. In smit, select System Storage
> > Management:Logical Volume Manager:Volume Groups:Export a Volume Group
> > (fastpath "exportvg") and specify the volume group(s) to be exported.
> > 4) Remove the defined hdisks. In smity, select Devices:Fixed
> > Disk:Remove a Disk (fastpath "disk") and select any disk listed as
> > defined. Repeat until all disks are removed.
> > 5) Move the SSA cables to the target system. If the target system has
> > SSA devices attached, verify that there are no conflicting mount
> > points, volume groups, logical volume names, or hdisk IDs. If there
> > are, follow the above procedures on the target system to remove the
> > file systems and volume groups.
> > 6) Remove the SSA enclosures. Run rmdev -l enclosure# -d for each
> > removed enclosure. The command lsdev -C | grep enc will list the
> > enclosures.
> > 7) Scan for new devices. In smit, select Devices:Install/Configure
> > Devices Added After IPL (fastpath "cfgmgr"), or (re)boot the server.
> > 8) Import the volume groups. In smit, select System Storage
> > Management:Logical Volume Manager:Volume Groups:Import a Volume Group
> > and (fastpath "importvg") specify a physical volume of the volume
> > group to be imported and the volume group name.
> > 9) Mount the file systems.
> > HTH -
> > KB
> > > Assuming that he did not set any pdisks to system disks, what would be the
> > > next set of steps to retrieve the array definition and bring it online
> > > import it )?
> > > Thanks,
> > > -Kevin
> > > > > Hello
> > > > > I am trying to move an SSA RAID-5 array from one machine to another.
> > > > > Unfortunately, now that the discs are connected to the new server, we
> > > > > are unable to access the RAID-5 array.
> > > > > After running cfgmgr, the system found the SSA pdisk devices, but did
> > > > > not add an 'hdisk' for the RAID-5 array, although clearly it knows
> > > > > that the RAID-5 array exists:
> > > > > % ssaraid -I -z -l ssa0
> > > > > pdisk0 0060947EBFC200D member n/a 18.2GB Physical disk
> > > > > pdisk1 0060947EEA5400D member n/a 18.2GB Physical disk
> > > > > pdisk2 0060947EEA6400D member n/a 18.2GB Physical disk
> > > > > pdisk3 0060947EEB5400D member n/a 18.2GB Physical disk
> > > > > pdisk4 0060947EEBDB00D member n/a 18.2GB Physical disk
> > > > > pdisk5 0060947EEE8C00D member n/a 18.2GB Physical disk
> > > > > pdisk6 0060947EF22200D spare n/a 18.2GB Physical disk
> > > > > 99BA3C5EBFD24CK 99BA3C5EBFD24CK unknown 0 RAID-5 array
> > > > > When you try and change the use of the RAID-5 array to 'system disk'
> > > > > (which I want to do in order to get an hdisk device created), we get
> > > > > the following error:
> > > > > % ssaraid -H -l ssa0 -n '99BA3C5EBFD24CK' -a use=system -d
> > > > > ssachg: Object 99BA3C5EBFD24CK is not known
> > > > > ssaraid: Change method failed for 99BA3C5EBFD24CK
> > > > > Does anybody have any suggestions for how I can 'import' this RAID-5
> > > > > array, and keep the data it contains, into the new system? Is there
> > > > > something I could create in the ODM? It almost seems like a vicious
> > > > > circle - the status of the RAID-5 array is unknown because there isn't
> > > > > an hdisk, but I can't create an hdisk because the array is unknown...
> > > > > Chicken? Egg? Anyone?!
> > > > > Thanks
> > > > > Chris Eason
> > > > Chris, unfortunately you may have gone too far already, but if you want to
> > > > use the raid5 array you did *not* want to change any pdisk to a system
> > > > disk. That would destroy the array. I suggest either calling support or
> > > > (if you feel lucky) trying to find something in the ODM with the raid5
> > > > array id ("odmget CuAt | pg" and search for 99BA3C5EBFD24CK), then
> > > > deleteing it, then deleting all your pdisks and starting again once you
> > > > have made sure that the system you are working on has all the same ssa
> > > > software as the original one.