[manjaro-chroot] Fails if multiple linux installs to automount

oberon commented

2016-01-06 12:46:17 +00:00

(Migrated from gitlab2.manjaro.org)

UEFI machine with two manjaro installs present. Attempting to chroot from a live environment:

[manjaro@manjaro-i3 ~]$ manjaro-chroot -a
mkdir: cannot create directory '/etc/manjaro-tools/pkg.d': Permission denied
mkdir: cannot create directory '/etc/manjaro-tools/iso.d': Permission denied
 * Starting lvmetad ...                                                                                                                          [ ok ]
 * Setting up the Logical Volume Manager ...
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.                                                                      [ ok ]
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
==> Selected OS: ManjaroLinuxlinux
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot/boot/efi
==> ERROR: Error! Attempting to overwrite existing EXIT trap

Alternatively using mhwd-chroot works fine.

UEFI machine with two manjaro installs present. Attempting to chroot from a live environment: ``` [manjaro@manjaro-i3 ~]$ manjaro-chroot -a mkdir: cannot create directory '/etc/manjaro-tools/pkg.d': Permission denied mkdir: cannot create directory '/etc/manjaro-tools/iso.d': Permission denied * Starting lvmetad ... [ ok ] * Setting up the Logical Volume Manager ... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. [ ok ] /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. ==> Selected OS: ManjaroLinuxlinux -> mounted: /var/lib/manjaro-tools/manjaro-chroot -> mounted: /var/lib/manjaro-tools/manjaro-chroot/boot/efi ==> ERROR: Error! Attempting to overwrite existing EXIT trap ``` Alternatively using **mhwd-chroot** works fine.

philm commented

2016-01-06 15:00:02 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Problem is this:

grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.

Could you provide the fstab for sda and sdb?

*Created by: udeved* Problem is this: ``` grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. ``` Could you provide the fstab for sda and sdb?

oberon commented

2016-01-06 15:12:14 +00:00

(Migrated from gitlab2.manjaro.org)

This is sda:

UUID=42E3-E09A                            /boot/efi      vfat    defaults,noatime 0       2
UUID=73a66e33-e67b-4547-947c-018b60eef818 /              ext4    defaults,noatime 0       1
UUID=26156d25-6030-44a2-a099-b677467bc84a /home          ext4    defaults,noatime 0       2
UUID=415f5d44-86a7-4ca2-bdac-892c7e5f5b3f swap           swap    defaults,noatime 0       0

sdb is the USB stick with the live env.

This is sda: ``` UUID=42E3-E09A /boot/efi vfat defaults,noatime 0 2 UUID=73a66e33-e67b-4547-947c-018b60eef818 / ext4 defaults,noatime 0 1 UUID=26156d25-6030-44a2-a099-b677467bc84a /home ext4 defaults,noatime 0 2 UUID=415f5d44-86a7-4ca2-bdac-892c7e5f5b3f swap swap defaults,noatime 0 0 ``` sdb is the USB stick with the live env.

philm commented

2016-01-06 15:13:34 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Ok, but where gets /boot/efi mounted on sda? There is no /boot entry.

*Created by: udeved* Ok, but where gets /boot/efi mounted on sda? There is no /boot entry.

philm commented

2016-01-06 15:15:33 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

The fstab of my laptop looks like this:

# /dev/sda4 LABEL=manjaro
UUID=3ee8925b-e1b8-4155-a6f8-ac3acfee78a2       /               ext4            rw,noatime,data=ordered 0 1

# /dev/sda3 LABEL=boot
UUID=b3a38888-ecbf-4990-aa66-af33bb9c1a18       /boot           ext4            rw,noatime,data=ordered 0 2

# /dev/sda1 LABEL=EFI
UUID=F49B-1F24          /boot/efi       vfat            rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro     0 2

