Hi ! I'm still out of lack moving software RAID L1 to another server. Despite adding kernel modules to initial RAM disk (required by 2nd server m/b), system doesn't boots successfully -- failed to get Error Log Address Range Devices listed in fstab options by Device ID, connected to the same # of SATA ports, so bootloader / fstab should be OK. Anyone have any idea what to do next? Thanks. On Dec 13, 2012, at 4:22 PM, Anton Aylward wrote:
andreil1 said the following on 12/13/2012 08:50 AM:
Hi, folks !
I was requested to move software SATA RAID 0 (no LVM) from one OpenSUSE server to another. Both are Intel based but 2nd is much more beefy.
I've done this a number of times with a number of distributions. It seems scary but I must admit I've become blaze abut it after having little trouble.
In every case I just moved the disk and rebooted.
I have checked which kernel modules are required for server #2 and loaded into initial ramdisk.
I never did that. Kernel modules get dynamically loaded. Well, OK, I use LVM and I'd already mkinitrd for that, but you say you're not using LVM. If your initrd deals with all your file systems then the kernel modules become an issue for modprobe.
Apart from adding kernel modules to initrd, what else should be checked in order to load system on PC #2? /etc/fstab entries / mount points options?
Was never a problem for me. I swapped the whole drive so all that went over as complete package.
What would be the best options for /etc/fstab/ entries (taking into account software RAID 0 config): UUID, Device ID, Device path ?
For myself, as I say, swapping drives, so as to get more CPU power, none of this was ever a concern. As I use LVM, many other things about upgrading drives become a 'not a problem'. As with backups, file system growth and much more.
The thing is to do it all in small steps. Each step is the minimum amount of change and easily reversible. TEST! TEST!! TEST!!!
Anything else to be taken into consideration (apart from re-assgning network cards)?
Maybe not even that !! My servers have fixed addresses so I never had to fiddle with DHCP reassignment.
This is working server, used for web / mail / calendaring / IP telephony for 5 offices simultaneously, so I had to be very quick even if move will be performed on holidays.
Mine were (are) too. They are due for another "upgrade", either new hardware or more memory. It will, again, be a disk swap, and I don't foresee any problems. The last one went from AMD chip to Intel chip - no problem with that either.
The important thing is to SCHEDULE THE DOWNTIME and tell everyone that the system will be off line. Ideally, being the holiday, no-one should be working (except you...). If they are and complain, tell them to get a life and spend the holiday with their family.
-- The interests of society are better served by a system that encourages efficient trade activity than by one that encourages litigation. -- Amber Manx in Charles Stross's "Accerando" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org