1 |
On 04/02/2010 08:46 AM, Joseph wrote: |
2 |
> On 04/02/10 09:42, Neil Bothwick wrote: |
3 |
>> On Thu, 01 Apr 2010 19:47:09 -0700, walt wrote: |
4 |
>> |
5 |
>>> However, if you want to leave both cables connected and change your |
6 |
>>> BIOS to boot from 'sdb', you will need to edit some of the files on |
7 |
>>> 'sdb', |
8 |
>> |
9 |
>> Check your BIOS first, some allow you to disable individual SATA ports, |
10 |
>> so you can disconnect the drive without pulling cables. |
11 |
>> |
12 |
>> |
13 |
>> -- |
14 |
>> Neil Bothwick |
15 |
> |
16 |
> Good suggestion, but I'm not sure my motherboard BIOS supports it. |
17 |
> I have GA-MA790GP-DS4H motherboard, reading from the manual: |
18 |
> |
19 |
> it has OnChip SATA Type (SATA2_0 ~ SATA2_3 connectors) |
20 |
> Mode: Native IDE |
21 |
> RAID |
22 |
> AHCI - Advanced Host Controller to enable advanced Serial ATA features such as Native Command Queuing and hot plug. |
23 |
> |
24 |
> Is it the one AHCI? I've never used it. 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 an ssh access to it. |
25 |
> |
26 |
> 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 second drive, and it will be "sdb" (hd1); but during normal operation, when running from "sda" I want |
27 |
> to backup some application files to it so "sdb" stays current. |
28 |
|
29 |
Ah, well, having only remote access rules out unplugging cables or changing |
30 |
BIOS settings unless there is someone at the site who can do those things. |
31 |
|
32 |
Seems like you would be better off to set up grub on sda so it can boot from |
33 |
sda by default, but also so a remote user can just choose sdb from grub's menu. |
34 |
That assumes that sda is physically intact enough to load grub from sda. You |
35 |
seem to be more worried about software screwups than hardware failure. But |
36 |
you will need to edit the handful of config files on sdb so all the right |
37 |
filesystems will mount correctly. |