*Created by: udeved* The fstab of my laptop looks like this: ``` # /dev/sda4 LABEL=manjaro UUID=3ee8925b-e1b8-4155-a6f8-ac3acfee78a2 / ext4 rw,noatime,data=ordered 0 1 # /dev/sda3 LABEL=boot UUID=b3a38888-ecbf-4990-aa66-af33bb9c1a18 /boot ext4 rw,noatime,data=ordered 0 2 # /dev/sda1 LABEL=EFI UUID=F49B-1F24 /boot/efi vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2 ```

oberon commented

2016-01-06 15:23:23 +00:00

(Migrated from gitlab2.manjaro.org)

Is it not there in the first line?

UUID=42E3-E09A                            /boot/efi      vfat    defaults,noatime 0       2

Is it not there in the first line? ``` UUID=42E3-E09A /boot/efi vfat defaults,noatime 0 2 ```

oberon commented

2016-01-06 15:34:05 +00:00

(Migrated from gitlab2.manjaro.org)

Wait, rubbish. I have to do this from the live again. :P

oberon commented

2016-01-06 15:38:19 +00:00

(Migrated from gitlab2.manjaro.org)

Uhm. From the live env I see this:
fstab:

/dev/mapper/root-image /             auto      defaults           0      0
/dev/sda5 swap swap defaults 0 0 #configured by manjaro-tools

and

$ fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: 040B4375-F4EC-4797-86AE-DDCB384DC558

Device         Start       End   Sectors   Size Type
/dev/sda1  771971072 976773119 204802048  97.7G Linux filesystem
/dev/sda2       2048   1230847   1228800   600M EFI System
/dev/sda3  103630848 763779071 660148224 314.8G Linux filesystem
/dev/sda5  763779072 771971071   8192000   3.9G Linux swap
/dev/sda6    1230848 103630847 102400000  48.8G Linux filesystem

Uhm. From the live env I see this: fstab: ``` /dev/mapper/root-image / auto defaults 0 0 /dev/sda5 swap swap defaults 0 0 #configured by manjaro-tools ``` and ``` $ fdisk -l Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: 040B4375-F4EC-4797-86AE-DDCB384DC558 Device Start End Sectors Size Type /dev/sda1 771971072 976773119 204802048 97.7G Linux filesystem /dev/sda2 2048 1230847 1228800 600M EFI System /dev/sda3 103630848 763779071 660148224 314.8G Linux filesystem /dev/sda5 763779072 771971071 8192000 3.9G Linux swap /dev/sda6 1230848 103630847 102400000 48.8G Linux filesystem ```

oberon commented

2016-01-06 15:40:20 +00:00

(Migrated from gitlab2.manjaro.org)

I have no separate /boot partition

philm commented

2016-01-06 15:42:58 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

I have never had a linux system without a /boot, I may be wrong, but I thought installers would create /boot.
May well be os-prober expects /boot, because the error is thrown by os-prober.

*Created by: udeved* I have never had a linux system without a /boot, I may be wrong, but I thought installers would create /boot. May well be os-prober expects /boot, because the error is thrown by os-prober.

oberon commented

2016-01-06 15:45:53 +00:00

(Migrated from gitlab2.manjaro.org)

Hm. GRUB in this case was installed by Calamares (automatic install to whole partition)...

philm commented

2016-01-06 15:52:19 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

I'll try in vbox, to see if /boot gets created.
You can also test this, if you have two manjaro installed, and chroot from one install to the other.
I doesn't necessarily have to be from livecd.

*Created by: udeved* I'll try in vbox, to see if /boot gets created. You can also test this, if you have two manjaro installed, and chroot from one install to the other. I doesn't necessarily have to be from livecd.

oberon commented

2016-01-06 16:18:20 +00:00

(Migrated from gitlab2.manjaro.org)

I know. From one install to the other in the dual boot I have no issues. Just from the live when trying to chroot into one of the two installed systems I have this problem...

philm commented

2016-01-06 16:28:06 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Ah, I think I know whats going on, the live root needs to be excluded from detected systems.

