Can you post the messages that were logged in /var/adm/messages when you had this failure, if they are not too long.
It looks like Volume Manager has attempted to relocate subdisk A5200-r-07-01 on to another disk, and your recovery procedure may depends on whether or not it completed before that disk failed as well.
analyze> read
Ready to analyze (won't harm SunOS). This takes a long time,
but is interruptable with CTRL-C. Continue?
Ready to analyze (won't harm SunOS). This takes a long time,
but is interruptable with CTRL-C. Continue? y
The disk was cream crackered. Talked him through a bunch of Veritas commands to try and managed to get part of it back on line part 1 of them just wouldn't play ball. Conclusion Cream Crackered Disk.
Talked him through a bunch of Veritas commands to try and managed to get part of it back on line but 1 of them just wouldn't play ball (RAID-B-01 I think).
Thank you everyone for trying to help. I did realized we have to mirrow disk happens to be bad. We replaced the disks and created a filesystem and restore from the backup then rebuild our databases.
All the command you have giving us should work but we just happens to have a bad disk.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.