10-10-2018
I have no experience with boot from SAN on metal, to put a small disclaimer upfront.
Not related to the problem...what would really help you is to have a separated installed operating system on both environments (DCs), with data part replicated in separate volume groups.
That way, only thing you do is import the volume group and (possibly or not depends) an ip assignment, depending on the topology and services such as vrrp or higher layer used.
I never endorsed SAN boot on metal personally (but in vms of course), always had couple of local disks to mirror ...
Point being, i would go with service separation and clean install on each of the sites, while cloning data part via storage methods.
Hopefully someone else who used linux SAN boot will be of more assistance with the actual problem.
Regards
Peasant.
This User Gave Thanks to Peasant For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
I have solaris 10 sparc. I installed a Qlogic hba card.
This card is connected on a brocade switch and the brocade is connected on 2 different controllers on a Hitachi disk bay.
I formated 2 luns. On my solaris system, i have 4 disk.
How to configure solaris 10 to fix the dual disk view.
... (4 Replies)
Discussion started by: simquest
4 Replies
2. Solaris
Hi,
I saw your post on the forums about how to setup IP multipathing. I wanted your help on the below situation .
I have 2 servers A and B . Now they should be connected to 2 network switches . S1 and S2.
Now is it possible to have IP Multipathing on each of the servers as follows ?
... (0 Replies)
Discussion started by: maadhuu
0 Replies
3. Solaris
Hai
we using emc storage which is conneted to M5000 through san switch.
we asign 13 luns but in server it is showing 22 luns.
i enable the solaris multipathing (MPxIO)
#more /kernel/drv/fp.conf in that file
MPxio-disable=no
#mpathadm list lu
it shows ... (2 Replies)
Discussion started by: joshmani
2 Replies
4. Solaris
Hello,
I turned on the server multipathing:
# uname -a
SunOS caiman 5.10 Generic_141444-09 sun4v sparc SUNW,T5140
stmsboot -D fp -e
And after a reboot the server, multipathing is not enable:
# stmsboot -L
stmsboot: MPxIO is not enabled
stmsboot: MPxIO disabled
# ls /dev/dsk... (4 Replies)
Discussion started by: bieszczaders
4 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I'm trying to put puppy linux 4.2.1 (I can't use the latest because it won't boot on my hardware) on a grub2'd usb drive.
It throws the error that it can't find pup_421.sfs
Here is my /boot/grub/grub.cfg
menuentry "Puppy 4.2.1" {
loopback loop... (2 Replies)
Discussion started by: Narnie
2 Replies
6. Debian
Hello, firstly excuse for my poor english.
I have a busybox error when I try to run Debian 6. It's like Grub cannot find root (initramfs)
My system is:
- RAID0 with dmraid
- /boot ext2 (from moonOS installation --ubuntu based--)
- ext4 (moonOS wich have the Grub2 installation, where I... (0 Replies)
Discussion started by: neutralTTY
0 Replies
7. Linux
I got a dual boot with grub2, but everytime I turn on the computer and the booter is loaded, I can't handle the menu, so I am forced to wait the countdown and choose the default option.
I'd really like to know why!
This is my grub.cfg,
# # DO NOT EDIT THIS FILE # # It is automatically... (0 Replies)
Discussion started by: Luke Bonham
0 Replies
8. Red Hat
Hello
This is happening on: 3.13.7-200.fc20.x86_64
This happened already some weeks ago, until now i didn install linunx onto this machine, as i had to turn in the laptop to the service center so they could fix the UEFI flash storage.
Either way, its happening again. as i installed Fedora 20... (1 Reply)
Discussion started by: sea
1 Replies
9. Red Hat
I have a couple of questions regarding multipath.
If I do vgdisplay vg01, I see it is using 1 PV: /dev/dm-13
If I type multipath -ll I see dm-9, dm-10, dm-11, dm-12, but do not see dm-13. Is my vg01 multipathed? How can I actually know for sure?
Secondly, let's say this time vg01 says... (1 Reply)
Discussion started by: keelba
1 Replies
10. UNIX for Beginners Questions & Answers
I have centos 7 gui installed on vmware workstation12 on my laptop.WhenI want to pause my splash screen while starting my centos 7 using the 'esc key' nothing happens and the system just boots up.I also see a entry for aci_memory_fail... entry during the boot process.help me fix the system. (1 Reply)
Discussion started by: sabsac
1 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)