MX Linux Forum

Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/

[solved] I want to install MX-18.3 to partition #19 on my HDD, but...

http://www.forum.mxlinux.org/viewtopic.php?t=51965

Page 1 of 1

[solved] I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 8:31 pm
by jbMacAZ
With the minstall GUI installer, I only see up to partition 15. I found this topic https://mxlinux.org/forum/viewtopic.php ... 7&start=10 about setting /home beyond partition #9. Is there a .conf I can edit or some trick to install MX-linux on sda19? I have a swap partition below partition 15 that I could sacrifice, but I have a larger partition reserved for MX...

My (other) system is a skylake (i5-6400) Dell desktop (inspiron 3250) with a 1TB HDD w/16GB RAM. The HDD already has windows, several data partitions and a few other Linux (various former #1's) I've remastered the liveUSB (18.3 final ISO) with the latest updates, toram and persistence. So I am able to run (and it seems to run very well). Video, wifi, USB keyboard/mouse and HDMI w/sound all seem to work fine on the liveUSB.

Thanks in advance for any suggestions,
-John

Update: This old drive does not list the HDD partitions contiguously with lsblk. Temporary workaround: edit /usr/share/gazelle-installer-data/installer.conf so that "INSTALL_FROM_ROOT_DEVICE=true". A permanent fix is pending for this unlikely scenario.

Update2: Fixed in antiX19b3

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 8:51 pm
by fehlix
jbMacAZ wrote: Wed Aug 07, 2019 8:31 pm With the minstall GUI installer, I only see up to partition 15.
On scsi[sata] connected drives you have max of 15 partitions, e.g. sda1 ... sda15 for MBR/DOS -partition table scheme.
On GPT partition table scheme you can have up 128 partitions.
So I guess, the limiting factor is your chosen partition table scheme of that drive.
HTH
:puppy:

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 9:38 pm
by jbMacAZ
Thanks for the help. There is something odd about the partitions after sda15, namely "sda19 259:3". The target drive is GPT, but MX-Linux is running live from an MBR USB. FWIW, Devuan installed on sda18, Arcolinux is on sda17 and sda16 is an old ext4 data partition.

Code: Select all

$$ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0     7:0    0   2.2G  1 loop /live/linux
loop1     7:1    0     1G  0 loop /home
sda       8:0    0 931.5G  0 disk 
├─sda1    8:1    0   500M  0 part 
├─sda2    8:2    0   128M  0 part 
├─sda3    8:3    0  98.5G  0 part 
├─sda4    8:4    0  30.3G  0 part 
├─sda5    8:5    0   450M  0 part 
├─sda6    8:6    0  11.6G  0 part 
├─sda7    8:7    0  44.2G  0 part 
├─sda8    8:8    0  16.6G  0 part [SWAP]
├─sda9    8:9    0  16.1G  0 part 
├─sda10   8:10   0  25.4G  0 part 
├─sda11   8:11   0 152.4G  0 part 
├─sda12   8:12   0  97.7G  0 part 
├─sda13   8:13   0  39.4G  0 part 
├─sda14   8:14   0  17.6G  0 part [SWAP]
├─sda15   8:15   0  40.4G  0 part 
├─sda16 259:0    0 195.4G  0 part 
├─sda17 259:1    0  30.8G  0 part 
├─sda18 259:2    0  27.2G  0 part 
└─sda19 259:3    0  27.5G  0 part 
sdb       8:16   1  28.7G  0 disk 
└─sdb1    8:17   1  28.7G  0 part 
sdc       8:32   1  29.9G  0 disk 
└─sdc1    8:33   1  29.9G  0 part /live/boot-dev
sr0      11:0    1  1024M  0 rom

Code: Select all

$ inxi -Fxxxz
System:    Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 info: xfce4-panel wm: xfwm4 dm: LightDM 1.18.3 
           Distro: MX-18.3_x64 Continuum Dec 20  2018 base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: Dell product: Inspiron 3250 v: X00 serial: <filter> Chassis: 
           type: 3 serial: <filter> 
           Mobo: Dell model: 0DNMV1 v: A01 serial: <filter> UEFI: Dell v: 3.3.6 date: 09/30/2016 
Battery:   Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter> charge: Normal 
           status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP arch: Skylake-S 
           rev: 3 L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21696 
           Speed: 800 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 897 2: 896 3: 898 4: 890 
Graphics:  Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:1912 
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 18.2.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-H HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a170 
           Device-2: N/A type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-7:5 
           chip ID: 2875:0001 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell 
           driver: r8169 v: kernel port: e000 bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Dell 
           driver: ath9k v: kernel port: e000 bus ID: 02:00.0 chip ID: 168c:0036 
           IF: wlan0 state: down mac: <filter> 
           Device-3: Atheros type: USB driver: btusb bus ID: 1-3:7 chip ID: 0cf3:e005 
Drives:    Local Storage: total: 990.04 GiB used: 6.5 MiB (0.0%) 
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s 
           rotation: 7200 rpm serial: <filter> rev: A7S0 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra Fit size: 28.64 GiB 
           serial: <filter> rev: 1.00 scheme: MBR 
           ID-3: /dev/sdc type: USB vendor: Samsung model: Flash Drive size: 29.88 GiB 
           serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / size: 10.60 GiB used: 6.5 MiB (0.1%) fs: overlay dev: ERR-102 
           ID-2: swap-1 size: 16.60 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda8 
           ID-3: swap-2 size: 17.58 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda14 
Sensors:   System Temperatures: cpu: 26.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 1454 fan-2: 1076 
Info:      Processes: 194 Uptime: 9m Memory: 15.57 GiB used: 710.1 MiB (4.5%) Init: SysVinit 
           v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 Shell: bash v: 4.4.12 
           running in: xfce4-terminal inxi: 3.0.25

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 9:45 pm
by old_guy
I was told about that limit, but some time ago I set up my drive:

Code: Select all

 sudo fdisk -l
[sudo] password for earl: 
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0004f16f

Device     Boot      Start        End    Sectors  Size Id Type
/dev/sda1  *          2048    8390655    8388608    4G 83 Linux
/dev/sda2          8390656  113248255  104857600   50G 83 Linux
/dev/sda3        113248256  218105855  104857600   50G 83 Linux
/dev/sda4        218107902 3907029167 3688921266  1.7T  5 Extended
/dev/sda5        218107904  322965325  104857422   50G 83 Linux
/dev/sda6        322967552  427824973  104857422   50G 83 Linux
/dev/sda7        427827200  532684621  104857422   50G 83 Linux
/dev/sda8        532686848  637544269  104857422   50G 83 Linux
/dev/sda9        637546496  742403917  104857422   50G 83 Linux
/dev/sda10       742406144  847263565  104857422   50G 83 Linux
/dev/sda11       847265792  952123391  104857600   50G 83 Linux
/dev/sda12       952125440 1056982861  104857422   50G 83 Linux
/dev/sda13      1056985088 1161842509  104857422   50G 83 Linux
/dev/sda14      1161844736 1266702335  104857600   50G 83 Linux
/dev/sda15      1266704384 1371561983  104857600   50G 83 Linux
/dev/sda16      1371564032 1476421453  104857422   50G 83 Linux
/dev/sda17      1476423680 1581281101  104857422   50G 83 Linux
/dev/sda18      1581283328 1686140927  104857600   50G 83 Linux
/dev/sda19      1686142976 1791000397  104857422   50G 83 Linux
/dev/sda20      1791002624 1895860045  104857422   50G 83 Linux
/dev/sda21      1895862272 2000719871  104857600   50G 83 Linux
/dev/sda22      2000721920 2105579519  104857600   50G 83 Linux
/dev/sda23      2105581568 3907029167 1801447600  859G 83 Linux
and it seems to be working.

PS your odd looking partitions:

Code: Select all

lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda       8:0    0   1.8T  0 disk 
├─sda1    8:1    0     4G  0 part [SWAP]
├─sda2    8:2    0    50G  0 part 
├─sda3    8:3    0    50G  0 part 
├─sda5    8:5    0    50G  0 part 
├─sda6    8:6    0    50G  0 part 
├─sda7    8:7    0    50G  0 part 
├─sda8    8:8    0    50G  0 part 
├─sda9    8:9    0    50G  0 part 
├─sda10   8:10   0    50G  0 part 
├─sda11   8:11   0    50G  0 part 
├─sda12   8:12   0    50G  0 part 
├─sda13   8:13   0    50G  0 part 
├─sda14   8:14   0    50G  0 part 
├─sda15   8:15   0    50G  0 part 
├─sda16 259:0    0    50G  0 part /
├─sda17 259:1    0    50G  0 part 
├─sda18 259:2    0    50G  0 part 
├─sda19 259:3    0    50G  0 part 
├─sda20 259:4    0    50G  0 part 
├─sda21 259:5    0    50G  0 part 
├─sda22 259:6    0    50G  0 part 
└─sda23 259:7    0   859G  0 part /mnt/data2
sdb       8:16   0 931.5G  0 disk 
├─sdb1    8:17   0   100M  0 part 
└─sdb2    8:18   0 931.4G  0 part 
sdc       8:32   0   1.8T  0 disk 
└─sdc1    8:33   0   1.8T  0 part /mnt/data
sr0      11:0    1  1024M  0 rom
Earl

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 9:47 pm
by JayM
It doesn't make sense to me that changing the partition table type on the USB would help, but you could try it. If you have a second USB stick you can boot from the first one, open MX Live USB Maker, click the Advanced Options button and choose gpt, then up above instead of selecting an ISO choose clone existing system. I haven't tried it, but it should copy your existing, updated and remastered live USB to the second one but using a gpt partition table. That way you don't have to start all over again tweaking the USB the way you want it.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 9:55 pm
by jbMacAZ
Thanks,
Thunar sees the expected root directory on sda18. The partition >15 access issue seems specific to the installer.

Code: Select all

$ sudo fdisk -l
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: <snip>

Device          Start        End   Sectors   Size Type
/dev/sda1        2048    1026047   1024000   500M EFI System
/dev/sda2     1026048    1288191    262144   128M Microsoft reserved
/dev/sda3     1288192  207917055 206628864  98.5G Microsoft basic data
/dev/sda4   207917056  271405055  63488000  30.3G Microsoft basic data
/dev/sda5  1928237056 1929158655    921600   450M Windows recovery environment
/dev/sda6  1929158656 1953523711  24365056  11.6G Windows recovery environment
/dev/sda7   271405056  364187647  92782592  44.2G Linux filesystem
/dev/sda8   364187648  399003647  34816000  16.6G Linux swap
/dev/sda9   399003648  432795647  33792000  16.1G Linux filesystem
/dev/sda10  432795648  486043647  53248000  25.4G Linux filesystem
/dev/sda11  486043648  805531647 319488000 152.4G Linux filesystem
/dev/sda12  805531648 1010331647 204800000  97.7G Linux filesystem
/dev/sda13 1010331648 1092943871  82612224  39.4G Linux filesystem
/dev/sda14 1092943872 1129807871  36864000  17.6G Linux swap
/dev/sda15 1129807872 1214441471  84633600  40.4G Linux filesystem
/dev/sda16 1214441472 1624160255 409718784 195.4G Linux filesystem
/dev/sda17 1624160256 1688621055  64460800  30.8G Linux filesystem
/dev/sda18 1688621056 1745649663  57028608  27.2G Linux filesystem
/dev/sda19 1745649664 1803347967  57698304  27.5G Linux filesystem

Partition table entries are not in disk order.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 10:37 pm
by JayM
Like I said it doesn't make much sense to me, but it's possible that the partition table types on the USB and the hard drive have to match for it to work on your machine and with your partitioning scheme. Stranger things have happened. Either it will work or it won't make any difference, but then we've at least eliminated that possibility.

If you don't have an extra USB stick you could download the latest monthly snapshot ISO that includes updates up to mid-July from Sourceforge and burn it to your USB after creating a gpt partition table on it with gparted in one of your other Linuxes. Then you'll only have a few updates remaining.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 11:23 pm
by jbMacAZ
Thanks. I'm trying those experiments. I'll report back when I get this sorted out. The md5 checked on the ISO downloads, so...

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Wed Aug 07, 2019 11:49 pm
by JayM
If it still doesn't work, you could boot with persistence and install the latest installer that's still being tested, using gdebi on the .deb file, and see if it works with that one. The current installer is 19.7.4 and the testing one is 19.8.
https://github.com/MX-Linux/gazelle-ins ... -folder-mx
If you could run it in a teminal with

Code: Select all

sudo minsiall -E
then copy and paste the terminal's text (within code tags) that might help in troubleshooting and/or debugging the new installer, even if it works for you. (I had that happen to me once: MX installed fine, but my terminal output showed a bug that was affecting others and provided the clue that allowed the developer to fix it.)

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 12:20 am
by jbMacAZ
OK, I got frustrated with making unbootable USB sticks, so I installed MX on an old swap partition (sda14) and gave Manjaro a new swap partition. The install went pretty much as expected although my user 1000 has the name demo. I can fix that later.

I still have sda19 open, so I will try the installer launched from a terminal as shown. I'll be back a bit later.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 12:31 am
by jbMacAZ
I got the new installer, but it is complaining about libqt5core5a >= 5.11.0-rc1 and mine is 5.7.1+dfsg-3+deb9u1

Sounds like it will take quite a few updates to get this working??

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 12:49 am
by JayM
Hmm, maybe 19.8 is intended for MX-19 which is based on Debian Buster. Here's version 19.7 from July that I know works on MX-18 as I've used it:
https://www95.zippyshare.com/v/iVQzYtN3/file.html
Uninstall 19.8 using gdebi prior to installing 19.7. :)

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 1:55 am
by jbMacAZ
Thanks. I'll take my chances on the antix 19 beta ISO.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 8:01 am
by fehlix
JayM wrote: Wed Aug 07, 2019 10:37 pm download the latest monthly snapshot ISO that includes updates up to mid-July from Sourceforge
That should have been probaly the first question to ask: What version of MX Linux ISO did OP used to try to install?
The latest version MX 18.3-July, should have all fixes, including those with a greater number of partitions.
I think running this on the latest LiveISO/USB:

