SAN Boot RHEL 4.4

[ManojK_1]

Hi,

Recently we have made 3 of our Linux servers as SAN Boot.

We are using EVA8000 as storage and the Servers are HP Proliant DL580 G5 Servers.
Operating System is RHEL 4 Update 4.

After SAN boot everything is working fine except "/boot partition is Not mounting" and throwing the following error.

mount: mount: LABEL=/boot duplicate - not mounted

There is any solution for the same.

Thanks & Regards,
Manoj K

[Steven E. Protter]

Shalom,

You need to change the entry in /etc/fstab and make it match the disk in grub.conf you are booting from.

I also recommend against SAN boot. It makes problem diagnosis next to impossible.

You have a very reliable, internal disk and hardware raid on those systems and there is no reason why they should not boot from local disk. Unless you like having more difficulties than you already have.

SEP

[Ivan Ferreira]

Maybe the system is not recognizing multiple paths to the same LUN, that why you get "LABEL=/boot duplicate".

Also see:

http://kbase.redhat.com/faq/docs/DOC-7379

[ManojK_1]

Dear Steven,

We are using SAN boot as a DR solution. The application which are going to run on the server is not cluster aware. So there is a single point of failure if H/W failure or site failure.

Manoj

[harry d brown jr]

I have encounter multiple raid controller failures with the DL58x servers. In one case we lost a lot of development. We've been booting and running on SAN disk for 10 years now for products like HPux, Solaris, AIX, VMware, RedHat and Windows. I use the INTERNAL disks only for booting VMware.

Of course I rolled my EVA array to the dumpster and replaced it with a CLARiiON CX3. That EVA array was a big piece of junk. I lost all four battery units simultaneously. Lost an entire raid group. Lost disk space: The unit would say I have 5 terabytes, 3 TBs inuse, 1 TB available. Where did the other TB go? Who knows, but I do know where its going: its heading to the Landfill!

live free or die
harry