[SOLVED} MOW installation failing on Samsung NVMe SSD

[dibl]

I am attempting to install Masters of War on my System76 laptop, and ran into a problem. Here is the hardware, with the live MOW running on it:

Code Select Expand

System:
  Kernel: 6.2.6-1-siduction-amd64 arch: x86_64 bits: 64 Desktop: KDE Plasma
    v: 5.27.5 Distro: siduction 22.1.2 Masters_of_War - kde - (202303151559)
Machine:
  Type: Laptop System: System76 product: Oryx Pro v: oryp8
    serial: <superuser required>
  Mobo: System76 model: Oryx Pro v: oryp8 serial: <superuser required>
    UEFI: coreboot v: 2021-09-23_b9b0e89 date: 09/23/2021
Battery:
  ID-1: BAT0 charge: 60.3 Wh (100.0%) condition: 60.3/70.7 Wh (85.3%)
CPU:
  Info: 8-core model: 11th Gen Intel Core i7-11800H bits: 64 type: MT MCP
    cache: L2: 10 MiB
  Speed (MHz): avg: 2217 min/max: 800/4600 cores: 1: 2300 2: 2300 3: 2300
    4: 2300 5: 2300 6: 2300 7: 2300 8: 2300 9: 2300 10: 2300 11: 984 12: 2300
    13: 2300 14: 2300 15: 2300 16: 2300
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
  Device-2: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] driver: nouveau
    v: kernel
  Device-3: Bison BisonCam NB Pro driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
    resolution: 1920x1080~144Hz
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics (TGL GT1)
Audio:
  Device-1: Intel Tiger Lake-H HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.2.6-1-siduction-amd64 status: kernel-api
  Server-1: PipeWire v: 0.3.65 status: active
Network:
  Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp36s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb type: USB
  Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 3.0
Drives:
  Local Storage: total: 1.38 TiB used: 146.4 MiB (0.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
    size: 465.76 GiB
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS100T2B0C-00PXH0
    size: 931.51 GiB
  ID-3: /dev/sda model: USB DISK 2.0 size: 14.45 GiB type: USB
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 1546
Info:
  Processes: 297 Uptime: 1h 55m Memory: available: 31.2 GiB
  used: 6.73 GiB (21.6%) Shell: Bash inxi: 3.3.27
 
I prepared the SSD in advance, using the partitioning scheme shown in this article. I like this plan, and when my old SSD failed in my main desktop, I used it on my new NVMe SSD and it worked perfectly to install MOW, about two weeks ago.

Using the same MOW USB stick, it fails with a calamares "failed to unpack image /tmp/calames" and "rsync failed with error code 11". Screenshots attached. After it failed the first time, I installed gparted and took a screenshot that shows the partitions and it shows the mount points for /tmp/calamares -- it looks like there are four (4) of them.

I don't understand how it worked so well on the desktop, but not at all on the laptop. Both use 500 GB NVMe SSDs. Any suggestions?  Thanks!

[ro_sid]

I assume you made a typo when formatting the drive:
You have assigned only 40 MiB to the root-Partition. I do think, you meant 40 GiB (or more?).
[In the article cited, it are about 32 GiB.]
Good luck.

[vinzv]

Yip, that looks like something's wrong with your partition layout. But as far as I can see, the layout you tried to build yourself is pretty similar to the default layout. So maybe try sticking with this, at least for testing?

That said, I successfully installed Siduction MoW and earlier versions on laptops quite similar to the Oryx Pro (newer CPUs or different GPU variants). So, I have high hopes that it will work out for you as well. :-)

[dibl]

You have assigned only 40 MiB to the root-Partition. I do think, you meant 40 GiB (or more?).
...

OH Geez -- how did I miss that?  Yes, 40 GiB was the plan -- I think you have found my problem -- fixing and trying again.

[dibl]

YES, the problem was staring in my face -- the "MiB"s were intended to be GiBs. As soon as the partitioning was corrected, the installation finished perfectly. @ro_sid, come to Dayton and I'll buy you a beer!

Thank you.

[ro_sid]

You're welcome and I'm glad.

@ro_sid, come to Dayton and I'll buy you a beer!

Thank you very much for the offer, but its realization might take a while .