Re: Moving rootvg drive failed?

From: Ulrich--nO--(dot)-sPAM--Link (_at_Epost.de)
Date: 11/13/03 

Date: Thu, 13 Nov 2003 22:20:53 +0100

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)
>>
>>Gereon Wenzel
>
>
> 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.
>
> 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.

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

The trouble with "getty" leads into another direction:
try to disable the start of xdm from inittab.
If the graphics card is in a different slot is has got the next number.

The easiest way: make the mksysb and restore it. This will build a new
and clean device database. 

---
Uli

Relevant Pages

  • Re: Transferring Linux hard drive to a new system
    ... MS> In about a couple of weeks I'll be moving my Linux server to something ... MS> and never saw another problem again on the clean install. ... SCSI disks though. ...
    (comp.os.linux.misc)
  • Re: Ebaying - Comparisons
    ... > SCSI disks. ... a DNS server which caches everything in RAM). ... dough for SCSI. ... master per channel (preferrably using "cable select" with an UDMA ATA ...
    (comp.unix.solaris)
  • Re: Moving rootvg drive failed?
    ... "Gereon Wenzel" schrieb im Newsbeitrag ... > Now the machine started from disks, but went to frequent error messages ... 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. ...
    (comp.unix.aix)
  • Installing on a IBM PC320 Server
    ... I have an old IBM PC320 Server with the following hardware (use to have ... Microsoft SBS 4.5 installed before I tried to install FreeBSD): ... Quantum Viking WSE SCSI hard drives, one is SCSI ID#0 and the ... Or is there a way to get around it in the installation ...
    (freebsd-newbies)
  • Installing on a IBM PC320 Server
    ... I have an old IBM PC320 Server with the following hardware (use to have ... Microsoft SBS 4.5 installed before I tried to install FreeBSD): ... Quantum Viking WSE SCSI hard drives, one is SCSI ID#0 and the ... Or is there a way to get around it in the installation ...
    (freebsd-questions)