Dynamic Disk online (errors)
I am running a Windows 2003 server environment with 2 Seagate Disks (SCSI) that are mirrored. However, the server has failed and I think it may be a problem with one of the disks. The o/s would not load and just kept going round in an eternal loop. I have added a third disk and changed the SCSI id and loaded Windows 2003 on the new disc in order that the server will boot up and i can then see the status of the original two disks. When I go into Computer Manager I can see that the original two disks (now disk1 and disk 2) were dynamic and mirriored but have a status of failed redundancy. Disk 1 is online (errors) while Disk 2 is online. I have ran a diagnostic test on each of the disks using a Seagate Dianostic tool - coming back with no problems. Question:
1. Can i use any other tools to check these disks?
2. Can i "reactivate" the dynamic disks and then remove Disk0 to see will the system boot using the original two disks?
1. Can i use any other tools to check these disks?
2. Can i "reactivate" the dynamic disks and then remove Disk0 to see will the system boot using the original two disks?
To answer:
1. Can i use any other tools to check these disks?
This will fix any magnetic errors & save you wiping the disc.
hdd regenerator
http://www.dposoft.net/
1. Can i use any other tools to check these disks?
This will fix any magnetic errors & save you wiping the disc.
hdd regenerator
http://www.dposoft.net/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
From within Windows Explorer I can view the contents of the E drive - that was the shared drive. When you mention "data recovery" do you mean within the Recovery Console to repair windows or do you mean recovering all data from the latest backup?
You have no way of knowing what files are damaged. A full recovery is only way of insuring you have no corruption. Then what you can do is manually compare files and last modification times for what was written since the last recovery, and restore those files if you know they have not been modified.
The recovery console will get it to boot, but since you do not know what files, if any, might be corrupted, so best to restore to a known config .. unless you don't mind knowing whether or not you have corrupted files, and losing the data forever as your backups eventually write over the older copies before this all happened.
The recovery console will get it to boot, but since you do not know what files, if any, might be corrupted, so best to restore to a known config .. unless you don't mind knowing whether or not you have corrupted files, and losing the data forever as your backups eventually write over the older copies before this all happened.
Also, when you "view the contents of the drive", you are just looking at a few MB worth of directory entries. You aren't in any way even seeing if the files actually exist, let alone contain the data that they are supposed to contain.
otherwise, wipe the one with errors, it should be reimaged automatic when connected