Storage initialization via Web fails

[Underknowledge]

side Note:
While investigating this issue, discovered that explicit storage setup isn't required for initial Proxmox operation as the local storage can be used. However, this seem to prevent setting up additional storage types.

When attempting to initialize storage in Proxmox via the UI, the system fails to find necessary utilities despite adding them to the service PATH. While local storage can be used without explicit initialization, attempts to set up additional storage (LVM, LVM-Thin, or Directory) fail.

The following errors occurs during storage initialization:

# LVM
unable to change partition type for /dev/sda1: open3: exec of sgdisk -t1:8E00 /dev/sda failed: No such file or directory at /nix/store/m253dhx20wpg335gsljzddzlq1334lc9-perl-5.36.3-env/lib/perl5/site_perl/5.36.3/PVE/Tools.pm line 494.
  No command with matching syntax recognised.  Run 'vgcreate --help' for more information.
  vgcreate VG_new PV ...

TASK ERROR: pvcreate '/dev/sda1' error:   Correct command syntax is:

# LVM-Thin
unable to change partition type for /dev/sda1: open3: exec of sgdisk -t1:8E00 /dev/sda failed: No such file or directory at /nix/store/m253dhx20wpg335gsljzddzlq1334lc9-perl-5.36.3-env/lib/perl5/site_perl/5.36.3/PVE/Tools.pm line 494.
  No command with matching syntax recognised.  Run 'vgcreate --help' for more information.
  vgcreate VG_new PV ...

TASK ERROR: pvcreate '/dev/sda1' error:   Correct command syntax is:

# Directory
unable to change partition type for /dev/sda1: open3: exec of sgdisk -t1:8300 /dev/sda failed: No such file or directory at /nix/store/m253dhx20wpg335gsljzddzlq1334lc9-perl-5.36.3-env/lib/perl5/site_perl/5.36.3/PVE/Tools.pm line 494.
# /nix/store/2wvb4326f069mz8zan43yx6nak6lsjqk-util-linux-2.39.4-bin/bin/mkfs -t ext4 /dev/sda1
mkfs: failed to execute mkfs.ext4: No such file or directory
TASK ERROR: command '/nix/store/2wvb4326f069mz8zan43yx6nak6lsjqk-util-linux-2.39.4-bin/bin/mkfs -t ext4 /dev/sda1' failed: exit code 1

I tried to add the workaround mentioned in #28 or #63 by adding required utilities to the service PATH:

  systemd.services.pvedaemon.path = [ pkgs.zfs pkgs.e2fsprogs pkgs.gptfdisk pkgs.lvm2 pkgs.btrfs-progs ];
  systemd.services.pvestatd.path = [ pkgs.zfs pkgs.e2fsprogs pkgs.gptfdisk pkgs.lvm2 pkgs.btrfs-progs ];

However, this did not resolve the issue, but I was able to have some success with the directory:

# /nix/store/1z9gfzm7yp5ywcaznyqb6hipg6dz2hwm-gptfdisk-1.0.10/bin/sgdisk -n1 -t1:8300 /dev/sda
�Found valid GPT with corrupt MBR; using GPT and will write new
protective MBR on save.
The operation has completed successfully.
# /nix/store/2wvb4326f069mz8zan43yx6nak6lsjqk-util-linux-2.39.4-bin/bin/mkfs -t ext4 /dev/sda1
mke2fs 1.47.1 (20-May-2024)
Creating filesystem with 15629563 4k blocks and 3907584 inodes
Filesystem UUID: 6b305ebd-bff6-422a-8d22-491fbccbc808
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424

Allocating group tables:   0/477�������       �������done                            
Writing inode tables:   0/477�������       �������done                            
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information:   0/477�������       �������done

# /nix/store/2wvb4326f069mz8zan43yx6nak6lsjqk-util-linux-2.39.4-bin/bin/blkid /dev/sda1 -o export
TASK ERROR: unable to open file '/etc/systemd/system/mnt-pve-Blue\x2dUSB\x2dwith\x2dDebian\x2dSticker.mount.tmp.82271' - Read-only file system

systemd PrivateTmp? the path is very odd..

Both LVMs remained the same