Re: Migrating to a RAID 1 setup (hardware RAID)

Thanks for the response. Your solution is close to the answer on
linuxquestions.org.

I don't have an identical drive handy unfortunately, but drives are
cheap so I'll pick up a couple.

---
I don't know anything about 3ware RAID cards, but the first thing you
need to do is make sure the linux kernel supports them.

1 - Check for support. If supported continue...
2 - Recompile kernel with support for your card
3 - Configure your boot loader to add the new kernel so you can boot it
(take care NOT to wipe out your existing kernel!!)
4 - Power off system. Install card. Hookup your existing drive to it.
5 - Turn on system. Boot new kernel. If all goes well it should boot
fine. If you recieve a kernel panic it will most likely be due to the
hard drive device name changing (because of the RAID card) and your
/etc/fstab will need to be edited. If this is the case you will need to
boot from your distros cd, mount your root fs and edit the fstab to
reflect the device name change. Reboot once again.

Once you can succesfully boot the new kernel with the ONE drive hooked
up to the card:

- Shutdown system. Power off.
- Hook up second drive to RAID card.
- Turn on system. Press whatever key combo it is to enter your cards
config utility. Follow instructions to mirror one drive to another.
Basically mirror your existing drive to the new drive. You SHOULD be
using exact same drives btw!
- Some RAID utilities will allow the system to mirror while you
continue to work. Others don't. The process could take a while.
- When it's done you now have a working hardware RAID setup.

--

.

Relevant Pages

  • athlon-xp + fakeraid regression
    ... The build completes fine, the kernel boots fine, the machine will seem to be fine as long as it remains quiescent. ... At the beginning, just after hitting enter on the make command, one of the ad4 disk light goes on solid for several seconds. ... There is a well known thing where these cheap pata fakeraid cards will try to do ata133 if the drive says it can, when really, even if he drives are new ata133 drives and the cables are new and short and shielded, you still shouldn't try to do ata133 since the spec is too tight and you'll just get bit errors or other failures. ... The fix is use ata100 somehow, either by disabling dma entirely in loader.conf (since you have no more selective option there, and the raid card bios never has an option for controlling pio/dma mode like motherboard bios's have) and then use atacontrol in rc.early to set udma5, or by using disks that can only do ata100 and only advertise ata100 to the controller. ...
    (freebsd-current)
  • Re: libata: ide-drive mounted as sda : how to deal with 32-bit/multisector?
    ... the new card is a pci-card which is a raid card, but also works as "normal" ide card in socalled "pass-through"-mode. ... With kernel 2.6.17 or 2.6.15 the drive attached to the card is recognized as hde and the module in question ist it821x. ... I stepped on the problem when trying to activate multisec-support on the drive which I experienced as performace-improvment on other drives on other servers. ...
    (comp.os.linux.misc)
  • RE: Upgrading to 6.2-RELEASE from 6.2-STABLE
    ... Manually load my old kernel from the prompt worked. ... I believe the mountroot is during the boot load. ... support for IDE drives. ... unknown option "MD5" ...
    (freebsd-questions)
  • Re: pata_sil680 regression 2.6.22->2.6.24
    ... Having recently upgaded my Ubuntu install from Gutsy to Hardy, ... Seagate disk connected via a SiI680 PCI card is no longer detected. ... I'm not sure if the kernel config has changed as I ... Note, my bios does not support 750GB drives, so the drive is not ...
    (Linux-Kernel)
  • Re: 2.6.30 (Squeeze): no hda1 no sda1
    ... I'm runny Debian Testing (Squeeze) and have been for years. ... old kernel of course) and rebooted. ... Boot your 2.6.26 kernel and try changing your fstab to use the UUID or ... I have noticed changes to older drives in particular. ...
    (Debian-User)