Installation failed on an NVME

Issues & Assistance
1

Hello, I'm having some problem in reinstalling garuda on my system since when i tried booting with nvidia closed source driver my system kernel panicked and when booting without them if I try to install garuda the installer give me an error saying that the installation is failed with this log:


Create a new partition (953.57 GiB, btrfs) on ‘/dev/nvme0n1’


Job: Create new partition on device ‘/dev/nvme0n1’


Command: sfdisk --force --append /dev/nvme0n1


Command: sfdisk --list --output Device,UUID /dev/nvme0n1


Job: Set the label on partition ‘/dev/nvme0n1p2’ to "root"


Command: sfdisk --part-label /dev/nvme0n1 2 root


Job: Create file system ‘btrfs’ on partition ‘/dev/nvme0n1p2’


Command: mkfs.btrfs --force /dev/nvme0n1p2


Command: sfdisk --part-type /dev/nvme0n1 2 0FC63DAF-8483-4772-8E79-3D69D8477DE4


Job: Set the file system label on partition ‘/dev/nvme0n1p2’ to ""


Command: btrfs filesystem label /dev/nvme0n1p2 



sudo garuda-inxi
System:
Kernel: 5.16.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=it
tz=Europe/Rome misobasedir=garuda
misolabel=GARUDA_DR460NIZED_WHITETAILEDEAG quiet systemd.show_status=1
driver=free nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
Console: pty pts/0 wm: kwin_x11 DM: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: ROG MAXIMUS XII FORMULA v: Rev 1.xx serial: <filter>
UEFI: American Megatrends v: 2301 date: 07/13/2021
Battery:
ID-1: hidpp_battery_0 charge: 85% condition: N/A volts: 4.0 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
serial: <filter> status: Discharging
CPU:
Info: model: Intel Core i9-10900K socket: LGA1200 bits: 64 type: MT MCP
arch: Comet Lake family: 6 model-id: 0xA5 (165) stepping: 5 microcode: 0xEE
Topology: cpus: 1x cores: 10 tpc: 2 threads: 20 smt: enabled cache:
L1: 640 KiB desc: d-10x32 KiB; i-10x32 KiB L2: 2.5 MiB desc: 10x256 KiB
L3: 20 MiB desc: 1x20 MiB
Speed (MHz): avg: 3844 high: 5066 min/max: 800/5300 base/boost: 3700/8300
scaling: driver: intel_pstate governor: powersave volts: 0.9 V
ext-clock: 100 MHz cores: 1: 800 2: 1101 3: 4999 4: 5008 5: 5004 6: 5001
7: 4996 8: 5013 9: 4973 10: 4953 11: 5007 12: 5066 13: 5038 14: 4989
15: 4384 16: 3505 17: 2870 18: 2089 19: 1250 20: 836 bogomips: 147994
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
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: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nouveau
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: DP-1,DP-2,DP-3 empty: DVI-D-1,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:1b81 class-ID: 0300
Device-2: Logitech HD Pro Webcam C920 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2.2:7 chip-ID: 046d:082d
class-ID: 0102 serial: <filter>
Display: server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: nouveau unloaded: modesetting alternate: fbdev,nv,vesa gpu: nouveau
display-ID: :0 screens: 1
Screen-1: 0 s-res: 7280x1440 s-dpi: 96 s-size: 1926x381mm (75.8x15.0")
s-diag: 1963mm (77.3")
Monitor-1: DP-1 pos: primary,left model: Mi Monitor built: 2019
res: 3440x1440 hz: 50 dpi: 110 gamma: 1.2 size: 797x334mm (31.4x13.1")
diag: 864mm (34") modes: max: 3440x1440 min: 720x400
Monitor-2: DP-2 pos: center model: AOC 2460G5 serial: <filter>
built: 2017 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
size: 531x299mm (20.9x11.8") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-3: DP-3 pos: right model: LG (GoldStar) 24GL600F serial: <filter>
built: 2020 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
size: 531x298mm (20.9x11.7") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL: renderer: NV134 v: 4.3 Mesa 21.3.7 direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f0
class-ID: 0403
Device-3: Logitech HD Pro Webcam C920 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2.2:7 chip-ID: 046d:082d
class-ID: 0102 serial: <filter>
Device-4: RODE Microphones NT-USB type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-1:2 chip-ID: 19f7:0003
class-ID: 0300
Sound Server-1: ALSA v: k5.16.12-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion]
vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 2 link-max: lanes: 4 port: N/A bus-ID: 04:00.0 chip-ID: 1d6a:07b1
class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-14:10 chip-ID: 8087:0026 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:
Hardware-1: Intel Comet Lake PCH-H RAID driver: ahci v: 3.0 port: 4020
bus-ID: 00:17.0 chip-ID: 8086:06d6 rev: class-ID: 0104
Drives:
Local Storage: total: 1.62 TiB used: 3.5 MiB (0.0%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: N/A
size: 953.87 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: RKT343.4
temp: 27.9 C scheme: GPT
SMART: yes health: PASSED on: 8d 17h cycles: 142
read-units: 1,084,936 [555 GB] written-units: 1,766,041 [904 GB]
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 250GB
family: based SSDs size: 232.89 GiB block-size: physical: 512 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 2B6Q temp: 24 C
SMART: yes state: enabled health: PASSED on: 1y 288d 2h cycles: 2887
written: 32.81 TiB
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 250GB
family: based SSDs size: 232.89 GiB block-size: physical: 512 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 2B6Q temp: 25 C
SMART: yes state: enabled health: PASSED on: 1y 335d 13h cycles: 3162
written: 40.9 TiB
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 850 EVO 250GB
family: based SSDs size: 232.89 GiB block-size: physical: 512 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 1B6Q temp: 25 C
SMART: yes state: enabled health: PASSED on: 3y 124d 20h cycles: 2751
written: 40.93 TiB
ID-5: /dev/sdd maj-min: 8:48 type: USB model: OnePlus Device Driver
size: 8 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> rev: 0419 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.16 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 27.8 C mobo: N/A gpu: nouveau temp: 35.0 C
Fan Speeds (RPM): N/A gpu: nouveau fan: 0
Info:
Processes: 421 Uptime: 11m wakeups: 43 Memory: 31.16 GiB
used: 3.37 GiB (10.8%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 Packages: pacman: 1174 lib: 293 Shell: garuda-inxi (sudo)
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.13
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'chaotic-aur' does not exist (use '-Sy' to download)
Garuda (2.5.5-1):
System install date:     2022-03-12
Last full system update: 2022-03-12
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:            snapper-cleanup.service

I also specify that this system has already run garuda without problems in the past but now I can't even install it.

2

I can confirm this issue exists on Lenovo IdeaPad 3 and Dell Optiplex 5040.

3

That log doesn't seem very helpful, since there are not any obvious errors in it.

You shouldn't have to, but have you tried naming the filesystem (so that last command has an actual value in it)? You should be able to type in a name on the partitioning step where you assign mount points.

2 Likes
4

Maybe you could also get some more information from the terminal installing with

sudo -E calamares -d
1 Like
5

There seems to be the same issue on Manjaro 21.2.4:

1 Like
6

It appears to be a Calamares bug that has already been reported here: The installer failed to create a partition table on disk with previous AlmaLinux install. · Issue #1898 · calamares/calamares · GitHub

4 Likes
7

I'm not sure that is the same issue. For me the issue occurs even when the disk is without partitions before starting the installation.

Regardless, unchecking On Login and On Attach in Plasma settings -> Removable Storage -> Removable Devices seems to work around the issue.

4 Likes
8

After reading through the bug report more carefully, I think you are right--it does not seem like the same issue.

If you can reproduce your issue it might be helpful to submit a new bug report. Either way, I am glad you found a workaround! :blush:

3 Likes
9

Judging by the log contents and the mention of KDE, this could be the one: Calamares fails to create partitions · Issue #1872 · calamares/calamares · GitHub

1 Like
10

This solves the problem. I am not flagging it as a solution because I consider it a workaround, not a solution. The real solution is to fix the bug.

11

It is not a bug fix, but helpful for searchers until the bug is fixed.
So it can be marked.

4 Likes
12

The solution is in progress, per Calamares 3.2.53 released - Calamares

Automount-manipulation (to switch off KDE Plasma automounting new devices) now logs slightly more as it works. Defaults have changed in KDE Plasma 5.24 and it turns out the automount-manipulation does not work well. Distro’s are encouraged to turn off automount in the live ISO (see #1885).

#1885 is VBOX HARDDISK - authentication now required during installation to mount /dev/sda1 · Issue #1885 · calamares/calamares · GitHub

13

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