MX-18_January_x64 ISO issues

[matteopa]

Nah, I don't usually check checksum for doing Virtual Machine installs. If I do installs on host /main machines I check the checksums. I did download it from one of the linked mirrors from MXLinux site though. Not from outside sources / other odd ball sites.

ALWAYS check.

We need to be sure that your checksum is good or we'll be helping to no avail after all. :)

I will from now on. And true, if it's crap ISO and causing issues, then never know if it's MX issue or crap ISO issue.

I've tried last two times to install it and got through Grub installation and through rest of installer without root password error etc. I might try later and download another ISO and check the checksum and try to install again then. But will be later tonight while I'm sleeping. Otherwise I can't do anything online for an hour or two while ISO downloads... on crappy 3mbps connection here. lol Or I can try and reinstall MX again later with the same ISO. Cause it happened with this ISO before once so...

[matteopa]

Tried installing again, and this time again the Grub install bootloader issue again. Here's quick-system-info...

Code: Select all

System:
  Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
  Desktop: Xfce 4.12.3 Distro: MX-18_x64 Continuum Dec 20  2018 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek 
  v: VirtualBox date: 12/01/2006 
CPU:
  Topology: Single Core model: Intel Core2 Quad Q9550 bits: 64 type: MCP 
  arch: Penryn rev: A L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 bogomips: 5652 
  Speed: 2826 MHz min/max: N/A Core speed (MHz): 1: 2826 
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.2 driver: vmware 
  unloaded: fbdev,modesetting,vesa resolution: 800x600~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 
  v: kernel bus ID: 00:05.0 
  Sound Server: ALSA v: k4.19.0-1-amd64 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge 
  driver: piix4_smbus v: N/A port: d200 bus ID: 00:07.0 
