If hd5 is in stale state, resync it...

syncvg -l hd5
don't forget to perform bosboot to both disks.
eg:
bosboot -ad /dev/hdiskN

==============

Environment
OS Level: AIX Version 4.2
Type/Model:Unspecified
Problem
The error "Invalid or no boot device specified" is received when running a mksys
b or a mkszfile.
Solution
To resolve the error, complete the following steps:
1. Verify that the link to /dev/ipldevice is correct for the bosboot command.
The device should be linked to the physical volume that has hd5 on it. Find whi
ch disk has hd5 on it by entering:
# lslv -m hd5
The output will be similar to the following:
hd5:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
001 0001 hdisk0
The output should list one disk. If there is mirroring, two or three may d
isplay.
2. Create a link for the ipldevice to the raw hdisk, that is, use the rhdisk#
instead of the hdisk#.
3. If /dev/ipldevice already exists, verify that it is pointing to the correc
t disk and that it displays the correct major and minor numbers.
* Enter the following commands:
# cd /dev
# ls -l ipldevice
The output displays similar to the following:
crw-rw---- 2 root system 10, 3 Apr 30 22:28 ipldevice
* Search for the major and minor numbers displayed. Using the precedin
g output for example, you would enter (10 is the major number, 3 is the minor nu
mber):
ls -l | grep "10, 3"
The output displays similar to the following:
brw-rw---- 1 root system 10, 3 May 22 16:00 hd5
 crw-rw---- 2 root system 10, 3 Apr 30 22:28 ipldevice
crw-rw---- 2 root system 10, 3 Apr 30 22:28 rhd5
Using the sample output from the lslv -m hd5 command in step 2, the ipldev
ice above is incorrectly linked to rhd5. It should be linked to rhdisk0.
4. Incorrect links should be removed and relinked to the correct rhdisk using
hard links. Enter the following commands:
# rm ipldevice
# ln rhdisk0 /dev/ipldevice
# ls -l ipldevice rhdisk0
crw------- 2 root system 19, 0 Apr 30 22:28 ipldevice
crw------- 2 root system 19, 0 Apr 30 22:28 rhdisk0
This is the correct method for linking the ipldevice.

===================

Bosboot Error
Reply from Lamar Saxon | posted Feb 27, 2007 | Replies (15)

0
Please Sign-in or Register to vote
Working
The problem is not with the disks. The problem is the link to
/dev/ipldevice to the boot rhdisk is no longer present...
>cd /dev
> ls -ld ipldevice
crw------- 2 root system 21, 0 Sep 15 15:07 ipldevice
> bootinfo -b
hdisk0
> ls -l rhdisk0
crw------- 2 root system 21, 0 Sep 15 15:07 rhdisk0
> istat rhdisk0
Inode 16567 on device 10/4 Character Device
Protection: rw-------
Owner: 0(root) Group: 0(system)
Link count: 2 Length 0 bytes
Major Device 21 Minor Device 0
Last updated: Wed Jan 10 00:04:50 CST 2007
Last modified: Fri Sep 15 15:07:47 CDT 2006
Last accessed: Thu Jan 25 10:33:13 CST 2007
> find /dev -inum 16567 -ls
16567 0 crw------- 2 root system 21, 0 Sep 15 15:07
/dev/rhdisk0
16567 0 crw------- 2 root system 21, 0 Sep 15 15:07
/dev/ipldevice
Just recreate the hard link:
bootinfo -b
ln /dev/rhdiskX /dev/ipldevice
Thank you Lamar and all for the help, I did create the ln for hd5
and rhd5. And did ip_varyon -i and can create the bosboot on both
hdisk0 and hdisk1.
Actually, it is supposed to be linked to /dev/rhdisk<X> not the boot
logical volume. If bootinfo -b returns hdisk0 then:
ln /dev/rhdisk0 /dev/ipldevice
Lamar

============

0503-497 installp: An error occurred during bosboot verification processing

Technote (troubleshooting)
Problem(Abstract)
0503-497 installp: error when trying to install TSM filesets on AIX
Cause
/dev/ipldevice is missing or incorrect
Diagnosing the problem
The following errors are received when using smitty to install TSM filesets :
0503-409 installp: bosboot verification starting...
0503-497 installp: An error occurred during bosboot verification processing.
Resolving the problem
/dev/ipldevice is critical to the operation of installing certain products. It s
hould be a hardlink of your boot device. The bootlist command may be used to lis
t the boot device. For example :
[mysystem:root: /dev ] bootlist -om normal
hdisk0
In above command, hdisk0 is the boot device. In this case, the special files sho
uld be identical :
[mysystem:root: /dev ] ls -l /dev/rhdisk0 /dev/ipldevice
crw------- 2 root system 20, 0 Apr 07 2004 /dev/ipldevice
crw------- 2 root system 20, 0 Apr 07 2004 /dev/rhdisk0
If /dev/ipdevice is missing or incorrect, recreate the hard link using the comma
nd below :
#ln -f /dev/rhdisk0 /dev/ipldevice

=================
how to recover from an invalid or no boot device error in AIX
Description
When running the command "bosboot -ad /dev/ipldevice" in IBM AIX, you get the fo
llowing error:
0301-150 bosboot: Invalid or no boot device specified!
A device specified with the bosboot -d command is not valid. The bosboot command
was unable to finish processing because it could not locate the required boot d
evice. The installp command calls the bosboot command with /dev/ipldevice. If th
is error does occur, it is probably because /dev/ipldevice does not exist. /dev/
ipldevice is a link to the boot disk.
To determine if the link to the boot device is missing or incorrect :
1) Verify the link exists:
# ls -l /dev/ipldevice
ls: 0653-341 The file /dev/ipldevice does not exist.
2) In this case, it does not exist. To identify the boot disk, enter "lslv -m hd
5". The boot disk name displays.
# lslv -m hd5
hd5:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0001 hdisk4 0001 hdisk1
In this example the boot disk name is hdisk4 and hdisk1.
3) Create a link between the boot device indicated and the /dev/ipldevice file.
Enter:
# ln /dev/boot_device_name /dev/ipldevice
(An example of boot_device_name is rhdisk0.)
In my case, I ran:
# ln /dev/rhdisk4 /dev/ipldevice
4) Now run the bosboot command again:
# bosboot -ad /dev/ipldevice
Example
lslv -m hd5; ln /dev/rhdisk4 /dev/ipldevice; bosboot -ad /dev/ipldevice