Shahmatt
Master Member
- Joined
- Oct 2, 2006
- Messages
- 2,532
- Reaction score
- 48
Hello. I have a question regarding Intel RST and RAID 1 configs and would appreciate any help.
I purchased two new Western Digital Red 1TB HDDs with intent to configure as RAID 1 on my system. Also on my system are a 250GB Seagate Windows 7 drive which is accelerated using a Crucial M4 64GB SSD, and also a Samsung 1TB general storage drive.
I set up RAID 1, but suffered intermittent CPU slowdowns. An internet search told me that this could be an Intel RST driver issue. I deleted the RAID 1 volume and my system came back to normal again.
I then had two HDDs. On disk management one was visible. The second disk was offline due to Disk signature collision.
I read that this was because the disk signature had not been updated in Windows MBR, but I left it alone since I anyway wanted to redo the RAID 1 with an updated Intel RST.
I switched the disk "Online" and redid RAID 1. I was very careful to select the two WD HDDs at this point and I elected to preserve some of my previously backed up data in one of the WD HDs. It wasn't important I kept this data since my Samsung 1TB storage HD worked fine but I thought it would be a good experiment.
It took a few hours to redo the RAID 1. I restarted my computer and Windows would not boot due to the WD HD signature problem. I disconnected the WD and Windows started. However now my Samsung 1TB was not visible. In Disk Manager it said that this HD was not "initialized". In Intel RST for some reason the Samsung HD paired along with the two other WD HD's in RAID 1!!!!!!!!!!!!!!!!!!! How did this happen?????
I checked online and found out that initializing would wipe out the partitions and hence my data would become inaccessible.
I downloaded testdisk and photorec but neither was able to see the partitions/recover any data from the Samsung. Photorec kept saying "Error reading sector".
It seems that the RAID 1 has somehow been done with both the Samsung and two WDs, and in the process only one WD (data backed up earlier) has been retained. As mentioned earlier I was very careful to select the right two HDs. When you hover the mouse over the HD in Intel RST it tells you what HD brand it is. The Western Digital HDs had "WD" in front.
Anyway, before proceeding further I am transferring all the remaining data into external drives for safe keeping. Some data still remained in the Samsung but maybe not too important. Ideally I would like to retrieve the stuff that is inside.
My Samsung HD is not visible anymore on disk manager or diskpart. It is still present though as a 0GB drive in Intel RST.
The one WD HD with my data on it still remains alive until I transfer everything out. The second WD HD is offline due to the Disk signature collision.
I am pondering what to do next. Should I delete the RAID 1. Will this delete all of the stuff in the Samsung HD? Should I proceed to (now belatedly) fix the second WD HD? Why did Intel RST RAID 1 with my existing drive? I don't know but I am really mad about this.
Any advice is appreciated. In summary, the history of events as follows:
1. Set up RAID 1 with two new WD RED HDs.
2. RAID 1 set up successfully. Did some backup of essential data.
3. Intermittent slowdowns experienced, RAID 1 volume suspected and proved to be the cause.
4. Deleted RAID 1. One WD HD offline - Disk Signature Collision. Switched disk to "Online" and re-set up RAID 1 with newly downloaded Intel RST. Did not fix Disk signature collision (BIG MISTAKE!).
5. Restarted computer. Second WD still offline (RAID 1 did not fix it). Original Samsung HD also showing as needing "initialization" despite not being involved when setting up RAID 1. Intel RST shows three HDs as part of RAID 1.
6. Disconnected WDs with intent to save Samsung HD using testdisk and photorec - no luck.
7. Reconnected WDs and restarted. Samsung HD seems completely dead to Disk manager and diskpart. Intel RST shows it as 0GB. Only data remaining is what was backed up in WD1 in item 2. WD2 still showing disk signature collision error and offline.
Sorry for the long problem. Any help is appreciated.
I purchased two new Western Digital Red 1TB HDDs with intent to configure as RAID 1 on my system. Also on my system are a 250GB Seagate Windows 7 drive which is accelerated using a Crucial M4 64GB SSD, and also a Samsung 1TB general storage drive.
I set up RAID 1, but suffered intermittent CPU slowdowns. An internet search told me that this could be an Intel RST driver issue. I deleted the RAID 1 volume and my system came back to normal again.
I then had two HDDs. On disk management one was visible. The second disk was offline due to Disk signature collision.
I read that this was because the disk signature had not been updated in Windows MBR, but I left it alone since I anyway wanted to redo the RAID 1 with an updated Intel RST.
I switched the disk "Online" and redid RAID 1. I was very careful to select the two WD HDDs at this point and I elected to preserve some of my previously backed up data in one of the WD HDs. It wasn't important I kept this data since my Samsung 1TB storage HD worked fine but I thought it would be a good experiment.
It took a few hours to redo the RAID 1. I restarted my computer and Windows would not boot due to the WD HD signature problem. I disconnected the WD and Windows started. However now my Samsung 1TB was not visible. In Disk Manager it said that this HD was not "initialized". In Intel RST for some reason the Samsung HD paired along with the two other WD HD's in RAID 1!!!!!!!!!!!!!!!!!!! How did this happen?????
I checked online and found out that initializing would wipe out the partitions and hence my data would become inaccessible.
I downloaded testdisk and photorec but neither was able to see the partitions/recover any data from the Samsung. Photorec kept saying "Error reading sector".
It seems that the RAID 1 has somehow been done with both the Samsung and two WDs, and in the process only one WD (data backed up earlier) has been retained. As mentioned earlier I was very careful to select the right two HDs. When you hover the mouse over the HD in Intel RST it tells you what HD brand it is. The Western Digital HDs had "WD" in front.
Anyway, before proceeding further I am transferring all the remaining data into external drives for safe keeping. Some data still remained in the Samsung but maybe not too important. Ideally I would like to retrieve the stuff that is inside.
My Samsung HD is not visible anymore on disk manager or diskpart. It is still present though as a 0GB drive in Intel RST.
The one WD HD with my data on it still remains alive until I transfer everything out. The second WD HD is offline due to the Disk signature collision.
I am pondering what to do next. Should I delete the RAID 1. Will this delete all of the stuff in the Samsung HD? Should I proceed to (now belatedly) fix the second WD HD? Why did Intel RST RAID 1 with my existing drive? I don't know but I am really mad about this.
Any advice is appreciated. In summary, the history of events as follows:
1. Set up RAID 1 with two new WD RED HDs.
2. RAID 1 set up successfully. Did some backup of essential data.
3. Intermittent slowdowns experienced, RAID 1 volume suspected and proved to be the cause.
4. Deleted RAID 1. One WD HD offline - Disk Signature Collision. Switched disk to "Online" and re-set up RAID 1 with newly downloaded Intel RST. Did not fix Disk signature collision (BIG MISTAKE!).
5. Restarted computer. Second WD still offline (RAID 1 did not fix it). Original Samsung HD also showing as needing "initialization" despite not being involved when setting up RAID 1. Intel RST shows three HDs as part of RAID 1.
6. Disconnected WDs with intent to save Samsung HD using testdisk and photorec - no luck.
7. Reconnected WDs and restarted. Samsung HD seems completely dead to Disk manager and diskpart. Intel RST shows it as 0GB. Only data remaining is what was backed up in WD1 in item 2. WD2 still showing disk signature collision error and offline.
Sorry for the long problem. Any help is appreciated.
