Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Snapshot!!

User avatar
sg-1
Forum Novice
Forum  Novice
Posts: 67
Joined: Sat Apr 20, 2019 6:21 am

Re: Snapshot!!

#21

Post by sg-1 » Sat May 11, 2019 11:25 am

Hi, the problem of failed installation from pendrive, snapshot and MX iso are the amd catalist radeon video card drivers. After updating the same on windows10 system on reboot it stops on black screen with the flashing dash. I uninstalled the drivers via safe mode and everything starts working again. I decided as soon as possible to replace the video card.

Thank you all for your cooperation.

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Snapshot!!

#22

Post by figueroa » Sat May 11, 2019 12:36 pm

fehlix wrote:
Fri May 10, 2019 9:17 pm
I've run the script and it completes correctly giving me:

Code: Select all

-rw-rw---- 1 figueroa vboxusers 536 May 11 12:21 ZZ_Vbox_Mount_USB_dev_sdg.vmdk
Note, I changed the user to me, consistent with my other VMs.

I'm running Gentoo VirtualBox 5.2.26. Live-usb is plugged in sdg1 mounted at: /run/media/figueroa/Live-usb

But, it will not allow me to add it successfully to a VM:

Code: Select all

Failed to open the disk image file /home/figueroa/.VirtualBox/HardDisks/ZZ_Vbox_Mount_USB_dev_sdg.vmdk.

Permission problem accessing the file for the medium '/home/figueroa/.VirtualBox/HardDisks/ZZ_Vbox_Mount_USB_dev_sdg.vmdk' (VERR_ACCESS_DENIED).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
I get the same error no matter how I approach the vmdk.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4280
Joined: Wed Apr 11, 2018 5:09 pm

Re: Snapshot!!

#23

Post by fehlix » Sat May 11, 2019 12:57 pm

figueroa wrote:
Sat May 11, 2019 12:36 pm
But, it will not allow me to add it successfully to a VM:

Code: Select all

Failed to open the disk image file /home/figueroa/.VirtualBox/HardDisks/ZZ_Vbox_Mount_USB_dev_sdg.vmdk.
Permission problem accessing the file for the medium '/home/figueroa/.VirtualBox/HardDisks/ZZ_Vbox_Mount_USB_dev_sdg.vmdk' (VERR_ACCESS_DENIED).
I get the same error no matter how I approach the vmdk.
Yea, probably I forgot to mention I have added myself to the grub disk
and also to be part of vboxusers:

Code: Select all

sudo adduser $USER disk
sudo adduser $USER vboxusers
because the usb-block device ownership:

Code: Select all

ls -l /dev/sdg
brw-rw---- 1 root disk 8, 96 Mai 11 18:48 /dev/sdg
and the VMDK-ownership:

Code: Select all

$ ls -l ZZ_Vbox_Mount_USB_dev_sdg.vmdk
-rw-rw---- 1 root vboxusers 536 Mai 11 18:48 ZZ_Vbox_Mount_USB_dev_sdg.vmdk
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Snapshot!!

#24

Post by figueroa » Sat May 11, 2019 5:44 pm

fehlix wrote:
Sat May 11, 2019 12:57 pm
Yea, probably I forgot to mention I have added myself to the grub disk
and also to be part of vboxusers:

Code: Select all

sudo adduser $USER disk
sudo adduser $USER vboxusers
I added myself to the disk group. (already in vboxusers) That let me add the vmdk as a disk to the primary IDE controller. However, upon boot:

Code: Select all

Missing operating system.
FATAL: INT18: BOOT FAILURE
Should the partition(s) be mounted or unmounted, or does it matter?
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

User avatar
galaxysurfer
Forum Regular
Forum Regular
Posts: 137
Joined: Mon Jul 16, 2018 5:14 am

Re: Snapshot!!

#25

Post by galaxysurfer » Sun May 12, 2019 3:36 pm

Are you asking for a Linux equivalent of Macrium Reflect, which is a Win 10 software application that can create & restore partition images? If so I would be on board for something like that.

