This is a solution:

dd if=/dev/zero count=2106 of=/dev/hdisk#

"uncle_ziba" <uncle_ziba@yahoo.com> schrieb im Newsbeitrag
news:377e309d.0401221605.de88861@posting.google.co m...
> This is a solution:
>
> dd if=/dev/zero count=2106 of=/dev/hdisk#

Sorry? I am not sure whether you posted in the right newsgroup - here is
comp.unix.AIX and the preferred way to erase a pvid is
# chdev -l hdiskx -a pv=clear
This will leave you with a disk AIX can work with. If sector 0 cannot be
touched by the chdev command you might consider lowlevel formating that
disk.
From your count value I get the impression that you do not really have an
idea of what you are actually doing. Nobody will hold you back if you f*ck
up your own playstation but you should not try to sell that 'solution' in
public. To the others who also prefer the dd shotgun method to blank out the
pvid I would rather suggest using
# dd if=/dev/zero count=1 of=/dev/hdiskx

"Andreas Schulze" <b79xan@gmx.de> wrote in message news:<buqn0d$9mk11@news-1.bank.dresdner.net>...
> "uncle_ziba" <uncle_ziba@yahoo.com> schrieb im Newsbeitrag
> news:377e309d.0401221605.de88861@posting.google.co m...
> > This is a solution:
> >
> > dd if=/dev/zero count=2106 of=/dev/hdisk#
>
> Sorry? I am not sure whether you posted in the right newsgroup - here is
> comp.unix.AIX and the preferred way to erase a pvid is
> # chdev -l hdiskx -a pv=clear
> This will leave you with a disk AIX can work with. If sector 0 cannot be
> touched by the chdev command you might consider lowlevel formating that
> disk.
> From your count value I get the impression that you do not really have an
> idea of what you are actually doing. Nobody will hold you back if you f*ck
> up your own playstation but you should not try to sell that 'solution' in
> public. To the others who also prefer the dd shotgun method to blank out the
> pvid I would rather suggest using
> # dd if=/dev/zero count=1 of=/dev/hdiskx

We tried to add a disk to the veritas volume manager that was
previously owned by LVM and the VM would not allow to add the disk
unless the pvid was cleared. We did not care about the contents of
the disk. The brute force method I posted was actually recommended by
a support engineer, but I'm not sure how he'd come with the count
number. Your command is obviously better if it physically erases the
pvid on a disk (not just from the ODM). I will give it a try. Best
regards.

"uncle_ziba" <uncle_ziba@yahoo.com> schrieb im Newsbeitrag
news:377e309d.0401240826.463a3fa4@posting.google.c om...
> "Andreas Schulze" <b79xan@gmx.de> wrote in message
news:<buqn0d$9mk11@news-1.bank.dresdner.net>...
> > "uncle_ziba" <uncle_ziba@yahoo.com> schrieb im Newsbeitrag
> > news:377e309d.0401221605.de88861@posting.google.co m...
> > > This is a solution:
> > >
> > > dd if=/dev/zero count=2106 of=/dev/hdisk#
> >
> > Sorry? I am not sure whether you posted in the right newsgroup - here is
> > comp.unix.AIX and the preferred way to erase a pvid is
> > # chdev -l hdiskx -a pv=clear
> > This will leave you with a disk AIX can work with. If sector 0 cannot be
> > touched by the chdev command you might consider lowlevel formating that
> > disk.
> > From your count value I get the impression that you do not really have
an
> > idea of what you are actually doing. Nobody will hold you back if you
f*ck
> > up your own playstation but you should not try to sell that 'solution'
in
> > public. To the others who also prefer the dd shotgun method to blank out
the
> > pvid I would rather suggest using
> > # dd if=/dev/zero count=1 of=/dev/hdiskx
>
> We tried to add a disk to the veritas volume manager that was
> previously owned by LVM and the VM would not allow to add the disk
> unless the pvid was cleared. We did not care about the contents of
> the disk. The brute force method I posted was actually recommended by
> a support engineer, but I'm not sure how he'd come with the count
> number.
So that command was ment to be some format substitute - I understand.
>Your command is obviously better if it physically erases the
> pvid on a disk (not just from the ODM). I will give it a try. Best
> regards.
Right. You might need this: The chdev command cleans (just) the pvid from
location 200 at sector 0 and deletes the corresponding ODM entry also. Mind
that lspv reads just data from the ODM. Try
# dd if=/dev/hdiskx 2>&1 | od -x | grep 0000200
before and after to see how it works. Use this command with more instead of
grep to see that chdev just deletes the location 0000200 and not its
surroundings. Use
# odmget -q "name=hdiskx and attribute=pvid" CuAt
to see what's happening to the pvid in the ODM.