Code: Select all

sudo partition-info  -f all
should show all partitions available on the system, and so should also the MX Installer.
If not than that would be a bug.
:puppy:

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 12:23 pm
by jbMacAZ
I used the 18.3 final linked on the forum home page. I was not able to boot the 18.3-july snapshot, it hung before getting to grub with "\EFI\BOOT\mmx64.efi - Not Found". With 18.3 final that message flashes briefly just before the grub menu appears. mmx64.efi appears to have absolutely nothing to do with MX-Linux. Since I was able to boot the "final" 18.3 I stopped there. The md5s match on my downloaded ISO's.

I had a 3 download fails on antix 19 b2, I'll try again later this morning.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 12:29 pm
by dolphin_oracle
you can also update the running live system, so no real need to download the july snapshot.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 12:51 pm
by jbMacAZ
I updated and remastered my liveUSB before installing MX18.3 over an old swap partition. It'll take me about an hour to DL antiX 19 b2.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 1:26 pm
by fehlix
jbMacAZ wrote: Thu Aug 08, 2019 12:23 pm it hung before getting to grub with "\EFI\BOOT\mmx64.efi - Not Found"
mmx64.efi - so your UEFI is trying to load EFI MokManager, which is not on the USBstick.
That might be related to an unsuccessful boot and leaving UEFI in the state to try load the EFI-MokManager at the next boot.
You can try to turn off secure boot and anything related to 3rd party secureboot eif-key's.
Or alternatively try to copy grubx64.efi to mmx64.efi on that stick on the ESP partition on the USBstick.
:puppy:

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 3:43 pm
by jbMacAZ
The antiX19b2 installer has the same first 15 partition limitation as MX-Linux 18.3.

