[Info-vax] booting from newer SANS

[pcoviello at gmail.com]

On Thursday, December 10, 2020 at 8:00:55 PM UTC-5, pcoviello at gmail.com wrote:
> On Thursday, December 10, 2020 at 7:47:10 PM UTC-5, Jan-Erik Söderholm wrote: 
> > Den 2020-12-11 kl. 01:02, skrev pcov... at gmail.com: 
> > > I have run into an issue where we brought in a Primera 630 all SSD drives and have it connected to a rx2660 (test) and a rx8640 (production) 
> > > 
> > > I am running 8.4-1H1, and I am able to mount and shadow volumes between this and an EVA6400. the one thing I cannot get to happen is a boot from the Primera. 
> > > 
> > > Loading.: SSD Boot Device $1$DGA3010: FGA0.2031-0002-AC02-6B0D 
> > > Load of SSD Boot Device $1$DGA3010: FGA0.2031-0002-AC02-6B0D failed: Not Found 
> > > Press any key to continue 
> > > 
> > > well I have been told that 8.4-1H1 is not supported on it and I would have to go to 8.4-2L1. which I did this evening to test it. 
> > > 
> > > same message as above 
> > > and it was validated as it was under 8.4-1H1 
> > > 
> > > Validate EFI Boot Options list: Timeout = 7 secs. 
> > > -------------------------------------------------------------------------------- 
> > > 3 SSD Boot Device $1$DGA3010: FGA0.2031-0002-AC02-6B0D -fl 0,0 
> > > $1$DGA3010 PCI(0|3|0|0) Fibre(20310002AC026B0D,Lun2000000000000) 
> > > efi$bcfg: Option Validated. Success. 
> > > 
> > > 4 SSD Boot Device $1$DGA3010: FGA0.2131-0002-AC02-6B0D -fl 0,0 
> > > $1$DGA3010 PCI(0|3|0|0) Fibre(21310002AC026B0D,Lun2000000000000) 
> > > efi$bcfg: Option Validated. Success. 
> > > 
> > > -------------------------------------------------------------------------------- 
> > > 2 entries validated. 
> > > 
> > > 
> > > the vendor would like to bring in a 3PAR 8400 next week for us to test. 
> > > 
> > > I'm afraid we will have the same outcome. 
> > > 
> > > any thoughts? 
> > > 
> > > thanks 
> > > Paul 
> > > 
> > Just a shot in the dark... 
> > Does these SANs also require the "LUN-0" device to be available for 
> > full VMS support? But I'm not sure if it is boot support specifically 
> > that requires the LUN-0 to be defined...
> I have not seen that documented any where, not saying it's not the case, not sure giving it a LUN # was an option. I'll take a look.
and no it's not there to set... just to be sure I also did a 
$ SET BOOTBLOCK /PRESERVE=SIGNATURES /I64 $1$DGA3010:

which didn't help either.