*Created by: udeved* Ah, I think I know whats going on, the live root needs to be excluded from detected systems.

oberon commented

2016-01-06 16:38:55 +00:00

(Migrated from gitlab2.manjaro.org)

Möchtest du mich dann mal für SF/manjaro-testing freischalten? Dann würd
ich die ISOs mal dorthin hochladen und ich kann sie dann ja einfach per
ssh-shell auf die anderen Projekte verschieben. Direkt auf den
manjarolinux account hochzuladen ist vielleicht ja noch ein wenig zu
früh, oder? ;) Aber wie gesagt ja egal, es lässt sich ja alles ganz
einfach und schnell umkopieren...

On 06/01/16 17:28, udeved wrote:

Ah, I think I know whats going on, the live root needs to be excluded
from detected systems.

—
Reply to this email directly or view it on GitHub
https://github.com/manjaro/manjaro-tools/issues/171#issuecomment-169379384.

Möchtest du mich dann mal für SF/manjaro-testing freischalten? Dann würd ich die ISOs mal dorthin hochladen und ich kann sie dann ja einfach per ssh-shell auf die anderen Projekte verschieben. Direkt auf den manjarolinux account hochzuladen ist vielleicht ja noch ein wenig zu früh, oder? ;) Aber wie gesagt ja egal, es lässt sich ja alles ganz einfach und schnell umkopieren... On 06/01/16 17:28, udeved wrote: > Ah, I think I know whats going on, the live root needs to be excluded > from detected systems. > > — > Reply to this email directly or view it on GitHub > https://github.com/manjaro/manjaro-tools/issues/171#issuecomment-169379384.

philm commented

2016-01-06 16:42:36 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Wrong recipient for email? 😆

Yes, sure, I think it fails for you when trying at manjaro-testing?
Whats your SF account?

*Created by: udeved* Wrong recipient for email? :laughing: Yes, sure, I think it fails for you when trying at manjaro-testing? Whats your SF account?

oberon commented

2016-01-06 16:54:06 +00:00

(Migrated from gitlab2.manjaro.org)

;P dammit! Too much addresses/information lately 😆
It's oberon2007 :) Thanks

;P dammit! Too much addresses/information lately :laughing: It's oberon2007 :) Thanks

oberon commented

2016-01-06 16:58:43 +00:00

(Migrated from gitlab2.manjaro.org)

yes, 'permission denied' atm of course...

philm commented

2016-01-06 17:02:32 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Should work now @SF

*Created by: udeved* Should work now @SF

oberon commented

2016-01-06 17:03:11 +00:00

(Migrated from gitlab2.manjaro.org)

indeed! :) Thanks!

philm commented

2016-01-06 18:30:37 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Test in vbox, live session.

[manjaro@manjaro-openrc ~]$ manjaro-chroot -a
mkdir: cannot create directory '/etc/manjaro-tools/pkg.d': Permission denied
mkdir: cannot create directory '/etc/manjaro-tools/iso.d': Permission denied
 * Starting lvmetad ...                              [ ok ]
 * Setting up the Logical Volume Manager ...
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.                                     [ ok ]
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
==> Selected OS: ManjaroLinuxlinux
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot
[root@manjaro-openrc /]#

Works fine here.

*Created by: udeved* Test in vbox, live session. ``` [manjaro@manjaro-openrc ~]$ manjaro-chroot -a mkdir: cannot create directory '/etc/manjaro-tools/pkg.d': Permission denied mkdir: cannot create directory '/etc/manjaro-tools/iso.d': Permission denied * Starting lvmetad ... [ ok ] * Setting up the Logical Volume Manager ... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. [ ok ] /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ==> Selected OS: ManjaroLinuxlinux -> mounted: /var/lib/manjaro-tools/manjaro-chroot [root@manjaro-openrc /]# ``` Works fine here.

philm commented

2016-01-07 16:08:16 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

The OS list to select from looks like this:

