We updated to new kernel and subsequently rebooted the two Proxmox PVE having the same behavior. We will provide the info should the situation not fixed with the new updates. Stay tuned.
Hi Community!
We have migrated to 7.2-7, the most surprises so far are with backups. We did adjusted to the new schedule format and was able to set up two schedules alternating for two different storage devices - "mon,wed,fri 01" on backup01, and "tue,thu,sat 01" on backup02
But to our...
I followed your instruction but did not see the syslog unfortunately. So I gave up and installed PVE on PERC's hardware raid instead of zfs raid, which was un-eventful. Thanks for the help.
@wolfgang and @guletz, I upgraded the bios to a 2019 released but the issue remained.
So I reinstalled PVE 6.2.1 in the debug mode which gave the command prompt after the install. I was able to manually import the the zfs pool. Thought it could be a timing issues, I modified the grub...
Wofgang, yes, the server has network connectivity. I do not quite understand what you mean by "first boot." This issue started after the seeming flawless installation. Thanks!
Thanks, Wolfgan! I could not get to the command prompt to access the logs. Here however was the last screen when the boot failed. Immediately prior to this last screen, there was the zpool import failure.
Yes, I was using the freshly made 6.2.1 ISO on a USB. Prior to the halt, I could see failure of "zpool import -N rpool". I was hoping I could do a manual import and continue at the command prompt.
Hi community!
I recently purchased a Dell PE T320 with PERC H310 flashed in IT mode. Today I managed to install PVE6.2.1 with ZFS RAID1, without any incident; however the system hangs with the last few lines like
random: systemd-udevd: uninitialized urandom read (16 bytes read)
random...
Fabian,
Just curious, if a hook script option is added to the vzdump.cron, will it be overwritten next time the backup settings are changed via the web ui?
Cheers,
Bo
Thanks Fabian.
I just found out that the backups that were supposed to go into the USB disk actually went into the USB mount point folder! The USB automount somehow never worked after the recent re-building of the Proxmox host machine.
Here is fstab entry at the /usbbackup mount point...
i am running Virtual Environment 6.1-8 on a host. The host machine halted due to the root space getting full or close to full. So I moved a few vms to a different Proxmox node. However, the root space did not reduce much if at all. I am baffled by this...
Here are couple of screenshots of...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.