Re: Reinstall or restore with different disk config
- From: aus <aus@xxxxxxx>
- Date: Tue, 10 May 2005 04:14:02 +0100
HI, I use a Dell with the RAID 1 on th eonboard and it seems quite healthy but I have never done the pull the disk out test yet (I have faith!).
One thing to do maybe is to disable write caching on the drives (see in properties of the drive itself in Windows) you may or may not have this option depending on driver.
The boot.ini change relates to the fat that the path specifies a drive and partition to boot from - if the drive specified is off-line then the boot.ini path is invalid so you need to add a redundant entry pointing to the second mirror drive to start from. Thats the idea!
You are better off with hardware (non Windows) mirroring - hardware is faster and the Windows re-synchronising is crippling if the disks get out of sync - it took 6 hours (during work time) following a server crash on one system I use. The system does run but the disk i/o is so high that responsiveness really suffers. I used to always use Windows mirroring but I find it uses too much i/o time with the size of data that typical users now get up to. It does work though - switching to the second drive always worked for me with Windows software mirroring.
C_O wrote:
"Marshall Lai" <marshall_lai@xxxxxxxxx> wrote in message news:O2qt%23WKVFHA.2768@xxxxxxxxxxxxxxxxxxxxxxx
I doubt that you can mirror a system drive using the Windows SBS RAID.
I did indeed get a bizarre warning about boot.ini after this reinstall, when activating the mirror for drive C using the Windows disk management. I have not been able to find a good explanation of what I should do to boot.ini to fix that, if anything. It is particularly bizarre because the first time I installed SBS that is the way I had it set up and I did not get the warning. I then thought that it would be more clever to use the onboard SATA RAID, and reinstalled SBS after enabling the RAID in BIOS. But then I saw DMIO and HD not ready errors during the Exchange startup sequence. After shutting down the onboard SATA RAID and reinstalling with the Windows mirror, the DMIO and HD not ready errors have gone away.
Still to do: Try the hardware test: deliberate failure of the primary disk to see if the mirror works as advertised.
-- C_O
.
- References:
- Reinstall or restore with different disk config
- From: C_O
- RE: Reinstall or restore with different disk config
- From: Douglas Boyd [MSFT]
- Re: Reinstall or restore with different disk config
- From: C_O
- Re: Reinstall or restore with different disk config
- From: Marshall Lai
- Re: Reinstall or restore with different disk config
- From: C_O
- Reinstall or restore with different disk config
- Prev by Date: SBS 2K3 and NT4 clients
- Next by Date: Backup Errors and a new USB Drive
- Previous by thread: Re: Reinstall or restore with different disk config
- Next by thread: Re: Multiple DNS errors each day
- Index(es):
Relevant Pages
|
|
