-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
diskful provision cannot boot from disk #449
Comments
Probably a stupid question, but is a local disk boot configured in the BIOS, as in the list of bootable devices. Apologies if i ask a redundant question, but just have to make sure. -A |
Yes, there is. |
There might be a compatibility issue with the vmware approach. Not all vmware instances handle sanboot requests for 0x80 well. We try to support all possible combinations, including uefi disks but sometimes a setup falls through the cracks. Good news though, since we use templates, these can easily be changed to what you need. I'd try the following:
You can keep the original by adding # in front; comment out.
|
Sadly, it still does not boot, it shows the following but does not boot the OS: What's interesting is that CPU is doing something on node003: |
Do you do uefi and/or secure boot? What if you change the boot order temporarily in the bios and boot from disk. Does that work? |
This was BIOS, not uefi nor secure boot. I tried this: But gives me this error: Config is: |
Am not sure why qemu does this, but that's different from the vmware attempts right? The above gave me the feeling it was vmware, not qemu. I have to guess that some qemu setting prevents an uefi boot? Maybe regular bios boot approach solves this, not knowing whether qemu supports this? This will probably result in a lot of trial and error. I can report however that this approach, diskless through scripts plugin, does work in vsphere. The last one, not finding the kernel might be solved by making a symlink to /boot in /boot:
But you yeed to boot first. This can be solved by removing '/boot' from the grub menu as a one time attempt. |
This worked and the node booted from disk! |
Hello there!
I'm in a VMs setup to test.
Following the instructions here: https://docs.clustervision.com/howtos/disk-full-node/
I can see the node booting/downloading image/partitioning/formating and then switching to that installation
But after reboot it does exactly the same, it reinstalls again
I was expecting it to boot from disk
So I changed the node netboot to no:
luna node change node003 -nb n
And that changed the booting process and no longer tries to reinstall everything
But it does not boot the system
It stays in a blank screen with just one line saying:
Boot from SAN device 0x80
In BIOS boot order is net->disk
I tried to select the option of
Exit and continue BIOS boot order
But the result is a similar one:
Blank screen saying:
And stays like that
I also tried to boot from an ISO to check boot flags of partitions and I think it looks fine:
Any ideas?
Thanks!
The text was updated successfully, but these errors were encountered: