Sponsored Content
Operating Systems AIX NIM Restore hangs at the start Post 302785257 by MichaelFelt on Monday 25th of March 2013 06:58:03 AM
Old 03-25-2013
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.
This User Gave Thanks to MichaelFelt For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

NIM install hangs on LED 0608

Hi guys, I am trying to install a new machine via nim but it is hanging on 0608 => it should be a network issue here the situation hoping you will be able to help: server NIM on a subnet/IP 10.36.12.64 client on 161.43.56.25 the ping test is successful but when I launch the isntall it... (9 Replies)
Discussion started by: touny
9 Replies

2. AIX

How to backup and restore Linux uisng NIM.

Hi Friends, I've a hard question to ask. I have a NIM server running on AIX 5.3. Now my requirement is that , " From This NIM Server i would like to take the Image of Linux servers ". I mean that using NIM server i should be able to backup / restore the linux Servers. In Simple terms... (3 Replies)
Discussion started by: rdkumarj
3 Replies

3. AIX

NIM client mksysb restore

Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies

4. Solaris

start /SP/console hangs in X4500

when I type start /SP/console... the console shows up but i cannot type anything over there. I do not understand what might be the reason for that. -> start /SP/console Are you sure you want to start /SP/console (y/n)? y Serial console started. To stop, type ESC ( I pressed enter many... (8 Replies)
Discussion started by: bharu_sri
8 Replies

5. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

6. AIX

Single file restore from NIM backup

Hi, I've recently implemented a NIM backup procedure for 2 virtual AIX5.3 environments running on a JS22 blade server. The images transfer to an old p620 box connected to some old SSA storage, each server backs up a mksysb and a savevg image. Now seeing as this method should be replacing our... (3 Replies)
Discussion started by: thinboyslim
3 Replies

7. AIX

VIO restore from NIM dosen't work

Hello guys I have been trying to restore a VIO server from NIM using the nim_resource.tar file created from the same VIO lpar. The restoration goes fine and after 99% I get the following error 0516-304 putlvodm: Unable to find device id 000b5f62263b70a50000000000000000 in the Device... (1 Reply)
Discussion started by: balaji_prk
1 Replies

8. AIX

NIM client installation hangs at 0608

Hi All, I am facing very strange problem. I have created NIM server with 6.1 TL4SP3. I am having SPOT and MKsysb of the same version. I am able to install the client using this spot and mksysb. Now I got the requirement of installing the 5.3 ML11SP3 client. So using the mksysb of 5.3 ML11SP3, I... (3 Replies)
Discussion started by: falgun6666
3 Replies

9. AIX

Disabling cron after NIM restore

Hi Guys, We normally have a backup and restore nightly on our Prod machines. We do this via customized script and all unattended. The dilemma that I'm having is the disabling of the cron after the restore. I created a nim script to disable the cron after the restore has been completed. But... (6 Replies)
Discussion started by: kaelu26
6 Replies

10. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Discussion started by: omonoiatis9
0 Replies
SYSTEMD-MACHINE-ID-SETUP(1)				     systemd-machine-id-setup				       SYSTEMD-MACHINE-ID-SETUP(1)

NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id SYNOPSIS
systemd-machine-id-setup DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with a provisioned or randomly generated ID. See machine-id(5) for more information about this file. If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty. The new machine ID will be acquired in the following fashion: 1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID in /etc/machine-id. 2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID. The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM. 3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the machine ID. For details, see the documentation of the Container Interface[1]. 4. Otherwise, a new ID is randomly generated. The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below. Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images. OPTIONS
The following options are understood: --root=root Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for /etc/machine-id itself. --commit Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point. This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure that this file is always valid and accessible for other processes. This command is primarily used by the systemd-machine-id-commit.service(8) early boot service. --print Print the machine ID generated or committed after the operation is complete. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1) NOTES
1. Container Interface https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)
All times are GMT -4. The time now is 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy