Garuda Install - Calamares hangs on Partition Module

Heyo!
For the first time in approximately 2 years my Garuda Linux died.

First there was a huge system lag then my power went out.
Turns out btrfs was doing a balance or some sort but tl;dr I could not recover it and don't want to waste any more time on that.

I just want to do a fresh setup. That should be easy.
Well..
I have run into a variation of this issue:

Here is my infi -Faz

System:
Kernel: 5.15.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
misobasedir=garuda misolabel=GARUDA_DR460NIZEDGAMING_WHITETAI quiet
systemd.show_status=1 driver=nonfree nouveau.modeset=0 i915.modeset=1
radeon.modeset=1
Console: pty pts/2 wm: kwin_x11 DM: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X370 GAMING M7 ACK (MS-7A35) v: 1.0
serial: <filter> UEFI: American Megatrends v: 1.10 date: 09/12/2017
CPU:
Info: model: AMD Ryzen 7 1700X socket: AM4 bits: 64 type: MT MCP arch: Zen
family: 0x17 (23) model-id: 1 stepping: 1 microcode: 0x8001126
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 3400 min/max: 2200/3400 boost: enabled
base/boost: 3400/3900 scaling: driver: acpi-cpufreq governor: performance
volts: 1.4 V ext-clock: 100 MHz cores: 1: 3400 2: 3400 3: 3400 4: 3400
5: 3400 6: 3400 7: 3400 8: 3400 9: 3400 10: 3400 11: 3400 12: 3400
13: 3400 14: 3400 15: 3400 16: 3400 bogomips: 108785
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown 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: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 495.46
alternate: nouveau,nvidia_drm bus-ID: 24:00.0 chip-ID: 10de:1b06
class-ID: 0300
Device-2: Anker PowerConf C300 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-9.1:13 chip-ID: 291a:3361 class-ID: 0e02 serial: <filter>
Display: server: X.Org 1.21.1.2 compositor: kwin_x11 driver:
loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 5120x1440 s-dpi: 108 s-size: 1204x342mm (47.4x13.5")
s-diag: 1252mm (49.3")
Monitor-1: DP-2 res: 2560x1440 hz: 60 dpi: 93
size: 697x393mm (27.4x15.5") diag: 800mm (31.5")
Monitor-2: DP-4 res: 2560x1440 hz: 60 dpi: 109
size: 598x336mm (23.5x13.2") diag: 686mm (27")
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
Device-1: NVIDIA GP102 HDMI Audio driver: snd_hda_intel v: kernel
bus-ID: 24:00.1 chip-ID: 10de:10ef class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 26:00.3 chip-ID: 1022:1457
class-ID: 0403
Device-3: Anker PowerConf C300 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-9.1:13 chip-ID: 291a:3361 class-ID: 0e02 serial: <filter>
Sound Server-1: ALSA v: k5.15.12-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.43 running: yes
Network:
Device-1: Qualcomm Atheros Killer E2500 Gigabit Ethernet
vendor: Micro-Star MSI driver: alx v: kernel port: f000 bus-ID: 1e:00.0
chip-ID: 1969:e0b1 class-ID: 0200
IF: enp30s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: Rivet Networks driver: ath10k_pci v: kernel bus-ID: 1f:00.0
chip-ID: 168c:003e class-ID: 0280
IF: wlp31s0 state: down mac: <filter>
Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB
driver: r8152 bus-ID: 2-1.4:3 chip-ID: 0bda:8153 class-ID: 0000
serial: <filter>
IF: enp3s0f0u1u4 state: down mac: <filter>
Bluetooth:
Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 type: USB driver: btusb
v: 0.8 bus-ID: 1-13:15 chip-ID: 0cf3:e300 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 3.65 TiB used: 0 KiB (0.0%)
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 960 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B7QCXE7
temp: 35.9 C scheme: GPT
SMART: yes health: PASSED on: 371d 20h cycles: 2,094
read-units: 1,789,256,746 [916 TB] written-units: 152,607,450 [78.1 TB]
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Crucial model: CT1000P1SSD8
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: P3CR020
temp: 40.9 C scheme: GPT
SMART: yes health: PASSED on: 256d 18h cycles: 868
read-units: 27,146,089 [13.8 TB] written-units: 21,826,155 [11.1 TB]
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DX002-2DV162
family: FireCuda 3.5 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: CC41 temp: 36 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 184d 2h cycles: 1975
read: 6.22 TiB written: 657.67 GiB Pre-Fail: attribute: Spin_Retry_Count
value: 100 worst: 100 threshold: 97
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EADS-00L5B1 family: Caviar Green size: 931.51 GiB block-size:
physical: 512 B logical: 512 B sata: 2.5 speed: 3.0 Gb/s type: N/A
serial: <filter> rev: 1A01 temp: 38 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 7y 271d 15h cycles: 1812
ID-5: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk
model: Cruzer Blade size: 14.56 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 1.27 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.63 GiB used: 785.5 MiB (4.9%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.8 C mobo: N/A gpu: nvidia temp: 33 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 22%
Info:
Processes: 357 Uptime: 17m wakeups: 0 Memory: 15.63 GiB
used: 11.73 GiB (75.0%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 Packages: pacman: 1721 lib: 500 Shell: fish (sudo) v: 3.3.1
default: Bash v: 5.1.12 running-in: konsole inxi: 3.3.11

Here the stuck module since ~ 500 seconds.

19:09:10 [6]: void Calamares::RequirementsChecker::reportProgress()
Remaining modules: 1
"partition"

:man_shrugging:
I am running 2 m 2 NVMe SSDs.
1x Windoof for some games
1x Garuda

2 HDDs

  • 1x shared storage between Linux and Windows
  • 1x "Backup" / Snapshot

I already tried unplugging the two HDD drives, but same issue.
I really do not want to remove the other NVMe since that would involve draining my system and yada yada.

Any Ideas?

Have you tried rebooting and just trying again?

I do hundreds of Calamares installs and see this issue a small percentage of the time across several distros. Usually just trying again resolves it.

4 Likes

TL;DR

calamares is running:

/usr/bin/ntfsresize --info --force --no-progress-bar /dev/{$DEVICE}

Do not force quit calamares with ctrl+alt+esc or sudo kill -9 just wait and have patience.
If you killed calamares, reboot and wait.
For me a simple restart of calamares did not help since it would not start ntfsresize again and was stuck in a loop of waiting for the partition module.


More Information

aka. the verbose output of me trying to figure out whats going on.

I just noticed something... when starting calamares one hdd is starting to work on something.
Why?

λ sudo ps uax | grep -i /dev/
root       14950  0.9  0.1  34416 31236 ?        D    19:26   0:02 /usr/bin/ntfsresize --info --force --no-progress-bar /dev/sdb1
garuda     19238  0.0  0.0   6496  2420 pts/2    S<+  19:30   0:00 grep --color=auto -i /dev/

This is the HDD for shared storage. Why is there a ntfsresize running on it?
OK time to learn.

https://man.archlinux.org/man/ntfsresize.8.en

This option never causes any changes to the filesystem, the partition is opened read-only.

OK, so I just wait.
That worked!

OK If you ever have this issue do not quit / force quit ctrl+alt+esc or sudo kill -9 calamares.
There is a still a job running. :roll_eyes:

19:33:01 [6]: smartctl initialization failed for  "/dev/sdc" :  No such file or directory
19:33:01 [6]: error during smart output parsing for  "/dev/sdc" :  Success
19:33:01 [6]: smartctl initialization failed for  "/dev/zram0" :  No such file or directory
19:33:01 [6]: error during smart output parsing for  "/dev/zram0" :  Success
19:33:01 [6]: QList<Device*> PartUtils::getDevices(PartUtils::DeviceType)
Removing unsuitable devices: 6 candidates. 
..  Removing device with iso9660 filesystem (probably a CD) on it "/dev/sdc" 
..  Removing zram "/dev/zram0" 
..  there are 4 devices left. 
19:33:02 [6]: void PartitionCoreModule::doInit()
LIST OF DETECTED DEVICES: 
..  node    capacity        name    prettyName 
..  "/dev/nvme0n1" 1000202273280 DevName$a2ce06dc DevNamePretty$bbf85452 
..  "/dev/nvme1n1" 1000202273280 DevName$ac3c8061 DevNamePretty$8966f4c1 
..  "/dev/sda" 1000202273280 DevName$697cb041 DevNamePretty$dd99015b 
..  "/dev/sdb" 1000202273280 DevName$ab03f41a DevNamePretty$32ce1d49 
..  4 devices detected. 
19:33:02 [6]: void Calamares::RequirementsChecker::reportProgress()
Remaining modules: 1 
"partition" 
19:33:03 [6]: void Calamares::RequirementsChecker::reportProgress()
Remaining modules: 1 
"partition" 
19:33:04 [6]: void Calamares::RequirementsChecker::reportProgress()
Remaining modules: 1 
"partition" 
19:33:05 [6]: void Calamares::RequirementsChecker::reportProgress()
Remaining modules: 1 
"partition" 
..  Running ("blkid", "-s", "TYPE", "-o", "value", "/dev/nvme0n1p1") 
..  Finished. Exit code: 0 output:
vfat
19:33:06 [6]: FstabEntryList PartUtils::lookForFstabEntries(const QString&)
Checking device "/dev/nvme0n1p1" for fstab (fs= "vfat" ) 
..  Running ("mount", "-o", "ro", "/dev/nvme0n1p1", "/tmp/calamares-DUhroP") 
..  Running ("udevadm", "settle") 
..  Running ("sync") 
19:33:07 [2]: FstabEntryList PartUtils::lookForFstabEntries(const QString&)
WARNING: Could not read fstab from mounted fs 
..  Running ("umount", "-R", "/tmp/calamares-DUhroP") 
..  Running ("udevadm", "settle") 
..  Running ("sync") 
..  NO, insufficient storage 
Required  storage B: 34789235097 "(32.4GiB)" 
Available storage B: 77148160 "(0GiB)" for "/dev/nvme0n1p1" length: 204800 sectorsUsed: 54120 fsType: "fat32" 
19:33:07 [6]: OsproberEntryList PartUtils::runOsprober(DeviceModel*)
os-prober lines after cleanup: 
"/dev/[email protected]/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi" 
19:33:07 [6]: void Calamares::RequirementsChecker::reportProgress()
Remaining modules: 1 
"partition" 
19:33:07 [6]: void PartitionCoreModule::scanForEfiSystemPartitions()
system is EFI and new EFI system partition has been found. 
19:33:07 [6]: void Calamares::RequirementsChecker::addCheckedRequirements(Calamares::Module*)
Got 1 requirement results from "partition" 
19:33:07 [6]: void ChoicePage::updateDeviceStatePreview()
Updating partitioning state widgets. 
19:33:07 [6]: void ChoicePage::setupActions()
Setting up actions for "/dev/nvme0n1" with 1 entries. 
..  NO, insufficient storage 
Required  storage B: 34789235097 "(32.4GiB)" 
Available storage B: 77148160 "(0GiB)" for "/dev/nvme0n1p1" length: 204800 sectorsUsed: 54120 fsType: "fat32" 
..  Checking if "/dev/nvme0n1p1" can be replaced. 
..  NO, insufficient storage 
Required  storage B: 32641751449 "(29.9GiB)" 
Available storage B: 104857600 "(0GiB)" 
..  Can not resize "/dev/nvme0n1p2" , filesystem "unknown" does not support resize. 
..  Checking if "/dev/nvme0n1p2" can be replaced. 
..  NO, insufficient storage 
Required  storage B: 32641751449 "(29.9GiB)" 
Available storage B: 16777216 "(0GiB)" 
..  Partition "/dev/nvme0n1p3" authorized for resize + autopartition install. 
..  contains resizable "/dev/nvme0n1p3" 
..  Checking if "/dev/nvme0n1p3" can be replaced. 
..  Partition "/dev/nvme0n1p3" authorized for replace install. 
..  contains replaceable "/dev/nvme0n1p3" 
..  NO, insufficient storage 
Required  storage B: 34789235097 "(32.4GiB)" 
Available storage B: 92971008 "(0GiB)" for "/dev/nvme0n1p4" length: 1075200 sectorsUsed: 893616 fsType: "ntfs" 
..  Checking if "/dev/nvme0n1p4" can be replaced. 
..  NO, insufficient storage 
Required  storage B: 32641751449 "(29.9GiB)"
Available storage B: 550502400 "(0GiB)"
..  Can not resize "/dev/nvme0n1" , filesystem "unknown" does not support resize.
..  Checking if "/dev/nvme0n1" can be replaced.
..  NO, insufficient storage
Required  storage B: 32641751449 "(29.9GiB)"
Available storage B: 1777152 "(0GiB)"
19:33:07 [6]: ChoicePage::setupActions()::<lambda()>
Setting texts for 1 non-empty osprober entry
19:33:07 [6]: void ChoicePage::continueApplyDeviceChoice()
Previous device -1 new device 0
19:33:07 [6]: void ChoicePage::applyActionChoice(InstallChoice)
Prev -1 InstallChoice Config::NoChoice "none"
19:33:07 [6]: bool ChoicePage::calculateNextEnabled() const
No partitioning choice
19:33:07 [6]: void ChoicePage::updateActionChoicePreview(InstallChoice)
Updating partitioning preview widgets.
19:33:07 [6]: void Calamares::RequirementsChecker::finished()
All requirements have been checked.
19:33:07 [6]: void Calamares::RequirementsModel::describe() const
Requirements model has 6 items
..  requirement 0 "storage" satisfied? true mandatory? true
..  requirement 1 "ram" satisfied? true mandatory? true
..  requirement 2 "power" satisfied? true mandatory? false
..  requirement 3 "internet" satisfied? true mandatory? false
..  requirement 4 "root" satisfied? true mandatory? true
..  requirement 5 "partitions" satisfied? true mandatory? true
2 Likes

yea I tried :smiley: But I have found the "issue"

IT WAS ME! All along :smiley: haah! What a twist of events. :mage:

3 Likes

Time to start saving to buy a Universal Power Supply. Bad timing on the power failure.

2 Likes

Indeed but its kinda rare to have power outages in germany.
But it happens :man_shrugging:

3 Likes

I've had at least 3 outages in the last week, but we've been experiencing unusually high snowfall (for this area) since Xmas.

1 Like

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