Hello Gurus,
I have a couple of questions, I'm trying to do a mksysb restore from backup and it has just hung at the start.
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------
LOAD: Waiting 60 seconds for Spanning Tree
BOOTP R = 1 BOOTP S = 1
FILE: /tftpboot/bsrs6d
Load Addr=0x4000 Max Size=0xbfc000
FINAL Packet Count = 16105 Final File Size = 8245686 bytes.
-------------------------------------------------------------------------------
Welcome to AIX.
boot image timestamp: 11:10 11/28
The current time and date: 15:40:43 03/21/2013
number of processors: 1 size of memory: 1024Mb
boot device: /pci@80000000/ethernet@c:10.11.2.9,,10.11.2.88,10.11.0.1,00,00
closing stdin and stdout...
-------------------------------------------------------------------------------
Anyone know why this is happening and how I can break out of it without someone going to power off the machine from the front panel. I'm logged on through the console cable and not the HMC unfortunately.
I'd guess you have a LED code on the front telling you what is going on.. - anyone local you can ask to check?
Or you have a console or console cable problem.. - that is about where the serial handshake changes so you need a console / cable that can handle both hardware and software handshake.
So it is probably sitting there hung, or waiting for input but you cannot see the progress or what it wants an input for.
HTH
OK, got past that part but now the 2 new hdisks put into the box are not showing up on SMS. In fact the whole hdisk line is missing. Could I have a firmware issue with the new disks put into such and old machine?
1) the slow start may have to do with the IP addresses used:
boot device: /pci@80000000/ethernet@c:10.11.2.9,,10.11.2.88,10.11.0.1,00,00
Unless your netmask is 255.0.0.0, or 255.255.0.0 the system may be trying to communicate via the router at 10.11.0.1 (which is not the same network as 10.11.2.* if netmask is 255.255.255.0 (255.255.252 would work i think).
That the disks are not showing up - and you have an HMC. Can you verify that HMC has assigned the values (although, since you say serial port it should be a standalone, i.e., knows no HMC, system.
It is possible that the spot you are using (made from the mksysb image perhaps) does not have support for the adapter built in. If you are able to remake the mksysb image after installing all drivers that could solve an issue like this.
If the mksysb image was based on physical adapters and the drives are showing up now as vscsi (because VIOS is already installed) - it may be another variation of missing drivers.
So, please tell me/us more about the origins of the mksysb image. This may help.
As you have local access, can you try an installation from a DVD? That will tell more about what is not happening.
New disks won't show up in the SMS menu as they aren't bootable devices. once the misuse restore gets to the point where you choose the target disk you will be able to verify that the disks work.
Really without the LED code we are flying blind.
It looks from the screen shot that the tftpboot has completed so I'm going to guess that the LED code is 806, and that means that there is a network configuration issue. Can you provide us with the output of
lsnim -l server
To see if we can sport what has happened. once the tftpboot is complete the network settings from the Nim server are applied and if they are incorrect the process will fail at that point.
OK I did d a mksysb install alright-ish. Came up with the following error but I managed to copy a unix_up file from somewhere else into /usr/lib/boot/unix_up.
0301-153 bosboot: /unix not found.
BOS Install: Could not create boot image.
ID# OPTION
1 Continue
2 Perform System Maintenance and Then Continue
Enter ID number: 2
So it came to the reboot and failed with no operating system. I again went into the sms menu and it shows no hard disks. I'm pretty sure the nim install worked OK this time.
RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000RS/6000 RS/6000RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000
RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000
1 = SMS Menu 5 = Default Boot List
8 = Open Firmware Prompt 6 = Stored Boot List
memory keyboard network scsi speaker
.-----------------.
| PLEASE WAIT.... |
`-----------------'
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------
Multiboot
1 Select Software
2 Software Default
3 Select Install Device
4 Select Boot Devices
5 OK Prompt
6 Multiboot Startup <ON>
.------.
|X=Exit|
`------'
==>1
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------
Select Software
.---------------------------------.
| No Operating Systems Installed |
`---------------------------------'
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------
Multiboot
1 Select Software
2 Software Default
3 Select Install Device
4 Select Boot Devices
5 OK Prompt
6 Multiboot Startup <ON>
.------.
|X=Exit|
`------'
===>4
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------
Select Boot Devices
1 Display Current Settings
2 Restore Default Settings
3 Configure 1st Boot Device
4 Configure 2nd Boot Device
5 Configure 3rd Boot Device
6 Configure 4th Boot Device
7 Configure 5th Boot Device
.------.
|X=Exit|
`------'
===>3
Configure 1st Boot Device
Device Current Device
Number Position Name
1 - Diskette
2 - SCSI CD-ROM id=@3,0 ( Integrated )
3 - IBM 100/10 Ethernet Adapter ( Integrated )
4 None
.------.
|X=Exit|
`------'
===>
That may not be the correct solution.
/unix is normally a symbolic link to the file you copied. If you are going to copy from somewhere it would be better to try and copy the one it booted from. It should still be available via /SPOT (you can run the mount command to see where where everything is coming from. You want to focus on /SPOT and whereever /dev/hd4 is coming from.
Once you have this, run the command bosboot -ad hdiskX to create your boot image on disk. That should get you going. (You can also try without copying from /SPOT, but it is better to continue with a kernel you booted from. There are small, but crucial, differences - unless you know that the one you copied is the one you expect it to be.
Hope this helps.
1 Like
Nice one that worked..... Now to find out why the unix_up file didn't copy over in the first place!
Glad it worked for you!
re: how - If you still have the system - see if the file is still there. Could have been removed by accident. Does not happen often, and I forget "how they did it", but this is actually something that "went wrong" every now and then during AIX administration classes.
This is why/how I knew "what to do", rather suggest, when I saw your earlier post.
In short, cannot put on backup if the file is unlinked.
If I recall, it was something about people not wanting /unix to be a symbolic link (not what they were used to) and they "fixed it" - to their demise.
Some history: the origin of the symbolic link goes back to the days when you could boot as mp or up kernel (multi-processor or uni-processor). The up kernel was slightly faster on a uni-processor system but did not work on a multi-processor system. The mp kernel worked on both (so the boot program on installation media was always mp based). In short, on a uni-processor system you could swap between up or mp kernel by changing the link and creating the bosboot again.
Later this was also used to support switching between 32 and 64 bit kernels.
Now there is only the unix_64 kernel. (AIX 6.X and later)
1 Like