about the mmx64.efi: Secure boot is off. I ran into the same thing (mmx64.efi not found) with the antiX beta. I worked around it by formatting a USB stick to fat32, mounting the ISO image and copying it to the usb. This still gave me the error on the next boot attempt. So I copied the \EFI\BOOT\ folders from my working 18.3 liveUSB to my hacked liveUSB, but I also hacked the grub.cfg. The replacement .efi files were larger on the 18.3 final ISO than the antiX ISO. I've had issues on Manjaro with not enough modules in their .efi files.

Since no one else has run into this liveUSB won't boot, there is probably an issue with my system, perhaps the BIOS is too stale. I need to narrow down the exact change that gives me bootable USBs. I can't rule out anything including flaky USB ports or sticks.

BTW, the new antiX looks kind of cool! I'll be looking forward to MX-19. (Writing from antiX 19-b2)

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 4:57 pm
by jbMacAZ
I was able to "fix" my liveUSB boot problem by substituting my bootx64.efi from MX18.0 onto the /EFI/BOOT/bootx64.efi on the antiX-19-b2 on the liveUSB ESP partition. The older (12-19-2018) .efi file is about 200K larger. This liveUSB had been made using the liveUSBMaker and previously did not boot.

I still have an open partition (19) if anyone needs me to test any changes to the installer. Thanks for all the help and suggestions.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 5:07 pm
by fehlix
jbMacAZ wrote: Thu Aug 08, 2019 4:57 pm I was able to "fix" my liveUSB boot problem by substituting my bootx64.efi from MX18.0 onto the /EFI/BOOT/bootx64.efi on the antiX-19-b2 on the liveUSB ESP partition. The older (12-19-2018) .efi file is about 200K larger. This liveUSB had been made using the liveUSBMaker and previously did not boot.
Intersting.. could you try also the suggested "fix", by coping MX18.3_July /EFI/BOOT/bootx64.efi to /EFI/BOOT/mmx64.efi
and also antiX-19-b2 /EFI/BOOT/bootx64.efi to /EFI/BOOT/mmx64.efi, resp.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 5:21 pm
by jbMacAZ
So I'll create new liveUSBs for the 18.3-july and antiX-19b2 and copy the files as directed. If those fail, I'll try using the 18.0 file onto mmx64.efi instead.

Meanwhile, here is the partition information you requested earlier, sorry about the delay.

Code: Select all

$ sudo partition-info  -f all
[sudo] password for demo: 
Name      Size   FS      Label
sda1  -   500M - Fat32 - ESP
sda2  -   128M -      
sda3  -  98.5G - ntfs  - OS
sda4  -  30.3G - ntfs  - Shared
sda5  -   450M - ntfs  - WINRETOOLS
sda6  -  11.6G - ntfs  - Image
sda7  -  44.2G - ext4  - MINT
sda8  -  16.6G - swap 
sda9  -  16.1G - ext2 
sda10 -  25.4G - ext4 
sda11 - 152.4G - ext4  - projects
sda12 -  97.7G - ext4  - bisect
sda13 -  39.4G - ext4 
sda14 -  17.6G - ext4  - rootMX18.3
sda15 -  40.4G - ext4  - Spare
sdb1  -  29.9G - Fat32 - MX-LINUX
sdc1  -  28.6G - ext4  - antiX-Live-usb
sdc2  -    50M - Fat32 - antiX-uefi
sda16 - 195.4G - ext4  - Backup
sda17 -  30.8G - ext4 
sda18 -  27.2G - ext4 
sda19 -  27.5G - ext4  - MXlinux
sda20 -  16.7G - ext4  - MXHome
sda21 -  17.1G - swap

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 5:40 pm
by fehlix
jbMacAZ wrote: Thu Aug 08, 2019 5:21 pm So I'll create new liveUSBs for the 18.3-july and antiX-19b2 and copy the files as directed. If those fail, I'll try using the 18.0 file onto mmx64.efi instead.
Yes, note on FAT32 onyl USB you have only 1 Partion. ON the LUM-create USB you have an additionl ESP partittion,
whith the relevant /BOOT/EFI folder.
jbMacAZ wrote: Thu Aug 08, 2019 5:21 pm Meanwhile, here is the partition information you requested earlier, sorry about the delay.

Code: Select all

$ sudo partition-info  -f all
..
So partition-info sees the partitions in question, someone from the MX installer guys will look into this, I guess.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 5:52 pm
by jbMacAZ
I tried the antiX experiment first. I made a new LUM liveUSB copied the bootx64.efi to mmx64.efi and tried to boot. This time no error message at all, just a black screen. Next I replaced the antix mmx64.efi with the bootx64.efi from MX18.0 (as mmx64.efi) and antiX19b2 did boot. I still saw the "mmx64.efi not found message" flash briefly before the grub menu appeared. I chose not to test for a black screen with 18.3! I could, if you think there is something helpful in that experiment, but I'm kind of hang averse on this system.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 6:03 pm
by fehlix
jbMacAZ wrote: Thu Aug 08, 2019 5:52 pm I tried the antiX experiment first. I made a new LUM liveUSB copied the bootx64.efi to mmx64.efi and tried to boot.
We are getting closer: Yes, please do copy: grubx64.efi to bootx64.efi and to mmx64.efi please try on either antiX and mx18.3-july, better would checking on both as the grub-menu has changed a bit, so we could also check this.
Do also confirm that you have either secure boot enabled or disabled.
EDIT: with the above copy of grubx64.efi to bootx64.efi , secure boot would not work anyway.
Thanks

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 6:09 pm
by jbMacAZ
I'll be back a bit later with the results.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Thu Aug 08, 2019 8:03 pm
by jbMacAZ
grubx64.efi fixes the problem when copied over either bootx64.efi or to mmx64.efi. In either case, there is no briefly flashing error message before grub appears.

