Transfer persistence from live USB to HDD

[fehlix]

When booted LiveUSB/DVD in UEFI-mode the auto-installer "assumes" installation of EFI-grubloader and prefers GPT-partition layout.

Seeing that my live USB w persistence starts up in UEFI-mode, is it safe to "assume" that if I simply let the MX Linux Installer "Auto Install Using Entire Disk" that it will automatically proceed to create the needed GPT-partition table on the HDD?

Yes.

Or do I need to format the HDD first and manually create GPT partition tables?

No. The installer will create a new GPT partition table (and by this wipes the selected drive) and creates/formates a set of default partitions, like ESP, system-partition "/" (aka root-partition) and swap-partition.
After auto-installation of the system, you still need to choose for the GRUB-installation the target by selecting the pre-selected ESP-target, i.e accept the default. Just enter username and password for user and system-user "root". Atfer reboot it shall boot and shall display a GRUB-menu.

[Slasx]

No. The installer will create a new GPT partition table (and by this wipes the selected drive) and creates/formates a set of default partitions, like ESP, system-partition "/" (aka root-partition) and swap-partition.
After auto-installation of the system, you still need to choose for the GRUB-installation the target by selecting the pre-selected ESP-target, i.e accept the default. Just enter username and password for user and system-user "root". Atfer reboot it shall boot and shall display a GRUB-menu.

Hi Fehlix,

So I finally took the plunge today and wiped off Win 8 from my HDD and installed MX 18.3. Upon booting I noticed a few errors fly by so I did this:

cat /var/log/dmesg | grep Error and here is the output

[ 3.480743] ACPI BIOS Error (bug): Could not resolve [^^^PB2.VGA.AFN7], AE_NOT_FOUND (20180810/psargs-330)
[ 3.480869] ACPI Error: Method parse/execution failed \_SB.PCI0.VGA.LCDD._BCM, AE_NOT_FOUND (20180810/psparse-516)
[ 3.480989] ACPI Error: Evaluating _BCM failed (20180810/video-364)

I also see these messages in the log file:

[ 3.488196] ACPI: Thermal Zone [THRM] (54 C)
[ 3.507568] ACPI: bus type USB registered
[ 3.513446] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\SBSM) (20180810/utaddress-213)
[ 3.513460] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

I was getting no error messages booting from live USB on the same laptop.

Do any of these errors seem serious? Is there a work around?

It seems ACPI problems are common and can be ignored: https://www.linuxquestions.org/question ... 175605357/

BTW, what is the difference betw kernel 4.9.193.....xxxx and 4.9.193.....xxxx systemd? Which one should I choose to start up?

Any response would be much appreciated.

[KernSpy]

As far as the log goes: /var/log/bootlog .. I think.

[fehlix]

Any response would be much appreciated.

I tend to ignore those ACPI bios error warning - seems kind of never ending story, which either get fixed within newer kernel or new show up with the next kernel.

[Slasx]

I tend to ignore those ACPI bios error warning - seems kind of never ending story, which either get fixed within newer kernel or new show up with the next kernel.

Cool. I'll do the same. Surprised though that the error does not come up booting from live USB.

And what about systemd? Is that the kernel I should be using?

[fehlix]

And what about systemd? Is that the kernel I should be using?

systemd is not a kernel. MX come with two "init" ( kind of boot-strap-method of booting Linux OS. The one is called systemd the other "init" method is called SysVinit. The later is the default used with MX Linux. But some user prefer to boot with the systemd init-method. I do only use SysVinit.

[BitJam]

I tend to ignore those ACPI bios error warning - seems kind of never ending story, which either get fixed within newer kernel or new show up with the next kernel.

+1

[Slasx]

Success. Persistence was flawlessly xfered to HDD.

Something peculiar happened after the install though. I wanted to run the install again. However, when I booted from the live USB (on the laptop where I had xfered persistence to HDD, the menu option "Custom x64 *Oct 2019)" was unavailable!! Strange. Even stranger, if I booted the live USB on another laptop (where no MX is installed), the "Custom x64 *Oct 2019)" was still available!!

Is this a bug or a feature?