Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

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

MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

Message
Author
jacklarge
Forum Novice
Forum  Novice
Posts: 10
Joined: Sat Apr 14, 2018 7:49 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#21 Post by jacklarge » Tue Apr 17, 2018 1:49 pm

dolphin_oracle wrote:new installer update in the repo this morning that should work better in auto-installer mode. also fixed a few other odd problems. Only been tested so far with mmcblk devices, but they do have a similar partition numbering scheme to nmve so hopefully things work better.

There is some additional debugging info in the text output when you run from the cli, so please post any issues and feedback.

Thanks!
Cheers Dolphin. Excited. I’ll try it after dinner when I’ve calmed down a bit (I’m such a nerd).
Old enough to remember the Internet when graphics meant ascii art.
Dell XPS 13 9360 - 16GB - 512GB - i7

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16174
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#22 Post by Stevo » Tue Apr 17, 2018 4:10 pm

What brand of drive is it? Apparently the Debian kernel we backported is misconfigured for at least one type of Intel drive, though there is a boot workaround: http://forums.debian.net/viewtopic.php?f=5&t=137275

jacklarge
Forum Novice
Forum  Novice
Posts: 10
Joined: Sat Apr 14, 2018 7:49 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#23 Post by jacklarge » Wed Apr 18, 2018 8:07 am

Stevo wrote:What brand of drive is it? Apparently the Debian kernel we backported is misconfigured for at least one type of Intel drive, though there is a boot workaround: http://forums.debian.net/viewtopic.php?f=5&t=137275
Stevo it's a Toshiba - I'll check that out as while it went a lot further in the install this time when it came to installing GRUB it failed. And I've had issues with reinstallation using MX Boot Repair (i.e. it doesn't work).
Old enough to remember the Internet when graphics meant ascii art.
Dell XPS 13 9360 - 16GB - 512GB - i7

clicktician
Forum Regular
Forum Regular
Posts: 140
Joined: Sat May 02, 2015 4:35 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#24 Post by clicktician » Wed Apr 18, 2018 9:19 am

I ran into this exact same issue on my HP last week. I followed the Wiki instructions for manual partitioning a small ESP (see Jerry's link), and re-ran the installation with zero problems.
Son, someday all this will belong to your ex wife.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9298
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#25 Post by dolphin_oracle » Wed Apr 18, 2018 9:43 am

jacklarge wrote:
Stevo wrote:What brand of drive is it? Apparently the Debian kernel we backported is misconfigured for at least one type of Intel drive, though there is a boot workaround: http://forums.debian.net/viewtopic.php?f=5&t=137275
Stevo it's a Toshiba - I'll check that out as while it went a lot further in the install this time when it came to installing GRUB it failed. And I've had issues with reinstallation using MX Boot Repair (i.e. it doesn't work).
The text output from the grub install would be helpful thanks!

also, the output of the following command would be useful

Code: Select all

parted devicename -l

***edit*** crap, I found a typo that will potentially lead to a grub install failure. I will fix tonight.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9298
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#26 Post by dolphin_oracle » Wed Apr 18, 2018 1:33 pm

if possible, I would like to see the output of the parted command above AFTER the autoinstall starts copying to the drive, please. Just open a terminal and run the command, it won't hurt anything.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9298
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#27 Post by dolphin_oracle » Thu Apr 19, 2018 8:49 am

new installer fixes problem with grub installer, I think. At least it should fix any partition naming issues with the nvme naming format.

The output of that parted command

Code: Select all

parted devicename -l
while the installer is copying would be very beneficial, as I have no nvme drives to test with.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

jacklarge
Forum Novice
Forum  Novice
Posts: 10
Joined: Sat Apr 14, 2018 7:49 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#28 Post by jacklarge » Thu Apr 19, 2018 2:01 pm

Sorry for not getting back to you Dolphin. Decided to reinstall the working image of Ubuntu I had before all the messing about started as I thought things were getting a bit weird.
Then once I had a proper booting disk I then partitioned the disk and installed MX successfully (without any issues) as a second device. THEN when that worked i deleted the Ubuntu partition and resized the MX parition and even that worked fine. This was all done yesterday evening so it may well be that your fix was working. While I didn't capture that set of install commands - I did get the first (failed set from attempted install on 17/04):

Code: Select all

sudo minstall
yes
Error: device /dev/nvme0n1p3 is not mounted
The operation has completed successfully.
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: done                           
Creating filesystem with 120567633 4k blocks and 30146560 inodes
Filesystem UUID: 03af8120-bbce-4b44-8c3c-f921b8b3ba51
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
    102400000

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done    

mke2fs 1.43.4 (31-Jan-2017)
/dev/nvme0n1p3 contains a ext4 file system labelled 'rootMX17'
    created on Tue Apr 17 20:33:53 2018
Discarding device blocks: done                           
Creating filesystem with 120567633 4k blocks and 30146560 inodes
Filesystem UUID: 85acff9e-0d8c-44e6-a3dc-fc69ab4435a9
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
    102400000

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done    

  make-fstab: Create new /etc/fstab
  make-fstab: Put 0 hard drive entries into /etc/fstab
dpkg-query: package 'gpm' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
nfsd not running
boot for grub routine =  "nvme0n1p2"
"mount /dev/nvme0n1p2 /mnt/antiX/boot/efi"
mount: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
Exit code:  8192
"chroot /mnt/antiX grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX17 --recheck"
Installing for x86_64-efi platform.
grub-install: error: /boot/efi doesn't look like an EFI partition.
Exit code:  256
"chroot /mnt/antiX grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX17 --recheck"
Installing for x86_64-efi platform.
grub-install: error: /boot/efi doesn't look like an EFI partition.
Exit code:  256
Deferring virtual terminal setup until console accessible.
"hwclock --hctosys"
Exit code:  0
"umount -R /mnt/antiX"
Exit code:  0
"mount /dev/nvme0n1p3 /mnt/antiX"
Exit code:  0
sed: can't read /mnt/antiX/usr/local/share/appdata/panels/vertical/panel/xfce4-orageclock-plugin-1.rc: No such file or directory
sed: can't read /mnt/antiX/usr/local/share/appdata/panels/horizontal/panel/xfce4-orageclock-plugin-1.rc: No such file or directory
"chroot /mnt/antiX localize-repo default"
Exit code:  0
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
"cp -a /mnt/antiX/etc/skel /mnt/antiX/home"
Exit code:  0
"mv -f /mnt/antiX/home/skel /mnt/antiX/home/john"
Exit code:  0
"chown -R demo.users /mnt/antiX/home/john"
Exit code:  0
umount: /mnt/antiX/proc: not mounted
umount: /mnt/antiX/sys: not mounted
umount: /mnt/antiX/dev/shm: mountpoint not found
umount: /mnt/antiX/dev: not mounted
And this is what parted -l gives now:

Code: Select all

Model: Unknown (unknown)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                  Flags
 1      17.4kB  250MB   250MB   fat16           EFI System Partition  boot, esp
 2      250MB   3043MB  2793MB  fat32           fat32                 msftdata
 5      3044MB  478GB   475GB   ext4            mx
 4      478GB   512GB   33.8GB  linux-swap(v1).
Thanks a bunch for all your help in this fix - I'm very happy with the new install and am doing some post install tweaks. You're a gent.
Old enough to remember the Internet when graphics meant ascii art.
Dell XPS 13 9360 - 16GB - 512GB - i7

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9298
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX 17.1 install fails at partitioning (probably due to NVME & UEFI)

#29 Post by dolphin_oracle » Thu Apr 19, 2018 2:22 pm

Nice! I suspect somewhere boot flags got messed up, but I'm also certain that our autoinstall wasn't working properly before, so thank you for the excellent feedback!
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

Post Reply

Return to “Installation”