Why are you running "vgscan -a"? It's not part of a standard procedure for creating a new LVM VG.
The man page for vgscan says:
----
... This command should be run only in the event of a catastrophic error such as the deletion of the /etc/lvmtab file or the mismatch of names of the physical volumes in the /etc/lvmtab file to the actual physical volume path configuration.
If the /etc/lvmtab file exists, the information contained in the file is used to assist in rebuilding the file, but the existing file is updated with the new corrected configuration.
----
> Couldn't stat physical volume "/dev/dsk/c0t0d0":
> Invalid argument
/dev/dsk/c0t0d0 might be a CD-ROM/DVD drive with no disc inserted. If that's true, the message about it is expected and harmless.
> Physical Volume "/dev/dsk/c3t5d0" is not part of a Volume Group
The message about /dev/dsk/c3t5d0 is information only: c3t5d0 seems to be pvcreate'd, but not yet attached to any known VG.
The only real problem I see is this:
> The Volume Group /dev/vg01 was not matched with any Physical Volumes.
Should vg01 exist?
If it's an old VG that was supposed to be removed, this indicates it was removed using a wrong procedure. Maybe vgremove or vgexport was not used, and the disks were simply removed or "pvcreate -f" was used on them. If this is the case, use "vgexport vg01" to remove the old vg01 configuration.
(Note: the vgexport command will create a file named "mapfile" in the current directory. It could be used to restore the vg01 configuration... but if the disks are already gone, you can just remove the mapfile.)
Also run "ioscan -fnCdisk": if there are disk devices in NO_HW state and you know that they have been removed permanently and on purpose, use "rmsf -a
" to remove the NO_HW device entries and disk device files.
If vg01 is supposed to exist, this indicates its disks are not accessible to the system. What kind of disks *should* these be? Check first for loose or damaged cable connections, powered-off external storage units, etc.
MK
MK
