- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Boot MirrorDisk Fails
Disk Enclosures
1752790
Members
5923
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
тАО07-29-2003 09:54 PM
тАО07-29-2003 09:54 PM
Boot MirrorDisk Fails
Just wanted to confirm that what would be the procedure when one of the system mirror disk fail(from which system has booted) and we do not have a spare one at the moment.the buddy mirror disk takes over the system and system is working.But when we go to check the disk via ioscan or go for swap info it just keep looking for these things. i wanted to know whether we will have to run any command or procedure so that system just keep working accordingly till we have the spare disk to replace it with the failed mirror disk.similarly if we reboot the system with the one mirror system disk failed the system boots properly and shows everthing according i.e. the result of the ioscan and swapinfo command.we have 2 swap partitions on the system disk and are mirrored.
So the real question is whether i will have to run any command to stabilize the system to keep functioning without rebooting in case when one mirror disk fail from which system was booted up.
So the real question is whether i will have to run any command to stabilize the system to keep functioning without rebooting in case when one mirror disk fail from which system was booted up.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2003 11:25 PM
тАО07-29-2003 11:25 PM
Re: Boot MirrorDisk Fails
The system will run fine as long as the secondary disk does not fail. If a primary disk fails it automatically goes to the secondary. That's how mirrorDisk/UX works. If you attempt to reboot you will encounter a problem as the system will attempt to boot from your primary disk. You would need to change the primary boot disk. You can have a look at the 'setboot' from which I cam sure you can it to the secondary disk. The man page will explain it. In answer to your question, the system will run fine, and there is no need to reboot. Most of the internal disks are hot swappable these days. If it is an older model you may have to shutdown.
Anyone for a Mutiny ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2003 10:33 AM
тАО07-31-2003 10:33 AM
Re: Boot MirrorDisk Fails
Assume the original drive is C: and the mirror is on the drive the system sees as D:, to simplify the question. You must create a boot floppy , formatted unde NT, and put the boot files (boot.ini, ntdetect.com, ntldr) on this disk. Next you must go in and modify the boot.ini file on the floppy so that it points to the second drive in the mirror (D: in the example) so the system will boot to the second half of the mirror. This is boot disk only needed to boot when the primary drive fails, but is also a useful tool to verify that the second drive is still good.
If I read your question right, you have a bad drive, but can still boot, so the primary drive appears to be functioning correctly, and the problem must be with the mirror drive. Assuming this is correct, you might want to try breaking the mirror, wiping the bad part of the mirror drive, and then re-create the mirror and see if that solves the problem. I have had mirror drives get "out of sync" so to speak, which causes the mirror to show up as bad, and this has cured the issue. In any event, make sure you correctly identify which drive the problem is on before you break the mirror, and create the boot disk AND TEST IT OUT before you do anything to the mirror. Also a very good idea to have a COMPLETE backup of the drive before you do anything, just in case you make a mistake. :)
HTH
David
If I read your question right, you have a bad drive, but can still boot, so the primary drive appears to be functioning correctly, and the problem must be with the mirror drive. Assuming this is correct, you might want to try breaking the mirror, wiping the bad part of the mirror drive, and then re-create the mirror and see if that solves the problem. I have had mirror drives get "out of sync" so to speak, which causes the mirror to show up as bad, and this has cured the issue. In any event, make sure you correctly identify which drive the problem is on before you break the mirror, and create the boot disk AND TEST IT OUT before you do anything to the mirror. Also a very good idea to have a COMPLETE backup of the drive before you do anything, just in case you make a mistake. :)
HTH
David
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