I discovered that I can export from the old VirtualBox to OVF format
just by manually changing the name of the file it will create from .OVA
to .OVF. And the new VirtualBox on the Latitude will import it, except
that at the end the import fails:
VirtualBox Error
Failed to import appliance ...
So, you need OVF to import it?
Try export Virtual Appliance from menu then select one of the OVF
formats.
I do not bother - just:
rsync -a "VirtualBox VMs" .../home/$USER/
rsync -a .config/VirtualBox .../home/$USER/.config/
Then start your new virtualbox and you should see everything as it
By disappear I meant no longer visible, you have to do the vgscan and
vgchange for the logical volumes to become visible. Some distro do this
automatically for you.
On Fri, Feb 11, 2022 at 12:20 PM Rich Shepard
wrote:
> On Fri, 11 Feb 2022, Michael Ewan wrote:
>
> > The steps involved are
On Fri, 11 Feb 2022, Michael Ewan wrote:
The steps involved are pvcreate, vgscan, vgcreate, and lvcreate. The
pvcreate operation labels the disks for use in a volume group. Do not use
the UUID. The vgscan operation finds the pv labels. The vgcreate operation
takes those disks and adds them to a
The steps involved are pvcreate, vgscan, vgcreate, and lvcreate. The
pvcreate operation labels the disks for use in a volume group. Do not use
the UUID. The vgscan operation finds the pv labels. The vgcreate
operation takes those disks and adds them to a volume group.
So...
pvcreate /dev/sdc1
On Fri, 11 Feb 2022, Michael Rasmussen wrote:
Perhaps you can read up on UUIDs? Two sources I used while reading this
thread were:
https://www.uuidtools.com/what-is-uuid
and
https://en.wikipedia.org/wiki/Universally_unique_identifier
Thanks, Michael.
Rich
On Fri, 11 Feb 2022, Galen Seitz wrote:
Wait! I think you are missing an important point. UUIDs are used for many
things on a modern Linux system. There will typically be *multiple* UUIDs
used for multiple purposes. Here is some trimmed output from an Ubuntu
system that has three physical
On 2022-02-11 09:34, Rich Shepard wrote:
On Fri, 11 Feb 2022, Tomas Kuchta wrote:
The point about not using /dev/sd*, especially with external
enclosures,
is that the device letter can change (not just once) during the array
build.
Tomas,
I'll kill the mdadm create process and use the
On 2/11/22 09:34, Rich Shepard wrote:
On Fri, 11 Feb 2022, Tomas Kuchta wrote:
The point about not using /dev/sd*, especially with external enclosures,
is that the device letter can change (not just once) during the array
build.
Tomas,
I'll kill the mdadm create process and use the two
Two of the disks in the MediaSonic Probox have been partitioned and had ext4
installed but are otherwise empty of data. Rather than having two separate
disks for extra external storage I want to build a single LV.
The LVM docs I've read use partitions on a single hdd. I did not explictly
make a
On Fri, 11 Feb 2022, Bill Barry wrote:
You should also be aware of the useful tool blkid which lists your block
devices and their uuids.
BIll,
Ah, yes. Thanks. I forgot about that one.
Regards,
Rich
On Fri, 11 Feb 2022, Tomas Kuchta wrote:
The point about not using /dev/sd*, especially with external enclosures,
is that the device letter can change (not just once) during the array
build.
Tomas,
I'll kill the mdadm create process and use the two UUIDs instead. Do I
write:
mdadm --create
On Fri, Feb 11, 2022 at 9:50 AM Tomas Kuchta
wrote:
>
> On Fri, Feb 11, 2022, 08:39 Rich Shepard wrote:
>
> > On Thu, 10 Feb 2022, Galen Seitz wrote:
> >
> > > Using UUIDs should prevent much of this grief. For example, here's a line
> > > from mdadm.conf on one my my machines:
> >
> >
On Fri, Feb 11, 2022, 08:39 Rich Shepard wrote:
> On Thu, 10 Feb 2022, Galen Seitz wrote:
>
> > Using UUIDs should prevent much of this grief. For example, here's a line
> > from mdadm.conf on one my my machines:
>
> Galen/Tomas:
>
> Okay. I've six mdadm.conf files here, including
On Thu, 10 Feb 2022, Galen Seitz wrote:
Using UUIDs should prevent much of this grief. For example, here's a line
from mdadm.conf on one my my machines:
Galen/Tomas:
Okay. I've six mdadm.conf files here, including /etc/mdadm.conf which is all
commented out. Since mdadm has been working on
15 matches
Mail list logo