With 18.3-July I first copied grubx64.efi over bootx64.efi and it booted fine. Then I restored the original bootx64.efi and copied grubx64.efi to mmx64.efi. This also booted. With antiX19b2 I copied grubx64.efi to bootx64.efi which also booted. All three tests used the same USB stick created with LUM. Prior to these modifications to the ESP partition, the liveUSB fails to boot on my system.

Edit: Secure boot is off on my system.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 5:54 pm
by jbMacAZ
Update: My new MX-18.3 installation still has the installer showing on the desktop. When I launch that installer, partitions above 15 are available for selection. So apparently, just the ISO's have this limitation, even though the liveUSB and the installation both have minstall version 19.7.4.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 7:22 pm
by fehlix
jbMacAZ wrote: Fri Aug 09, 2019 5:54 pm Update: My new MX-18.3 installation still has the installer showing on the desktop. When I launch that installer, partitions above 15 are available for selection. So apparently, just the ISO's have this limitation, even though the liveUSB and the installation both have minstall version 19.7.4.
So the ISO has also minstall version 19.7.4, and can't see partions nr 16 onwards on you gpt drive, but the LiveUSB can?

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 8:22 pm
by jbMacAZ
No! minstall on the liveUSB can not see beyond partition 15. Minstall (same version) running on my actual installation on sda14 can.

I went further and made a snapshot of my install and then used it to make a liveUSB. When I run that liveUSB, it CAN'T see the partitions above #15 either. Something about the liveUSB makes the higher partitions invisible to minstall.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 11:05 pm
by JayM
Can Thunar on the live USB see partitions 16 through 19?

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 11:10 pm
by jbMacAZ
Thunar sees all! Edit: except the swap partition

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 11:23 pm
by jbMacAZ
The only difference between the live USB and the installation is whether the system booted from a gpt HDD or an MBR USB stick. That shouldn't be relevant, but... This possibility was mentioned earlier (post #2)

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Fri Aug 09, 2019 11:33 pm
by JayM
jbMacAZ wrote: Fri Aug 09, 2019 11:23 pm The only difference between the live USB and the installation is whether the system booted from a gpt HDD or an MBR USB stick. That shouldn't be relevant, but... This possibility was mentioned earlier (post #2)
Do you mean MSDOS, as in the type of partition table? In Live USB Maker under the Advanced Options you can tell it to use a GPT partition table when it burns the ISO to the stick. Can you try that and see if your higher partitions are detected when you boot from it?

Also an installed MX boots using grub and the USB doesn't, so that's another possibility. Though I don't know why that should affect just the installer since Thunar on the USB is able to see all partitions. Hmm.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sat Aug 10, 2019 12:01 am
by jbMacAZ
Unfortunately, the gpt partition table did not make the liveUSB minstall see the higher partitions.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sat Aug 10, 2019 12:02 am
by JayM
Well, that eliminated that possibility. Thanks for trying it.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sat Aug 10, 2019 6:40 am
by fehlix
jbMacAZ wrote: Fri Aug 09, 2019 8:22 pm No! minstall on the liveUSB can not see beyond partition 15. Minstall (same version) running on my actual installation on sda14 can.

I went further and made a snapshot of my install and then used it to make a liveUSB. When I run that liveUSB, it CAN'T see the partitions above #15 either. Something about the liveUSB makes the higher partitions invisible to minstall.
Just aut of curiosity, would you mind to install MX Linux on an USBstick using MX installer, so to say you install to the USB as you would do on internal drive. Do a full install, and let the Grub install onto the ESP of the USB stick. UEFI should see the ESP on the USB at boot and should find the /EFI/BOOT/BOOTx64.efi on that stick automatically (at least in theory).
:puppy:

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sat Aug 10, 2019 7:51 pm
by jbMacAZ
The good news is that the USB stick installation booted without any manipulation of the ESP .efi files. The bad news is that the installer ignored my choice of ESP partition and installed grub to the hard drive not the USB. Boot repair did not give me the option of installing grub to the USB. I also discovered when installing MX, it is very important to make sure that the MX root partition label is unique. Otherwise, the install fails.

My test procedure - installing MX 18.3-July to a USB:
Format the USB to FAT32
- Add a second small FAT32 partition with ESP and BOOT flags
Used Live USB Maker to burn 18.3-July.ISO to a second USB
- copied the grubx64.efi to mmx64.efi on the liveUSB ESP partition
booted the liveUSB (secure boot off)
minstall
- set root to sdc1 (FAT32 USB with 2 partitions)
- changed the default MX root label
- set EFI partition to sdc2
booted successfully to MX-18.3-July on the USB (unless you count grub in the wrong ESP partition)

FWIW, the new liveUSB of 18.3-July did show partitions above 15 in the installer. Perhaps something broke in remastering my original 18.3-Final liveUSB. Also, antiX19b2 minstall failed to format the necessary partitions on the USB and aborted with a grayed out screen and a watch icon mouse cursor, so a USB install is not currently possible with antiX19.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sat Aug 10, 2019 8:21 pm
by fehlix
jbMacAZ wrote: Sat Aug 10, 2019 7:51 pm FWIW, the new liveUSB of 18.3-July did show partitions above 15 in the installer.
Right, so the message is on hd-type install onto USB mx-install'er can read partitions above 15, but on the LiveUSB-type install
it cannot.
jbMacAZ wrote: Sat Aug 10, 2019 7:51 pm Perhaps something broke in remastering my original 18.3-Final liveUSB.
Rather suspect something else... not sure .. like some kernel modules not loaded with the Live initrd needed for those "extended above 15" gpt partitions ... that's a kind of missing module hunting for the live-initrd ... :cool:

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sat Aug 10, 2019 9:57 pm
by jbMacAZ
One last observation on high partition numbers. If I fire up the liveUSB the partitions above 15 are not visible to minstall. If I then plug in another USB stick and restart the installer, then the other partitions ARE visible. When I eject that second USB and restart minstall, the partitions above 15 disappear from the installer but only the sdc partitions drop off lsblk.

Code: Select all

