![]() ![]() SpinRite will see this and refuse to proceed since it always chooses to do nothing unless it's completely certain of what's going on.Ī "thin" RAID-1 mirroring controller or a high-end RAID controller with on-board caching: Since RAID-0 does not offer the mirroring redundancy of RAID-1, SpinRite's reads and writes are spread out and "striped" between the RAID drives, but there's still a "one for one" relationship between virtual and physical sectors, so SpinRite will be able to operate without requiring the drives to be temporarily removed from the RAID configuration.Īnd, in fact, for SpinRite v6.0, which uses the RAID controller BIOS, RAID-0 drives can not be removed from behind the controller since one of the drives will contain a partition table describing a "virtual drive" that's larger than the actual physical drive. Specifically, one that is not providing its own high-end microprocessor with megs of independent RAID caching RAM memory. By a "thin controller" we mean a controller like an add-on Promise controller, or typical RAID controller built into a motherboard. ![]() SpinRite is able to operate upon drives behind a thin RAID-0 controller configuration without any modification. There are three possible situations with different consequences for SpinRite:Ī "thin" RAID controller in a striping, RAID-0 configuration: Spinrite rocks.there's Spinrite on one hand and everything else on the other. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |