Login or Register to Ask a Question and Join Our Community


AIX

Problem with bosboot

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX Problem with bosboot
# 1  
Old 11-11-2014
Problem with bosboot
This is my problem: I couldn't create boot image for hdisk7
Code:
test02:/]lspv
hdisk2          00c8ac36cfdf99b4                    old_rootvg      
hdisk5          00c8abd6d05f83ca                    newvg           active
hdisk6          00c8abd6d4ad141f                    rootvg          active
hdisk7          00c8abd6d4ad14b6                    altinst_rootvg  active  
test02:/]bosboot -ad hdisk7     

0301-168 bosboot: The current boot logical volume, /dev/hd5,
        does not exist on /dev/hdisk7.

More infomations
Code:
bootlist -m normal -o
hdisk6 blv=hd5 pathid=0
test02:/]bootinfo -b
hdisk6
test02:/]test02:/]ipl_varyon -i
[S 2752822 3407952 11/11/14-14:52:20:940 ipl_varyon.c 1282] ipl_varyon -i 


PVNAME          BOOT DEVICE     PVID                    VOLUME GROUP ID
hdisk2          NO              00c8ac36cfdf99b40000000000000000        00c8abe600004c00
hdisk5          NO              00c8abd6d05f83ca0000000000000000        00c8abd600004c00
hdisk6          YES             00c8abd6d4ad141f0000000000000000        00c8abd600004c00
hdisk7          NO              00c8abd6d4ad14b60000000000000000        00c8abf600004c00
[E 2752822 0:088 ipl_varyon.c 1422] ipl_varyon: exited with rc=0
test02:/]lslv -m hd5
hd5:N/A
LP    PP1  PV1               PP2  PV2               PP3  PV3
0001  0001 hdisk6

Code:
test02:/]lsvg -l altinst_rootvg
altinst_rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
bootlv00            boot       1       1       1    closed/syncd  N/A
pagelv00            paging     64      64      1    closed/syncd  N/A
loglv05             jfs2log    1       1       1    closed/syncd  N/A
fslv12              jfs2       2       2       1    closed/syncd  N/A
fslv13              jfs2       12      12      1    closed/syncd  N/A
fslv14              jfs2       4       4       1    closed/syncd  N/A
fslv15              jfs2       40      40      1    closed/syncd  N/A
fslv16              jfs2       39      39      1    closed/syncd  N/A
fslv17              jfs2       8       8       1    closed/syncd  N/A
lv01                sysdump    12      12      1    closed/syncd  N/A
test02:/]bootlist -m normal /dev/hdisk7 blv=bootlv00
0514-202 bootlist: Invalid device name (/dev/hdisk7)

Somebody knows how to fix this, please SmilieSmilieSmilie
# 2  
Old 11-11-2014
Hmm,

The error it is throwing clearly says it cannot find /dev/hd5
There is something utterly wrong in the configuration, why are all the LV names changed? why bootlv00? it should be something like alt_hd5.
If I am not wrong you created the alt_disk from existing rootvg (which resides on hdisk6), which has hd5 as boot logical volume.

Do you mind telling us why did you change the LV names?

Paste the output of
lsvg -l rootvg

Moreover the syntax for bootlist should be
bootlist -m normal hdiskX blv=Y
Where X=0,1,2,3 etc.., and Y=alt_hd5 or hd5, depending on rootvg or alt_rootvg.
There is NO /dev/hdiskX
This User Gave Thanks to ibmtech For This Post:
bobochacha29
# 3  
Old 11-11-2014
ibmtech is absolutely correct: this "altinst_rootvg" might be named like it was created by alt_disk_copy, but it has either been tampered with or created by different means (i can create a Vg called "altinst_rootvg", but that will not make it a eligible target for alt_disk-operations at all).

I suggest to remove the VG and recreate it, this time using correct procedures:

Code:
# alt_disk_install -X altinst_rootvg
# alt_disk_copy -d hdisk7

then proceed from there.

Just as an aside: even when using the correct command which ibmtech told you and assuming that whatever you have on hdisk7 is bootable and legit to boot AIX at all (i doubt that, but lets assume it for the sake of the argument) you need to use "hdisk7" in the bosboot command, not "/dev/hdisk7", because you need to name the disk, not its device file (which is just a driver construct representing the disk).

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
bobochacha29
# 4  
Old 11-12-2014
Thanks guys. Maybe there was something wrong with the altinst_rootvg. I removed it and recreated it. Then I booted the hdisk7 from SMS ( no bosboot or bootlist commands anymore ) and it worked.
This User Gave Thanks to bobochacha29 For This Post:
Corona688
# 5  
Old 11-12-2014
I would think that as altinst_rootvg it would be varied off and therefore you cannot see logical volume hd5 on it. I did once vary on one of these and the OS naturally objected to the matching names of the LVs and promptly renamed them as seems to have happened here, making it unusable. I had to recreate it.


Robin
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sed Or Grep Problem OR Terminal Problem?

I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore. Here is what 's happening: * I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies

2. AIX

bosboot issue

Hi i wanted to know for what reasons, bosboot fails with the error below.? # /usr/sbin/bosboot.dp -a -p /usr/lib/boot/chrp.disk.proto -d /dev/ipldevice dd: 0511-053 The write failed. : There is a request to a device or address that does not exist. 65893+1 records in. 1029+1 records out. ... (1 Reply)
Discussion started by: gnakul
1 Replies

3. IP Networking

Problem with forwarding emails (SPF problem)

Hi, This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question. I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Discussion started by: carwe
0 Replies

4. AIX

Cannot uninstall powerpath - bosboot issues

Hi Guys, I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one. I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors: ... (4 Replies)
Discussion started by: zxmaus
4 Replies

5. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

6. AIX

bosboot issue

bosboot -ad hdisk0 give the following error .. malloc failed 0301-177 A previous bosdebug command has changed characteristics of this boot image. Use bosdebug -L to display what these changes are. 0301-106 /usr/lib/boot/bin/mkboot_chrp: The malloc call failed for size: 216174592 ... (1 Reply)
Discussion started by: b_manu78
1 Replies

7. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

8. AIX

installp -C error: 'bosboot verification failed'

Hi, I'm a noob with AIX, can anybody help me solve this issue I'm stuck with on an 5.3 box. bash# installp -C 0503-409 installp: bosboot verification starting... 0503-497 installp: An error occurred during bosboot verification processing. Thanks. (4 Replies)
Discussion started by: thebytegrill
4 Replies

9. AIX

bosboot: Boot image is 22995 512 byte blocks.

My mksysb scripts gives the following text on standard error: bosboot: Boot image is 22995 512 byte blocks. How come on a Aix 5200-07 aix-system. I thought this message meant that the tape (/dev/rmt0) is not bootable, but I read about a limit of 12 MB and 22995 block is less than 12 MB ... (0 Replies)
Discussion started by: frankwiel
0 Replies

10. UNIX for Dummies Questions & Answers

bosboot problem please help!

each time I try to do a bosboot or a mksysb the cpu says that he doesn't find /unix... I don't understand cause the kernel is here on the computer and at this exact place with the right name. I tried to force with -k /unix but it doesn't do anything. He doesn't find it and it is here... Do you... (6 Replies)
Discussion started by: jericho
6 Replies
Login or Register to Ask a Question