Operating System - HP-UX
1752795 Members
6101 Online
108789 Solutions
New Discussion юеВ

Re: Removing vPar and decommissioning HPUX

 
Charles Holland
Trusted Contributor

Removing vPar and decommissioning HPUX

We are in the process of decommissioning our HPUX servers after migrating everything to the Windows platform.

Background:
rp7410 with 2 cells
each cell has 2 vPars

While reading though the vPar installation manual it tells you how to get rid of one vPar simply by doing the vparremove command.

With server "4" shutdown and sitting on server "3" I did a vparremove -p 4 vPar is now gone and Cell 1 now only has 1 vpar.

How do I then remove vPar "3"? I'd like to get vpmon out of the picture and boot straight to vmunix.

subsequent to getting to that point, how do I wipe out the HPUX OS so that I can then put the HW up for sale?

Thanks for all who respond, and points do get assigned.
"Not everything that can be counted counts, and not everything that counts can be counted" A. Einstein
6 REPLIES 6
melvyn burnard
Honored Contributor

Re: Removing vPar and decommissioning HPUX

reboot the server, and at the boot prompt, interrupt it and use hpux /stand/vmunix, that will boot oin nPar mode,
or you could change the AUTO file on the boot disk with the mkboot commmand, and THEN reboot.
That is all you ned to do
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Kenan Erdey
Honored Contributor

Re: Removing vPar and decommissioning HPUX

Hi,

in vpar3 run vparenv -m npars. and do a hard reset from MP. it will reboot from npar mode.

rm -rf / will wipe out everything. But if you want nobody will recover data after selling your hw,

dd if=/dev/zero of=/dev/rdisk/diskxx bs=4096k

or

mediainit -v /dev/rdisk/diskxx
Computers have lots of memory but no imagination
Steven E. Protter
Exalted Contributor

Re: Removing vPar and decommissioning HPUX

Shalom,

Either dd every disk in the system like this:

dd if=/dev/random of=

Best way to go actually is to install the OS clean include all disk.

That does enough writing to the disks to make PCI, SOX happy and event he NSA would have a hard time recovering any data from the disks.

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
Charles Holland
Trusted Contributor

Re: Removing vPar and decommissioning HPUX

Melvyn:
If I should change the AUTO file it will boot to vmunix as you say.

Kenan:
Changed to / and tried the following:

# mediainit -v /dev/rdsk/c5t6d0
mediainit: initialization process starting
mediainit: locking SCSI device
mediainit: scsi_mi: Target lock failed
mediainit: scsi_mi: LUN lock failed
scsi_mi: Unable to set EXCLUSIVE mode: Device busy


Then tried from /:
# rm -rf /
rm: cannot remove .. or .

from / tried the dd command:
dd if=/dev/zero of=/dev/rdsk/cdt6d0 bs=4096k

results:
msgcnt 2 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent
)
I/O error
90+0 records in
89+1 records out

"Not everything that can be counted counts, and not everything that counts can be counted" A. Einstein
Charles Holland
Trusted Contributor

Re: Removing vPar and decommissioning HPUX

to all: never could get dd or mediainit to work
but if I do

# rm -Rf /* I get a whole lot of
rm: emsagent not removed. Text file busy
rm: p_client not removed. Text file busy
rm: registrar not removed. Text file busy
rm: directory lbin not removed. Directory not empty
rm: libresmon.1 not removed. Text file busy
rm: directory lib not removed. Directory not empty
rm: directory resmon not removed. Directory not empty

which is kind of like half removing everything.
"Not everything that can be counted counts, and not everything that counts can be counted" A. Einstein
Charles Holland
Trusted Contributor

Re: Removing vPar and decommissioning HPUX

see last post
"Not everything that can be counted counts, and not everything that counts can be counted" A. Einstein