$ manjaro-chroot -a
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
==> /dev/sda4:Gentoo_Base_System_release_2.2:Gentoo:linux /dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi:Windows_Boot_Manager:Windows:efi
==> linux
==> count: 1
==> List of found systems
 --> 0) Gentoolinux
==> Please enter your choice [0-0] : 
0
==> Selected OS: Gentoolinux

It used to show arch linux too, when I still had it installed.

*Created by: udeved* The OS list to select from looks like this: ``` $ manjaro-chroot -a /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ==> /dev/sda4:Gentoo_Base_System_release_2.2:Gentoo:linux /dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi:Windows_Boot_Manager:Windows:efi ==> linux ==> count: 1 ==> List of found systems --> 0) Gentoolinux ==> Please enter your choice [0-0] : 0 ==> Selected OS: Gentoolinux ``` It used to show arch linux too, when I still had it installed.

philm commented

2016-01-07 19:18:06 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

@oberon2007

You did boot live from usb key. right?

*Created by: udeved* @oberon2007 You did boot live from usb key. right?

oberon commented

2016-01-07 19:33:36 +00:00

(Migrated from gitlab2.manjaro.org)

yes, exactly!

philm commented

2016-01-07 19:35:13 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

I will test out with a triple boot, so I can edits manjaro-chroot in vbox.
Thing is, a usb key is being handled like a hard drive, not like a optical drive.

*Created by: udeved* I will test out with a triple boot, so I can edits manjaro-chroot in vbox. Thing is, a usb key is being handled like a hard drive, not like a optical drive.

philm commented

2016-01-07 19:36:49 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Take all the time you need. I just released v0.10 (94ff111a92) as a zero package so everybody who wants already to play with the current master packages can do so. This should take a way the pressure to fix this properly. Also it depends which edition you test. x86_64 has a special EFI setup on the USB stick which might create trouble. i686 however should be fine ;)

*Created by: philmmanjaro* Take all the time you need. I just released v0.10 (94ff111a92884eea165d4a94dac9d505534a6030) as a zero package so everybody who wants already to play with the current master packages can do so. This should take a way the pressure to fix this properly. Also it depends which edition you test. x86_64 has a special EFI setup on the USB stick which might create trouble. i686 however should be fine ;)

philm commented

2016-01-07 19:39:47 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

I believe the trouble comes with livecd on usb key atm.

*Created by: udeved* I believe the trouble comes with livecd on usb key atm.

philm commented

2016-01-07 22:15:58 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Ok, I got it solved for multiple systems.
Just some minor issues to fix now.

$ manjaro-chroot -a
[sudo] password for vtux: 
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
==> List of found systems:
 --> 0) Archlinux
 --> 1) ManjaroLinuxlinux
==> Please enter your choice [0-2] : 
0
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot/boot
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot/home
[root@localhost /]#

*Created by: udeved* Ok, I got it solved for multiple systems. Just some minor issues to fix now. ``` $ manjaro-chroot -a [sudo] password for vtux: /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ==> List of found systems: --> 0) Archlinux --> 1) ManjaroLinuxlinux ==> Please enter your choice [0-2] : 0 -> mounted: /var/lib/manjaro-tools/manjaro-chroot -> mounted: /var/lib/manjaro-tools/manjaro-chroot/boot -> mounted: /var/lib/manjaro-tools/manjaro-chroot/home [root@localhost /]# ```

philm commented

2016-01-07 22:25:52 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Great news my friend ;)

*Created by: philmmanjaro* Great news my friend ;)

philm commented

2016-01-07 22:30:13 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Will have to test on my real box after the vbox session for triple boot.
Need to see at least how it works out with windows efi to be filtered out.
I rewrote some stuff, its always spaghetti a bit, if code is integrated.

*Created by: udeved* Will have to test on my real box after the vbox session for triple boot. Need to see at least how it works out with windows efi to be filtered out. I rewrote some stuff, its always spaghetti a bit, if code is integrated.