demo@mx1:~
$ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0     7:0    0   1.3G  1 loop /live/linux
sda       8:0    0 931.5G  0 disk 
├─sda1    8:1    0   500M  0 part 
├─sda2    8:2    0   128M  0 part 
├─sda3    8:3    0  98.5G  0 part 
├─sda4    8:4    0  30.3G  0 part 
├─sda5    8:5    0   450M  0 part 
├─sda6    8:6    0  11.6G  0 part 
├─sda7    8:7    0  44.2G  0 part 
├─sda8    8:8    0  16.6G  0 part [SWAP]
├─sda9    8:9    0  16.1G  0 part 
├─sda10   8:10   0  25.4G  0 part 
├─sda11   8:11   0 152.4G  0 part 
├─sda12   8:12   0  97.7G  0 part 
├─sda13   8:13   0  39.4G  0 part 
├─sda14   8:14   0  17.6G  0 part 
├─sda15   8:15   0  40.4G  0 part 
├─sda16 259:0    0 195.4G  0 part 
├─sda17 259:1    0  30.8G  0 part 
├─sda18 259:2    0  27.2G  0 part 
├─sda19 259:3    0  27.5G  0 part 
├─sda20 259:4    0  16.7G  0 part 
├─sda21 259:5    0  17.1G  0 part [SWAP]
└─sda22 259:6    0  25.8G  0 part 
sdb       8:16   1  28.7G  0 disk 
├─sdb1    8:17   1  21.4G  0 part /live/boot-dev
└─sdb2    8:18   1    50M  0 part 
sdc       8:32   1  59.8G  0 disk 
├─sdc1    8:33   1  59.3G  0 part 
└─sdc2    8:34   1   489M  0 part 
sr0      11:0    1  1024M  0 rom

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 6:48 am
by fehlix
jbMacAZ wrote: Sat Aug 10, 2019 9:57 pm One last observation on high partition numbers. If I fire up the liveUSB the partitions above 15 are not visible to minstall. If I then plug in another USB stick and restart the installer, then the other partitions ARE visible. When I eject that second USB and restart minstall, the partitions above 15 disappear from the installer but only the sdc partitions drop off lsblk.
That't an important observation. Also please confirm that in both variants LiveUSB and "installed"-USB lsblk and blkid provides the full list of the partitions, as lsblk /blkid is used by minstall to list partitions.
Thanks

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 10:18 am
by dolphin_oracle
Am I reading this right that there are 2 issues?

1. Partitions over 15 don't always show up?

2. Installs to usb drives seem to ignore the esp selected?

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 10:21 am
by fehlix
dolphin_oracle wrote: Sun Aug 11, 2019 10:18 am 1. Partitions over 15 don't always show up?
That's a weird one...
dolphin_oracle wrote: Sun Aug 11, 2019 10:18 am 2. Installs to usb drives seem to ignore the esp selected?
That's probably a minor issue, I guess easy to fix.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 1:22 pm
by jbMacAZ
dolphin_oracle wrote: Sun Aug 11, 2019 10:18 am Am I reading this right that there are 2 issues?
3 issues, if you count the liveUSB boots to "\EFI\BOOT\mmx64.efi - Not Found" unless I manipulate the .efi files in the liveUSB ESP partition. Copying the existing grubx64.efi to mmx64.efi fixes it on my system (my "secure" boot is always off.)

A 4th is the partition format fails when installing to a USB from a liveUSB of antiX19b2.
fehlix wrote: Sun Aug 11, 2019 6:48 am both variants LiveUSB and "installed"-USB lsblk and blkid provides the full list of the partitions
As for the lsblk, that is confirmed on the liveUSB. I'll need to rerun the experiments for installed lsblk and both liveUSB and installed for blkid.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 3:30 pm
by dolphin_oracle
One problem at a time I think...

First the partitions.

I would like to see the /var/log/minstall.log for an instance when minstall doesn't list all the partitions.

for the same instance, then I would also like to see the raw output of this command

Code: Select all

$ lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL
for now, please stick to the mx18.3 iso with updated mx-installer to Installer version: 19.7.4, just so we are on same page.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 3:44 pm
by jbMacAZ
I've now confirmed that blkid and lsblk show all partitions whether on a liveUSB or an installation. minstall shows all suitable partitions when run either from an installation on a HDD or from a liveUSB when a second USB stick is present. If just the liveUSB stick is mounted, minstall does not see partitions greater than 15 on my system's HDD.

I've also pieced together the most likely path that gave me an install with the user demo and left installer on the desktop.

I made a liveUSB of the 18.3-Final with root and home persistence and with the toram option. Once I booted the live USB, I updated and remastered. Then I installed the liquorix kernel and remastered again. After rebooting I made a snapshot with personal data included. This is last option seems to be the problem - don't snapshot "personal" data with liveUSB user "demo". When I installed that snapshot, the user setup screen never appeared. That left me with user demo and left the installer (minstall) on the desktop of the installation. This is a seriously obscure corner case. BTW, the personal data was properly retained in my snapshot installation.

I have to say though, all these anitX/MX tools are really quite cool. Edit: OK, now to the partion logs...

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 4:05 pm
by jbMacAZ
minstall not showing partitions > 15 (liveUSB 18.3-July snapshot)

Code: Select all

demo@mx1:~
$ cat /var/log/minstall.log
2019-08-11 15:52:31.667 DBG default: Installer version: 19.7.4
2019-08-11 15:52:31.774 DBG default: +++ void MInstall::startup() +++
2019-08-11 15:52:31.774 DBG default: "uname -m | grep -q i686"
2019-08-11 15:52:31.809 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:31.809 DBG default: "test -d /sys/firmware/efi"
2019-08-11 15:52:31.816 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:31.816 DBG default: uefi = true
2019-08-11 15:52:31.816 DBG default: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
2019-08-11 15:52:31.864 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:31.864 DBG default: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
2019-08-11 15:52:31.878 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:31.878 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2019-08-11 15:52:31.886 DBG default: "locale -a | grep -Ev '^(C|POSIX)\\.?' | grep -E 'utf8|UTF-8'"
2019-08-11 15:52:31.893 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:31.894 DBG default: "grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus"
2019-08-11 15:52:33.565 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:33.566 DBG default: "/bin/ls -1 /home | grep -Ev '(lost\\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]"
2019-08-11 15:52:33.574 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:33.575 DBG default: "test -d /live/linux/home/demo"
2019-08-11 15:52:33.579 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:33.579 DBG default: "dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'"
2019-08-11 15:52:33.634 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:33.635 DBG default: +++ void MInstall::buildServiceList() +++
2019-08-11 15:52:33.640 DBG default: +++ void MInstall::updatePartitionWidgets() +++
2019-08-11 15:52:33.640 DBG default: "/sbin/partprobe"
2019-08-11 15:52:46.515 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:46.515 DBG default: "blkid -c /dev/null"
2019-08-11 15:52:47.901 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:47.901 DBG default: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\  -f1 | cut -d/ -f3"
2019-08-11 15:52:48.115 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:48.116 DBG default: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL | grep -E '^(disk|part)'"
2019-08-11 15:52:48.159 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:48.159 DBG default: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
2019-08-11 15:52:48.166 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:48.175 DBG default: "blkid /dev/sdb | grep -q PTTYPE=\\\"gpt\\\""
2019-08-11 15:52:48.181 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:52:48.182 DBG default: Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
2019-08-11 15:52:48.182 DBG default: "sda" 1000204886016 "TOSHIBA DT01ACA1" "" | true true false false false false
2019-08-11 15:52:48.182 DBG default: "sda1" 524288000 "" "vfat" | false true false true false false
2019-08-11 15:52:48.182 DBG default: "sda2" 134217728 "" "" | false true false false false false
2019-08-11 15:52:48.182 DBG default: "sda3" 105793978368 "" "ntfs" | false true false false false false
2019-08-11 15:52:48.182 DBG default: "sda4" 32505856000 "" "ntfs" | false true false false false false
2019-08-11 15:52:48.182 DBG default: "sda5" 471859200 "" "ntfs" | false true false false false false
2019-08-11 15:52:48.182 DBG default: "sda6" 12474908672 "" "ntfs" | false true false false false false
2019-08-11 15:52:48.182 DBG default: "sda7" 47504687104 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda8" 17825792000 "" "swap" | false true false false true true
2019-08-11 15:52:48.182 DBG default: "sda9" 17301504000 "" "ext2" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda10" 27262976000 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda11" 163577856000 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda12" 104857600000 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda13" 42297458688 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda14" 18874368000 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sda15" 43332403200 "" "ext4" | false true false false true false
2019-08-11 15:52:48.182 DBG default: "sdb" 30752636928 "Ultra Fit" "" | true false true false false false
2019-08-11 15:52:48.182 DBG default: "sdb1" 23009951744 "" "ext4" | false false true false true false
2019-08-11 15:52:48.183 DBG default: "sdb2" 52428800 "" "vfat" | false false true true false false
2019-08-11 15:52:48.183 DBG default: "sda16" 209776017408 "" "ext4" | false false true false true false
2019-08-11 15:52:48.183 DBG default: "sda17" 33003929600 "" "ext4" | false false true false true false
2019-08-11 15:52:48.183 DBG default: "sda18" 29198647296 "" "ext4" | false false true false true false
2019-08-11 15:52:48.183 DBG default: "sda19" 29541531648 "" "ext4" | false false true false true false
2019-08-11 15:52:48.183 DBG default: "sda20" 17904435200 "" "ext4" | false false true false true false
2019-08-11 15:52:48.183 DBG default: "sda21" 18323865600 "" "swap" | false false true false true true
2019-08-11 15:52:48.183 DBG default: "sda22" 27713863680 "" "ext4" | false false true false true false

Code: Select all

$ lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL
loop loop0  1413382144  squashfs  
disk sda  1000204886016    TOSHIBA\x20DT01ACA1
part sda1 08A4-5E19 524288000 c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat ESP 
part sda2  134217728 e3c9e316-0b5c-4db8-817d-f92df00215ae   
part sda3 3648FF5E48FF1B77 105793978368 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs OS 
part sda4 C67EB4A77EB49223 32505856000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs Shared 
part sda5 90CC6126CC610834 471859200 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs WINRETOOLS 
part sda6 2EC662C7C6628EC1 12474908672 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs Image 
part sda7 4c60405c-d022-4d95-bf92-e1b151e8992e 47504687104 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 MINT 
part sda8 5b990e61-9ddb-428c-b4d8-eaf70f9bdbe5 17825792000 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap  
part sda9 c1d808de-60cc-44af-9fd2-c47a270e9aa4 17301504000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext2  
part sda10 1031ac34-1399-4498-976f-58fdedb3044b 27262976000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda11 36920ff9-36e1-43ff-94e4-58985e78bd89 163577856000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 projects 
part sda12 51c60e72-96d0-4fa3-8b3d-4361022b3587 104857600000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 bisect 
part sda13 b676e546-9459-4d8e-9720-c1e7e3fdcc3c 42297458688 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda14 b05b83da-d22f-4dec-bf01-c63f2b1e12de 18874368000 44479540-f297-41b2-9af7-d131d5f0458a ext4 rootMX18.3 
part sda15 9f5352a2-bcc3-4a83-858f-5d455fcf7b11 43332403200 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Spare 
disk sdb  30752636928    Ultra\x20Fit\x20\x20\x20\x20\x20\x20\x20
part sdb1 1a5f3c48-5e96-4718-b53e-5bbe7af0eeff 23009951744 0x83 ext4 Live-usb 
part sdb2 9910-BC36 52428800 0xef vfat Live-uefi 
rom sr0  1073741312    DVD+-RW\x20SU-208GB
part sda16 b8e1d2b0-c2dc-4d1f-b1fe-511d4045ce33 209776017408 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Backup 
part sda17 d8cd1ae8-8a9e-40ea-8170-ed0f0e029300 33003929600 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda18 727b02f4-53f0-42e2-9a58-2ba75f7a7922 29198647296 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda19 87c92711-adfa-4a47-8df1-7cf2afdd9a18 29541531648 44479540-f297-41b2-9af7-d131d5f0458a ext4 MXLinux 
part sda20 a2268d9e-fa4b-49db-b381-1fa7f0d1b1d6 17904435200 44479540-f297-41b2-9af7-d131d5f0458a ext4 homeMX 
part sda21 d7a86f99-16e2-4b6e-8c50-166856186622 18323865600 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap  
part sda22 68034b16-7395-4c48-9a28-4db4454ba320 27713863680 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 MiscLinux
After plugging in second USB and restarting minstall (all suitable partitions showing)

Code: Select all

 <snip>
2019-08-11 15:59:53.810 DBG default: Installer version: 19.7.4
2019-08-11 15:59:53.866 DBG default: +++ void MInstall::startup() +++
2019-08-11 15:59:53.866 DBG default: "uname -m | grep -q i686"
2019-08-11 15:59:53.894 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:53.894 DBG default: "test -d /sys/firmware/efi"
2019-08-11 15:59:53.896 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:53.896 DBG default: uefi = true
2019-08-11 15:59:53.896 DBG default: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
2019-08-11 15:59:53.909 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:53.909 DBG default: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
2019-08-11 15:59:53.923 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:53.923 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2019-08-11 15:59:53.924 DBG default: "locale -a | grep -Ev '^(C|POSIX)\\.?' | grep -E 'utf8|UTF-8'"
2019-08-11 15:59:53.928 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:53.928 DBG default: "grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus"
2019-08-11 15:59:55.445 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:55.445 DBG default: "/bin/ls -1 /home | grep -Ev '(lost\\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]"
2019-08-11 15:59:55.454 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:55.454 DBG default: "test -d /live/linux/home/demo"
2019-08-11 15:59:55.458 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:55.458 DBG default: "dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'"
2019-08-11 15:59:55.513 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 15:59:55.513 DBG default: +++ void MInstall::buildServiceList() +++
2019-08-11 15:59:55.515 DBG default: +++ void MInstall::updatePartitionWidgets() +++
2019-08-11 15:59:55.515 DBG default: "/sbin/partprobe"
2019-08-11 16:00:08.323 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:08.324 DBG default: "blkid -c /dev/null"
2019-08-11 16:00:09.731 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:09.732 DBG default: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\  -f1 | cut -d/ -f3"
2019-08-11 16:00:09.894 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:09.895 DBG default: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL | grep -E '^(disk|part)'"
2019-08-11 16:00:09.922 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:09.923 DBG default: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
2019-08-11 16:00:09.934 DBG default: Exit: 0 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:09.936 DBG default: "blkid /dev/sdb | grep -q PTTYPE=\\\"gpt\\\""
2019-08-11 16:00:09.947 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:09.947 DBG default: "blkid /dev/sdc | grep -q PTTYPE=\\\"gpt\\\""
2019-08-11 16:00:09.958 DBG default: Exit: 1 QProcess::ExitStatus(NormalExit)
2019-08-11 16:00:09.959 DBG default: Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
2019-08-11 16:00:09.959 DBG default: "sda" 1000204886016 "TOSHIBA DT01ACA1" "" | true true false false false false
2019-08-11 16:00:09.959 DBG default: "sda1" 524288000 "" "vfat" | false true false true false false
2019-08-11 16:00:09.959 DBG default: "sda2" 134217728 "" "" | false true false false false false
2019-08-11 16:00:09.959 DBG default: "sda3" 105793978368 "" "ntfs" | false true false false false false
2019-08-11 16:00:09.959 DBG default: "sda4" 32505856000 "" "ntfs" | false true false false false false
2019-08-11 16:00:09.959 DBG default: "sda5" 471859200 "" "ntfs" | false true false false false false
2019-08-11 16:00:09.959 DBG default: "sda6" 12474908672 "" "ntfs" | false true false false false false
2019-08-11 16:00:09.959 DBG default: "sda7" 47504687104 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda8" 17825792000 "" "swap" | false true false false true true
2019-08-11 16:00:09.960 DBG default: "sda9" 17301504000 "" "ext2" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda10" 27262976000 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda11" 163577856000 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda12" 104857600000 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda13" 42297458688 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda14" 18874368000 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sda15" 43332403200 "" "ext4" | false true false false true false
2019-08-11 16:00:09.960 DBG default: "sdb" 30752636928 "Ultra Fit" "" | true false true false false false
2019-08-11 16:00:09.960 DBG default: "sdb1" 23009951744 "" "ext4" | false false true false true false
2019-08-11 16:00:09.960 DBG default: "sdb2" 52428800 "" "vfat" | false false true true false false
2019-08-11 16:00:09.960 DBG default: "sdc" 32229130240 "Mass Storage" "" | true false false false false false
2019-08-11 16:00:09.960 DBG default: "sdc1" 31457214464 "" "vfat" | false false false false false false
2019-08-11 16:00:09.961 DBG default: "sda16" 209776017408 "" "ext4" | false false false false true false
2019-08-11 16:00:09.961 DBG default: "sda17" 33003929600 "" "ext4" | false false false false true false
2019-08-11 16:00:09.961 DBG default: "sda18" 29198647296 "" "ext4" | false false false false true false
2019-08-11 16:00:09.961 DBG default: "sda19" 29541531648 "" "ext4" | false false false false true false
2019-08-11 16:00:09.961 DBG default: "sda20" 17904435200 "" "ext4" | false false false false true false
2019-08-11 16:00:09.961 DBG default: "sda21" 18323865600 "" "swap" | false false false false true true
2019-08-11 16:00:09.961 DBG default: "sda22" 27713863680 "" "ext4" | false false false false true false

