Proxmox ZFS Mirror, not accessible with one NVME down

E

enrax

New Member
Jun 29, 2025
2
0
1
As a total noob in Proxmox and in Linux, please bear with me...

I've been running TrueNAS approx 2 years now with HomeAssistant as an VM in truenas. Since HA was installed as Supervised, HA announced that this method will be deprecated. So I use this as an excuse to finally start learning Proxmox.
For hardware, I have a Asus Prime B550-Plus and I installed an extra NVME disk and installed Proxmox as a ZFS mirror. This for extra redundancy.
Installed HA and reinstalled the backup and passthrough USB. All good and all up and running in no time.
Then, to simulate a NVME failed disk, I disconnected one of the NVMEs and booted system again. System OK but with system degraded as expected. All accessible through browser.
I then reinstalled the NVME disk and did vica versa. Proxmox booted as normal but it's not possible to access it through a web browser. IP has not changed according to console.
Not possible to ping other PC's in the network from the console or to the Proxmox server so it seems that it's not on the network.
I can't figure out where to troubleshoot?
 
Sorry for late reply. I'm currently 2 weeks away from home due to work.

I've not documented what I did other that what's stated in the post above.
1. Installed proxmox. During installation, mirror ZFS was chosen. NVME 1tb installed in M2.1 and M2.2 slot.
2. After installation, Proxmox booted with local ip 192.168.1.149 and logged into webgui. Both NVME disk in healthy mirror condition
3. Shutdown system, removed NVME in M2.1 slot
4. Proxmox booted with local ip 192.168.1.149 and logged into webgui. System is degraded due to missing disk.
5. Shutdown system, reinstalled NVME in M2.1 slot. Removed NVME in M2.2 slot.
6. Proxmox booted with local ip 192.168.1.149. Not possible to access webgui
7. Logged in as root user. Tried to ping other devices in network. No response. Tried pinging Proxmox server from laptop on same network. No response.
8. Shutdown system and installed NVME disk from M2.1 slot to M2.2 slot.
9. Proxmox booted with local ip 192.168.1.149 and logged into webgui. System is degraded due to missing disk.
10. Reinstalled NVME disk in M2.1 slot
11. Proxmox booted with local ip 192.168.1.149 and logged into webgui. Both NVME disk in healthy mirror condition

These are the steps I performed. I did some google engineering but could not find any else with the same problem as I'm experincing. It seems that for some reason I'm not at the local network when booting from M2.1 slot? Not sure where to continue to troubleshoot from here. As mention before, I'm a noob in Linux.
 
You must log in or register to reply here.
Top Bottom