- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Stlale extents
Operating System - HP-UX
1753261
Members
5015
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО01-20-2006 02:35 AM
тАО01-20-2006 02:35 AM
Re: Stlale extents
Couldn't get an outage window until tomorrow, Saturday night. I will update with results when complete. We have a good Ignite image prior to the stale extents so worst case we will be able to blow that down. Fortunately, the stale extents are in /usr, which is very static since the server has been in freeze mode for a month.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2006 03:34 AM
тАО01-20-2006 03:34 AM
Re: Stlale extents
Eric,
here is my advice, that may work but still proceed on your request for outage. This is just the process of replacing the defective disk, other things being equal.
Follow below steps and you may not need an outage. You would know immediately you need it.
Please, do this during the outage window. To be on the safe side shutdown all databases, go to init 2. umount all other file systems not relevant to O/S but do not forget that umount -a would umount /stand. then mount it back.
If you have your vgcfgbackup file anywhere then you can proceed. The backup file is by default in /etc/lvmconf/vg00.conf
If you physically hot swap the bad drive from the system and you can still work and access /usr then there is a change that you do not need an outage.
follow these steps.
1. # vgcfgrestore -n /dev/vg00 /dev/rdsk/
Start the mirror synchronize process.
2. # vgsync /dev/vg00 (This process takes time to resync.)
Place the boot utilities in the boot area.
3. # mkboot /dev/rdsk/
Add an Auto file in the boot LIF area.
4. # mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/
Note: The -lq switch could be added to override quorum on HIGH AVAILABILITY systems.
EXAMPLE: # mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/
Update LIF'S Lable file with information contained in the BDRA. (Boot Data Reserved Area)
5. # lvlnboot -Rv
Getting diagnostics on the root mirror disk
List the offline diagnostics from the good root boot disk.
6. # lifls -il /dev/rdsk/cXtXd0
Copy the diagnostics to the mirror root disk.
7. # cd /usr/sbin/diag/lif
# mkboot -b updatediaglif -p ISL -p HPUX -p LABEL -p AUTO /dev/rdsk/
here is my advice, that may work but still proceed on your request for outage. This is just the process of replacing the defective disk, other things being equal.
Follow below steps and you may not need an outage. You would know immediately you need it.
Please, do this during the outage window. To be on the safe side shutdown all databases, go to init 2. umount all other file systems not relevant to O/S but do not forget that umount -a would umount /stand. then mount it back.
If you have your vgcfgbackup file anywhere then you can proceed. The backup file is by default in /etc/lvmconf/vg00.conf
If you physically hot swap the bad drive from the system and you can still work and access /usr then there is a change that you do not need an outage.
follow these steps.
1. # vgcfgrestore -n /dev/vg00 /dev/rdsk/
Start the mirror synchronize process.
2. # vgsync /dev/vg00 (This process takes time to resync.)
Place the boot utilities in the boot area.
3. # mkboot /dev/rdsk/
Add an Auto file in the boot LIF area.
4. # mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/
Note: The -lq switch could be added to override quorum on HIGH AVAILABILITY systems.
EXAMPLE: # mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/
Update LIF'S Lable file with information contained in the BDRA. (Boot Data Reserved Area)
5. # lvlnboot -Rv
Getting diagnostics on the root mirror disk
List the offline diagnostics from the good root boot disk.
6. # lifls -il /dev/rdsk/cXtXd0
Copy the diagnostics to the mirror root disk.
7. # cd /usr/sbin/diag/lif
# mkboot -b updatediaglif -p ISL -p HPUX -p LABEL -p AUTO /dev/rdsk/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2006 03:56 AM
тАО01-20-2006 03:56 AM
Re: Stlale extents
Eric,
just discovered that you have an Itanium server.
Then the process is different apologies. This I have not tested very well but the process I listed below is a combination of steps for replacing HPUX version root disks and steps in creating mirror root disk and I believe it should work. You do not have anything to loose except time.
You would need to create the EFI partition first.
1. Create the system, OS, and service partitions.
# vi /tmp/partitionfile
3
EFI 500MB
HPUX 100%
HPSP 400MB
# idisk -wf /tmp/partitionfile /dev/rdsk/
idisk version: 1.31
********************** WARNING ***********************
If you continue you may destroy all data on this disk.
Do you wish to continue(yes/no)? yes <-- Answer "yes" and not "y"
3. Create device files needed for the new partitions.
# insf -eC disk
4. Verify the partition table.
# idisk /dev/rdsk/
5. Verify that the device files were created properly.
# ioscan -efnC disk -->
6. Populate the /efi/hpux/ directory in the new EFI system partition.
# mkboot -e -l /dev/rdsk/
7. Change the auto file for the mirror to boot without quorum.
NOTE: Using "s1"
# echo "boot vmunix -lq" > /tmp/AUTO.lq
# efi_cp -d /dev/rdsk/s1 /tmp/AUTO.lq /EFI/HPUX/AUTO
Please, do not forget the s1 behind the newdisk CTD.
NOTE: We assume that if we boot from the primary, the mirror is fully
functional and therefore we don't need to override quorum. Your site might
require that both disks override quorum.
9. Verify the contents of the auto file on the primary and the mirror.
NOTE: Using "s1"
# efi_cp -d /dev/rdsk/s1 -u /EFI/HPUX/AUTO /tmp/AUTO.pri
# efi_cp -d /dev/rdsk/s1 -u /EFI/HPUX/AUTO /tmp/AUTO.alt
# cat /tmp/AUTO.pri
# cat /tmp/AUTO.alt
then you can proceed on the vgcfgrestore and others.
1. # vgcfgrestore -n /dev/vg00 /dev/rdsk/s2
(Note this is section 2)
Start the mirror synchronize process.
2. # vgsync /dev/vg00 (This process takes time to resync.)
systems.
Update LIF'S Table file with information contained in the BDRA. (Boot Data Reserved Area)
5. # lvlnboot -Rv
Getting diagnostics on the root mirror disk
List the offline diagnostics from the good root boot disk.
6. # lifls -il /dev/rdsk/cXtXd0s2
Copy the diagnostics to the mirror root disk.
just discovered that you have an Itanium server.
Then the process is different apologies. This I have not tested very well but the process I listed below is a combination of steps for replacing HPUX version root disks and steps in creating mirror root disk and I believe it should work. You do not have anything to loose except time.
You would need to create the EFI partition first.
1. Create the system, OS, and service partitions.
# vi /tmp/partitionfile
3
EFI 500MB
HPUX 100%
HPSP 400MB
# idisk -wf /tmp/partitionfile /dev/rdsk/
idisk version: 1.31
********************** WARNING ***********************
If you continue you may destroy all data on this disk.
Do you wish to continue(yes/no)? yes <-- Answer "yes" and not "y"
3. Create device files needed for the new partitions.
# insf -eC disk
4. Verify the partition table.
# idisk /dev/rdsk/
5. Verify that the device files were created properly.
# ioscan -efnC disk -->
6. Populate the /efi/hpux/ directory in the new EFI system partition.
# mkboot -e -l /dev/rdsk/
7. Change the auto file for the mirror to boot without quorum.
NOTE: Using "s1"
# echo "boot vmunix -lq" > /tmp/AUTO.lq
# efi_cp -d /dev/rdsk/
Please, do not forget the s1 behind the newdisk CTD.
NOTE: We assume that if we boot from the primary, the mirror is fully
functional and therefore we don't need to override quorum. Your site might
require that both disks override quorum.
9. Verify the contents of the auto file on the primary and the mirror.
NOTE: Using "s1"
# efi_cp -d /dev/rdsk/
# efi_cp -d /dev/rdsk/
# cat /tmp/AUTO.pri
# cat /tmp/AUTO.alt
then you can proceed on the vgcfgrestore and others.
1. # vgcfgrestore -n /dev/vg00 /dev/rdsk/
(Note this is section 2)
Start the mirror synchronize process.
2. # vgsync /dev/vg00 (This process takes time to resync.)
systems.
Update LIF'S Table file with information contained in the BDRA. (Boot Data Reserved Area)
5. # lvlnboot -Rv
Getting diagnostics on the root mirror disk
List the offline diagnostics from the good root boot disk.
6. # lifls -il /dev/rdsk/cXtXd0s2
Copy the diagnostics to the mirror root disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2006 04:02 AM
тАО01-20-2006 04:02 AM
Re: Stlale extents
Hi Eric,
I would recommend you issue a vgsync and then issue a strings /etc/lvmtab. Then try running the following command.
dd if=/dev/rdsk/c4t8d0 of=/dev/null bs=1024k
If you get an I/O error from dd, the disk is bad.
Regards,
Simon
I would recommend you issue a vgsync and then issue a strings /etc/lvmtab. Then try running the following command.
dd if=/dev/rdsk/c4t8d0 of=/dev/null bs=1024k
If you get an I/O error from dd, the disk is bad.
Regards,
Simon
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP