| 1 |
On 04/02/10 09:42, Neil Bothwick wrote: |
| 2 |
>On Thu, 01 Apr 2010 19:47:09 -0700, walt wrote: |
| 3 |
> |
| 4 |
>> However, if you want to leave both cables connected and change your |
| 5 |
>> BIOS to boot from 'sdb', you will need to edit some of the files on |
| 6 |
>> 'sdb', |
| 7 |
> |
| 8 |
>Check your BIOS first, some allow you to disable individual SATA ports, |
| 9 |
>so you can disconnect the drive without pulling cables. |
| 10 |
> |
| 11 |
> |
| 12 |
>-- |
| 13 |
>Neil Bothwick |
| 14 |
|
| 15 |
Good suggestion, but I'm not sure my motherboard BIOS supports it. |
| 16 |
I have GA-MA790GP-DS4H motherboard, reading from the manual: |
| 17 |
|
| 18 |
it has OnChip SATA Type (SATA2_0 ~ SATA2_3 connectors) |
| 19 |
Mode: Native IDE |
| 20 |
RAID |
| 21 |
AHCI - Advanced Host Controller to enable advanced Serial ATA features such as Native Command Queuing and hot plug. |
| 22 |
|
| 23 |
Is it the one AHCI? I've never used it. |
| 24 |
I'm more interested in configuring it as an auxiliary drive "sdb" to serve as a bootable backup. The box will be installed in a remote location and I'll have |
| 25 |
an ssh access to it. |
| 26 |
|
| 27 |
The box is running in a medical clinic and I'm mostly concern that after the emerge if something happens, I want the user to be able to boot "grub" from |
| 28 |
second drive, and it will be "sdb" (hd1); but during normal operation, when running from "sda" I want to backup some application files to it so "sdb" stays |
| 29 |
current. |
| 30 |
|
| 31 |
-- |
| 32 |
Joseph |
Archives