Recent content by ptr727

Trying to install PVE 8.2 on a SuperMicro X10SDV-4C-7TP4F board, I write ISO to USB using Rufus (also tried Balena), boot from USB, see garbage pixels on top of physical VGA monitor screen, and also on remote HTML5 IPMI screen. Found forum posts that talks about needing to use `nomodeset` on...

I am using ZFS as storage, so QCOW2 automatically gets converted to RAW on import. I created a report, this seems like generally useful template functionality: https://bugzilla.proxmox.com/show_bug.cgi?id=5301

Thank you for the reply. The workaround is unfortunately no better than creating a new template every time the cloud image is updated, i.e. in-use templates cannot be deleted, and I will end up with a new template for every update, defeating the purpose of keeping one template per cloud image...

I am using `import-from` when create a VM or changing the assigned disk, and the imported disk images are always `raw`, wasting lots of space for templates. Using `qm set <vmid> --scsi0 "<storage>,import-from=<image>,format=qcow2"` creates a `raw` image, and ignores the `qcow2` format request...

I am trying to automate up to date cloud images for Ubuntu and Debian VM templates. Once a template has been cloned using linked clones, it is not possible to delete the template, so I just change the disk to be used in new clones, while the existing clones can still link to previous disk...

With no solution in sight I upgraded to PVE 8.0.3, and no more error 25. The upgrade did initially fail to install the kernel, I had to "dkms remove aufs/4.19+20190211", and after that all was well.

I did, as I mentioned in the stackoverflow post, same results, if I run the shell script over SSH console it works, if I run the shell script over Ansible script command it also weirdly fails with similar results. That is why I went the command route to refine the steps with e.g. conditional...

I also asked in stackoverflow, but trying here. I am updating my Ansible PVE deployment to create cloud image templates. I have a working shell script, and I just converted the commands to an Ansible "shell" command, the results are weird, sometimes working, sometimes not, sometimes I end up...

This has nothing to do with the expander not passing anything through. In this same chassis over the same expander SATA drives are correctly identified. The problem is the use of `ID_ATA_ROTATION_RATE_RPM`, it is not a reliable method to identify disk types. `ID_ATA_ROTATION_RATE_RPM` is an ATA...

SAS3 HBA to SAS3 backplane to SAS3 drive, typical config, really should not make a difference. Same config works with SATA drives, and obviously SATA is ATA so the SATA disks on the same chassis is detected as hard drives. The key here is that ID_ATA is missing, SAS drive not SATA drive, so you...

Ok, so it is a bug in the UI code then that looks for an ATA attribute that is typically not present for SAS drives, i.e. ID_ATA is not 1? How about looking for ID_DISK, or using info from smartctl (and please add disk temperature)?

root@server-2:~# cat /sys/block/sdd/queue/rotational 1 root@server-2:~# udevadm info -p /sys/block/sdd --query all | grep ID_ATA_ROTATION_RATE_RPM root@server-2:~# udevadm info -p /sys/block/sdd --query all P...

Hi, I just installed 4 x SAS3 drives in ZFS mirror config. The disks UI shows the type as unknown, and the serial number shows the WWN not the serial number. smartctl does identify the disks as SAS3, and does show the correct serial number. 1) How do I get the disk type to correctly show as...

I tried to install again, on a 64GB USB3 mSATA, this time I modified the install options, swapsize=8, minfree=0, maxvz=0, and maxroot=48, the result is a 14.8GB root volume. root@server-1:~# lsblk ... sdr 65:16 0 59.6G 0 disk ├─sdr1 65:17 0 1007K 0 part ├─sdr2...

I installed PVE ona 32GB USB stick, that leaves me with a 7GB pve-root partition, 3.5G for swap, and 12.1G for data. After using PVE for a week, I started running out of root space. I thought about re-installing and correcting the space allocation, but the install wiki says that the max root...