Damaged SSD after installing Proxmox with ZFS?

[gatoxx]

So I have this weird behavior after installing Proxmox 8.3.0 in two ThinkCentre M910Q's that are equipped with a 4TB SSD each.
The machines came with a Windows pre installed which seemed to be working fine. I booted into the install ISO and installed Proxmox 8.3.0 (latest ISO download as per today), set everything up (ZFS with RAID0) and rebooted.

Sadly the machine says there is no bootable operating system on the disk and BIOS shows NOTHING installed as the "M.2 Drive 1" any more (as opposed to the initial state when Windows was still there, BIOS showed 4TB SSD).

When I now start the installer again, it shows an error message that there is no harddisk where Proxmox can be installed.

Did the Proxmox installer (or me) erase something from the disk to make it inaccessible to the BIOS? Did I accidentally damage the SSD?
I got the same behavior on both machines so I exclude a hardware error on both SSDs at the same time.

 

[arcticheat]

I had the exact same thing happen to me on 8.3. I was following the instructions here, which initially worked, but when I rebooted, it displayed a secure boot error. I tried disabling secure boot, and then it could no longer find the drives and errored with "failed to import pool 'rpool'. Manually import the pool and exit". Re-enabling secure boot didn't do anything.

Even after wiping the drive using killdisk in another computer and then trying to reinstall Proxmox from scratch with just one drive resulted in it "the installer could not find any supported hard disks".

Did you ever find a fix?

 

[arcticheat]

I got closer to the resolution by trying to run an Ubuntu install, but it asked me to turn off Intel Rapid Storage Technology before proceeding.

My issue was with a BIOS setting - "Configure Storage Controller for Intel Optane." In an HP Elitedesk, toggling "Configure Storage Controller for RAID" on and off, even without saving, causes the optane checkbox to enable but not disable when the storage controller option is unchecked. So, even though I didn't think I changed a setting, I accidentally did. Disabling "Configure Storage Controller for Intel Optane" fixed the issue.

 

[gatoxx]

I never found a proper fix (tried A LOT in the BIOS settings) but I installed a cheap SATA ssd as the boot disk and installed proxmox there. I now use the 4 TB nvme ssd as a secondary internal disk in my ThinkCentres with ext4 format instead of zfs. This setup works quite well so far but obviously isn’t what I intended with the machines.