AW: F30, MKSYSB and not enough space for OS
- From: Christian Sippel <Christian.Sippel@xxxxxxxxx>
- Date: Wed, 13 Sep 2006 18:03:25 +0200
just an idea: was the rootvg mirrored on 2 disks with LVM when you created the mksysb-tape? If it was, maybe you have to selected 2 target disks to restore the mksysb - but I'm really not sure about it.
regards,
Christian
-----Ursprüngliche Nachricht-----
Von: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] Im Auftrag von Robert Miller
Gesendet: Mittwoch, 13. September 2006 17:30
An: aix-l@xxxxxxxxxxxxx
Betreff: Re: F30, MKSYSB and not enough space for OS
If you're not at the latest firmware level, you may want to update the microcode level on the box. I've had a problem somewhat similar in the past with a B80 where I couldn't restore a mksysb; the problem was something to do with the address ranges it was trying to load the OS into (it's been awhile, I don't remember specifics), and updating the microcode fixed the problem.
--rm
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of Karl Jones
Sent: Wednesday, September 13, 2006 7:50 AM
To: aix-l@xxxxxxxxxxxxx
Subject: F30, MKSYSB and not enough space for OS
After one of three disks on our F30 (formerly) running AIX 4.3 failed to
spin up, an IBM hardware tech replaced it (hdisk0) with a working drive of
identical capacity. However while trying to restore from a MKSYSB tape, the
message "not enough disk space selected to contain the operating system"
comes up.
Though not too happy about it, the hardware tech said that we now had a
working drive.. software configuration was up to us. He also mentioned that
he had heard from other techs that there was something out on the IBM
support site about this situation. I searched some but got nowhere.
Any ideas?
- Prev by Date: Re: F30, MKSYSB and not enough space for OS
- Next by Date: Mksysb Script
- Previous by thread: lsof 64 bit
- Next by thread: Mksysb Script
- Index(es):
Relevant Pages
- Re: restoring from one B50 to another (MKSYSB) problem
... install CD and insert it after the Storix install starts, ... RSPC machines
to CHRP with entirely different drivers and disk configs ... > disks, and the SCSI adapter.
... > Should I make another MKSYSB with different options or should I be ...
(comp.unix.aix) - Re: rootvg not on hdisk0 but on hdisk4
... > Hallo Piotr, ... > disks where still present that were removed
later. ... When you restore a mksysb, the ODM is rebuild, using the "new" hardware ...
> disk of the rootvg, remove that disk from rootvg, extend rootvg by the ... (comp.unix.aix) - Re: mksysb not restoring ends with led 554
... copies of the mksysb of same machine as well as the mksysb of similar ... >
It may be a hardware problem leaving one of your hard disks in rootvg ... (comp.unix.aix) - Re: Replacing internal disks on an H80
... Do a mksysb restore (either boot from tape, ... then take the
newly-cloned 9GB disks and physically ... (comp.unix.aix) - F30, MKSYSB and not enough space for OS
... After one of three disks on our F30 running AIX 4.3 failed to spin up, an IBM hardware
tech replaced it (hdisk0) with a working drive of identical capacity. ... (AIX-L)
