gaqmedic.blogg.se - Diskinternals linux reader raid damaged

I have encountered this problem, (I am almost certain of this), only when re-booting the machine after having booted from a Linux live CD. One thing I have noted, though, (please bear with me, because this is a little complicated):

It's too hard to use a process of elimination, (especially when, as in my case, the fault is intermittent), because I don't have a second MB with the same controller available.

I have no way of determining whether the problem is with the disks themselves, the ICH10R controller, or one (or both) of the SATA channels on the mainboard. In my case, the two offending disks are on SATA #0 and #1, and the cables are marked accordingly, so that I won't connect them in the wrong order.

In my case, this has fixed it every time, and no data has been lost.

Watch RAID info and check whether or not error has gone away, (i.e., the RAID BIOS again sees the array as it was originally set up).

NOTE: "Power down" means shut machine down, and then switch off at the power supply, or the mains outlet. Some weeks later, the same thing happened again, so I decided to try something else. The RAID error was then, and still is, with the "SYSTEM" array the "STORAGE" array has never given Data loss was negligible, as I store everything of The array and re-installed Windows, etc, etc. When I first had this problem about 6 months ago, I had no idea what to do, so I just re-created "STORAGE" is not bootable, and, again, is partitioned as a single "basic" partition, (except that The whole array is partitioned as a single Originally occurred, it contained Win7 Ultimate 圆4.

"SYSTEM" is bootable and contains Windows, now Win8 Pro 圆4, but when the problem 2 x 2TB HDDs, set up as 1 x 4TB RAID0 array. 2 x 1TB HDDs, set up as 1 x 2TB RAID0 array.