Issue :File - /usr/lib/boot/unix_64 becomes 0 bytes
Probable causes for above Issue:
1>Filesystem Full.
2>Abnormal IO issues on rootvg hdisk which results in panic system halt/reboot.
3>Sometimes even while software upgradation.
Option 1> Restore the file from good mksysb backup.
Procedure:
cd /tmp
restore -xqvf /storage/mksysb.aix530.052013 ./usr/lib/boot/unix_64
mv /tmp/usr/lib/boot/unix_64 /usr/lib/boot/unix_64
ln -s /usr/lib/boot/unix_64 /unix
ln -s /usr/lib/boot/unix_64 /usr/lib/boot/unix
Run a bosboot and confirm successful creation of BLV.
Option 2> Restore the file from Media(CD/DVD) or from a NIM resource(LPP source) of same software level.
Procedure:
cd /tmp
restore -qxvf /mnt/lppsource_53-12-01/bos.mp64 ./usr/lib/boot/unix_64
mv /tmp/usr/lib/boot/unix_64 /usr/lib/boot/unix_64
ln -s /usr/lib/boot/unix_64 /unix
ln -s /usr/lib/boot/unix_64 /usr/lib/boot/unix
Run a bosboot and confirm successful creation of BLV.
Option 3> Copy the kernel file from another machine.
Procedure:
If you have another machine running the 64-bit kernel and at the same level of AIX oslevel.
Then copy the kernel file (/usr/lib/boot/unix_64) from another machine and follow remaining below steps.
ln -s /usr/lib/boot/unix_64 /unix
ln -s /usr/lib/boot/unix_64 /usr/lib/boot/unix
Run a bosboot and confirm successful creation of BLV.
In the past instances this has proved to work fine without any problems.
Note : Recommended method and Best practice is to use option 1 or 2 and during worstcase scenarios option 3 can be used.
Probable causes for above Issue:
1>Filesystem Full.
2>Abnormal IO issues on rootvg hdisk which results in panic system halt/reboot.
3>Sometimes even while software upgradation.
Option 1> Restore the file from good mksysb backup.
Procedure:
cd /tmp
restore -xqvf /storage/mksysb.aix530.052013 ./usr/lib/boot/unix_64
mv /tmp/usr/lib/boot/unix_64 /usr/lib/boot/unix_64
ln -s /usr/lib/boot/unix_64 /unix
ln -s /usr/lib/boot/unix_64 /usr/lib/boot/unix
Run a bosboot and confirm successful creation of BLV.
Option 2> Restore the file from Media(CD/DVD) or from a NIM resource(LPP source) of same software level.
Procedure:
cd /tmp
restore -qxvf /mnt/lppsource_53-12-01/bos.mp64 ./usr/lib/boot/unix_64
mv /tmp/usr/lib/boot/unix_64 /usr/lib/boot/unix_64
ln -s /usr/lib/boot/unix_64 /unix
ln -s /usr/lib/boot/unix_64 /usr/lib/boot/unix
Run a bosboot and confirm successful creation of BLV.
Option 3> Copy the kernel file from another machine.
Procedure:
If you have another machine running the 64-bit kernel and at the same level of AIX oslevel.
Then copy the kernel file (/usr/lib/boot/unix_64) from another machine and follow remaining below steps.
ln -s /usr/lib/boot/unix_64 /unix
ln -s /usr/lib/boot/unix_64 /usr/lib/boot/unix
Run a bosboot and confirm successful creation of BLV.
In the past instances this has proved to work fine without any problems.
Note : Recommended method and Best practice is to use option 1 or 2 and during worstcase scenarios option 3 can be used.
Hi I am trying to run a 32 bit binary on 64 bit multiprocessor kernel i.e. AIX 7.2 bit it fails with error cannot execute binary file: Exec format error, i checked bootinfo my KERNEL is 64 bit and i do not /usr/lib/boot/unix_mp folder on my filesystem therefore i m not able to change Kernel.
ReplyDelete