ASROCK P67 EXTREME4 SATA RAID DRIVER DETAILS:
|File Size:||37.3 MB|
|Supported systems:||Windows 7/8/10, Windows XP 64-bit, Mac OS X 10.X|
|Price:||Free* (*Free Registration Required)|
ASROCK P67 EXTREME4 SATA RAID DRIVER
I installed three mobile racks in the chassis.
ASRock P67 Extreme4 - Best Compatible ASRock P67 Extreme4 Mobo
The top one is for the 4TB "original system" drive. The middle one is for a 4TB "resident clone" of the original system drive.
The bottom one is for two additional 4TB "swapped clones" that will be cloned to on alternate days Asrock P67 Extreme4 SATA RAID stored in a waterproof, fireproof data safe when not in use. The "resident clone" will stay in the computer and, in addition to periodically being recloned to, will have data files mirrored to it from the original system drive in close to real time. Or are they dynamically assigned at startup according to some scheme that I haven't been able to determine?
But apart from that lingering doubt, so far, so good. The thing is, you want to test a clone's bootability from time to time, and that's where the puzzle comes in. If we always boot to the original system drive, in the top rack SATA port 0no problem.
We can start the system with all of the drives powered on, and the system will continue to boot from the correct drive time after time. If we try to test a clone's bootability by shutting down, leaving the clone in its original mobile rack, powering off the other drives, and restarting, still no problem for the moment.
ASRock P67 Extreme4 - motherboard - ATX - LGA1155 Socket - P67 Specs
The system will boot to the clone. The problem is, once we've booted from a different drive connected to a different port, the system wants to continue booting from that drive and that port.
It doesn't matter what the UEFI hard drive boot order is or if you manually trigger the boot menu at startup what Asrock P67 Extreme4 SATA RAID port we choose, the system will try to boot from the same drive and port it booted from the previous time. For example, if the resident clone port 1 is left powered on after its bootability is tested, and the original system drive port 0 is powered back on, and the system Asrock P67 Extreme4 SATA RAID started, the system will boot to the clone. And if only the original system drive port 0 is powered on at startup, the system won't find a bootable drive anywhere.
2 raid 기능이 지원되지 않는 windows, 7 / 7 64 비트 / vista, Vista – ASRock P67 Extreme4 Gen3 User Manual
To reset the system after it Asrock P67 Extreme4 SATA RAID on booting from the wrong drive and port, you apparently have to cut mains power to the chassis. Shouldn't the hard drive boot order and manual boot menu actually do something? Is the UEFI immediately handing over boot control to Windows and allowing Windows to decide what drive and port to boot from?
And if so, why bother having a hard drive boot order or Asrock P67 Extreme4 SATA RAID a boot menu? For Linux? And was I supposed to know that? For the time being, there is a relatively easy Asrock P67 Extreme4 SATA RAID for us, only because we have mobile racks: I then imaged the drive. All good so far. Then I plugged my first HDD and restarted and initialized and formatted it and assigned it a drive letter. Then I did the same for my second HDD. I mapped my drives A: DVD C: SSD D: HDD1 E: All good again, I have two data drives, just like it was before I started this thread.
It rebooted as normal. The Intel RST service wasn't running on reboot but that's because Services lists it as a delayed start so I opened it up because I'm impatient. Intel RST recognizes all my drives fine.
ASRock DuraCap ( x longer life time), % Japan made high quality conductive polymer capacitors; Digi P67 Extreme4. 2 x SATA 1 to 1 Power Cables. P67 Extreme4 Gen3 4 x SATA2 Gb/s connectors, support RAID (RAID 0, Asrock P67 Extreme4 SATA RAID 1, RAID 10, RAID 5 and Intel® Rapid 2 x SATA 1 to 1 Power Cables.