MX-Linux 21.2.1 install: 5.7 GB minimum root partition required [Solved]

[Plurix]

Hi There!

Is there a way to resize (increase) the ESP partition?

My 2 TB NVMe GPT drive has a 1000 MiB ESP partition (nvme0n1p1, FAT32) followed by a msftres (nvmw0n1p2, 16 MiB) partition created by W10 it was later moved to a SATA 2.5" SSD GPT drive (sdb1/msftres, sbd2/msftdata, sbd3/hidden-diag).

But when trying to install MX-Linux 21.2.1 on it (nvme), it complains of no room enough for root partition (at least 5.7 GB required).

Not sure it is possible to safely move msftres partition to expand ESP partition to comply with MX-Linux requirement.

My guess is, even moving to sbd room would be needed anyway, right?...

Any thoughts?

[fehlix]

Hi There!

Is there a way to resize (increase) the ESP partition?

My 2 TB NVMe GPT drive has a 1000 MiB ESP partition (nvme0n1p1, FAT32)

You would not need to increase the ESP (EFI System Partition).

followed by a msftres (nvmw0n1p2, 16 MiB) partition created by W10 it was later moved to a SATA 2.5" SSD GPT drive (sdb1/msftres, sbd2/msftdata, sbd3/hidden-diag).

But when trying to install MX-Linux 21.2.1 on it (nvme), it complains of no room enough for root partition (at least 5.7 GB required).

Yes, it asks you to create or use an existing partition and select this partition within the "used for column" as "root" partition. You do not want to use ESP as a root-partition.

[Plurix]

Hi There!

Is there a way to resize (increase) the ESP partition?

My 2 TB NVMe GPT drive has a 1000 MiB ESP partition (nvme0n1p1, FAT32)

You would not need to increase the ESP (EFI System Partition).

Oh my!... Bingo!... I was able to mix ESP with root in my head... How come?...

followed by a msftres (nvmw0n1p2, 16 MiB) partition created by W10 it was later moved to a SATA 2.5" SSD GPT drive (sdb1/msftres, sbd2/msftdata, sbd3/hidden-diag).

But when trying to install MX-Linux 21.2.1 on it (nvme), it complains of no room enough for root partition (at least 5.7 GB required).

Yes, it asks you to create or use an existing partition and select this partition within the "used for column" as "root" partition. You do not want to use ESP as a root-partition.

Yep, I did that with Size 16 Gb, Used For root, Labeled rootMX21, Format Ext4, and in Options defaults to Discard (or something like that).

Then clicking on Next, it pops up (MX Linux Installer):

The following drives are, or will be, setup with GPT, but do not have a BIOS-GRUB partition:
nvme0n1
This system may not boot from GPT drives without a BIOS-GRUB partition.
Are you sure you want to continue?

A opted for NO as I do not know the ramifications of going ahead...

[fehlix]

Then clicking on Next, it pops up (MX Linux Installer):

The following drives are, or will be, setup with GPT, but do not have a BIOS-GRUB partition:
nvme0n1
This system may not boot from GPT drives without a BIOS-GRUB partition.
Are you sure you want to continue?

A opted for NO as I do not know the ramifications of going ahead...

Good.
Suggest, to post QSI "Quick System Info" from running MX LiveUSB, which would probably reduce starting to ask too many questions.
Also note: When booted in UEFI-mode and the intention would be to install in UEFI-bootable mode, the GRUB-efi loader requires an ESP "EFI System Partition" during installation - otherwise it won't boot - except you'r intention would be to install in BIOS-bootable mode, which would require a BIOS-GRUB partition on a GPT-partition table.
HTH

[pbear]

Is this a dual boot computer? If so, does Windows boot in UEFI mode?* If the answer to both questions is yes, do you have a particular reason for booting Linux in BIOS mode?

* If you're not sure of the Windows boot mode, boot the system, open Run (right-click of Start) and run msinfo32. Line 14 will report Boot Mode: UEFI or UEFI (legacy).

[Plurix]

Then clicking on Next, it pops up (MX Linux Installer):

The following drives are, or will be, setup with GPT, but do not have a BIOS-GRUB partition:
nvme0n1
This system may not boot from GPT drives without a BIOS-GRUB partition.
Are you sure you want to continue?

A opted for NO as I do not know the ramifications of going ahead...

