OK for the record:
mkdev -l hdisk# -p ssar -c disk -s ssar -t hdisk -w connectionlocation
You can get the connection location by running
lsdev -Ccpdisk -r connwhere
I'm online again. I can mark it done.
Thanks so much for everyone's patience and help.
I really don't think I'm missing anything to make these disks work except for the SMIT scripts to make it easier.
The disks are all there, online, available. There's just not mapping between
hdisk4 -> pdisk1
Or whatever it used to be. I'm pretty sure that's it. So what I need is a command...
From earlier question: Output:
pdisk0 Available 00-05-P 2GB SSA C Physical Disk Drive
pdisk1 Available 00-05-P 2GB SSA C Physical Disk Drive
pdisk2 Available 00-05-P 2GB SSA C Physical Disk Drive
pdisk3 Available 00-05-P 2GB SSA C Physical Disk Drive
pdisk4 Available 00-05-P 2GB SSA C...
I've recovered an old AIX 4.2 box. I've imported all the VG's on the internal disks.
Now I need to move onto the SSA enclosure.
I'll preface this by saying the root of all my problems over the past few weeks was that my SSA disks went offline. Thinking it wasn't hardware (because how weird...
Going by the numbers, this is what happens:
-------------------------------------------------------
Installing Base Operating System
If you used the system key to select SERVICE mode,
turn the system key to the NORMAL position any time before the
installation ends...
Well, if you've seen my other threads you know the whole saga.
Dropping all previous posts, this is my situation.
I've got a 7013 that was running AIX 4.2 when something happened to it to make it semi-disfuntctional.
Where I am now is, I have 4 blank disks. I've installed AIX 4.2 and I'm at...
Well, I was able to obtain 4 blank disks to use. So I'm working on a system restore onto new disks.
See followup message for more: Restoring my system from MKSYSB
There are volume groups defined on them, but I can't correlate any mounting to anything that's on these disks.
In my /etc/filesystems file, there's no mention of these devices at all.
I'm having trouble with my system and I want to start over on it. I have 4 physical disks in the system. It >>SEEMS<< to me that HDISKs 1-3 are all unused. But before I start moving them around and overwriting them I want to make sure what I'm seeing is correct.
I want to make sure that they...
Hmmm... I decided to make some backups of my system in it's current state. I told my management that I've lost hope of being able to fix the system without doing something that's initially destructive.
(System rebuild from tape, or re-install OS)
So I'm making a MKSYSB tape and a regular...
How do I tell if there is mirroring going on with the other hdisk's?
I found:
Error Description
InfoExplorer article "How to Mirror rootvg for Maximum Operating
System Availability" should advise the user that whenever the
boot lv hd5 is updated it is the users responsibility to...
I have tried your suggesting with recreating the BLV. I get the same results. I can destroy and recreate hd5 with no errors but I still get the same 888 on bootup.
This is really killing me. I'm beginning to wonder if this isn't a hardware problem after all. Nothing on bootup identifies a...
Here's another clue. I may have to drop this path I'm on for something else because I'm not making any progress here.
I did a shutdown and at the end of the shutdown I got the same 888 error.
No parameters. Just "shutdown".
Can you help me understand the significance of the...
I went into the command, removed the -Kernel and now the boot image is smaller when it's done. omething is being stripped.
The command ran without error.
I rebooted and got the same error.
So I'm going to try AIXSPAdmin's suggestion again (I'm assuming it's killing all boot info and boot...
Not fixed yet, but I did a cat bosboot and looked at the one actually running on my system, not one I found online. Lo and behold:
strip -Kernel $skernel > /dev/null
So, strip -Kernel is interpreted as strip -K.
Now, in what world is it ok to use strip -Kernel and in what world isn't it OK?
OK, thanks much for the suggestions. so far I still haven't had success.
I tried both suggestions and it all worked as advertised, but I still get the 888 102 700 0c8 right after the {299}.
Here is exactly what happens:
#bosboot -a -d /dev/hdisk0
strip: illegal option -- K
strip: -- Usage...
I'm certain that I have a /unix file. I've tried using the -k to specify the unix file, to make sure it wasn't missing anything.
But it's not BOSBOOT that's throwing the error. It's STRIP which is called in the BOSBOOT routine:
# Function state_func4
state_func4 () {
#
# Strip required...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.