Problem with boot from san

[Kristián Feldsam]

Hello,

I setup esos two node cluster with 2 dual port qle2462 cards each. So I have 8 targets. I have installed proxmox on 3 initiators with 1 emulex dual port card lpe11002 each with latest FW/BIOS. Everything works fine month ago. Now I have problem with booting. Emulex cards see all 8 targets and I can configure all 8 targets as boot devices. Sometimes it boot (5%) sometime not (95%). I don't know why? So I go to reinstall proxmox from usb key, installer see all 8 disks, so I pick /dev/sda, install was success, but after reboot it won't boot. Also I try debian, fedora but nothing change.

Latest working version was 759, them I update to 772 and boot problem occurred, so I go back to 759, but it's don't work ever.

Today I delete whole scst config and setup device for only one initiator, boot problem persists :(

scst node1 config http://pastebin.com/vC0QaeXB

scst node2 config http://pastebin.com/SBrK0tHc

crm node1 log http://pastebin.com/tbWbvgQv

crm node2 log http://pastebin.com/QGSCtS0P 

dmesg node1 http://pastebin.com/3vMuCqih

dmesg node2 http://pastebin.com/iCTZ0sKz

[Kristián Feldsam]

Screenshot of boot screen 

[Marc Smith]

Hi,

I've experienced strangeness with boot-from-SAN in the past, not just with ESOS arrays, but with other vendors' Fibre Channel disk arrays as well. I don't have any experience personally with Emulex FC HBAs on the initiator side, but have used QLogic in the past. One of the issues was it seemed as though the adapter or possibly the fibre channel switch "cached" a previous configuration and in the LUN screen in BIOS it would show a previous (no longer mapped) volume. Seems like some full power-offs on the initiator side cleared that up.

I wonder if the Emulex FC BIOS is looking at the ALUA configuration at all, or doing anything with that. Also, if I remember correctly from my SAN boot days, if I had multiple HBAs (adapters) on the initiator side, and the volume wasn't accessible on all paths, it would not boot too. With the Emulex BIOS do you specify the order of paths to try? Maybe its just trying the first path? Or randomly selecting one of the paths if multiple are configured? Some of your paths will be advertised as active/non-optimized so maybe its trying those non-optimized paths? Maybe it ignores ALUA all together, I'm honestly not sure.

I'd start with disabling the ALUA configuration... maybe take down one node so it doesn't make your cluster freak out, copy your /etc/scst.conf file and then remove the ALUA parts (device groups, target groups) and start with that.

--Marc

On Tue, Apr 7, 2015 at 3:52 PM, Kristián Feldsam <fel...@gmail.com> wrote:

Screenshot of boot screen 

--
You received this message because you are subscribed to the Google Groups "esos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kristián Feldsam]

Hi, problem solved by replacing all initiators emulex hbas by qlogic. qlogic works like charm :).

Dňa utorok, 7. apríla 2015 21:43:18 UTC+2 Kristián Feldsam napísal(-a):