PS I too recently tried to use the snapshot pkg to create a personalized live usb to no success. I didn't investigate further what the underlying issue was. Is the current consensus that it is often related to hardware drivers?

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4280
Joined: Wed Apr 11, 2018 5:09 pm

Re: Snapshot!!

#26

Post by fehlix » Sun May 12, 2019 3:50 pm

figueroa wrote:
Sat May 11, 2019 5:44 pm

Code: Select all

Missing operating system.
FATAL: INT18: BOOT FAILURE
Should the partition(s) be mounted or unmounted, or does it matter?
You should unmount the USBstick but not eject. So that it is still visable,
e.g with

Code: Select all

lsblk -f
I'm not using Thunar to unmount, as I found sometime thunar also ejects the stick to not available.
I would also disabale any automount to not conflicting with access from with Vbox.
Don't touch the stick during boot, as writing to the stick could cause issues.

Well, at least it tries to boot. from that attached IDE/USB stick. Also make sure you have not additionally attached the USB as an USB-device and try first to user an USB2 port and than try to use USB3. ALso I found it works to attach to the SATA port.
You can press F12 quickly after starting the Vbox to get a list of attached devices to select to boot from,
in case you haven't prepared to boot order properly.
Also make sure you have created fresh VMDK-device, do create a new one after reboot, delete the old from last day ....
--
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Snapshot!!

#27

Post by figueroa » Sun May 12, 2019 7:37 pm

fehlix wrote:
Sun May 12, 2019 3:50 pm
Well, at least it tries to boot. from that attached IDE/USB stick. Also make sure you have not additionally attached the USB as an USB-device and try first to user an USB2 port and than try to use USB3. ALso I found it works to attach to the SATA port.
You can press F12 quickly after starting the Vbox to get a list of attached devices to select to boot from,
in case you haven't prepared to boot order properly.
Also make sure you have created fresh VMDK-device, do create a new one after reboot, delete the old from last day ....
This has been very interesting, but I've given up on booting from a Live-usb in VirtualBox for now. Darned VirtualBox remembers everything, so it whines that the recreated vmdk UUID doesn't match one stored in VirtualBox.xml. I don't have a compelling reason to fight this fight.

Later on I'll try this again from an MX installation rather than my main Gentoo desktop.

Back to the main thread, making a snapshot and creating a Live-usb from the snapshot works great.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Snapshot!!

#28

Post by figueroa » Sun May 12, 2019 7:43 pm

galaxysurfer wrote:
Sun May 12, 2019 3:36 pm
PS I too recently tried to use the snapshot pkg to create a personalized live usb to no success. I didn't investigate further what the underlying issue was. Is the current consensus that it is often related to hardware drivers?
This works, so don't give up too easily. The Live-usb you create in MX from a snapshot iso should work fine on the box the snapshot was made from, even if you've made changes to drivers. It's certainly possible that a snapshot from a system that has been "customized" may encounter errors if one tries to boot it from other hardware that may not be the same. With enough knowledge, one can work around those kinds of issues, but this would be outside of the domain of what's easy to do by new Linux user.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4280
Joined: Wed Apr 11, 2018 5:09 pm

Re: Snapshot!!

#29

Post by fehlix » Sun May 12, 2019 7:45 pm

figueroa wrote:
Sun May 12, 2019 7:37 pm
This has been very interesting, but I've given up on booting from a Live-usb in VirtualBox for now. Darned VirtualBox remembers everything, so it whines that the recreated vmdk UUID doesn't match one stored in VirtualBox.xml. I don't have a compelling reason to fight this fight.
Yep, VirtualBox is picky, you need to remove the Disk first from the known devices :alien:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: Snapshot!!

#30

Post by figueroa » Sun May 12, 2019 8:03 pm

fehlix wrote:
Sun May 12, 2019 7:45 pm
Yep, VirtualBox is picky, you need to remove the Disk first from the known devices
It's better that I be experimenting with this from a non-mission-critical system. And, I can, and will, as time permits.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

Post Reply

Return to “Chat”