Search results

This example "mon *-1..7,15..21 15:00" does not work for me, I get an error message, Parameter verification failed. (400) schedule: invalid format - invalid calendar event 'mon *-1..7,15..21 15:00' - date specification not implemented at /usr/share/perl5/PVE/CalendarEvent.pm line 126.

I got the same issue, the cloning process just hanged after what seemed to be done.. but it was frozen and locked. So, this is the work around I did to get it working. 1: Stop the cloning (just click stop on the GUI) 2.- Go into host console and unlock the vm 3.- rm the config file 4.- CP the...

Hi, my backup jobs do not seem to finish today, I wanted to stop the job to release the VMs for work, but I can not find them on the task list, to STOP it. The VM shows as "config Lock (backup)" .. I need to stop the backup job. Please, how do I do it? I remember being able to just click on...

Adding drives might actually be the best solution, if you have the drives and the space. After a few years using proxmox I find that it works best with 'many' drives

Can't do that, this server only has 6 slots.

Thanks.. Lesson learned.. I will rebuilt the server next Monday if I can drive there.. It is not such a big job and rather not risk putting VMs on the server.. not becuase of the data, but because of possible downtime, even if only 3 minutes.. Thanks, really appreciate your help.

uff... thanks but that is not an option today either.. I am on 5.4-3 on this node... and I rather not try a remote update today.. I guess I'll have to drive to datacenter next week, if still possible with the coronavirus.. really appreciate your help.. do you think I have no redundancy at...

executed but nothing on screen root@pve1:~# zpool get feature@device_removal rpool root@pve1:~#

root@pve1:~# get feature@device_removal rpool -bash: get: command not found root@pve1:~#

root@pve1:~# dpkg-query -s zfsutils-linux Package: zfsutils-linux Status: install ok installed Priority: optional Section: contrib/admin Installed-Size: 1049 Maintainer: Proxmox Support Team <support@proxmox.com> Architecture: amd64 Source: zfs-linux Version: 0.7.13-pve1~bpo2 Provides: zfsutils...

How do I know that ?

It was already posted, but here it is again root@pve1:~# zpool status rpool pool: rpool state: ONLINE scan: resilvered 268G in 0h56m with 0 errors on Wed Mar 18 18:21:56 2020 config: NAME STATE READ WRITE CKSUM rpool...

I was actually thinking about that, just pulling the drive (it would be 10 minutes of engineer support) and hopefully get the zraid back to normal after removing that one... is that what you mean? just pull the drive from the server? and just to make sure, I can not add a 6th drive to a 5...

I appreciate your comments but there are several points to 'validate' This is one node of 3, I do put VMs on this node, but my calculation of load is that one of my 3 nodes should be able to handle all the VMs, so I only have 3 because I can :) I have 3 clusters, of 3 servers each..all more or...

Uppss, you got me there.. This was the default setup, I didn't know better and it has been running, no issue at all , until that one drive died, for almost 400 days. So, no, this is the boot drive, nothing else on this server... Does that mean, I am out of luck and my only option is to reformat...

What I meant with that, was not to drive to reinstall proxmox from scratch .. in which I need to physically connect the USB drive to boot into it. I have 100% terminal and web access. But I do not have "hands on" to actually put a USB on the server.

Thanks, appreciate the reply.. The remove does not work.

Hi, One of the drives on my 5 drives raidz2 failed. I replaced that one drive perfectly fine, and resilvered in about 35 minutes.. BUT my ambition got the best of me and I tried to add a 6th drive to the pool, and I thought it was perfectly added ... This is command I used zpool add rpool...

Yes... they work perfectly fine.. I have used the backups many times and not one problem.. Of course this is not the only backup I have since I use also a NAS and also local backups..

Very good point.. lol.. but you can also say that not always newer is better :)