Hello all!
I've been noticing some weird remnants of either Proxmox, TrueNAS VM or both even after wiping the disks.
I would use the Windows 11 USB Boot to clean the drives using diskpart and then execute the 'clean' command on both the Proxmox 512GB NVMe and the 8TB Oyen NVME that is used for the TrueNAS VM.
On top of that I also run EaseUS Partition Master WinPE to destroy the partitions (if any) and format to NTFS -> Unformatted -> back to NTFS to make sure that all partitions and files are gone - leaving the disk squeaky clean. Sometimes I reboot and repeat the process again.
However, I have noticed that when I install Proxmox on the 512GB Firecuda NVMe, everything seems fine but when Proxmox boots I get an error message saying 'Cannot import ZFS pool'. Weird, the error message would only pop up when I have the TrueNAS VM set up with the 8TB Oyen NVMe as the NAS pool drive.
I click on the wipe option in the Proxmox GUI, initialize and use GPT, then start setting up a VM for TrueNAS. Once VM is booted up, and the 8TB NVMe configured for TrueNAS VM, I see that trueNAS is picking up the old NAS drive name and identifies that it was part of a different TrueNAS pool.
What would be the cause as to why data still remains even after a wipe? Would this happen to be something that is cached in the DRAM and causing it to populate once it sees the familiar OS (Proxmox) again?
Thank you for any info/assistance!
I've been noticing some weird remnants of either Proxmox, TrueNAS VM or both even after wiping the disks.
I would use the Windows 11 USB Boot to clean the drives using diskpart and then execute the 'clean' command on both the Proxmox 512GB NVMe and the 8TB Oyen NVME that is used for the TrueNAS VM.
On top of that I also run EaseUS Partition Master WinPE to destroy the partitions (if any) and format to NTFS -> Unformatted -> back to NTFS to make sure that all partitions and files are gone - leaving the disk squeaky clean. Sometimes I reboot and repeat the process again.
However, I have noticed that when I install Proxmox on the 512GB Firecuda NVMe, everything seems fine but when Proxmox boots I get an error message saying 'Cannot import ZFS pool'. Weird, the error message would only pop up when I have the TrueNAS VM set up with the 8TB Oyen NVMe as the NAS pool drive.
I click on the wipe option in the Proxmox GUI, initialize and use GPT, then start setting up a VM for TrueNAS. Once VM is booted up, and the 8TB NVMe configured for TrueNAS VM, I see that trueNAS is picking up the old NAS drive name and identifies that it was part of a different TrueNAS pool.
What would be the cause as to why data still remains even after a wipe? Would this happen to be something that is cached in the DRAM and causing it to populate once it sees the familiar OS (Proxmox) again?
Thank you for any info/assistance!