LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise
User Name
Password
Linux - Enterprise This forum is for all items relating to using Linux in the Enterprise.

Notices



Reply
 
Search this Thread
Old 03-22-2010, 02:27 PM   #1
jbilderb
LQ Newbie
 
Registered: Mar 2010
Distribution: RHEL 4.5
Posts: 7

Rep: Reputation: 1
Migrating RHEL4 OS to EMC SAN with PowerPath


We are currently working on a boot-to-san project, and we're trying to find out if we can take our current RHEL boxes, and migrate them to boot-to-san, or if we have to do a fresh install of the OS and all the applications (Oracle mainly).

Working with a test box, I can load RHEL on a host, dd it to the san, and it will boot-from-san just fine. However, if I have PowerPath installed and working, and then dd it to the san, it will not work.

If there is anyone that can help me, thank you.
 
Old 03-22-2010, 08:00 PM   #2
anomie
Senior Member
 
Registered: Nov 2004
Location: Texas
Distribution: RHEL, Scientific Linux, Debian, Fedora, Lubuntu, FreeBSD
Posts: 3,930
Blog Entries: 5

Rep: Reputation: Disabled
How does it "not work" exactly? How far along in the boot process do you get, and what error messages do you see?
 
Old 03-24-2010, 01:01 PM   #3
jbilderb
LQ Newbie
 
Registered: Mar 2010
Distribution: RHEL 4.5
Posts: 7

Original Poster
Rep: Reputation: 1
And, of course, 1 hour after I posted this, we figured out what went wrong, and have our box booting to SAN.

Thanks.

Just as an FYI, you have to change the /boot line of fstab to point to the PowerPath pseudoname of the boot partition on the SAN.

So this line:
LABEL=/boot /boot ext3 defaults 1 2
will read this:
/dev/emcpowerXX /boot ext3 defaults 1 2
with the first X being the PowerPath pseudoname for the LUN, and the second X being the partition # (ours was emcpowerf1)

I'm writing up the entire process now, if anyone wants a copy of it, please let me know.
 
Old 03-26-2010, 08:01 PM   #4
anomie
Senior Member
 
Registered: Nov 2004
Location: Texas
Distribution: RHEL, Scientific Linux, Debian, Fedora, Lubuntu, FreeBSD
Posts: 3,930
Blog Entries: 5

Rep: Reputation: Disabled
Makes sense. Thanks for following up on your thread.

(Note that you could also update your /boot label to point to the emcpower device. But your solution is fine.)
 
Old 03-29-2010, 09:24 AM   #5
jbilderb
LQ Newbie
 
Registered: Mar 2010
Distribution: RHEL 4.5
Posts: 7

Original Poster
Rep: Reputation: 1
Sorry if I wasn't clear, but that is exactly what we did.
 
Old 04-19-2010, 10:05 AM   #6
jbilderb
LQ Newbie
 
Registered: Mar 2010
Distribution: RHEL 4.5
Posts: 7

Original Poster
Rep: Reputation: 1
Further adventures with bfs migration:
Since we're moving ALL of our RedHat boxen to either bfs, or P2V, I've been having a lot of fun with all sorts of problems. My definition of "a lot of fun" of course includes the fact that I've only been doing Linux for about 2 months now.

Latest adventure: After using dd to copy the local hardrive to the LUN on the SAN, it couldn't find the volume group, which caused a kernel panic. This has only happened on one box so far, but here is how I finally made it work:
I did a fresh install on a different box, upgraded that box to the same kernel as the box we were having trouble with, and then copied the initrd .img file to the bad box.

When the bad box booted up, it started looking for the volume group name from the fresh install. From linux rescue, I mounted all the partitions into the bad box, did a chroot to the /mnt/sysimage, and from there was able to do a mkinitrd, which directed the initrd to the correct volume groups, and the box booted succesfully.

So, to sum up the fix:
1) dd the local hard drive to the SAN
2) edit the /boot line of the fstab to look to the boot partition on the SAN (/dev/sdc3 in this case) instead of LABEL=/boot
3) if the system has a kernel panic, get into linux rescue, mount the system's partitions to the corresponding place in the /mnt/sysimage (for example: mount /dev/sdc3 to /mnt/sysimage/boot, or /dev/VolGroup_ID_31829/usr to /mnt/sysimage/usr, etc)
4) chroot to /mnt/sysimage
5) copy the initrd .img from the fresh install to /boot on the SAN drive
6) mkinitrd
7) reboot

You may not need to copy the initrd .img if you can do the mkinitrd without that step, but I wasn't even able to do that.

It was just a bit difficult finding the rpm for the kernel, because it was an older kernel (2.6.9-67.0.15.ELsmp)

My only remaining concern is about how this will affect the Oracle databases on this server.
I hope this is somewhat clearer than mud for folks reading it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
EMC PowerPath how to change psuedo names using powermt ? shellshock79 Linux - Newbie 9 06-17-2013 07:33 AM
RHEL5.2 - Can't register naviagent with EMC SAN properly bhoros Linux - Enterprise 4 04-19-2012 01:53 PM
How do I create a partition on our SAN, RHEL Qlogic and EMC krigby Linux - Enterprise 13 08-07-2011 08:07 AM
EXT3 Filesystems (EMC SAN) Keeps Going Read-Only!!! Othyisar Linux - Hardware 1 08-04-2008 01:28 PM
emc powerpath problem sachin1361 Linux - Enterprise 1 08-27-2007 04:47 PM


All times are GMT -5. The time now is 12:21 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration