I have a feeling that something(hpe?) is trying to be too smart and swapping the drive locations.
It'd be easily fixable if I knew where to tweak the knobs that tells the PXE loader which drive to boot. On Mon, Dec 4, 2017 at 9:03 PM, Lloyd Parkes <[email protected]> wrote: > This is a me too post. Sorry about that. > > > On 4/12/2017, at 3:27 PM, Daniel K <[email protected]> wrote: > > > > I'm having an issue installing to the micro-sd card of some HP SL230S > servers. The card is detected, I configure the node to mount the card at > "/" using the btrfs filesystem and tick the boot radio button next to it. > Deploying completes up to the final reboot. the PXE boot selects the wrong > drive and I get a "illegal opcode" error. > > I’ve seen the same thing on other HPE gear with Red Hat Satellite booting. > In my case Linux is installed onto a SAN volume and server knows that when > booting from disk it should boot from the SAN volume. If the server PXE > boots and the PXE boot image says to boot from the local disk, then the > booter appears to select the wrong drive and I get a "illegal opcode" error. > > I haven’t bothered tracking this down for … reasons, but I would be > interested to hear from anyone who might know what’s going on. I suspect > that PXELinux simply doesn’t do as good a job as the BIOS of knowing which > disk to boot from, or even what disks are bootable. > > Cheers, > Lloyd > p.s. I’m (fortunately?) not in the right country to get at MAAS right now. > I do however have access to a lagoon, a mask and a snorkel.
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
