Category: Computer

Computer is miraculous!

Check CPU temperature

Posted on by Bian Xi Leave a Comment on Check CPU temperature

Check CPU temperature

Windows

Download and run CPUID HWMonitor.

Download and install HWiNFO

Linux

Run following command

cat /sys/class/thermal/thermal_zone*/temp

MacOS

Download and run XRG

Synology

System

  • Go to Control Panel -> Info Center -> General

  • CPU cores

/sys/devices/platform/coretemp.0/temp3_input
/sys/devices/platform/coretemp.0/temp2_input

following files might be useful

/sys/devices/platform/coretemp.0/temp3_label
/sys/devices/platform/coretemp.0/temp2_crit_alarm
/sys/devices/platform/coretemp.0/temp2_crit
/sys/devices/platform/coretemp.0/temp3_crit
/sys/devices/platform/coretemp.0/temp3_crit_alarm
/sys/devices/platform/coretemp.0/temp2_label
  • Run following command (not working)
cat /sys/class/hwmon/hwmon0/device/temp1_input

Disk

  • Go to Control Panel -> Info Center -> Storage

  • Run following commands

smartctl -d sat -T permissive -l scttempsts /dev/sdX | grep Current
  • Run following commands
synodisk --read_temp /dev/sda

References

CPUID HWMonitor
Professional System Information and Diagnostics
How to Check CPU Temperature on Linux
XRG

Import existing zpool as Proxmox storage

Posted on by Bian Xi Leave a Comment on Import existing zpool as Proxmox storage

Import existing zpool as Proxmox storage

Steps

Import zpool

zpool import <existing_pool_name> <new_pool_name>

Create storage

Create storage via GUI

You have to connect to the node where you create the zpool to create storage in Proxmox Datacenter.

References

ZFS Pool Import - Proxmox single host reinstall without full backup
zpool not shown when add storage

Disable Windows `thumbs.db` file creation

Posted on by Bian Xi Leave a Comment on Disable Windows `thumbs.db` file creation

Disable Windows thumbs.db file creation

Steps

  • Run gpedit.msc
  • Navigate to User Configuration -> Administrative Templates -> Windows Components -> File Explorer
  • Double-click on the Turn off the caching of thumbnails in hidden thumbs.db files setting
  • Select the Enabled option.
  • Click the OK button.

References

How to disable Windows Thumbs.db files from being created

Change configuration of `systemd-resolved`

Posted on by Bian Xi Leave a Comment on Change configuration of `systemd-resolved`

Change configuration of systemd-resolved

If the configuration in /etc/resolv.conf as below

...
nameserver=127.0.0.53
...

Most likely the DNS configuration is controlled by systemd-resolved service.

To confirm, run following command

lsof -i :53

or

ls -ld /etc/resolv.conf

Change configuration

Change /etc/resolv.conf

If change /etc/resolv.conf directly, the file will be overwritten by systemd-resolved again when next reboot, because the file /etc/resolv.conf is a link as below.

lrwxrwxrwx 1 root root 39 Oct  5  2021 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

If recreate the file /etc/resolv.conf, then it could be overwritten by systemd-resolved when run service reconfiguration.

Change /etc/systemd/resolved.conf

The configuration of systemd-resolved is in /etc/systemd/resolved.conf, it can be changed as below.

DNS=<DNS_Server>
Domains=<Doman_name>
....

References

Changing DNS with systemd-resolved

Error Starting Proxmox VM: `pve-ssl.pem` is empty

Posted on by Bian Xi Leave a Comment on Error Starting Proxmox VM: `pve-ssl.pem` is empty

Error Starting Proxmox VM: pve-ssl.pem is empty

Got following error when starting a Proxmox VM with Spice driver.

kvm: warning: Spice: reds.c:2893:reds_init_ssl: Could not load certificates from /etc/pve/local/pve-ssl.pem
kvm: warning: Spice: error:0909006C:PEM routines:get_name:no start line
kvm: warning: Spice: error:140DC009:SSL routines:use_certificate_chain_file:PEM lib
kvm: failed to initialize spice server
TASK ERROR: start failed: QEMU exited with code 1

pve-ssl.pem size

The file size of /etc/pve/local/pve-ssl.pem is 0.

Fix

Standalone server

Regenerate following files using method stated in https://pve.proxmox.com/wiki/Proxmox_SSL_Error_Fixing

/etc/pve/pve-root-ca.pem
/etc/pve/local/pve-ssl.key
/etc/pve/local/pve-ssl.pem

Cluster node

Copy following files from other Proxmox node, normally, /etc/pve/pve-root-ca.pem files are the same.

/etc/pve/nodes/<node_name>/pve-ssl.key
/etc/pve/nodes/<node_name>/pve-ssl.pem

Note: These certificates can be used for all nodes.
Note: /etc/pve/local is a link to nodes/<node_name>

References

Proxmox SSL Error Fixing

Change Subscription of Proxmox VE to `pve-no-subscription`

Posted on by Bian Xi Leave a Comment on Change Subscription of Proxmox VE to `pve-no-subscription`

Change Subscription of Proxmox VE to pve-no-subscription

In order to update PVE, server needs to be under pve-no-subscription

Error

Following error occurred if the subscription hasn't changed.

starting apt-get update
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease
Get:3 http://ftp.debian.org/debian bullseye-updates InRelease [39.4 kB]
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
  401  Unauthorized [IP: 51.79.159.216 443]
Reading package lists...
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease  401  Unauthorized [IP: 51.79.159.216 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
TASK ERROR: command 'apt-get update' failed: exit code 100

Fix

Got to Updates => Repositories, add No-Subscription in the list, and disable pve-enterprise subscription.

References

Package Repositories

Failed to start Corosync Cluster Engine After PVE Reboot

Posted on by Bian Xi Leave a Comment on Failed to start Corosync Cluster Engine After PVE Reboot

Failed to start Corosync Cluster Engine After PVE Reboot

Error

After reboot PVE, following error occurred.

# systemctl status pve-cluster
...
Jun 26 09:33:26 pve01 pmxcfs[3506]: [quorum] crit: quorum_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [quorum] crit: can't initialize service
Jun 26 09:33:26 pve01 pmxcfs[3506]: [confdb] crit: cmap_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [confdb] crit: can't initialize service
Jun 26 09:33:26 pve01 pmxcfs[3506]: [dcdb] crit: cpg_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [dcdb] crit: can't initialize service
Jun 26 09:33:26 pve01 pmxcfs[3506]: [status] crit: cpg_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [status] crit: can't initialize service
...
# journalctl -u corosync.service
...
Jun 26 09:26:17 pve01 corosync[1826]:   [MAIN  ] failed to parse node address 'pve01.xx.xx'
Jun 26 09:26:17 pve01 corosync[1826]:   [MAIN  ] Corosync Cluster Engine exiting with status 8 at main.c:1417.
Jun 26 09:26:17 pve01 systemd[1]: corosync.service: Main process exited, code=exited, status=8/n/a
Jun 26 09:26:17 pve01 systemd[1]: corosync.service: Failed with result 'exit-code'.
Jun 26 09:26:17 pve01 systemd[1]: Failed to start Corosync Cluster Engine.
...

Fix

Change ring0_addr pve01.xx.xx of node in pve01 corosync.conf to IP address.

References

cluster node cant sync after reboot