RAID migration
Dear freebsd-questions, I have a HighPoint 1820 RAID controller that is using 1 channel for an OS drive and 3 channels for a RAID-5 array. I'm interested in migrating to a new (possibly non-HighPoint) card, and am wondering if I will be able to plug the OS drive into one channel on the new card and have it just work. Is it a safe bet that it will? I'm curious to know if the array could be migrated just as easily, or if I should listen to my instinct and count on bumping into incompatibilities due to proprietary implementations. Here are the relevant dmesg lines of my system as it stands: hptrr: HPT RocketRAID controller driver v1.1 (Jun 7 2008 14:01:57) hptmv0: RocketRAID 182x SATA Controller mem 0xf200-0xf207 irq 24 at device 1.0 on pci2 hptmv0: [GIANT-LOCKED] hptmv0: [ITHREAD] hptrr: no controller detected. da0 at hptmv0 bus 0 target 0 lun 0 da0: Maxtor 6 Y080M0 YAR5 Fixed Direct Access SCSI-0 device da1 at hptmv0 bus 0 target 1 lun 0 da1: RR182x RAID 5 Array 3.00 Fixed Direct Access SCSI-0 device -- Anthony Chavez http://hexadecagram.org/ mailto:[EMAIL PROTECTED]xmpp:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID migration
On Sun, Oct 12, 2008 at 07:10:31PM -0600, Anthony Chavez wrote: Dear freebsd-questions, I have a HighPoint 1820 RAID controller that is using 1 channel for an OS drive and 3 channels for a RAID-5 array. I'm interested in migrating to a new (possibly non-HighPoint) card, and am wondering if I will be able to plug the OS drive into one channel on the new card and have it just work. Is it a safe bet that it will? It probably will work, assuming that the OS disk is not configured as a RAID or array member in the RAID cards' BIOS. Meaning, if you're using the disk on the controller purely in a JBOD fashion, yes, it should work. I'm curious to know if the array could be migrated just as easily, or if I should listen to my instinct and count on bumping into incompatibilities due to proprietary implementations. I can absolutely guarantee you that you will lose access to all of your data once you plug those 3 disks into another controller. You need to back up all of your data from the RAID-5 array using something like rsync, cpdup, or dump, move the disks over to the non-RAID controller, format them (in whatever fashion you want), and then restore the backup. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID migration
Jeremy Chadwick wrote: On Sun, Oct 12, 2008 at 07:10:31PM -0600, Anthony Chavez wrote: Dear freebsd-questions, I have a HighPoint 1820 RAID controller that is using 1 channel for an OS drive and 3 channels for a RAID-5 array. I'm interested in migrating to a new (possibly non-HighPoint) card, and am wondering if I will be able to plug the OS drive into one channel on the new card and have it just work. Is it a safe bet that it will? It probably will work, assuming that the OS disk is not configured as a RAID or array member in the RAID cards' BIOS. Meaning, if you're using the disk on the controller purely in a JBOD fashion, yes, it should work. In the WebGUI's logical device information section, that particular drive is listed as a hard disk whereas the other 3 are clearly spelled out as a RAID 5 array. When I shut the machine down, I will check the BIOS itself to see if it specifically states JBOD. Thanks for the pointer. Regardless, I will be backing it up before I attempt to plug it into a new RAID controller. I'm curious to know if the array could be migrated just as easily, or if I should listen to my instinct and count on bumping into incompatibilities due to proprietary implementations. I can absolutely guarantee you that you will lose access to all of your data once you plug those 3 disks into another controller. You need to back up all of your data from the RAID-5 array using something like rsync, cpdup, or dump, move the disks over to the non-RAID controller, format them (in whatever fashion you want), and then restore the backup. Exactly what I planned to do, but figured I'd ask anyhow. ;-) Thank you for responding. -- Anthony Chavez http://hexadecagram.org/ mailto:[EMAIL PROTECTED]xmpp:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID migration
On Sun, Oct 12, 2008 at 10:27:47PM -0600, Anthony Chavez wrote: Jeremy Chadwick wrote: On Sun, Oct 12, 2008 at 07:10:31PM -0600, Anthony Chavez wrote: Dear freebsd-questions, I have a HighPoint 1820 RAID controller that is using 1 channel for an OS drive and 3 channels for a RAID-5 array. I'm interested in migrating to a new (possibly non-HighPoint) card, and am wondering if I will be able to plug the OS drive into one channel on the new card and have it just work. Is it a safe bet that it will? It probably will work, assuming that the OS disk is not configured as a RAID or array member in the RAID cards' BIOS. Meaning, if you're using the disk on the controller purely in a JBOD fashion, yes, it should work. In the WebGUI's logical device information section, that particular drive is listed as a hard disk whereas the other 3 are clearly spelled out as a RAID 5 array. When I shut the machine down, I will check the BIOS itself to see if it specifically states JBOD. Thanks for the pointer. It probably won't. JBOD is just a term used to describe a hard disk hooked to a RAID controller but not part of a RAID array. I'd start by pulling the OS disk out and hooking it to a non-Highpoint controller and ensure it boots. Chances are it will. Some advice, assuming you haven't done this before: 1) Make note of what your filesystem layout is before migrating. df output should be sufficient. 2) When you boot it, FreeBSD will probably complain unable to determine root filesystem. I'm guessing these are ATA/SATA disks. The kernel messages shown should list off what ATA disks are attached, and you'll have to make some educated guesses as to what it is, e.g. ufs:ad4s1a rather than the old ufs:da0s1a. You'll have to mount all the filesystems by hand (mount /dev/ad4s1d /var, etc. -- this is what #1 was for :-) ) so you can get access to vi, so you can vi /etc/fstab and fix the problem. You can also use ed(1) to do the fstab editing without having to mount everything, if you're familiar with it. Hope this helps. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