Drives:
  Local Storage: total: 30.00 GiB used: 5.02 GiB (16.7%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 30.00 GiB 
Partition:
  ID-1: / size: 756.0 MiB used: 217.2 MiB (28.7%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 2.00 GiB used: 3.5 MiB (0.2%) fs: swap dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/stretch stretch main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
  2: deb http://security.debian.org/ stretch/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ stretch main non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 161 Uptime: 12m Memory: 987.1 MiB used: 411.8 MiB (41.7%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 
  inxi: 3.0.29 

And the install / grub stuff from terminal doing sudo -E minstall...

Code: Select all

$ sudo -E minstall
"awk -F '\t' '!/^#/ { print $3 }' /usr/share/zoneinfo/zone.tab | sort"
exit code: 0
+++ void MInstall::setupkeyboardbutton() +++
"cat /usr/share/antiX/locales.template"
exit code: 0
"grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus"
exit code: 1
+++ void MInstall::firstRefresh(QDialog*) +++
"command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
exit code: 0
+++ void MInstall::refresh() +++
+++ void MInstall::updatePartitionWidgets() +++
+++ static int MInstall::getPartitionNumber() +++
+++ bool MInstall::checkDisk() +++
+++ void MInstall::prepareToInstall() +++
"mountpoint -q /mnt/antiX/boot/efi"
exit code: 1
"/bin/umount -l /mnt/antiX/home >/dev/null 2>&1"
exit code: 32
"/bin/umount -l /mnt/antiX >/dev/null 2>&1"
exit code: 32
+++ bool MInstall::makeDefaultPartitions() +++
"uname -m | grep -q i686"
exit code: 1
"test -d /sys/firmware/efi"
exit code: 1
"/sbin/swapoff -a 2>&1"
exit code: 0
"/bin/umount -l /dev/sda1 >/dev/null 2>&1"
exit code: 32
could not umount:  "/dev/sda1"
"/sbin/sfdisk -s /dev/sda"
exit code: 0
"/bin/dd if=/dev/zero of=/dev/sda bs=512 count=100"
exit code: 0
"parted -s /dev/sda mklabel msdos"
exit code: 0
"parted -s /dev/sda mkpart primary 0 28640MiB"
exit code: 0
"parted -s /dev/sda mkpart primary 28640MiB 30688MiB"
exit code: 0
+++ bool MInstall::makeSwapPartition(QString) +++
"/sbin/mkswap /dev/sda2 -L swapMX"
exit code: 0
"make-fstab -s"
exit code: 0
"/sbin/swapon -a 2>&1"
exit code: 0
+++ bool MInstall::makeLinuxPartition(QString, const QString&, bool, const QString&) +++
"mkfs.ext4 -F /dev/sda1 -L "rootMX18""
exit code: 0
"/sbin/tune2fs -c0 -C0 -i1m /dev/sda1"
exit code: 0
"blkid /dev/sda | grep -q PTTYPE=\"gpt\""
exit code: 1
"parted -s /dev/sda set 1 boot on"
exit code: 0
+++ bool MInstall::mountPartition(QString, QString, QString) +++
"/bin/mount /dev/sda1 /mnt/antiX -o defaults,noatime"
exit code: 0
+++ void MInstall::installLinux() +++
+++ void MInstall::copyLinux() +++
+++ void MInstall::buildServiceList() +++
+++ void MInstall::copyDone(int, QProcess::ExitStatus) +++
"mkdir -m 1777 /mnt/antiX/tmp"
exit code: 0
Create fstab entries for:
rootdev "/dev/sda1"
homedev ""
swapdev "/dev/sda2"
bootdev ""
+++ QString MInstall::getPartType(QString) +++
"blkid /dev/sda1 -o value -s TYPE"
exit code: 0
change fstab entries to use UUIDs
"mount -o bind /dev /mnt/antiX/dev"
Exit code:  0
"mount -o bind /sys /mnt/antiX/sys"
Exit code:  0
"mount -o bind /proc /mnt/antiX/proc"
Exit code:  0
"chroot /mnt/antiX dev2uuid_fstab"
# Pluggable devices are handled by uDev, they are not in fstab
UUID=3ebdac42-30b1-4c7a-9f93-42a7d00b2f1e / ext4 defaults,noatime 1 1
UUID=2d0eeddf-bed6-4120-b339-2ac4565786d4 swap swap defauts 0 0 
DONE!
Exit code:  0
clear chroot env
"umount /mnt/antiX/proc"
Exit code:  0
"umount /mnt/antiX/sys"
Exit code:  0
"umount /mnt/antiX/dev"
Exit code:  0
"/usr/sbin/live-to-installed /mnt/antiX"
exit code: 0
Desktop menu
"chroot /mnt/antiX desktop-menu --write-out-global"
chroot: failed to run command ‘desktop-menu’: No such file or directory
Exit code:  32512
"/bin/rm -rf /mnt/antiX/home/demo"
exit code: 0
"/bin/rm -rf /mnt/antiX/media/sd*"
exit code: 0
"/bin/rm -rf /mnt/antiX/media/hd*"
exit code: 0
"blkid /dev/sda | grep -q PTTYPE=\"gpt\""
exit code: 1
+++ bool MInstall::installLoader() +++
"blkid /dev/sda | grep -q PTTYPE=\"gpt\""
exit code: 1
"parted -s /dev/sda set 1 boot on"
"parted -s /dev/sda set 1 boot on"
Exit code:  0
"mount -o bind /dev /mnt/antiX/dev"
Exit code:  0
"mount -o bind /sys /mnt/antiX/sys"
Exit code:  0
"mount -o bind /proc /mnt/antiX/proc"
Exit code:  0
Installing Grub
"grub-install --target=i386-pc --recheck --no-floppy --force --boot-directory=/mnt/antiX/boot /dev/sda"
Installing for i386-pc platform.
grub-install: warning: this msdos-style partition label has no post-MBR gap; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
Exit code:  0
grubDefault is  "quiet splash"
intermediate ("quiet", "quiet", "splash")
Add cmdline options to Grub ("quiet", "splash")
cmdlinestring "quiet splash"
Add cmdline options to Grub
"sed -i -r 's|^(GRUB_CMDLINE_LINUX_DEFAULT=).*|\1"quiet splash"|' /mnt/antiX/etc/default/grub"
Exit code:  0
"uname -m | grep -q i686"
df: write error: Broken pipe
Floating point exception
demo@mx1:~

[sunrat]

There are anomalies in the system info, system info Drives doesn't match Partition info:

Code: Select all

Drives:
  Local Storage: total: 30.00 GiB used: 5.02 GiB (16.7%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 30.00 GiB 
Partition:
  ID-1: / size: 756.0 MiB used: 217.2 MiB (28.7%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 2.00 GiB used: 3.5 MiB (0.2%) fs: swap dev: /dev/sda2

VirtualBox using VMware graphics?:

Code: Select all

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.2 driver: vmware

Also note PAE/NX is selected. Is that useful on a 64 bit system? Or even counterproductive?

None of these things might be relevant, but maybe...

[matteopa]

There are anomalies in the system info, system info Drives doesn't match Partition info:

Code: Select all

Drives:
  Local Storage: total: 30.00 GiB used: 5.02 GiB (16.7%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 30.00 GiB 
Partition:
  ID-1: / size: 756.0 MiB used: 217.2 MiB (28.7%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 2.00 GiB used: 3.5 MiB (0.2%) fs: swap dev: /dev/sda2

VirtualBox using VMware graphics?:

Code: Select all

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.2 driver: vmware

Also note PAE/NX is selected. Is that useful on a 64 bit system? Or even counterproductive?

None of these things might be relevant, but maybe...

I left the installer do the partitioning itself. So not sure if that's bug with MX installer or not... >_>

Um, for graphics controller the default selected was used: VMSVGA
not sure if that's VirtualBox graphic controller or not? There's also "VboxVGA" and "VboxSVGA" options there but never thought to change that?

I only did the PAE/NX cause got in habit watching a guy on youtube select it for installing some other distro. But did try a fresh installation without it and so forth. Didn't seem to make much difference cause the bugs are there anyway..lol

[dolphin_oracle]

thank you for the info. the grub fault happened in the same place it looks like, but its likely that the problem is not in the grub installer itself but in the system installers connection to it. This may take a little while to sort out.

I'm glad it installed eventually, even if it was a little ugly.

If we are able to make a change to the installer, I'll be sure to notify here so that you can test again, since you have such a "good" system to test this with.

And thanks for sticking with it.

[Stevo]

Um, for graphics controller the default selected was used: VMSVGA
not sure if that's VirtualBox graphic controller or not? There's also "VboxVGA" and "VboxSVGA" options there but never thought to change that?

I've never seen this option on the Linux Virtual Box, but I'm only running 5.2.24, so maybe it's something you see in version 6 or only on Windows hosts. On a Linux host, an MX guest reports:

Code: Select all

$ inxi -G
Graphics:  Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter driver: vboxvideo 
           v: kernel 

[matteopa]

thank you for the info. the grub fault happened in the same place it looks like, but its likely that the problem is not in the grub installer itself but in the system installers connection to it. This may take a little while to sort out.

I'm glad it installed eventually, even if it was a little ugly.

If we are able to make a change to the installer, I'll be sure to notify here so that you can test again, since you have such a "good" system to test this with.

And thanks for sticking with it.

You're welcome and glad I can help you guys out. :) I'll keep trying installs here and there to see if the root password bug happens again and then post the details from terminal. I might also try and download another ISO later tonight before I go to bed and do checksum and see if it happens after grabbing another ISO.

[Adrian]

I made a change to the installer, would you like to try this one see if you get any crash?
https://github.com/MX-Linux/gazelle-ins ... _amd64.deb

Even with the old one (the one on the ISO) I tried and installed GRUB 20 times without a crash, but I did get 2 in a row first time I tried (same location) so hopefully this change fixed this issue. Too bad I cannot reliably reproduce the problem to know if I really fixed it.

[matteopa]

Um, for graphics controller the default selected was used: VMSVGA
not sure if that's VirtualBox graphic controller or not? There's also "VboxVGA" and "VboxSVGA" options there but never thought to change that?

I've never seen this option on the Linux Virtual Box, but I'm only running 5.2.24, so maybe it's something you see in version 6 or only on Windows hosts. On a Linux host, an MX guest reports:

Code: Select all

$ inxi -G
Graphics:  Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter driver: vboxvideo 
           v: kernel 

Not sure, but I had 5.x.x version of VirtualBox up until two nights ago and had those same controllers and not "vboxvideo". I'm on Windows 7 Home 64bit, so probably is for Windows host machines... hmm.

I made a change to the installer, would you like to try this one see if you get any crash?
https://github.com/MX-Linux/gazelle-ins ... _amd64.deb

Even with the old one (the one on the ISO) I tried and installed GRUB 20 times without a crash, but I did get 2 in a row first time I tried (same location) so hopefully this change fixed this issue. Too bad I cannot reliably reproduce the problem to know if I really fixed it.

I had downloaded another MX-18_January_x64 ISO last night while I slept and checked the checksum and it matches, so the checksum passed. First time I installed I got grub error again and it crashed doing grub install, same error as before. I left VM open and ran the command sudo -E minstall again and got through grub installation and the rest of the installation as well. No root password error popup or whatever.

Will that DEB file of yours work on Windows VirtualBox instead of using an "ISO" mounted in it? Or is that DEB only for debian host machines with virtualbox on Linux machine?

[Adrian]

Will that DEB file of yours work on Windows VirtualBox instead of using an "ISO" mounted in it? Or is that DEB only for debian host machines with virtualbox on Linux machine?

It's a deb that you need to install in MX (VirtualBox has nothing to do with it, you can install on MX running in VirtualBox or running on metal), actually I asked Tim to update the installer so if it's not yet in the pool it should be soon then you won't need to download and install the deb you could run just a regular update before trying the installer -- but depending on what mirror you are connected to it might not come right now, so in a way is clearer if you download and install the deb and try again.