From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NxlC0-0006HM-JW for garchives@archives.gentoo.org; Fri, 02 Apr 2010 18:02:08 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4ADDCE08D1; Fri, 2 Apr 2010 18:01:08 +0000 (UTC) Received: from mail.shawcable.com (shawmail.shawcable.com [64.59.128.220]) by pigeon.gentoo.org (Postfix) with ESMTP id 1E965E08D1 for ; Fri, 2 Apr 2010 18:01:08 +0000 (UTC) Received: from bpd2mi5no-svcs.prod.shawcable.com ([10.0.184.160]) by bpd2mo2no-ssvc.prod.shawcable.com with ESMTP; 02 Apr 2010 12:01:07 -0600 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=1 a=5tK76u9szHkA:10 a=VphdPIyG4kEA:10 a=8nJEP1OIZ-IA:10 a=dgx804EzjhD8CRYpIFkhZA==:17 a=R-ewKwHxqYZM8j7BB2IA:9 a=HZtarvguSHdp5eVOGMYA:7 a=Ja94TW9Q38a4uT49WvsYuVDMcUYA:4 a=wPNLvfGTeEIA:10 X-IronPort-AV: E=Sophos;i="4.51,354,1267426800"; d="scan'208";a="140162894" Received: from unknown (HELO bpd2mi5no-cmts.prod.shawcable.com) ([192.168.183.160]) by bpd2mi5no-cmts.prod.shawcable.com with ESMTP; 02 Apr 2010 12:01:07 -0600 X-reinject: true Received: from unknown (HELO syscon4.localdomain) ([68.148.245.78]) by bpd2mi5no-dmz.prod.shawcable.com with ESMTP; 02 Apr 2010 12:01:07 -0600 Received: by syscon4.localdomain (Postfix, from userid 1000) id A2160C4265; Fri, 2 Apr 2010 12:01:01 -0600 (MDT) Date: Fri, 2 Apr 2010 12:01:01 -0600 From: Joseph To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Duplicate identical Hard Disk Message-ID: <20100402180101.GG5637@syscon4.inet> References: <20100401224820.GA5637@syscon4.inet> <20100402014000.GD5637@syscon4.inet> <20100402094250.42983e9b@digimed.co.uk> <20100402154620.GE5637@syscon4.inet> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: 2d8aa290-4cfd-4ca2-8b28-23937641e4b3 X-Archives-Hash: 96fd4e184dc4c94006bbec21251784df On 04/02/10 09:47, walt wrote: >On 04/02/2010 08:46 AM, Joseph wrote: >>On 04/02/10 09:42, Neil Bothwick wrote: >>>On Thu, 01 Apr 2010 19:47:09 -0700, walt wrote: >>> >>>>However, if you want to leave both cables connected and change your >>>>BIOS to boot from 'sdb', you will need to edit some of the files on >>>>'sdb', >>> >>>Check your BIOS first, some allow you to disable individual SATA ports, >>>so you can disconnect the drive without pulling cables. >>> >>> >>>-- >>>Neil Bothwick >> >>Good suggestion, but I'm not sure my motherboard BIOS supports it. >>I have GA-MA790GP-DS4H motherboard, reading from the manual: >> >>it has OnChip SATA Type (SATA2_0 ~ SATA2_3 connectors) >>Mode: Native IDE >>RAID >>AHCI - Advanced Host Controller to enable advanced Serial ATA features such as Native Command Queuing and hot plug. >> >>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. >> >>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 >>to backup some application files to it so "sdb" stays current. > >Ah, well, having only remote access rules out unplugging cables or changing >BIOS settings unless there is someone at the site who can do those things. > >Seems like you would be better off to set up grub on sda so it can boot from >sda by default, but also so a remote user can just choose sdb from grub's menu. >That assumes that sda is physically intact enough to load grub from sda. You >seem to be more worried about software screwups than hardware failure. But >you will need to edit the handful of config files on sdb so all the right >filesystems will mount correctly. As I've mentioned earlier I have enough backups on another system, so I'm not much worry about hardware failure. From my years of experience with Gentoo, I'm more worry about things working correctly after emerge :-/ I've made list what I need to do, but I'm not sure if this is all: 1.) Boot from external CD dd if=/dev/sda of=/dev/sdb 2.) modify (add to) grub.conf on sda #title boot sda current title=1st HD sda Kernel Current root (hd0,0) kernel /boot/kernel-current root=/dev/sda3 #title boot sdb current title=2nd HD sdb Kernel Current root (hd1,0) kernel /boot/kernel-current root=/dev/sdb3 3.) Modify fstab You have mentioned to use "rdev" but reading man pages it is only i386, and all my boxes running amd64 (x86_64). -- Joseph