Code: Select all

loop loop0  1413382144  squashfs  
disk sda  1000204886016    TOSHIBA\x20DT01ACA1
part sda1 08A4-5E19 524288000 c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat ESP 
part sda2  134217728 e3c9e316-0b5c-4db8-817d-f92df00215ae   
part sda3 3648FF5E48FF1B77 105793978368 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs OS 
part sda4 C67EB4A77EB49223 32505856000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs Shared 
part sda5 90CC6126CC610834 471859200 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs WINRETOOLS 
part sda6 2EC662C7C6628EC1 12474908672 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs Image 
part sda7 4c60405c-d022-4d95-bf92-e1b151e8992e 47504687104 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 MINT 
part sda8 5b990e61-9ddb-428c-b4d8-eaf70f9bdbe5 17825792000 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap  
part sda9 c1d808de-60cc-44af-9fd2-c47a270e9aa4 17301504000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext2  
part sda10 1031ac34-1399-4498-976f-58fdedb3044b 27262976000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda11 36920ff9-36e1-43ff-94e4-58985e78bd89 163577856000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 projects 
part sda12 51c60e72-96d0-4fa3-8b3d-4361022b3587 104857600000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 bisect 
part sda13 b676e546-9459-4d8e-9720-c1e7e3fdcc3c 42297458688 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda14 b05b83da-d22f-4dec-bf01-c63f2b1e12de 18874368000 44479540-f297-41b2-9af7-d131d5f0458a ext4 rootMX18.3 
part sda15 9f5352a2-bcc3-4a83-858f-5d455fcf7b11 43332403200 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Spare 
disk sdb  30752636928    Ultra\x20Fit\x20\x20\x20\x20\x20\x20\x20
part sdb1 1a5f3c48-5e96-4718-b53e-5bbe7af0eeff 23009951744 0x83 ext4 Live-usb 
part sdb2 9910-BC36 52428800 0xef vfat Live-uefi 
disk sdc  32229130240    Mass\x20Storage\x20\x20\x20\x20
part sdc1 CC36-80A8 31457214464 0xc vfat  
rom sr0  1073741312    DVD+-RW\x20SU-208GB
part sda16 b8e1d2b0-c2dc-4d1f-b1fe-511d4045ce33 209776017408 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Backup 
part sda17 d8cd1ae8-8a9e-40ea-8170-ed0f0e029300 33003929600 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda18 727b02f4-53f0-42e2-9a58-2ba75f7a7922 29198647296 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda19 87c92711-adfa-4a47-8df1-7cf2afdd9a18 29541531648 44479540-f297-41b2-9af7-d131d5f0458a ext4 MXLinux 
part sda20 a2268d9e-fa4b-49db-b381-1fa7f0d1b1d6 17904435200 44479540-f297-41b2-9af7-d131d5f0458a ext4 homeMX 
part sda21 d7a86f99-16e2-4b6e-8c50-166856186622 18323865600 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap  
part sda22 68034b16-7395-4c48-9a28-4db4454ba320 27713863680 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 MiscLinux

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 4:36 pm
by dolphin_oracle
can you give us a screen shot of the combo box entry with the missing partitions and one with the partitions showing?

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 5:02 pm
by dolphin_oracle
also, do you have a disc in your optical drive?

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 5:19 pm
by jbMacAZ
Missing partitions
https://drive.google.com/open?id=1JSMNy ... FxxcL1q-QI

All suitable partitions
https://drive.google.com/open?id=1xBET- ... PlbKxr-NeG

Edit: I have an optical drive but there is nothing in it.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 6:13 pm
by dolphin_oracle
Ok great thanks.

I've got a working theory that I need to test. Thanks for sticking with this. If my local test works out I'll have something for you to try to confirm.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 7:07 pm
by dolphin_oracle
I've duplicated your environment in a test situation. the problem is in the filter that removes the boot device from the list of available install devices.

to test.

edit /usr/share/gazelle-installer-data/installer.conf and change the "INSTALL_FROM_ROOT" from false to true. start minstall as usually and see if your partitions show up.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 7:30 pm
by jbMacAZ
Changing "INSTALL_FROM_ROOT_DEVICE" to true does give me the other partitions.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 8:04 pm
by dolphin_oracle
Ok great!

I've narrowed the problem with drive listing down to a weird issue in lsblk that the installer code doesn't account for. what happens is that for some reason, partitions after 15 are listed after all other drivers are also listed. so you get sda1-15, sdb1-15, sdc-1-15, then sda15-? and so on. the problem comes when we apply the "isBoot" parameter, where partitions after the boot drive get tagged as boot partitions as well. the bug is broken when you insert a second usb disk because that disk is listed between the boot disk and the extra +15 partitions, and since that disk is not a boot disk, the extra partitions aren't tagged as boot partitions.

This shouldn't be too hard to fix, now that we have the problem zeroed in. Thank you!

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 8:11 pm
by jbMacAZ
You're welcome! I was beginning to suspect that some status was getting stuck after the boot device partitions, reset by an extra device in the list. Very weird that the partitions weren't all together... I guess that's cruft on an old drive that has been re-partitioned a time or two.

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 9:19 pm
by fehlix
dolphin_oracle wrote: Sun Aug 11, 2019 8:04 pm This shouldn't be too hard to fix, now that we have the problem zeroed in.
A quick fix, without changing to much logic within the code would be to sort the output of lsblk by the 2nd field,
so that the isBoot-tag get's not wrongly assigned for partitions above 15:

Code: Select all

lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL | LANG=C sort -k2
would produce somethig like:

Code: Select all

loop loop0  1413382144  squashfs   
disk sda  1000204886016    TOSHIBA\x20DT01ACA1
part sda1 08A4-5E19 524288000 c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat ESP 
part sda10 1031ac34-1399-4498-976f-58fdedb3044b 27262976000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda11 36920ff9-36e1-43ff-94e4-58985e78bd89 163577856000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 projects 
part sda12 51c60e72-96d0-4fa3-8b3d-4361022b3587 104857600000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 bisect 
part sda13 b676e546-9459-4d8e-9720-c1e7e3fdcc3c 42297458688 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda14 b05b83da-d22f-4dec-bf01-c63f2b1e12de 18874368000 44479540-f297-41b2-9af7-d131d5f0458a ext4 rootMX18.3 
part sda15 9f5352a2-bcc3-4a83-858f-5d455fcf7b11 43332403200 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Spare 
part sda16 b8e1d2b0-c2dc-4d1f-b1fe-511d4045ce33 209776017408 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 Backup 
part sda17 d8cd1ae8-8a9e-40ea-8170-ed0f0e029300 33003929600 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda18 727b02f4-53f0-42e2-9a58-2ba75f7a7922 29198647296 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4  
part sda19 87c92711-adfa-4a47-8df1-7cf2afdd9a18 29541531648 44479540-f297-41b2-9af7-d131d5f0458a ext4 MXLinux 
part sda2  134217728 e3c9e316-0b5c-4db8-817d-f92df00215ae   
part sda20 a2268d9e-fa4b-49db-b381-1fa7f0d1b1d6 17904435200 44479540-f297-41b2-9af7-d131d5f0458a ext4 homeMX 
part sda21 d7a86f99-16e2-4b6e-8c50-166856186622 18323865600 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap  
part sda22 68034b16-7395-4c48-9a28-4db4454ba320 27713863680 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 MiscLinux 
part sda3 3648FF5E48FF1B77 105793978368 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs OS 
part sda4 C67EB4A77EB49223 32505856000 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs Shared 
part sda5 90CC6126CC610834 471859200 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs WINRETOOLS 
part sda6 2EC662C7C6628EC1 12474908672 de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs Image 
part sda7 4c60405c-d022-4d95-bf92-e1b151e8992e 47504687104 0fc63daf-8483-4772-8e79-3d69d8477de4 ext4 MINT 
part sda8 5b990e61-9ddb-428c-b4d8-eaf70f9bdbe5 17825792000 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap  
part sda9 c1d808de-60cc-44af-9fd2-c47a270e9aa4 17301504000 0fc63daf-8483-4772-8e79-3d69d8477de4 ext2  
disk sdb  30752636928    Ultra\x20Fit\x20\x20\x20\x20\x20\x20\x20
part sdb1 1a5f3c48-5e96-4718-b53e-5bbe7af0eeff 23009951744 0x83 ext4 Live-usb 
part sdb2 9910-BC36 52428800 0xef vfat Live-uefi 
disk sdc  32229130240    Mass\x20Storage\x20\x20\x20\x20
part sdc1 CC36-80A8 31457214464 0xc vfat  
rom sr0  1073741312    DVD+-RW\x20SU-208GB
:puppy:

Re: I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Sun Aug 11, 2019 9:32 pm
by jbMacAZ
With the unsanctioned workaround, I was able to install MX18.3 to /dev/sda19 with /home on sda20. Grub install failed (complained about error writing NVRAM). I think the conflict comes from the MX-Linux already on sda14 or perhaps the USB install's grub which is still first in boot order. But Manjaro owns my grub and it found and boots both MX HDD installs. I'll mark this solved when the official fix is verified. Thanks again for the support.

Re: [solved]I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Mon Aug 19, 2019 2:06 pm
by jbMacAZ
I tested the new antiX19b3 ISO and its installer "sees" all of my suitable partitions. Thank you.

I still had to adjust the .efi files in the FAT32 ESP partition, to get antiX liveUSB to boot. debian-live-10.0.0-amd64-cinnamon.iso has the same problem and the mmx64.efi workaround also works. I have to assume this has more to do with some peculiarity of my system rather being a widespread issue.

Re: [solved]I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Mon Aug 19, 2019 4:56 pm
by fehlix
jbMacAZ wrote: Mon Aug 19, 2019 2:06 pm I tested the new antiX19b3 ISO and its installer "sees" all of my suitable partitions. Thank you.

I still had to adjust the .efi files in the FAT32 ESP partition, to get antiX liveUSB to boot. debian-live-10.0.0-amd64-cinnamon.iso has the same problem and the mmx64.efi workaround also works. I have to assume this has more to do with some peculiarity of my system rather being a widespread issue.
You might check whether you have a not-yet enrolled MOK key pending for enrollment. (That's stored with the UEFI.)
If so even when booting with disabled secure boot, it might be that UEFI tries to trigger the enrollment process during boot.
You can check enrolled and not-yet enrolled (new) MOK-keys, after installing "mokutil"
with this

Code: Select all

sudo mokutil --list-new
and/or

Code: Select all

sudo mokutil --list-enrolled
If anything is showing up you might "clear" the MOK-list with

Code: Select all

mokutil --reset
What I'm unsure about it is the "reset", whether this would work without having mokmanager in place when booting.
Perhaps you boot with ISO which provide a mokmanager (latest Debian / Ubuntu),
:puppy:

Re: [solved]I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Mon Aug 19, 2019 8:44 pm
by jbMacAZ
The list-new had two keys for openSUSE, the list-enrolled was empty. Resetting did clear the list-new, without needing mokmanager. The problem still persists, except with the suggested .efi workaround.

Re: [solved]I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Mon Aug 19, 2019 10:13 pm
by fehlix
jbMacAZ wrote: Mon Aug 19, 2019 8:44 pm The list-new had two keys for openSUSE, the list-enrolled was empty. Resetting did clear the list-new, without needing mokmanager. The problem still persists, except with the suggested .efi workaround.
I fear it's a bit more .. you probably still see the keys with
mokutil --list-delete
which is "List keys to be deleted"
And this is the crucial bit: The actual process of adding/deleting/revoking keys is done during boot through shim/mokmanager combo.
As long as there is something not "finished" or marked as to do, the process at boot with UEFI triggers shim to call mokmanager. :eek:
:puppy:

Re: [solved]I want to install MX-18.3 to partition #19 on my HDD, but...

Posted: Tue Aug 20, 2019 3:33 am
by jbMacAZ
While --list-delete also came up empty, loading a Ubuntu liveUSB did invoke mok. It apparently was sufficient to run it even though I didn't know what password it wanted. Anyway, this solved the issue, and now my Debian liveUSBs boot without manipulating the ESP .efi files. Thank you so much.
All times are UTC-04:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited