Recent content by Wouter Samaey

I'm running into an issue where Proxmox shuts down unexpectedly. I noticed this a few times when my server would not remain online and just goes down after some time after boot. I had an SSH connection open at the time and the message "The system will suspend now" appeared just before. Looks...

Hey @Kingneutron . I took your advice. Bought 2 small SSDs and installed Proxmox fresh on these 2 disks using ZFS Raid1. These will be for OS only. Proxmox is now booting, and the previous zpool is available (i did rename it so not to conflict with the new rpool). Is there a guide on next...

Thanks for your help so far. I was able to mount the zfs rpool (i only have the 1 zpool and everything is in there), but after mounting I’m not sure what should be next. Leaving Busybox with CTRL+D isn’t enough as a new error appears. I’m a bit out of my league here, so thanks a million

thank @Kingneutron . That was it. Iwas now able to continue with proxmox-boot-tool, but when finished and rebooting, I ended up in Busybox without any errors. I believe ZFS rpool was not imported somehow? I’m seeing on this forum some peope have issues with /etc/default/grub config, but mine...

I too got stuck with an unbootable legacy ZFS setup and am just now trying to switch to ESP using proxmox-boot-tool. I don’t have any partitions on hand that could be used, but I do have a ZFS cache disk that I have removed, partitioned and would now like to use as an ESP. I’ll re-add as cache...

But what about mDNS and Bonjour/avahi for example? Mac machines can find other machines using their hostname.local, just not the Proxmox VMs that are on the same LAN.

I have the latest version of Proxmox with a few containers and VMs and was wondering what if required for the other machines (Linux and Mac) to be able to reach these containers and VMs using `hostname.local` instead of using their IPs. On a Mac, you can tyrpically use the `hostname.local`...

I was able to write a shell script that runs after the backup, and that executes a curl command, kinda the same thing. the link provided by aaron explains it.

@tburger why does ZFS not create a BIOS Boot partition first? If we replace disks and forget to setup a bootloader, you can't boot anymore. Did the wise people at ZFS On Linux not consider this or is there something I don't know?

@tburger yes, they were WD Red 6TB disks with SMR. There's a separate forum thread about this: https://forum.proxmox.com/threads/zfs-cannot-replace-a-faulted-disk-every-new-disk-becomes-faulted-too-in-a-raidz2-rpool.76290/#post-340171 The WD Red Pro disks with CMR are good replacements.

The solution here is indeed booting from a live USB disk, mounting 3 things and running grub-install. This only works if there is no resilvering going on, so that’s confusing and terribly annoying. Why the disks are partitioned differently is beyond me. I’m now in the process of replacing all...

Using the new WD Red Pro disk, I was able to finish the resilvering succesfully. Phew! Thanks for your help, @aaron and @LnxBil

@LnxBil the errors have indeed disappeared after the resilver process. I'm now running a scrub. The 4 errors were all metadata errors, so that's why I wasn't sure how to fix them. I guess ZFS must've taken care of it?

I ordered new WD Red Pro drives (with CMR) and will update this post as I get them. @aaron Any ideas how to fix the metadata? There are 4 errors, but I can't tell which files for example. Do I simply scrub a few times? Read that this works for some people.

More dmesg