Operating System - HP-UX
1855704 Members
8923 Online
104103 Solutions
New Discussion

Re: failure in kernel rebuild

 
Scott Dunkley
Regular Advisor

failure in kernel rebuild

Hi all,

I am trying to claw back some space from VG00 so I can install a new patch bundle. My system is running HP-UX 11.00. So far I have,

trimmed the logs
run cleanup -i and -c

I was having a look through SAM and found an option to remove unused file sets so I chose that and run phase 1 but not phase 2. This failed configuring the kernel so I tried it manually and got the same error. The errors are listed below:

ishpd380# mk_kernel -s system
WARNING: No such device, tunable, or cdio pa.
Ignoring the following line.
pa
WARNING: No such device, tunable, or cdio autofsc.
Ignoring the following line.
autofsc
WARNING: No such device, tunable, or cdio nfsm.
Ignoring the following line.
nfsm
WARNING: No such device, tunable, or cdio rpcmod.
Ignoring the following line.
rpcmod
WARNING: No such device, tunable, or cdio num_clients.
Ignoring the following line.
num_clients 40
Compiling conf.c...
Loading the kernel...
/usr/ccs/bin/ld: Unsatisfied symbols:
socachecallback (code)
*** Error exit code 1

Stop.
config: make did an exit(1)

Can someone explain what this means and how I correct the problem. I guess its the symbol problem that is causing the failure as the other messages say ignored.
Better to regret something you have done, than something you havn't
6 REPLIES 6
Steven E. Protter
Exalted Contributor

Re: failure in kernel rebuild

Perhaps we have cleaned a little too much?

You didn't remove any files from /stand did you?

dmesg

Something appears to be removed or unmounted or missing.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Scott Dunkley
Regular Advisor

Re: failure in kernel rebuild

I did remove the .prev files from .stand (not removed just moved) as I guessed I was having a space issue, /stand was 80% full.

I have just run dmesg and it reports /stand as full see below:

/stand: file system full
/stand: file system full
ishpd380# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 86016 76179 9247 89% /
/dev/vg00/lvol1 47829 21539 21507 50% /stand
/dev/vg00/lvol8 614400 445172 160899 73% /var
/dev/vg00/lvol7 819200 535291 266961 67% /usr
/dev/vg00/lvol4 32768 6581 24674 21% /tmp
/dev/vg00/lvol6 438272 232964 193045 55% /opt
/dev/vg00/lvol5 20480 1109 18168 6% /home
/dev/dsk/c2t2d0 2457600 2457600 0 100% /cdrom
ishpd380#

I have a few Mb left in VG00 enough to exetnd /stand by 40Mb or so which will give me enough space however it needs to be contgious so can I actually do this?

I guess /stand is fillinmg up during the mk_kernel and then rolls it back out on failure, is that right?
Better to regret something you have done, than something you havn't
Scott Dunkley
Regular Advisor

Re: failure in kernel rebuild

quick update, tried the mk_kernel again but it failed the same. I dont think this is space related as there is no new message in the syslog, only the messages from an hour a go when I tried it the first time.

Another question is wether my system will boot as is? I presume it hasnt actually changed the existing kernel so cant see why it wouldn't boot.
Better to regret something you have done, than something you havn't
doug mielke
Respected Contributor

Re: failure in kernel rebuild

You may want to poke around in the /usr/conf directory, and look at file dates. It could be that sam corrupted something here. I've never done it in HP/UX, but in other flavors it has been safe to simply replace these files from a backup or even another system.

Again, I cant say this works on HP/UX, but it's an idea.
Fabio Ettore
Honored Contributor

Re: failure in kernel rebuild

Hi,

first of all report .prev kernel in /stand and then boot from it:

- stop boot and interacyt with IPL;
- insert the string
hpux (;0)/stand/vmunix.prev

it should go up.

HTH.

Best regards,
Ettore
WISH? IMPROVEMENT!
Scott Dunkley
Regular Advisor

Re: failure in kernel rebuild

the system is still up and I havnt actually tried a reboot yet as I am nervous it wont come up. Am hoping for a response to this overnight, if no response by tommorow I will put the re instate the .prev files and reboot.

I dont understand why letting the system decide which filesets need removing has now caused the kernel not to rebuild!!!!!
Better to regret something you have done, than something you havn't