Why is the user disconnecting SATA #0?
This is an expected behavior since RAID 5 stripes both data and parity information across three or more drives. Drive on SATA 0 keeps Windows files as the rest of the drives.
Thanks for answering.
As we cannot simulate a failure of a drive, we disconnected disk by disk (after rebuild) and rebuild the volume.
The OS crash only when the disk connected to SATA#0 is removed. With SATA#1-2, the screen freezes around 30 seconds during the reconstruction of the parity between others SATA.
Is it an expected behavior? Why is it happen only with the SATA#0?
It might be because drive on SATA 0 keeps Windows files as the rest of the drives.
Yes, it's what I'm assuming.
So I cannot guarantee NO crash OS with a RAID5? If I remove a disk why the OS crash before the reconstruction thanks to the parity?
Do you think with cash size or other RAID Controller configuration I can pass this issue?
Thanks again for your help Allan,
I'm still working on it, I tested with:
- a previous version IRST 11.2 and I did not get the bluescreen but a very long freeze time
- windows 7 PRO (not embedded) 32bits version and everything works fine.
I created a new thread support link bellow:
Thanks for the information. I will take a look at the other thread.