OS/2, eCS & ArcaOS - Technical > Storage
Virtualbox - LVM stopped working
Dariusz Piatkowski:
Any chance the LIBPATH stuff got messed up somehow?
What happens if you "cd" to let's say \os2\dll and try to fire it up from there?
lvmgui.cmd is in \os2, and if you start that up it'll look for lvmgui.zip in your CLASSPATH or directly in \os2\javaapps.
Roderick Klein:
--- Quote from: Dariusz Piatkowski on February 09, 2023, 03:02:15 pm ---Any chance the LIBPATH stuff got messed up somehow?
What happens if you "cd" to let's say \os2\dll and try to fire it up from there?
lvmgui.cmd is in \os2, and if you start that up it'll look for lvmgui.zip in your CLASSPATH or directly in \os2\javaapps.
--- End quote ---
If OS2\DLL would not be correctly in the libpath OS/2 would most not even start up...
Roderick
Roderick Klein:
--- Quote from: Glenn on February 09, 2023, 11:28:39 am ---
--- Quote from: Andi B. on February 09, 2023, 10:30:36 am ---Mini-LVM (from the System folder/icon), lvmgui (java based) or lvm??? cli version?
--- End quote ---
The ones I tried were mini-LVM from system folder icon and lvm on command line (the screenshot). Have not tried the java based. Is there any hope it would work when the others do not?
--- End quote ---
All not going to help. LVM.DLL can be loaded but for some reason the LVM dll can not access the disc somehow.
Hence wording it failed to open the LVM engine. Its not an issue of not being able to load the DLL.
Minilvm, lvm.exe and the java version all use lvm.dll so they will all have the same resuit.
Hmmm interesting.
Did you update to Virtualbox 7 ?
Roderick
Glenn:
--- Quote from: Roderick Klein on February 09, 2023, 03:10:12 pm ---
--- Quote from: Glenn on February 09, 2023, 11:28:39 am ---
--- Quote from: Andi B. on February 09, 2023, 10:30:36 am ---Mini-LVM (from the System folder/icon), lvmgui (java based) or lvm??? cli version?
--- End quote ---
The ones I tried were mini-LVM from system folder icon and lvm on command line (the screenshot). Have not tried the java based. Is there any hope it would work when the others do not?
--- End quote ---
All not going to help. LVM.DLL can be loaded but for some reason the LVM dll can not access the disc somehow.
Hence wording it failed to open the LVM engine. Its not an issue of not being able to load the DLL.
Minilvm, lvm.exe and the java version all use lvm.dll so they will all have the same resuit.
Hmmm interesting.
Did you update to Virtualbox 7 ?
Roderick
--- End quote ---
Hi Roderick.. Yes I updated to Virtualbox 7, but quite a bit ago, and it had been working fine until yesterday...
Rich Walsh:
To my fellow posters: if you don't know the answer, please keep your hands off the keyboard! Ill-considered, *untested* answers that send people down deadends are not "helpful".
Glenn, Remy offered one of two likely reasons for this (LVM engine already open).
The other is that your 2nd disk isn't using an MBR layout. To keep LVM engine from destroying disks laid-out using GPT & LUKS, a crude fix was added: if it finds one of these disks, it won't even start the LVM engine. The solution is either recreate/repartition as MBR or just blank the first 63 sectors of the disk. If this still doesn't fix the issue, I can PM you a workaround to get rid of the message (AYOR!).
FWIW... in AOS 5.1, GPT disks will be supported and any other type of layout will be hidden by the disk drivers, so this problem shouldn't arise.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version