Re: Moving rootvg drive failed?

From: Gereon Wenzel (wenzel_at_ibh.rwth-aachen.de)
Date: 11/18/03


Date: Tue, 18 Nov 2003 11:45:00 +0100


"Ulrich--nO--(dot)-sPAM--Link" schrieb:
>
> Andreas Schulze wrote:
> > "Gereon Wenzel" <wenzel@ibh.rwth-aachen.de> schrieb im Newsbeitrag
> > news:3FB35901.E4E2E6F4@ibh.rwth-aachen.de...
> >
> >>I know this is about pretty old machines,
> >>but I want to learn whats going on:
> >>Just moved a set of 400MB drives from a 7012-320H to a 340.
> >>Lacking the SCSI Riser the 340 has a MCA scsi installed too.
> >>Booting the disks failed, so i booted from tape,
> >>an ran diag -a in maintenance mode,
> >>reset boot device to hdisk0 and rebootet.
> >>Now the machine started from disks, but went to frequent error messages
> >>about "ioctr error", looks like the getty process is "respawning too
> >>fast"?
> >>What does this mean?
> >>Is there any way to fix this without installing the mksysb?
> >>BTW OS-level is 3.2.5 (due to an Irisvision graphics board)
> >>
> > Hallo Gereon,
> >
> > IMHO it is not a good idea, to recycle an AIX installation in a different
> > type of server with different devices by simply exchanging the disks. It
> > might have been even worse that you ran a diag -a on the new server as it
> > can 'clean up' your installation with some rmdev commands without
> > unconfiguring the devices in question before deleting them. That diag -a
> > might also have made it impossible for you to return the disks to the
> > original system without any quirks already.

No need to swap back the disks, source machine went to someone else
allready.
Just tried the simple swap 'cause its much faster than the mksysb
procedure.
BTW: Mksysb was taken from the same system (320H),
so there are the same drivers availiable.
Just they might not being linked to the kernel yet?

> > To clone 3.2.5 from a 320H to a 340H (read: any different server type)I
> > would really recommend to use the mksysb. It will be much easier. To make
> > cloning work you just need to supply (during the restore) drivers needed by
> > the new server but not present on the original server (therefore not being
> > included in the mksysb). Search the IBM website, cloning is documented
> > pretty well.
> >
> I had no problems moving the whole scsi-riser with the 2 hd's between a
> 7012-370 and a 7012-340. Both have the same on board-scsi, ethernet and
> keyboard,mouse and serial connectors.

So did I before, thats why i was looking forward to the procedure.
mksysb seems to work with 3.2.5 only because it installs all drivers to
any system.
It looks like 4.3.3 just installes drivers needed for devices found
during install?
I'm going to prove this later, as i installed 4.3.3 from CD only yet,
while my only 3.2.5 install media is an old mksysb.

> The 320H has no onboard ethernet and no onboard scsi, so the scsi in
> slot 1 will be scsi1 and not scsi0.

Indeed, but I'm lacking the SCSI riser, so I can't even use
the external port due to termination errors.
Looks there are some other changes on the planar as well?
 
> The trouble with "getty" leads into another direction:
> try to disable the start of xdm from inittab.

No xdm started, console login only?

> If the graphics card is in a different slot is has got the next number.

Same slot(s) next to the CPU on both machines.
 
> The easiest way: make the mksysb and restore it. This will build a new
> and clean device database.

Did this before posting allready,
but being curious on the reason...

Gereon



Relevant Pages

  • Re: differences between IBM Fibre Channel adapters
    ... mksysb was created. ... (Did the original system have the drivers ... I would expect that you will need to install the SAN ... rootvg is on internal drives. ...
    (comp.unix.aix)
  • Re: NIM install with image.data - Follow up
    ... a mksysb image but attempting to create a generic RTE install. ... be able to bring your machine up with the NIM spot and see EVERYTHING ... I restored the entire image.data from the mksysb ...
    (AIX-L)
  • Re: Aix 5.3 boot
    ... But almost useless for production if we ... > cannot rely on mksysb restoring images and NIM working reliably. ... I'm having NIM and mksysb working fine on 5.3. ... install media should be planned in till the next release of install ...
    (comp.unix.aix)
  • Re: differences between IBM Fibre Channel adapters
    ... mksysb was created. ... (Did the original system have the drivers ... installed on it to permit the creation of a "generic" mksysb.) ... I would expect that you will need to install the SAN ...
    (comp.unix.aix)
  • Re: importvg/exportvg vs. savevg/(restorevg??)
    ... Complete new install ... ... so with the new machine its a 5.3 -> 5.3 migration. ... do i just install/configure aix on the ... new machine while i'm performing a mksysb on the old machine, ...
    (comp.unix.aix)