Good.
Suggest, to post QSI "Quick System Info" from running MX LiveUSB, which would probably reduce starting to ask too many questions.
Also note: When booted in UEFI-mode and the intention would be to install in UEFI-bootable mode, the GRUB-efi loader requires an ESP "EFI System Partition" during installation - otherwise it won't boot - except you'r intention would be to install in BIOS-bootable mode, which would require a BIOS-GRUB partition on a GPT-partition table.
HTH

@Fehlix
Thank you for pointing me that out. Here it is:

Code: Select all

System:    Kernel: 5.18.0-4mx-amd64 [5.18.16-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.18.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.2.1_ahs_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: <filter> 
           Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 4021 date: 08/10/2021 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech K520 serial: <filter> 
           charge: 70% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: 12-Core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3 
           family: 19 (25) model-id: 21 (33) stepping: 0 microcode: A201016 cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 177259 
           Speed: 2224 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 2224 
           2: 2752 3: 2190 4: 2196 5: 2190 6: 2195 7: 2193 8: 2197 9: 2197 10: 2233 11: 2192 
           12: 2193 13: 2194 14: 2195 15: 2194 16: 2193 17: 2194 18: 2194 19: 2194 20: 2192 
           21: 2190 22: 2193 23: 2193 24: 2190 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, 
           RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nouveau v: kernel bus-ID: 09:00.0 
           chip-ID: 10de:1f82 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") 
           diag: 604mm (23.8") 
           OpenGL: renderer: NV167 v: 4.3 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: NVIDIA driver: snd_hda_intel v: kernel bus-ID: 09:00.1 chip-ID: 10de:10fa 
           class-ID: 0403 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403 
           Sound Server-1: ALSA v: k5.18.0-4mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl bus-ID: 04:00.0 
           chip-ID: 8086:2723 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel port: N/A 
           bus-ID: 05:00.0 chip-ID: 8086:15f3 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:2 
           chip-ID: 8087:0029 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 2014 hci-v: 5.2 rev: 2014 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 5.91 TiB used: 9.13 GiB (0.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 5B2QGXA7 temp: 33.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD40EZRZ-00GXCB0 
           size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD 
           rpm: 5400 serial: <filter> rev: 0A80 scheme: GPT 
           ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WDS500G2B0A-00SM50 
           size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
           serial: <filter> rev: 20WD scheme: GPT 
Partition: ID-1: / raw-size: 40 GiB size: 39.08 GiB (97.69%) used: 7.49 GiB (19.2%) fs: ext4 
           dev: /dev/nvme0n1p3 maj-min: 259:3 
           ID-2: /boot/efi raw-size: 1000 MiB size: 998 MiB (99.80%) used: 25.8 MiB (2.6%) 
           fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-3: /home raw-size: 200 GiB size: 195.8 GiB (97.90%) used: 1.62 GiB (0.8%) fs: ext4 
           dev: /dev/nvme0n1p4 maj-min: 259:4 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 187.5 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p11 maj-min: 259:11 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 1944 lib: 981 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 512 Uptime: 5h 36m wakeups: 168 Memory: 125.72 GiB used: 7.06 GiB (5.6%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

A little while after my last posting, I decided to review the MB's UEFI BIOS manual, which was of no use at all. But eventually I found where to enable UEFI boot mode in the MB's UEFI BIOS cryptic settings. It's called Boot/CSM (for Compatibility Support Module) in Advanced Mode, which has to be set to Disabled:



(Not sure image will popup, although less than 640x620 size)

UEFI BIOS Utility - Advanced Mode UEFI Settings

IMHO it would have been a much better idea to use a wording like UEFI Disable/Enable instead, to make thinks easier for the end user...

So once the boot mode was properly set to UEFI (by disabling CSM), the install process was a breeze, and the Wildflowers are now blooming on my screen!...

Thank you Fehlix and you all for the heads up.

[Plurix]

Is this a dual boot computer? If so, does Windows boot in UEFI mode?* If the answer to both questions is yes, do you have a particular reason for booting Linux in BIOS mode?

* If you're not sure of the Windows boot mode, boot the system, open Run (right-click of Start) and run msinfo32. Line 14 will report Boot Mode: UEFI or UEFI (legacy).

Hi PBear,

Yeap, it's a dual boot computer. The issue was UEFI disabled in the MB's UEFI BIOS Setup.

See my previous post above (Reply to Fehlix).

Thank you for your heads up.