Pulled only disk on running system

Nov 16, 2022
105
12
18
Sweden
Hi,

My second post here.

Yesterday I planned to add a second disk to my single-disk ZFS setup running Proxmox 7.2. I was a bit tired and accidentally pulled the only disk for the OS system - rpool (storage for VMs being on another pool). System was still running but I immediately got a bunch of errors from the kernel that the disk was OFFLINE, that systemctl was interrupted, and loads of other stuff. I put the disk back in when I realized my mistake, but everything froze, so I did a hard reset on the whole system.

After the incident I directly added the second disk to the system and made it a mirror pool. I did a scrub afterwards, and both resilver and scrub checked out OK for the OS pool (rpool). I then added a SLOG to the storage pool and the scrub is still running on that one.

Now, Proxmox was booting and everything seems OK as of today, but I think I experience higher loads on the system (might be my worried imagination). So my question is; should I be worried that I damaged anything? The setup is still quite new and I could just go through the hassle of making a new installation and restore backups for all the VMs, but do I really need to do that? I mean, scrub checks out without any cheksum errors, system is booting fine, and I can't seem to notice anything except maybe higher load - which could be because of other factors like the scrub. And yeah, VNC doesn't work on my Windows machines anymore, but that might also just be temporary.

proxmox-ve: 7.2-1 (running kernel: 5.15.64-1-pve) pve-manager: 7.2-11 (running version: 7.2-11/b76d3178) pve-kernel-5.15: 7.2-13 pve-kernel-helper: 7.2-13 pve-kernel-5.15.64-1-pve: 5.15.64-1 pve-kernel-5.15.30-2-pve: 5.15.30-3 ceph-fuse: 15.2.16-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve1 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-4 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-3 libpve-guest-common-perl: 4.1-4 libpve-http-server-perl: 4.1-4 libpve-storage-perl: 7.2-10 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 openvswitch-switch: 2.15.0+ds1-2+deb11u1 proxmox-backup-client: 2.2.7-1 proxmox-backup-file-restore: 2.2.7-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.1 pve-cluster: 7.2-2 pve-container: 4.2-3 pve-docs: 7.2-2 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-6 pve-firmware: 3.5-6 pve-ha-manager: 3.4.0 pve-i18n: 2.7-2 pve-qemu-kvm: 7.0.0-4 pve-xtermjs: 4.16.0-1 qemu-server: 7.2-4 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.6-pve1

Thanks for reading all the way down here.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!