Re: Recover data from mirrored set after motherboard goes down
- From: "SimonDMZ" <SimonDMZ@xxxxxxx>
- Date: 28 Oct 2005 11:20:18 -0700
Thanks Joep. I was sure the server supported 48bit LBA at the BIOS
level, and I was running W2K SP4, so it had to be something else.
I found the clues in XP Reskits online:-
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prkb_cnc_klvo.asp
After all, it was down to my paranoia I am afraid, not wanting to
corrupt the data. However, after reading "Do not import mirrored or
RAID-5 volumes into computers running Windows XP Professional or
Windows 2000 Professional. Because these operating systems do not
support mirrored or RAID-5 volumes, you cannot access data on these
volumes after the import. You must move the volume back to a computer
running Windows 2000 Server to access the volume". So I felt confident
that it was possible to get these drives up and running. So I connected
BOTH drives and bit the bullet and imported the first "foreign disks"
and it said "mirrored set 2 of 2" with "data not redundant" in the
Condition box on pressing Disk button. Said the same for the other
disk. So I held my breath and clicked OK and it imported both disks.
Then it went and synced the second disk to the first and after about
four hours (250GB) they came up healthy. Needed to allocate a drive
letter and then could read the data.
Thanks for your help. Glad to have that diydatarecovery link too!
.
- References:
- Prev by Date: Re: Recover data from mirrored set after motherboard goes down
- Next by Date: Re: What is the Usn Journal
- Previous by thread: Re: Recover data from mirrored set after motherboard goes down
- Next by thread: What is the Usn Journal
- Index(es):
Loading