philm commented

2016-01-07 22:33:59 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Sure, take your time and don't forget to put some Tomato sauce on it ;)

*Created by: philmmanjaro* Sure, take your time and don't forget to put some Tomato sauce on it ;)

philm commented

2016-01-07 23:16:31 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Looks fine on my dev box

$ manjaro-chroot -a
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
==> List of found systems:
 --> 0) Archlinux
 --> 1) Gentoolinux
 --> 2) Windowsefi
==> Please enter your choice [0-3] :

*Created by: udeved* Looks fine on my dev box ``` $ manjaro-chroot -a /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ==> List of found systems: --> 0) Archlinux --> 1) Gentoolinux --> 2) Windowsefi ==> Please enter your choice [0-3] : ```

philm commented

2016-01-07 23:17:34 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

@philmmanjaro

No tomato sauce, spaghetti are out now, 😆

*Created by: udeved* @philmmanjaro No tomato sauce, spaghetti are out now, :laughing:

philm commented

2016-01-08 00:57:29 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

On dev box, has win7efi, arch, gentoo and manjaro installed:

$ manjaro-chroot -a
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
==> Detected systems:
 --> 0) Arch
 --> 1) Gentoo
==> Select system to mount [0-1] : 
0
  -> mounted: /build/manjaro-tools/manjaro-chroot
  -> mounted: /build/manjaro-tools/manjaro-chroot/boot
  -> mounted: /build/manjaro-tools/manjaro-chroot/boot/efi
  -> mounted: /build/manjaro-tools/manjaro-chroot/home
  -> mounted: /build/manjaro-tools/manjaro-chroot/build
[root@manjaro-openrc /]# pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra                                      1764.9 KiB   959K/s 00:02 [#######################################] 100%
 community is up to date
:: Starting full system upgrade...
 there is nothing to do
[root@manjaro-openrc /]# exit
exit

In vbox, triple boot, all 3 manjaro, but one pretends to be arch, it has for testing purposes lsb-release changed:

$ manjaro-chroot -a
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
==> Detected systems:
 --> 0) Arch
 --> 1) ManjaroLinux
==> Select system to mount [0-1] : 
0
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot/boot
  -> mounted: /var/lib/manjaro-tools/manjaro-chroot/home
[root@localhost /]# exit
exit

Please reopen, if something goes wrong with a special setup.

*Created by: udeved* On dev box, has win7efi, arch, gentoo and manjaro installed: ``` $ manjaro-chroot -a /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ==> Detected systems: --> 0) Arch --> 1) Gentoo ==> Select system to mount [0-1] : 0 -> mounted: /build/manjaro-tools/manjaro-chroot -> mounted: /build/manjaro-tools/manjaro-chroot/boot -> mounted: /build/manjaro-tools/manjaro-chroot/boot/efi -> mounted: /build/manjaro-tools/manjaro-chroot/home -> mounted: /build/manjaro-tools/manjaro-chroot/build [root@manjaro-openrc /]# pacman -Syu :: Synchronizing package databases... core is up to date extra 1764.9 KiB 959K/s 00:02 [#######################################] 100% community is up to date :: Starting full system upgrade... there is nothing to do [root@manjaro-openrc /]# exit exit ``` In vbox, triple boot, all 3 manjaro, but one pretends to be arch, it has for testing purposes lsb-release changed: ``` $ manjaro-chroot -a /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. ==> Detected systems: --> 0) Arch --> 1) ManjaroLinux ==> Select system to mount [0-1] : 0 -> mounted: /var/lib/manjaro-tools/manjaro-chroot -> mounted: /var/lib/manjaro-tools/manjaro-chroot/boot -> mounted: /var/lib/manjaro-tools/manjaro-chroot/home [root@localhost /]# exit exit ``` Please reopen, if something goes wrong with a special setup.

Rows
Columns

[manjaro-chroot] Fails if multiple linux installs to automount #171