You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having completed the installation on the target hardware, the first boot booted into a previous boot option. Checking the BIOS it seems that Serpent OS is not listed as an option.
I used the default/ suggested partition for booting. My setup has a small /boot/efi/ partition (exFAT 500 megs), followed by a 5 gig ext4 partition, followed by a 300 gig / partition.
I think I mistakenly picked the wrong boot partition to use, and this caused the problem, when attempting the post-installation boot
Is it possible after setting the boot partition, for a test to be carried out, that the nominated boot partition is in fact valid/ usable, a little like the test that GRUB carries out?
Thanks,
Chris
The text was updated successfully, but these errors were encountered:
I'll try a fresh installation today. I saw some slightly conflicting partitioning suggestions on the forum/ blog. I've attached my current partitioning (465gb drive), and this is the one that failed. Any pointers, I prefer a separate /home and swap? I'll close this one, if I do a successful install.
Version tested: GNOME Edition 0.24.6
Having completed the installation on the target hardware, the first boot booted into a previous boot option. Checking the BIOS it seems that Serpent OS is not listed as an option.
I used the default/ suggested partition for booting. My setup has a small /boot/efi/ partition (exFAT 500 megs), followed by a 5 gig ext4 partition, followed by a 300 gig / partition.
I think I mistakenly picked the wrong boot partition to use, and this caused the problem, when attempting the post-installation boot
Is it possible after setting the boot partition, for a test to be carried out, that the nominated boot partition is in fact valid/ usable, a little like the test that GRUB carries out?
Thanks,
Chris
The text was updated successfully, but these errors were encountered: