Page 41 of 42
Re: Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 4:40 pm
by Buck Fankers
blindside wrote: Fri Sep 06, 2019 4:50 am
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap.
As a work around, if you don't plan to use hibernate, but only suspend, then swap file is better solution than swap partition.
You could try to install without swap partition then after installation is completed, run these 4 commands:
Code: Select all
sudo fallocate -l 2G /swapfile <- set the size (4G for 4GB, 8G for 8GB...)
sudo chmod 600 /swapfile <- set correct permission
sudo mkswap /swapfile <- format the swap file
sudo swapon /swapfile <- activate swap file
Re: Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 8:13 pm
by blindside
Thanks so much. Will be working on this after dinner
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 9:04 pm
by jj1j1
Has anyone got kodi, from mxpi, to install addons in mx19?
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 12:27 am
by Eadwine Rose
I have no idea if it will work, will have to test still and haven't gotten that far, but I always just copy over the existing .kodi folder from install to install.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 12:52 am
by blindside
I fell like a frickin complete newbie. I have never had issues installing, but maybe if the partition schemes in gparted were broken down to me, I might be successful. Can anyone tell me, in gparted, how they set up this beta and were successful.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 12:57 am
by Eadwine Rose
Well.. images and thousand words and such.
I do have more than one hard drive, AND a UEFI system, but here are the two hard drives that hold the important info.
18.3 install
sda.jpg
19 beta install
sdc.jpg
That's how I got it all set up.
I don't know who swap on the beta got to be sdc1, I definitely didn't set it up like that, 1 is root, 2 is home and 3 is swap. Maybe I goofed up, or maybe the installer thought it knew better lol. Keeping a close eye when I install the next beta, but this works.
Re: Stuck on formatting swap on the new beta
Posted: Sat Sep 07, 2019 1:10 am
by ChrisUK
Buck Fankers wrote: Fri Sep 06, 2019 4:40 pm
blindside wrote: Fri Sep 06, 2019 4:50 am
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap.
As a work around, if you don't plan to use hibernate, but only suspend, then swap file is better solution than swap partition.
You could try to install without swap partition then after installation is completed, run these 4 commands:
Code: Select all
sudo fallocate -l 2G /swapfile <- set the size (4G for 4GB, 8G for 8GB...)
sudo chmod 600 /swapfile <- set correct permission
sudo mkswap /swapfile <- format the swap file
sudo swapon /swapfile <- activate swap file
Unless I've misunderstood - also add
to /etc/fstab
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 1:13 am
by blindside
JayM wrote: Fri Sep 06, 2019 6:33 am
I thought the latest version of the installer which should be part of the beta did a swapoff already.
@blindside: It would be nice if you could open a terminal and run
then copy everything in the terminal and paste it here
inside of code tags.
Code: Select all
$ sudo minstall -E
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Installer version: 19.8.06
+++ void MInstall::startup() +++
Exec #1: "uname -m | grep -q i686"
Exit #1: 1 QProcess::ExitStatus(NormalExit)
Exec #2: "test -d /sys/firmware/efi"
Exit #2: 0 QProcess::ExitStatus(NormalExit)
uefi = true
Exec #3: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
Exit #3: 0 QProcess::ExitStatus(NormalExit)
Exec #4: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
Exit #4: 0 QProcess::ExitStatus(NormalExit)
Exec #5: "ps -aux |grep -v grep | grep devmon"
Exit #5: 1 QProcess::ExitStatus(NormalExit)
Exec #6: "grep space /home/$(logname)/.desktop-session/desktop-code.*"
SErr #6: "grep: /home/demo/.desktop-session/desktop-code.*: No such file or directory\n"
Exit #6: 2 QProcess::ExitStatus(NormalExit)
+++ void MInstall::setupkeyboardbutton() +++
Exec #7: "locale -a | grep -Ev '^(C|POSIX)\\.?' | grep -E 'utf8|UTF-8'"
Exit #7: 0 QProcess::ExitStatus(NormalExit)
Exec #8: "grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus"
Exit #8: 1 QProcess::ExitStatus(NormalExit)
Exec #9: "/bin/ls -1 /home | grep -Ev '(lost\\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]"
Exit #9: 1 QProcess::ExitStatus(NormalExit)
Exec #10: "test -d /live/linux/home/demo"
Exit #10: 1 QProcess::ExitStatus(NormalExit)
Exec #11: "dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'"
Exit #11: 0 QProcess::ExitStatus(NormalExit)
+++ void MInstall::buildServiceList() +++
+++ void MInstall::updatePartitionWidgets() +++
Exec #12: "/sbin/partprobe"
SErr #12: "Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.\n"
Exit #12: 1 QProcess::ExitStatus(NormalExit)
Exec #13: "blkid -c /dev/null"
SOut #13: "/dev/nvme0n1: PTUUID=\"327faf03-b588-452e-a9d0-835a95aef2d7\" PTTYPE=\"gpt\"\n/dev/sda1: UUID=\"2019-08-25-19-38-05-00\" LABEL=\"MX-Live\" TYPE=\"iso9660\" PTUUID=\"5d95e9ad\" PTTYPE=\"dos\" PARTUUID=\"5d95e9ad-01\"\n/dev/sda2: SEC_TYPE=\"msdos\" LABEL_FATBOOT=\"EFI-LIVE\" LABEL=\"EFI-LIVE\" UUID=\"6CFD-B910\" TYPE=\"vfat\" PARTUUID=\"5d95e9ad-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
Exit #13: 0 QProcess::ExitStatus(NormalExit)
Exec #14: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\ -f1 | cut -d/ -f3"
Exit #14: 0 QProcess::ExitStatus(NormalExit)
Exec #15: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL |sed 's/├─//' |sed 's/└─//' | grep -E '^(disk|part)'"
Exit #15: 0 QProcess::ExitStatus(NormalExit)
Exec #16: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
Exit #16: 1 QProcess::ExitStatus(NormalExit)
Exec #17: "blkid /dev/nvme0n1 | grep -q PTTYPE=\\\"gpt\\\""
Exit #17: 0 QProcess::ExitStatus(NormalExit)
Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
"sda" 31010586624 "USB_3.0_FD" "iso9660" | true false false false false false
"sda1" 1441792000 "" "iso9660" | false false false false false false
"sda2" 3284992 "" "vfat" | false false false true false false
"nvme0n1" 500107862016 "Samsung SSD 970 EVO 500GB" "" | true true false false false false
"nvme0n1p1" 268435456 "" "ext4" | false true false false true false
"nvme0n1p2" 497658363904 "" "" | false true false false true false
"nvme0n1p3" 2147483648 "" "ext4" | false true false false true false
Exec #18: "[ -f /usr/sbin/gparted ] && /usr/sbin/gparted || /usr/bin/partitionmanager"
SOut #18: "======================\nlibparted : 3.2\n======================\n"
SErr #18: "System has not been booted with systemd as init system (PID 1). Can't operate.\nFailed to connect to bus: Host is down\nToo few arguments.\nToo few arguments.\n/bin/bash: /usr/bin/partitionmanager: No such file or directory\n"
Exit #18: 127 QProcess::ExitStatus(NormalExit)
+++ void MInstall::updatePartitionWidgets() +++
Exec #19: "/sbin/partprobe"
SErr #19: "Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.\n"
Exit #19: 1 QProcess::ExitStatus(NormalExit)
Exec #20: "blkid -c /dev/null"
SOut #20: "/dev/nvme0n1: PTUUID=\"60443ed4-f97b-4d6b-85b7-7d4eb15da25b\" PTTYPE=\"gpt\"\n/dev/sda1: UUID=\"2019-08-25-19-38-05-00\" LABEL=\"MX-Live\" TYPE=\"iso9660\" PTUUID=\"5d95e9ad\" PTTYPE=\"dos\" PARTUUID=\"5d95e9ad-01\"\n/dev/sda2: SEC_TYPE=\"msdos\" LABEL_FATBOOT=\"EFI-LIVE\" LABEL=\"EFI-LIVE\" UUID=\"6CFD-B910\" TYPE=\"vfat\" PARTUUID=\"5d95e9ad-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
Exit #20: 0 QProcess::ExitStatus(NormalExit)
Exec #21: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\ -f1 | cut -d/ -f3"
Exit #21: 0 QProcess::ExitStatus(NormalExit)
Exec #22: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL |sed 's/├─//' |sed 's/└─//' | grep -E '^(disk|part)'"
Exit #22: 0 QProcess::ExitStatus(NormalExit)
Exec #23: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
Exit #23: 1 QProcess::ExitStatus(NormalExit)
Exec #24: "blkid /dev/nvme0n1 | grep -q PTTYPE=\\\"gpt\\\""
Exit #24: 0 QProcess::ExitStatus(NormalExit)
Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
"sda" 31010586624 "USB_3.0_FD" "iso9660" | true false false false false false
"sda1" 1441792000 "" "iso9660" | false false false false false false
"sda2" 3284992 "" "vfat" | false false false true false false
"nvme0n1" 500107862016 "Samsung SSD 970 EVO 500GB" "" | true true false false false false
"nvme0n1p1" 314572800 "" "vfat" | false true false true false false
"nvme0n1p2" 16106127360 "" "ext4" | false true false false true false
"nvme0n1p3" 8589934592 "" "swap" | false true false false true true
+++ bool MInstall::validateChosenPartitions() +++
+++ bool MInstall::saveHomeBasic() +++
+++ bool MInstall::checkTargetDrivesOK() +++
+++ void MInstall::cleanup(bool) +++
Exec #25: "/bin/umount -l /mnt/antiX/boot/efi"
SErr #25: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
Exit #25: 32 QProcess::ExitStatus(NormalExit)
Exec #26: "/bin/umount -l /mnt/antiX/proc"
SErr #26: "umount: /mnt/antiX/proc: no mount point specified.\n"
Exit #26: 32 QProcess::ExitStatus(NormalExit)
Exec #27: "/bin/umount -l /mnt/antiX/sys"
SErr #27: "umount: /mnt/antiX/sys: no mount point specified.\n"
Exit #27: 32 QProcess::ExitStatus(NormalExit)
Exec #28: "/bin/umount -l /mnt/antiX/dev/shm"
SErr #28: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
Exit #28: 32 QProcess::ExitStatus(NormalExit)
Exec #29: "/bin/umount -l /mnt/antiX/dev"
SErr #29: "umount: /mnt/antiX/dev: no mount point specified.\n"
Exit #29: 32 QProcess::ExitStatus(NormalExit)
Exec #30: "/bin/umount -l /mnt/antiX/home"
SErr #30: "umount: /mnt/antiX/home: no mount point specified.\n"
Exit #30: 32 QProcess::ExitStatus(NormalExit)
Exec #31: "/bin/umount -lR /mnt/antiX"
SErr #31: "umount: /mnt/antiX: not found\n"
Exit #31: 1 QProcess::ExitStatus(NormalExit)
+++ bool MInstall::makePartitions() +++
Exec #32: "swapoff /dev/nvme0n1p2"
SErr #32: "swapoff: /dev/nvme0n1p2: swapoff failed: Invalid argument\n"
Exit #32: 255 QProcess::ExitStatus(NormalExit)
Exec #33: "/bin/umount /dev/nvme0n1p2"
SErr #33: "umount: /dev/nvme0n1p2: not mounted.\n"
Exit #33: 32 QProcess::ExitStatus(NormalExit)
---- PARTITION FORMAT SCHEDULE ----
Root: "/dev/nvme0n1p2" -1
Home: "/dev/nvme0n1p2" 0
Swap: "/dev/nvme0n1p3" 0
Boot: "/dev/nvme0n1p2" 0
ESP: "" 0
BIOS-GRUB: ""
Exec #34: "/sbin/sgdisk /dev/nvme0n1 --typecode=2:8303"
SOut #34: "The operation has completed successfully.\n"
Exit #34: 0 QProcess::ExitStatus(NormalExit)
Exec #35: "partprobe"
SErr #35: "Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.\n"
Exit #35: 1 QProcess::ExitStatus(NormalExit)
+++ bool MInstall::formatPartitions() +++
+++ bool MInstall::makeLinuxPartition(const QString&, const QString&, bool, const QString&) +++
Exec #36: "mkfs.ext4 -F /dev/nvme0n1p2 -L \"rootMX19\""
SErr #36: "mke2fs 1.44.5 (15-Dec-2018)\nThe file /dev/nvme0n1p2 does not exist and no size was specified.\n"
Exit #36: 1 QProcess::ExitStatus(NormalExit)
+++ void MInstall::cleanup(bool) +++
Exec #37: "/bin/umount -l /mnt/antiX/boot/efi"
SErr #37: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
Exit #37: 32 QProcess::ExitStatus(NormalExit)
Exec #38: "/bin/umount -l /mnt/antiX/proc"
SErr #38: "umount: /mnt/antiX/proc: no mount point specified.\n"
Exit #38: 32 QProcess::ExitStatus(NormalExit)
Exec #39: "/bin/umount -l /mnt/antiX/sys"
SErr #39: "umount: /mnt/antiX/sys: no mount point specified.\n"
Exit #39: 32 QProcess::ExitStatus(NormalExit)
Exec #40: "/bin/umount -l /mnt/antiX/dev/shm"
SErr #40: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
Exit #40: 32 QProcess::ExitStatus(NormalExit)
Exec #41: "/bin/umount -l /mnt/antiX/dev"
SErr #41: "umount: /mnt/antiX/dev: no mount point specified.\n"
Exit #41: 32 QProcess::ExitStatus(NormalExit)
Exec #42: "/bin/umount -l /mnt/antiX/home"
SErr #42: "umount: /mnt/antiX/home: no mount point specified.\n"
Exit #42: 32 QProcess::ExitStatus(NormalExit)
Exec #43: "/bin/umount -lR /mnt/antiX"
SErr #43: "umount: /mnt/antiX: not found\n"
Exit #43: 1 QProcess::ExitStatus(NormalExit)
Re: Stuck on formatting swap on the new beta
Posted: Sat Sep 07, 2019 2:14 am
by Buck Fankers
ChrisUK wrote: Sat Sep 07, 2019 1:10 am
Unless I've misunderstood - also add
to /etc/fstab
Oh, yes, how did I miss this line, it was late, sorry and thanks for correction!
All together:
Code: Select all
sudo fallocate -l 2G /swapfile <- set the size
sudo chmod 600 /swapfile <- set correct permission
sudo mkswap /swapfile <- format the swap file
sudo swapon /swapfile <- activate swap file
/swapfile none swap defaults 0 0 <- add this line to /etc/fstab
To add last line to fstab, you can highlight last line with mouse, copy, run in the terminal:
Move cursor to the bottom of the text in new line and paste it there then save changes with: Ctrl-X
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 3:50 am
by chrispop99
I've just tried the new MX Date and Time application from the latest updates. It's very slick!
Presumably the MX Time Settings application will be removed in the future?
Chris