https://community.hpe.com/t5/disk-enclosures/vgimport-returns-dev-vg01-already-exist/m-p/2755852#M5310 To be on the safe side what you can do is don't import it as vg01, use another vg name that's not been used yet (say vg02). You would then do this ..<BR /># mkdir /dev/vg02<BR /># mknod /dev/vg02/group c 64 0x020000<BR />==&gt; remember minor number 0x020000 has to be unique<BR /># vgimport /dev/vg02 /dev/dsk/xxx /dev/dsk/xxy<BR /># vgchange -a y /dev/vg02<BR />==&gt; activate it<BR /># vgdisplay -v vg02<BR />==&gt; check it<BR /><BR />Once this is ok .. get rid of the non-existing vg01 ..<BR /># vgexport /dev/vg01<BR /> Tue, 02 Jul 2002 03:57:04 GMT S.K. Chan 2002-07-02T03:57:04Z https://community.hpe.com/t5/disk-enclosures/vgimport-returns-dev-vg01-already-exist/m-p/2755851#M5309 I ran vgimport /dev/vg01 /dev/dsk/xxx /dev/dsk xxy ... and it returns that /dev/vg01 is already in lvmtab. <BR /><BR />This is true since I ran vgscan prior. How do I get those lvol's in /dev/vg01 ? Do I need to recreate them ??? Mon, 01 Jul 2002 20:57:11 GMT https://community.hpe.com/t5/disk-enclosures/vgimport-returns-dev-vg01-already-exist/m-p/2755851#M5309 Jay_41 2002-07-01T20:57:11Z https://community.hpe.com/t5/disk-enclosures/vgimport-returns-dev-vg01-already-exist/m-p/2755852#M5310 To be on the safe side what you can do is don't import it as vg01, use another vg name that's not been used yet (say vg02). You would then do this ..<BR /># mkdir /dev/vg02<BR /># mknod /dev/vg02/group c 64 0x020000<BR />==&gt; remember minor number 0x020000 has to be unique<BR /># vgimport /dev/vg02 /dev/dsk/xxx /dev/dsk/xxy<BR /># vgchange -a y /dev/vg02<BR />==&gt; activate it<BR /># vgdisplay -v vg02<BR />==&gt; check it<BR /><BR />Once this is ok .. get rid of the non-existing vg01 ..<BR /># vgexport /dev/vg01<BR /> Tue, 02 Jul 2002 03:57:04 GMT https://community.hpe.com/t5/disk-enclosures/vgimport-returns-dev-vg01-already-exist/m-p/2755852#M5310 S.K. Chan 2002-07-02T03:57:04Z