richardnguyen
Hi all,
I am new to Obarun, please be patient with my lack of knowledge.
I tried to boot from the 2021.07.26 ISO (both the minimal and JWM) a got the error:
::Mounting '/dev/disk/by-label/obarun-JWM-2021.07.26' to '/run/archiso/bootmnt'
Waiting 30 seconds for device /dev/disk/by-label/obarun-JWM-2021.07.26...
Mounting '/dev/disk/by-label/obarun-JWM-2021.07.26' device did not show up after 30 seconds
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job control turned off.
[rootfs ]#
What should I do in order to proceed?
Thank you!
banned_9-26-2021
Not a good day to ask, as you will not be able to do an installation as obarun's repositories are down.
How are you trying to boot? Did you transfer the iso to a disk or usb stick? Is the boot menu (pale-blue-white screen with obarun logo and options coming up?), is it on hw, vm, ??? If hw what hw, do you have safe boot? If vm, what vm, what host?
You should be able to boot the live image but you can't do an installation other than hacking it and copying the live image into a partition then do some chroot modification to get it to boot from HD.
Hi again Richard :)
richardnguyen
Hi fungal_net,
Thank you for your prompt reply.
I am trying to boot it from the Hyper-V VM.
with 2G allocated RAM
4 virtual proocessors
and secure boot disabled
There was a text-based menu with the options:
Obarun iso UEFI CD
UEFI Shell x86_64 v1
UEFI Shell x86_64 v2
EFI Default Loader
Reboot Into Firmware Interface
I chose the first option, it led to the error mentioned.
4 other options doesnt work either.
I tried to boot off USB on hw but there was another error. I will try again to inform you the specific dialog given.
banned_9-26-2021
Can you switch from UEFI to Bios boot? Although this is the first I heard of such a problem for years, there may be a bug nobody knows yet. If it is booting normally with bios than we know where to look.
Unfortunately I know nothing about hyper-V
I have not ever seen this menu either, it must be hyper-V uefi simulation that somehow seems incompatible. On real hw I can't even remember the last time someone reported a problem.