- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- es45 root mirror problem
Operating System - Tru64 Unix
1752808
Members
5907
Online
108789
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
тАО10-08-2008 06:38 AM
тАО10-08-2008 06:38 AM
es45 root mirror problem
I have an es45/tru64 v5.1A system that was installed recently. The system was installed to dsk0 and the volrootmir -a was used to mirror to dsk1.
After a few days, dsk0a was shown as FAILED.
We removed the disk and started to remove the plexes and volumes using volplex -dis and voledit -f -r rm
We then hit a problem whereby we couldn't remove the swapvol-01 plex. We found another forum post about this and removed patch 1998 to work around this issue.
The problem now is that we are unable to re-mirror the disk. The new disk we inserted was seen as dsk4, rather than dsk0.
volprint shows the following:
# volprint -Aht
Disk group: rootdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
dg rootdg default default 0 1223295187.1026.20750:10:26:17
dm dsk1d dsk1d simple 4096 0 -
dm dsk1g-AdvFS dsk1g nopriv 0 4300800 -
dm root01 - - - - NODEVICE
dm root02 - - - - NODEVICE
dm swap01 - - - - NODEVICE
dm swap02 dsk1b nopriv 0 786432 -
dm usr01 - - - - NODEVICE
v rootvol root DISABLED ACTIVE 786432 ROUND -
pl rootvol-02 rootvol DISABLED NODEVICE 786432 CONCAT - RW
sd root02-02p rootvol-02 root02 0 16 0 - NDEV
sd root02-02 rootvol-02 root02 16 786416 16 - NDEV
v swapvol swap ENABLED ACTIVE 786432 ROUND -
pl swapvol-02 swapvol ENABLED ACTIVE 786432 CONCAT - RW
sd swap02-02 swapvol-02 swap02 0 786432 0 dsk1b ENA
v usrvol fsgen ENABLED ACTIVE 4300800 ROUND -
pl usrvol-02 usrvol ENABLED ACTIVE 4300800 CONCAT - RW
sd dsk1g-01 usrvol-02 dsk1g-AdvFS 0 4300800 0 dsk1g ENA
The issue seems to be around root02 - surely this is on dsk1 and shouldn't be shown as NODEVICE?
Can anyone suggest how I fix this?
Thanks
After a few days, dsk0a was shown as FAILED.
We removed the disk and started to remove the plexes and volumes using volplex -dis and voledit -f -r rm
We then hit a problem whereby we couldn't remove the swapvol-01 plex. We found another forum post about this and removed patch 1998 to work around this issue.
The problem now is that we are unable to re-mirror the disk. The new disk we inserted was seen as dsk4, rather than dsk0.
volprint shows the following:
# volprint -Aht
Disk group: rootdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
dg rootdg default default 0 1223295187.1026.20750:10:26:17
dm dsk1d dsk1d simple 4096 0 -
dm dsk1g-AdvFS dsk1g nopriv 0 4300800 -
dm root01 - - - - NODEVICE
dm root02 - - - - NODEVICE
dm swap01 - - - - NODEVICE
dm swap02 dsk1b nopriv 0 786432 -
dm usr01 - - - - NODEVICE
v rootvol root DISABLED ACTIVE 786432 ROUND -
pl rootvol-02 rootvol DISABLED NODEVICE 786432 CONCAT - RW
sd root02-02p rootvol-02 root02 0 16 0 - NDEV
sd root02-02 rootvol-02 root02 16 786416 16 - NDEV
v swapvol swap ENABLED ACTIVE 786432 ROUND -
pl swapvol-02 swapvol ENABLED ACTIVE 786432 CONCAT - RW
sd swap02-02 swapvol-02 swap02 0 786432 0 dsk1b ENA
v usrvol fsgen ENABLED ACTIVE 4300800 ROUND -
pl usrvol-02 usrvol ENABLED ACTIVE 4300800 CONCAT - RW
sd dsk1g-01 usrvol-02 dsk1g-AdvFS 0 4300800 0 dsk1g ENA
The issue seems to be around root02 - surely this is on dsk1 and shouldn't be shown as NODEVICE?
Can anyone suggest how I fix this?
Thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2008 12:04 PM
тАО10-08-2008 12:04 PM
Re: es45 root mirror problem
Hi,
I've not used LSM for a *long* time, however you should be able to get the new disk, back onto dsk0 using dsfmgr.
# dsfmgr -m dsk4 dsk0
Hope this helps,
Regards,
Rob
I've not used LSM for a *long* time, however you should be able to get the new disk, back onto dsk0 using dsfmgr.
# dsfmgr -m dsk4 dsk0
Hope this helps,
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2008 06:14 PM
тАО10-08-2008 06:14 PM
Re: es45 root mirror problem
hello Robert Sandham
if cann't dis plex,I would like to use other methods can be replaced.
eg
disklabel dsk0 > /tmp/dsk0.label
voldg -g rootdg -k rmdisk
voldisk -rm
replace field harddisk
disklabel -z dsk1
disklabel -wr dsk1
disklabel -R -r -t advfs dsk1 /tmp/dsk0.label SCSI
disklabel -sF dsk1a(a~g) unused
voldisk -g rootdg -f -n init dsk1a type=nopriv
....
voldisk -g rootdg -f -n init dsk1g type=nopriv
voldg -g rootdg -k adddisk dsk1a=dsk1a
....
disklabel -R -r -t advfs dsk1 /tmp/dsk0.label SCSI(This is a very important step)
volrecover -sb rootvol
....
i wanted to useful for you
if cann't dis plex,I would like to use other methods can be replaced.
eg
disklabel dsk0 > /tmp/dsk0.label
voldg -g rootdg -k rmdisk
voldisk -rm
replace field harddisk
disklabel -z dsk1
disklabel -wr dsk1
disklabel -R -r -t advfs dsk1 /tmp/dsk0.label SCSI
disklabel -sF dsk1a(a~g) unused
voldisk -g rootdg -f -n init dsk1a type=nopriv
....
voldisk -g rootdg -f -n init dsk1g type=nopriv
voldg -g rootdg -k adddisk dsk1a=dsk1a
....
disklabel -R -r -t advfs dsk1 /tmp/dsk0.label SCSI(This is a very important step)
volrecover -sb rootvol
....
i wanted to useful for you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 04:49 AM
тАО10-13-2008 04:49 AM
Re: es45 root mirror problem
Just rename the disk by
dsgmgr -e dsk4 dsk0
then do
#volrootmir -a dsk4 &
this will take some time.
This should solve the issue.
BR,
Kapil+
dsgmgr -e dsk4 dsk0
then do
#volrootmir -a dsk4 &
this will take some time.
This should solve the issue.
BR,
Kapil+
I am in this small bowl, I wane see the real world......
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