Search results

My curiosity: I have this server that I known it has an old disk that isn't in "perfect status" (many recent errors reported by smartctl -a). The GUI Disks table reports: GUI SMART Values reports: But a complete smartctl -a reports: === START OF INFORMATION SECTION === Model Family...

I had sshd listening on port 82. Changed the port and now I can log into PBS Seems this solve my first PBS problem and now I can start play ... ;-) Thanks, P.

# apt info libpve-storage-perl Package: libpve-storage-perl Version: 6.3-3 Priority: optional Section: perl Maintainer: Proxmox Support Team <support@proxmox.com> Installed-Size: 498 kB . . . I usually authenticate using Linux PAM as realm. Tried also P. B. Authentication server just in case...

I think it is a little different situation. I can't neither log in to :8007 Anyway, tried to replace "localhost" with "127.0.0.1" in /etc/pve/storage.cfg (odd bug if present), but the situation is unchanged. Thanks, P.

I have a test PVE box That I use as backup/spare. Reading of the new PBS since some month ago I decided to try an install following the instructions for "Proxmox Backup Server on Proxmox VE" (https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-proxmox-ve). Update PVE...

I tried to understand the situatiion using "top" & c., but I can't find a logical answer (for me). Top always give something like: top - 22:26:52 up 20 days, 21:38, 7 users, load average: 0.79, 0.75, 1.02 Tasks: 257 total, 1 running, 255 sleeping, 0 stopped, 1 zombie %Cpu(s): 0.6 us...

I have this small box that I use as firewall for my office/lab test. There are only 2 little VM running (both pfsense box with 1 GB RAM, minimal network traffic): # qm list VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 21971 pfSenseF1 running 1024...

Thanks. The "Manual approach" works fine (other methods don't works). some rows like: up ip addr add 192.168.1.43/24 dev $IFACE label $IFACE:0 down ip addr del 192.168.1.43/24 dev $IFACE label $IFACE:0 solved my needs. Regards, P.

Until Proxmox 4.x I used to add lines like: ifconfig vmbr0:74 99.99.99.99 broadcast 99.99.99.99 netmask 255.255.255.255 in /etc/rc.local In Proxmox 5.x (Debian 9.x), no more /etc/rc.local. I suppose I can create a service to have it again available, or I may play with some @reboot action in...

The P410i controller is in basic configuration with zero cache battery. There is a slot to add the cache, but this wasn't the problem. Not having cache only limits to max 2 defined array and for about 5 years it had worked fine before with Proxmox 2.x and then with ProxMox 4.x using a couple of...

I am going to fix my problem changing the topology of the disks, but still interested to hints that allow me to understand why the RAID controller blocks the boot and the pve management. And obviousy how to eventually fix them in a clean manner. Regards, P.

Nothing :-( Booting with a rescue CD I get: root@sysresccd /root % lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk sda1 8:1 0 1.8T 0 part sdb 8:16 0 1.8T 0 disk sdc 8:32 0 136.7G 0 disk sdc1 8:33 0 136.7G 0 part sdd 8:48...

Already tried. Added 'rootdelay=30' and tried also 5,10.20,100. Same result :-( If I connect the old defective disk (originally I had 2 disks in RAID-1 with one that present errors), the system boots normally. If I connect the old "good disk" to a PC it boots normally. Also the cloned disks tha...

Update: If I connect the disk to a standard PC, the Proxmox boot whitout problems (except for nic configuration ...). Attached to the controller I always have the usual result:

Trying to boot I obtain: Volume group "pve" not found Cannot process volume group pve Unable to find LVM volume pve/root Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the...

In my experience, update to the same kernel you are using, swappiness set to 0 AND a reboot solved. only set the swappiness to 0 having already the last kernel didn't solve (only LXC and mixed LXC/VM configuration). I temporary solved it with a "swapoff -a && swapon -a", until I could reboot the...

May be you can get some ideas from: https://forum.proxmox.com/threads/swap-usage.33062/ Regards, P.

I can only reports what I remember, not a full diagnosys. For VE 4.4 I remember that If I tried to install into an already used disks, it merged the installations. I finally found files from the previous install in what I suppose to be a fresh clean install. Same if I remove the partitions using...

proxmox-ve_5.0-af4267bf-4.iso Downloaded 2 days ago Same problem with proxmox-ve_4.4-eb2d6f1e-2.iso downloaded some months ago.

I don't know if it can considered a bug, but I noticied that istalling Proxmox VE (both 4.x and 5.x), into disks that was already used for installation (test or ...), cause many types of problems. It can simply not complete the installation or complete it but you last having a system that is a...