Manjaro Xfce installation problem

Hello, everyone. I’m dual booting my Lenovo Ideapad 320 and for this I’m trying to install Manjaro Xfce 18.0.4. I already followed the user guide and used Calamares for the automatic installation and partitioning (I chose to put 440 GB for Windows and 460 GB for Manjaro). I believe that the problem lies in the partitioning: installation runs perfectly in the beginning, but when Calamares reaches “running the mounted points” (around 13% of the installation process), it suddenly closes. I’ve been trying to re-install and understand this for a while now but couldn’t find an answer or someone with this same problem. Could someone help me? Thanks in advance.

Not sure if is related, but as pe arch wiki for that model:

Might be helpful too. Since has a UEFI BIOS (AFAIK) make sure you also have the boot partition marked as ESP and if you use the one made by Win$ - DO NOT FORMAT IT, but you have to be sure the partition table is GPT and not MBR.

Also see this

lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0  76.6M  1 loop /run/miso/sfs/livefs
loop1    7:1    0 274.6M  1 loop /run/miso/sfs/mhwdfs
loop2    7:2    0     1G  1 loop /run/miso/sfs/desktopfs
loop3    7:3    0 475.5M  1 loop /run/miso/sfs/rootfs
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   260M  0 part 
├─sda2   8:2    0    16M  0 part 
├─sda3   8:3    0 454.1G  0 part 
├─sda4   8:4    0    25G  0 part 
├─sda5   8:5    0  1000M  0 part 
├─sda6   8:6    0   200M  0 part 
├─sda7   8:7    0   4.1G  0 part 
├─sda8   8:8    0 205.1G  0 part 
└─sda9   8:9    0 241.8G  0 part 
sdb      8:16   1   7.5G  0 disk /run/miso/bootmnt
├─sdb1   8:17   1   1.9G  0 part 
└─sdb2   8:18   1     4M  0 part

-------------------------------------------------

sudo fdisk -l:

Disk /dev/loop0: 76.6 MiB, 80293888 bytes, 156824 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


Disk /dev/loop1: 274.6 MiB, 287899648 bytes, 562304 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


Disk /dev/loop2: 1 GiB, 1123639296 bytes, 2194608 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


Disk /dev/loop3: 475.5 MiB, 498569216 bytes, 973768 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


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM035-1RK1
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: 98FD1C64-BA5F-4232-8A37-38361FB401C5

Device          Start        End   Sectors   Size Type
/dev/sda1        2048     534527    532480   260M EFI System
/dev/sda2      534528     567295     32768    16M Microsoft reserved
/dev/sda3      567296  952939445 952372150 454.1G Microsoft basic data
/dev/sda4  1899046912 1951475711  52428800    25G Microsoft basic data
/dev/sda5  1951475712 1953523711   2048000  1000M Windows recovery environment
/dev/sda6   952940544  953350143    409600   200M EFI System
/dev/sda7   953350144  961951743   8601600   4.1G Linux swap
/dev/sda8   961951744 1392031743 430080000 205.1G Linux filesystem
/dev/sda9  1392031744 1899046911 507015168 241.8G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 7.5 GiB, 8002732032 bytes, 15630336 sectors
Disk model: Cruzer Blade    
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: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *         64 4007655 4007592  1.9G  0 Empty
/dev/sdb2       4007656 4015847    8192    4M ef EFI (FAT-12/16/32)

I just tried to partition the hard disk manually but it’s the same as always: when the installation runs mounting points, it closes. By the way, the output above it’s from the manually partitioning. I don’t know what to do now.

Ok, the fact that you decided to have a separate EFI for Manjaro than the one used by the Windows install, i consider it a + and inspired decision (as windows will not overwrite it with the next “super-update”), but i would put the SWAP partition at the end of the drive.
From what i know, that linux EFI partition should be marked as boot ESP and mounted as /efi/boot …
@gohlip might confirm or correct me on that :slight_smile:

From the data, we are unable to pin point any problem (if there is a problem).
Try using this first post and the [More Complicated Setups] section and see if you can boot to the installed Manjaro partition. And then do the commands there if you can boot it up. And provide the information required there.
If you are unablle to boot using this method, boot up the livecd OS and also provide the information and also go to the file manager and at the installed manjaro partition provide contents of
/etc/fstab

The information required are

efibootmgr -v
sudo parted -l
sudo blkid

After nearly two days fighting with Calamares and the automatic installation I gave up and switch to Architect installation. I found a video describing Architect’s installation step-by-step and finally got it running! Still don’t know what that problem was, though.
Thank you all for trying to help me! :smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.