This is going to mean nothing to most....
I'm working on a E4500 server running Solaris 2.5.1 and VXVM 2.5.5 
I've replaced the rootmirror and would like to monitor progress of the resync
It's only a 2Gb /partition so it shouldn't take too long.
In later versions
vxtask list
would supply the info.... but 2.5.5 doesn't have vxtask
It will have finished by the time I post this but I have several disks to replace and would like to know if there is a command that'd say it was 60% done or somesuch
Many thanks in advance
Martin
I'm afraid I don't have the answer to your question, but I'd love to see a couple of pictures of this hardware. Is there any chance you can share a couple? Thanks and GL!
Why on earth would someone want a photo of an E4500 and some D1000's?
They might still have an e10k 
And RSM Trays
I'm a newb who likes antiques, what can I say. Now, the 10k would be really sweet.
Did you get your problem addressed yet? I wish I could do more to help.
I'm now having an issue with Solaris ..... I'm running off my root mirror and have done a vxdiskadm option 4 on the root disk .... I've replaced the rootdisk with an 18gb disk and need to vxdiskadm option 5 back in, however .... When I try to run vxdiskadm I get
/usr/bin/vxdiskadm: Cannot create lock file /var/spool/locks/.DISKADD.LOCK
:0/
If I go to /var/spool/locks it's in there
rm /var/spool/locks/.DISKADD.LOCK
rm: /var/spool/locks/.DISKADD.LOCK not removed: No such device or address
If I do a pwd
/usr/bin/pwd: No such device or address
So it looks like a Solaris issue to me....
Checked in /usr/bin and pwd is in there ok.....
Any suggestions?
---------- Post updated at 04:28 PM ---------- Previous update was at 11:07 AM ----------
It's gone from bad to worse.
After investigation, a general consensus was the 2.5.1 was not very good and often required a reboot ..... which I duly did .... uh-oh....
The system failed to boot from the rootmirror.
I put the original rootdisk back in. Failed to boot.
It wont even boot from a cdrom .... just getting Fast Access Data MMU Miss errors....
Was supposed to be an easy job :0/
at the moment it's goosed
You might want to start a new thread in the Emergency support forum. That will ensure the quickest response from this forum.