| 1 |
On 04/02/10 09:47, walt wrote: |
| 2 |
>On 04/02/2010 08:46 AM, Joseph wrote: |
| 3 |
>>On 04/02/10 09:42, Neil Bothwick wrote: |
| 4 |
>>>On Thu, 01 Apr 2010 19:47:09 -0700, walt wrote: |
| 5 |
>>> |
| 6 |
>>>>However, if you want to leave both cables connected and change your |
| 7 |
>>>>BIOS to boot from 'sdb', you will need to edit some of the files on |
| 8 |
>>>>'sdb', |
| 9 |
>>> |
| 10 |
>>>Check your BIOS first, some allow you to disable individual SATA ports, |
| 11 |
>>>so you can disconnect the drive without pulling cables. |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>>>-- |
| 15 |
>>>Neil Bothwick |
| 16 |
>> |
| 17 |
>>Good suggestion, but I'm not sure my motherboard BIOS supports it. |
| 18 |
>>I have GA-MA790GP-DS4H motherboard, reading from the manual: |
| 19 |
>> |
| 20 |
>>it has OnChip SATA Type (SATA2_0 ~ SATA2_3 connectors) |
| 21 |
>>Mode: Native IDE |
| 22 |
>>RAID |
| 23 |
>>AHCI - Advanced Host Controller to enable advanced Serial ATA features such as Native Command Queuing and hot plug. |
| 24 |
>> |
| 25 |
>>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. |
| 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 second drive, and it will be "sdb" (hd1); but during normal operation, when running from "sda" I want |
| 28 |
>>to backup some application files to it so "sdb" stays current. |
| 29 |
> |
| 30 |
>Ah, well, having only remote access rules out unplugging cables or changing |
| 31 |
>BIOS settings unless there is someone at the site who can do those things. |
| 32 |
> |
| 33 |
>Seems like you would be better off to set up grub on sda so it can boot from |
| 34 |
>sda by default, but also so a remote user can just choose sdb from grub's menu. |
| 35 |
>That assumes that sda is physically intact enough to load grub from sda. You |
| 36 |
>seem to be more worried about software screwups than hardware failure. But |
| 37 |
>you will need to edit the handful of config files on sdb so all the right |
| 38 |
>filesystems will mount correctly. |
| 39 |
|
| 40 |
As I've mentioned earlier I have enough backups on another system, so I'm not much worry about hardware failure. |
| 41 |
From my years of experience with Gentoo, I'm more worry about things working correctly after emerge :-/ |
| 42 |
I've made list what I need to do, but I'm not sure if this is all: |
| 43 |
|
| 44 |
1.) Boot from external CD |
| 45 |
dd if=/dev/sda of=/dev/sdb |
| 46 |
|
| 47 |
2.) |
| 48 |
modify (add to) grub.conf on sda |
| 49 |
#title boot sda current |
| 50 |
title=1st HD sda Kernel Current |
| 51 |
root (hd0,0) |
| 52 |
kernel /boot/kernel-current root=/dev/sda3 |
| 53 |
|
| 54 |
#title boot sdb current |
| 55 |
title=2nd HD sdb Kernel Current |
| 56 |
root (hd1,0) |
| 57 |
kernel /boot/kernel-current root=/dev/sdb3 |
| 58 |
|
| 59 |
3.) Modify fstab |
| 60 |
|
| 61 |
You have mentioned to use "rdev" but reading man pages it is only i386, and all my boxes running amd64 (x86_64). |
| 62 |
|
| 63 |
-- |
| 64 |
Joseph |
Archives