Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
0516-1734 extendlv: Warning, savebase failed 2
- Thread starter gatetec
- Start date
-
2
- #2
No it is not critical, it just means you need to run savebase before you reboot.
Just like it said on the screen.
Simple if you think about it.
When it says "run savebase before rebooting", what it actually means is, run savebase before rebooting.
You may have a problem if you reboot without running savebase though.
This is implied in the message, the bit that says: run savebase before rebooting.
What this means is that you should run savebase before rebooting.
So the message is posted to warn you to run savebase before rebooting.
FFS
As root, from the command line, logged in as root, type the suggested command, savebase, that's it, job done.
Nothing to worry about.
just login as root, or login as another user and su to root, then type savebase and press return.
If you get a message you don't understand at this point then please post it here and we'll offer further advice.
If you don't get any warnings or errors then you are OK to reboot.
If you reboot without running savebase, or the system hangs, crashes, has a power outage, etc. - which kind of means it will reboot without you having run savebase - then you will have a problem, probably a fairly big problem.
man savebase
for more information.
Where do these people come from?
Just like it said on the screen.
Simple if you think about it.
When it says "run savebase before rebooting", what it actually means is, run savebase before rebooting.
You may have a problem if you reboot without running savebase though.
This is implied in the message, the bit that says: run savebase before rebooting.
What this means is that you should run savebase before rebooting.
So the message is posted to warn you to run savebase before rebooting.
FFS
As root, from the command line, logged in as root, type the suggested command, savebase, that's it, job done.
Nothing to worry about.
just login as root, or login as another user and su to root, then type savebase and press return.
If you get a message you don't understand at this point then please post it here and we'll offer further advice.
If you don't get any warnings or errors then you are OK to reboot.
If you reboot without running savebase, or the system hangs, crashes, has a power outage, etc. - which kind of means it will reboot without you having run savebase - then you will have a problem, probably a fairly big problem.
man savebase
for more information.
Where do these people come from?
Well, there's a reason of course that savebase didn't (and probably won't) run. I've known it to happen after I was fiddling around with the PV members of rootvg and ended up loosing the /dev/ipldevice link to the boot disk (or some other apparent vital device link). Only got that cleared up after a reboot I think... catch22 I guess.
HTH,
p5wizard
HTH,
p5wizard
KenCunningham
Technical User
Thanks for the Eater laugh, Duke! Have another star, and yes, they probably are out to get you.
I want to be good, is that not enough?
I want to be good, is that not enough?
KenCunningham
Technical User
Eater = doh, too many eggs!
I want to be good, is that not enough?
I want to be good, is that not enough?
Actually, the solution to this problem might not seem as clear cut as some think. It is not a very common error.
If you run savebase -v and you get "non-bootable LV name given" try reconstucting your /dev/ipldevice file. (I believe there is a posting somewhere here that tells you how to do that. Use Search to find those procedures.)
Run savebase -v again and if you get the same error, this is what we were told to do by IBM's LVM team:
run:
bosboot -ad on /dev/hdiskX (a disk that has hd5 on it)
bosboot -ad /dev/hdiskY (a disk that has hd5 on it)
ipl_varyon -i
[You'll get a return on every physical disk on the sysetm]
savebase -v
You will then get a return similar to this:
# savebase -v
saving to '/dev/hd5'
172 CuDv objects to be saved
608 CuAt objects to be saved
47 CuDep objects to be saved
68 CuVPD objects to be saved
459 CuDvDr objects to be saved
4 CuPath objects to be saved
0 CuPathAt objects to be saved
0 CuData objects to be saved
Number of bytes of data to save = 82051
Compressing data
Compressed data size is = 21059
bi_start = 0x3600
bi_size = 0xf03e00
bd_size = 0xee3e00
ram FS start = 0x4fc220
ram FS size = 0x9e7ad2
sba_start = 0xee7400
sba_size = 0x20000
sbd_size = 0x5247
Checking boot image size:
new save base byte cnt = 0x5247
Wrote 21063 bytes
savebase : successful completion
If you run savebase -v and you get "non-bootable LV name given" try reconstucting your /dev/ipldevice file. (I believe there is a posting somewhere here that tells you how to do that. Use Search to find those procedures.)
Run savebase -v again and if you get the same error, this is what we were told to do by IBM's LVM team:
run:
bosboot -ad on /dev/hdiskX (a disk that has hd5 on it)
bosboot -ad /dev/hdiskY (a disk that has hd5 on it)
ipl_varyon -i
[You'll get a return on every physical disk on the sysetm]
savebase -v
You will then get a return similar to this:
# savebase -v
saving to '/dev/hd5'
172 CuDv objects to be saved
608 CuAt objects to be saved
47 CuDep objects to be saved
68 CuVPD objects to be saved
459 CuDvDr objects to be saved
4 CuPath objects to be saved
0 CuPathAt objects to be saved
0 CuData objects to be saved
Number of bytes of data to save = 82051
Compressing data
Compressed data size is = 21059
bi_start = 0x3600
bi_size = 0xf03e00
bd_size = 0xee3e00
ram FS start = 0x4fc220
ram FS size = 0x9e7ad2
sba_start = 0xee7400
sba_size = 0x20000
sbd_size = 0x5247
Checking boot image size:
new save base byte cnt = 0x5247
Wrote 21063 bytes
savebase : successful completion
- Status
Similar threads
- Locked
- Question