Recent content by urbanator

Ok, the server has been rebooted and is back up and running. Now just to wait and see if the edit above fixes things (it can takes days before it becomes unresponsive). :) Update: This seems to have fixed things, the server has been stable for around a month.

Hi Aaron, I'm giving that workaround another try tonight when I can reboot. I've edited /etc/lvm/lvm.conf so that it now filters out the tandberg drive (sdb): global_filter = ["r|/dev/sdb|", "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|" "r|/dev/mapper/.*-(vm|base)--[0-9]+--disk--[0-9]+|"] Here's the...

Hi, sorry to bring back an old thread. I have since transferred my old proxmox install onto new hardware, and need to use the Tandberg usb drive as part of new daily backups. As part of this I have set up cron-jobs to automatically mount the removable hard drives (it uses sata drive cartridges...

Hi dietmar, Yes, the BIOS has been updated to the latest, and I checked that VT-d is enabled in there also. I'm going to try re-flashing the USB stick again using Rufus + DD mode to try and rule out that being the issue.

Hi, I'm trying to install proxmox onto an old HP Proliant ML350 G6, but get the following error when trying to install: Anyone know what could be causing this? I'm not sure if this is an ISO related error, or hardware related. Thanks.

Another update on this; I disabled the "Cool'n'quiet" setting in the BIOS (using an AMD Ryzen setup) around 7 days ago and the system seems to be slightly more stable. It was going well for just over 4 days and then crashed again, and then 3 days after that before again crashing. Which is an...

Thanks, will give this a try and see how it goes.

Just an update on this, a memtest found no errors. I re-installed the latest kernel and headers to rule out any problems with that. I have installed kdump-tools but as suggested here, but it didn't create a log (I assume we need to give it longer to create the log and reboot). The only...

Hi, I'm having a problem with my proxmox server crashing intermittently (no CLI is shown just the kernel log), from anywhere between 90mins to 24hours after a reboot. I've checked the logs in /var/logs and have not found anything that stands out in them in the lead up to a crash. The first...

Update: After 3 days of disconnecting the Tandberg USB drive the server has been completely stable. I have re-enabled the scheduled daily backups and they now complete successfully, and the web interface no longer shows an unknown status. The drive was definitely the cause of the issues. I'm...

Thanks Aaron, that did the job and got the server booting up once again. We have decided to try the system without the Tandberg drive plugged in for the time being (as it is not currently being used anyway). I will report back on whether this solves any of the instability problems we have had...

Thanks I will give this a try. I think I did miss the closing "|". I did notice this after I edited the lvm.conf and ran the update process before the planned reboot, and the same syntax error was shown. I corrected the error then, but I'm guessing during the update the incorrect version had...

Yes I replaced <tandberg> it with sdc as this was the Tandberg drive, however I think there may have been a typo in there and I think it's filtering out the system disk which is the issue. It is dropping out to shell on bootup:

I noticed that a removable drive that is in my server is also a Tandberg drive, and edited the lvm.conf as suggested to try out the workaround. However after restarting the server, I get errors at boot stating that it has "failed to create a global regex device filter" and that there are...

Both pvs and lvs hang and do not output anything (I left them both running for ~30 mins). Here's the storage.cfg contents: