Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:37 AM
07-16-2002 04:37 AM
I have inserted the secondary disk, ran ioscan and insf -e.
I was told that I could now run a vgsync vg00 and the disks would go back into a mirrored system disks again. When I run a vgsync vg00, this is the error message I receive:
# vgsync /dev/vg00 /dev/dsk/c2t2d0
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol1".
vgsync: Couldn't resynchronize volume group "/dev/vg00".
vgsync: Volume group "/dev/dsk/c2t2d0" does not exist in the "/etc/lvmtab" file.
vgsync: Couldn't resynchronize volume group "/dev/dsk/c2t2d0".
When I do a #more /etc/lvmtab I get the following (yuck!!):
# more /etc/lvmtab
^CM-h^B/dev/vg00
^_M-!M-pi9-uM-k^B/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/vg01
^_M-!M-pi=^XM-DM-_^B/dev/dsk/c1t0d0
/dev/dsk/c2t0d0
Please consult.
Thanks!!!
..Joe
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:44 AM
07-16-2002 04:44 AM
Re: vgsync
You only need to give the command :
# vgsync /dev/vg00
Since you have tried giving the command
#vgsync /dev/vg00 /dev/dsk/c2t2d0,
it is trying to find out if there is a volumegroup by the name /dev/dsk/c2t2d0 and giving you this error.
Always do a
#strings /etc/lvmtab ( since it is a binary file ) and not #more /etc/lvmtab
So, just issue
#vgsync /dev/vg00 and you will be through
HTH,
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:46 AM
07-16-2002 04:46 AM
Re: vgsync
This member has assigned points to 108 of 567 responses to his/her questions.
http://forums.itrc.hp.com/cm/TopSolutions/1,,CA497804!1!questions,00.html
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:48 AM
07-16-2002 04:48 AM
Re: vgsync
# vgsync /dev/vg00
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol1".
vgsync: Couldn't resynchronize volume group "/dev/vg00".
#strings /etc/lvmtab
/dev/vg00
i9-u
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/vg01
/dev/dsk/c1t0d0
/dev/dsk/c2t0d0
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:49 AM
07-16-2002 04:49 AM
Re: vgsync
First, since '/etc/lvmtab' is a binary file, you need to view it with 'strings':
# strings /etc/lvmtab
Using 'more' with this kind of file exposes non-printable characters which merely confuse. However, you *do* have 'dev/dsk/c2t2d0' as part of vg00, along with '/dev/dsk/c1t2d0'.
I suggest you see if you have a viable connection to c1t2d0 by doing:
# diskinfo -v /dev/rdsk/c1t2d0
You should be able to read the physical disk and obtain a disk size that is non-zero. If you can't then you have a connectivity problem or a bad disk.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:53 AM
07-16-2002 04:53 AM
Re: vgsync
#diskinfo -v /dev/rdsk/c2t2d0
both had good results
SCSI describe of /dev/rdsk/c1t2d0:
vendor: IBM
product id: DMVS18D
type: direct access
size: 17783240 Kbytes
bytes per sector: 512
rev level: HP05
blocks per disk: 35566480
ISO version: 0
ECMA version: 0
ANSI version: 3
removable media: no
response format: 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 04:55 AM
07-16-2002 04:55 AM
Re: vgsync
I think that the disk /dev/dsk/c2t2d0 is having problems. Check for any loose connections and you can reboor your server once and see. If not then you will have to replace the disk. Also use
#diskinfo /dev/rdsk/c2t2d0
If you still want to check the disk
#dd if=/dev/rdsk/c2t2d0 of=/dev/null bs=512k
This will take some time to check the disk.
If you get input records = output records then your disk is OK or else there is some problem.
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:00 AM
07-16-2002 05:00 AM
Re: vgsync
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:11 AM
07-16-2002 05:11 AM
Re: vgsync
34732+1 records in
34732+1 records out
Any other suggestions???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:15 AM
07-16-2002 05:15 AM
Re: vgsync
If you give the command
# lvsync /dev/vg00/lvol1
what is the output.
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:17 AM
07-16-2002 05:17 AM
Re: vgsync
lvsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
lvsync: Couldn't resynchronize logical volume "/dev/vg00/lvol1".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:20 AM
07-16-2002 05:20 AM
Re: vgsync
Can you use the dd command on the /dev/rdsk/c1t2d0 also.
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:36 AM
07-16-2002 05:36 AM
Re: vgsync
34732+1 records in
34732+1 records out
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:40 AM
07-16-2002 05:40 AM
Re: vgsync
waht tis o/p of vgdisplay -v /dev/vg00 I think there is some PV which is not getting activated properly , can you please post that o/p too.
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:41 AM
07-16-2002 05:41 AM
Re: vgsync
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t2d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 12
Open LV 12
Max PV 16
Cur PV 2
Act PV 1
Max PE per PV 4350
VGDA 2
PE Size (Mbytes) 4
Total PE 4340
Alloc PE 4274
Free PE 66
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t2d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 84
Current LE 21
Allocated PE 42
Used PV 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:47 AM
07-16-2002 05:47 AM
Re: vgsync
# lvlnboot -v
lvlnboot: Couldn't query physical volume "/dev/dsk/c2t2d0":
The specified path does not correspond to physical volume attached to
this volume group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:47 AM
07-16-2002 05:47 AM
Re: vgsync
This means that your PV /dev/dsk/c2t2d0 is not getting detected by the LVM.
What is the output of the
#lvdisplay -v /dev/vg00/lvol1 command.
Does it shows the stale blocks for the primary or secondary harddisk. If you can post the output.
What is the output of the
#lvlnboot -v
Regards,
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:49 AM
07-16-2002 05:49 AM
Re: vgsync
# lvdisplay /dev/vg00/lvol1
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t2d0":
The specified path does not correspond to physical volume attached to
this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 84
Current LE 21
Allocated PE 42
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:54 AM
07-16-2002 05:54 AM
Re: vgsync
What is the output of
#ioscan -fnC disk | grep c2t2d0
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:58 AM
07-16-2002 05:58 AM
Re: vgsync
vgchange -a y /dev/vg00
Is the above command mandatory (based on what my situation) before i vgsync?
Thanks to all!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:58 AM
07-16-2002 05:58 AM
Re: vgsync
Your vg00 was not activated and hence all these problems. Nice catch ...JRF....couldnt guess it right !!!
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 06:06 AM
07-16-2002 06:06 AM
Re: vgsync
The kernel "thought" the disk was still absent. The 'vgchange -a y' updated kernel tables indictating its presence. Given the way you performed the operation, you would probably have to do this again.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 06:07 AM
07-16-2002 06:07 AM
Re: vgsync
Since you had removed the secondary harddisk for loading the pacthes on the primary, these problems happened. When you loaded the patches on the primary harddisk, the OS knew that you had only one harddisk. Since your vg00 had two harddisk the vg00 had been deactivated. It could come up only beacuse of the -lq option set in the AUTO file which overrides the quorum.
Piyush