- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: New disk problem
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
11-09-2004 03:47 AM
11-09-2004 03:47 AM
Please help
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 03:52 AM
11-09-2004 03:52 AM
Re: New disk problem
Could you give us a bit more details ?
How different is this disk ?
Are there more disks inside volume group you have lost ?
could you post
# vgdisplay -v vgname
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 03:53 AM
11-09-2004 03:53 AM
Re: New disk problem
Man vgcfgrestore, vgexport, vgreduce for details.
You really should be mirroring so that losing a disk is a complete non-event; if your disks are hot-plug you wouldn't even have to shut down. I haven't shut down to replace a failed disk in years although in that time I replaced many, many disks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 06:58 PM
11-09-2004 06:58 PM
Re: New disk problem
Then using vgscan -a to scan all of physical volumes for LVM volume groups and create the new lvmtab file.
Create again. I think it works!
Best and regard,
Jimkery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 08:02 PM
11-09-2004 08:02 PM
Re: New disk problem
Many Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 08:15 PM
11-09-2004 08:15 PM
SolutionYou should not be creating a new VG because this device file is already recorded in another VG. The correct procedure is to use 'vgcfgrestore'. Do not run 'vgscan'. If you did already, put your old /etc/lvmtab back. Here is the procedure. Since this disk is not part of a mirror, you have lost the data. What you can do is create LVM structures and get the logical volumes back but not the data. Find out the VG that this disk is part of 'strings /etc/lvmtab |more' will give you that information. Confirm the VG before you do the below say it is vg01.
#vgcfgrestore -n vg01 /dev/rdsk/c1t1d0
#vgchange -a y vg01
Now do a pvdisplay on this disk and find out all the logical volumes this disk has
#pvdisplay -v vg01 |more
For each logical volume, create a new filesystem.
#newfs -F vxfs /dev/vg01/rlvol1
Once all the LVs are done, mount them.
#mount -a
Now restore the data because these filesystems would be empty.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 08:17 PM
11-09-2004 08:17 PM
Re: New disk problem
Instead of 'pvdisplay -v /dev/vg01' read it as 'pvdisplay -v /dev/dsk/c1t1d0'.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 08:20 PM
11-09-2004 08:20 PM
Re: New disk problem
Was the volumegroup wgere the disk failed only containing one disk ? And you want to recreate the volumegroup with the same name ?
Then, first export the old volumegroup
vgexport vgXX
now it soould be possible to use SAM for recreating vgXX or:
pvcreate -f /dev/rdsk/
vgcreate vgXX /dev/dsk/block_disk_devicefile
vgchange -a y vgXX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 09:03 PM
11-09-2004 09:03 PM
Re: New disk problem
check out the screen shot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 09:08 PM
11-09-2004 09:08 PM
Re: New disk problem
Did you export the VG rtvg01 already?. If so, then you may have to import it back. However, as said before if you have only one disk in that VG, then it's better to recreate the VG.
Post the outputs of the folloowing.
strings /etc/lvmtab
strings /etc/lvmtab.
vgdisplay -v
ll /dev/*/group
We should be able to determine what's happening with the above.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 09:24 PM
11-09-2004 09:24 PM
Re: New disk problem
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 09:31 PM
11-09-2004 09:31 PM
Re: New disk problem
Yep. I don't see rtvg01 in /dev directory. Since this is only the PV in that VG, you can safely export it. Do
#vgexport rtvg01
Then use SAM to recreate the VG, filesystems and restore the data.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 09:41 PM
11-09-2004 09:41 PM
Re: New disk problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 09:46 PM
11-09-2004 09:46 PM
Re: New disk problem
#cp /etc/lvmtab /etc/lvmtab.good
#vgscan -a
#strings /etc/lvmtab
Make sure you get all VGs except rtvg01 in there. Once it is confirmed, you can go ahead and recreate this VG. Your vgdisplay -v etc., may complain but next reboot should take care of it.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 10:03 PM
11-09-2004 10:03 PM
Re: New disk problem
here is what i go
if you could please explain how to do this all the way through including the sam part
i need to create volume group rtvg01 and the the logical volumes rtd1 and rtd1v1 and the both need to be 2040mb big.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 10:07 PM
11-09-2004 10:07 PM
Re: New disk problem
#mv /etc/lvmtab /etc/lvmtab.junk
#vgscan -a
#strings /etc/lvmtab
That should get you rid of rtvg01.. Post the output before you proceed. Your leftvg* are giving errors. Do you have them working at this time?.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 10:14 PM
11-09-2004 10:14 PM
Re: New disk problem
i did that and it's looking pretty good
here is what i got on the screen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2004 10:20 PM
11-09-2004 10:20 PM
Re: New disk problem
Can you verify the following now?.
1. Are you sure the VGs leftvg01, leftvg02, leftvg03 not used anymore?. Obviously vgscan couldn't find the disks corresponding to them.
2. Run 'mount -a'. You should see only errors related to rtvg01 unless you have bad entries in /etc/fstab file.
3. Run 'lvlnboot -R' and make sure your 'lvlnboot -v' displays boot,root,swap and dump(optionally) lvols.
4. Make sure everything is working fine. Your database, application etc.,.
Once the above is confirmed, proceed with creating a new VG with c1t1d0.
Since you have only one disk in the VG, you could use 'vgscan' command. However, it may not be used as a generic solution in this situation.
-Sri