Can't access proxmox web UI

redsky

New Member
Jun 22, 2023
8
0
1
ISSUE:

Issue started on reboot, I think it was after I assigned the proxmox login IP to 192.168.1.199 in web GUI before the restart.

I can access via putty logging in as root.

Can't access web UI, I have a feeling it's because of the inconsistency between my /etc/hosts/ (192.168.1.120) and ip a (192.168.1.199).

I have tried both below and neither work:

https://192.168.1.199:8006
https://192.168.1.120:8006

I have tried to sudo nano to modify the /etc/hosts file but the issue is I do not have sudo installed. When I try to install sudo, I see the partial folder is missing. The resolution online appears to mkdir it but I don't have sudo to do that :mad:

I have tried below but it did not resolve:

systemctl restart pveproxy.service pvedaemon.service

Any suggestions? Thanks for your help.

----------------------------------------------
OUTPUT:

apt install sudo

Code:
root@proxmox:~# apt install sudo
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory)

--------

/etc/hosts

Code:
127.0.0.1 localhost.localdomain localhost
192.168.1.120 proxmox.home proxmox

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

------

ip a

Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 1c:69:7a:6a:a5:31 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0c:7a:15:54:e6:60 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:69:7a:6a:a5:31 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.199/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::1e69:7aff:fe6a:a531/64 scope link
       valid_lft forever preferred_lft forever

-------

journalctl -f

Code:
-- Journal begins at Thu 2023-03-09 19:12:21 AEDT. --
Jun 27 17:52:47 proxmox pveproxy[909]: worker 1166 finished
Jun 27 17:52:47 proxmox pveproxy[909]: starting 2 worker(s)
Jun 27 17:52:47 proxmox pveproxy[909]: worker 1170 started
Jun 27 17:52:47 proxmox pveproxy[909]: worker 1171 started
Jun 27 17:52:47 proxmox pveproxy[1170]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 17:52:47 proxmox pveproxy[1171]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 17:52:47 proxmox pveproxy[909]: worker 1168 finished
Jun 27 17:52:47 proxmox pveproxy[909]: starting 1 worker(s)
Jun 27 17:52:47 proxmox pveproxy[909]: worker 1172 started
Jun 27 17:52:47 proxmox pveproxy[1172]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.

-------

hostname -i

192.168.1.120

-------
root@proxmox:~# cat /etc/network/interfaces
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface enx00e04c680112 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.199/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

iface wlp0s20f3 inet manual

------------

root@proxmox:~# nmap -p 8006 192.168.1.120

Code:
Starting Nmap 7.80 ( https://nmap.org ) at 2023-06-27 18:07 AEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 0.48 seconds

------------

root@proxmox:~# systemctl status pve-cluster.service
Code:
pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-06-27 21:05:04 AEST; 13s ago
    Process: 11171 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 8ms

Jun 27 21:05:04 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jun 27 21:05:04 proxmox systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 27 21:05:04 proxmox systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jun 27 21:05:04 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 27 21:05:04 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
root@proxmox:~#

-------------


root@proxmox:~# systemctl status pveproxy.service
Code:
 pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-06-27 21:02:22 AEST; 4min 54s ago
    Process: 11003 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111)
    Process: 11005 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 11006 (pveproxy)
      Tasks: 4 (limit: 9303)
     Memory: 135.0M
        CPU: 7.600s
     CGroup: /system.slice/pveproxy.service
             ├─11006 pveproxy
             ├─11284 pveproxy worker
             ├─11285 pveproxy worker
             └─11286 pveproxy worker

Jun 27 21:07:14 proxmox pveproxy[11006]: worker 11284 started
Jun 27 21:07:14 proxmox pveproxy[11006]: worker 11281 finished
Jun 27 21:07:14 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 21:07:14 proxmox pveproxy[11006]: worker 11285 started
Jun 27 21:07:14 proxmox pveproxy[11006]: worker 11282 finished
Jun 27 21:07:14 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 21:07:14 proxmox pveproxy[11006]: worker 11286 started
Jun 27 21:07:14 proxmox pveproxy[11284]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 21:07:14 proxmox pveproxy[11285]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 21:07:14 proxmox pveproxy[11286]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
root@proxmox:~#
 
Last edited:
I have tried to sudo nano to modify the /etc/hosts file but the issue is I do not have sudo installed. When I try to install sudo, I see the partial folder is missing. The resolution online appears to mkdir it but I don't have sudo to do that :mad:
If you are already logged in as root user, you don't need sudo to modify the /etc/hosts.

192.168.1.120 proxmox.home proxmox
So you have to replace the /etc/hosts file using nano/vim (without sudo if you are root) and replace the 120 to 199.
 
Thanks for the reply, logged in as root@proxmox:

I get when opening:

File '/etc/hosts' is unwritable

I get when saving:

Error writing /etc/hosts: Read-only file system

Running chmod I get:

root@proxmox:~# chmod 777 /etc/hosts
chmod: changing permissions of '/etc/hosts': Read-only file system
 
Thank you for the output!

Can you also check if the /etc/pve is mounted using `ls /etc/pve` command?

Did you see anything in the syslog journalctl -f?
 
Thank you for the output!

Can you also check if the /etc/pve is mounted using `ls /etc/pve` command?

This returns nothing.

Did you see anything in the syslog journalctl -f?

There are a whole bunch of action-2 and action-11 messages but I cut them out as they went over post length (the ... bit).

Code:
root@proxmox:~# journalctl -f
-- Journal begins at Thu 2023-03-09 19:12:21 AEDT. --
Jun 27 23:44:51 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:44:51 proxmox pveproxy[11006]: worker 19473 finished
Jun 27 23:44:51 proxmox pveproxy[11006]: worker 19477 started
Jun 27 23:44:51 proxmox pveproxy[19477]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:44:51 proxmox pveproxy[11006]: worker 19475 finished
Jun 27 23:44:51 proxmox pveproxy[11006]: starting 2 worker(s)
Jun 27 23:44:51 proxmox pveproxy[11006]: worker 19478 started
Jun 27 23:44:51 proxmox pveproxy[11006]: worker 19479 started
Jun 27 23:44:51 proxmox pveproxy[19478]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:44:51 proxmox pveproxy[19479]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:44:53 proxmox spiceproxy[19476]: worker exit
Jun 27 23:44:53 proxmox spiceproxy[915]: worker 19476 finished
Jun 27 23:44:53 proxmox spiceproxy[915]: starting 1 worker(s)
Jun 27 23:44:53 proxmox spiceproxy[915]: worker 19482 started
Jun 27 23:44:53 proxmox spiceproxy[19482]: unable to open log file '/var/log/pveproxy/access.log' - Read-only file system
Jun 27 23:44:56 proxmox pveproxy[19477]: worker exit
Jun 27 23:44:56 proxmox pveproxy[19478]: worker exit
Jun 27 23:44:56 proxmox pveproxy[19479]: worker exit
Jun 27 23:44:56 proxmox pveproxy[11006]: worker 19477 finished
Jun 27 23:44:56 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:44:56 proxmox pveproxy[11006]: worker 19483 started
Jun 27 23:44:56 proxmox pveproxy[19483]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:44:56 proxmox pveproxy[11006]: worker 19478 finished
Jun 27 23:44:56 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:44:56 proxmox pveproxy[11006]: worker 19479 finished
Jun 27 23:44:56 proxmox pveproxy[11006]: worker 19484 started
Jun 27 23:44:56 proxmox pveproxy[19484]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:44:58 proxmox spiceproxy[19482]: worker exit
Jun 27 23:44:58 proxmox spiceproxy[915]: worker 19482 finished
Jun 27 23:44:58 proxmox spiceproxy[915]: starting 1 worker(s)
Jun 27 23:44:58 proxmox spiceproxy[915]: worker 19485 started
Jun 27 23:44:58 proxmox spiceproxy[19485]: unable to open log file '/var/log/pveproxy/access.log' - Read-only file system
Jun 27 23:45:01 proxmox cron[891]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jun 27 23:45:01 proxmox pveproxy[19483]: worker exit
Jun 27 23:45:01 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:45:01 proxmox pveproxy[11006]: worker 19486 started
Jun 27 23:45:01 proxmox pveproxy[19484]: worker exit
Jun 27 23:45:01 proxmox pveproxy[19486]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:45:01 proxmox pveproxy[11006]: worker 19483 finished
Jun 27 23:45:01 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:45:01 proxmox pveproxy[11006]: worker 19487 started
Jun 27 23:45:01 proxmox pveproxy[19487]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:45:01 proxmox pveproxy[11006]: worker 19484 finished
Jun 27 23:45:01 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:45:01 proxmox pveproxy[11006]: worker 19488 started
Jun 27 23:45:01 proxmox pveproxy[19488]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:45:03 proxmox spiceproxy[19485]: worker exit
Jun 27 23:45:03 proxmox spiceproxy[915]: worker 19485 finished
Jun 27 23:45:03 proxmox spiceproxy[915]: starting 1 worker(s)
Jun 27 23:45:03 proxmox spiceproxy[915]: worker 19489 started
Jun 27 23:45:03 proxmox spiceproxy[19489]: unable to open log file '/var/log/pveproxy/access.log' - Read-only file system
Jun 27 23:45:06 proxmox pveproxy[19486]: worker exit
Jun 27 23:45:06 proxmox pveproxy[19487]: worker exit
Jun 27 23:45:06 proxmox pveproxy[11006]: worker 19486 finished
Jun 27 23:45:06 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:45:06 proxmox pveproxy[11006]: worker 19490 started
Jun 27 23:45:06 proxmox pveproxy[19488]: worker exit
Jun 27 23:45:06 proxmox pveproxy[19490]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:45:06 proxmox pveproxy[11006]: worker 19487 finished
Jun 27 23:45:06 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:45:06 proxmox pveproxy[11006]: worker 19491 started
Jun 27 23:45:06 proxmox pveproxy[19491]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:45:06 proxmox pveproxy[11006]: worker 19488 finished
Jun 27 23:45:06 proxmox pveproxy[11006]: starting 1 worker(s)
Jun 27 23:45:06 proxmox pveproxy[11006]: worker 19492 started
Jun 27 23:45:06 proxmox pveproxy[19492]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1899.
Jun 27 23:45:08 proxmox spiceproxy[19489]: worker exit
Jun 27 23:45:08 proxmox rsyslogd[739]: action 'action-1-builtin:omfile' resumed (module 'builtin:omfile') [v8.2102.0 try https://www.rsyslog.com/e/2359 ]
Jun 27 23:45:08 proxmox rsyslogd[739]: action 'action-2-builtin:omfile' resumed (module 'builtin:omfile') [v8.2102.0 try https://www.rsyslog.com/e/2359 ]
...
Jun 27 23:45:08 proxmox spiceproxy[915]: worker 19489 finished
Jun 27 23:45:08 proxmox spiceproxy[915]: starting 1 worker(s)
Jun 27 23:45:08 proxmox spiceproxy[915]: worker 19493 started
Jun 27 23:45:08 proxmox spiceproxy[19493]: unable to open log file '/var/log/pveproxy/access.log' - Read-only file system

What does "mount" report?


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I added mount earlier for an external hard drive attached to the NUC that Proxmox is on. This should be the /dev/sdb1 on /media/usb5 portion.

Code:
root@proxmox:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=3969416k,nr_inodes=992354,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=800624k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (ro,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16249)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/sdb1 on /media/usb5 type ntfs (ro,relatime,uid=0,gid=0,umask=00,nls=utf8,errors=continue,mft_zone_multiplier=1)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=800620k,nr_inodes=200155,mode=700,inode64)
root@proxmox:~#
 
Last edited:
Check with df -h if your root filesystem ("/dev/mapper/pve-root" or "/") is full. This is a common case why it switches read-only.
 
Check with df -h if your root filesystem ("/dev/mapper/pve-root" or "/") is full. This is a common case why it switches read-only.
Code:
root@proxmox:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                  3.8G     0  3.8G   0% /dev
tmpfs                 782M   82M  701M  11% /run
/dev/mapper/pve-root   65G   12G   50G  20% /
tmpfs                 3.9G     0  3.9G   0% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/sda2             511M  336K  511M   1% /boot/efi
/dev/sdb1             4.6T  3.9T  671G  86% /media/usb5
tmpfs                 782M     0  782M   0% /run/user/0
 
/dev/mapper/pve-root on / type ext4 (ro,relatime)
your root filesystem is marked RO, that usually happens when on boot inconsistencies are found that cant be repaired, or IO issues.
Examine your journal from start of boot : journalctl -b0
Look for events related to root.

But also check your /etc/fstab, although unlikely that was changed.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
your root filesystem is marked RO, that usually happens when on boot inconsistencies are found that cant be repaired, or IO issues.
Examine your journal from start of boot : journalctl -b0
Look for events related to root.

But also check your /etc/fstab, although unlikely that was changed.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

root@proxmox:~# cat /etc/fstab

Code:
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro,rw,umask=0 0 1
UUID=8A6D-84F3 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

I restarted and ran journalctl -b0 - here's some section of it, that are red or look suspicious. There are a large number of messages after which look related to the read-only file system issue.

Code:
Jun 28 00:05:02 proxmox kernel: Policy zone: Normal
Jun 28 00:05:02 proxmox kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve root=/dev/mapper/pve-root ro quiet
Jun 28 00:05:02 proxmox kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve", will be passed to user space.
Jun 28 00:05:02 proxmox kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
Jun 28 00:05:02 proxmox kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)

Jun 28 00:05:02 proxmox kernel: AppArmor: AppArmor initialized
Jun 28 00:05:02 proxmox kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
Jun 28 00:05:02 proxmox kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
Jun 28 00:05:02 proxmox kernel: x86/cpu: SGX disabled by BIOS.
Jun 28 00:05:02 proxmox kernel: CPU0: Thermal monitoring enabled (TM1)
Jun 28 00:05:02 proxmox kernel: process: using mwait in idle threads
Jun 28 00:05:02 proxmox kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Jun 28 00:05:02 proxmox kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4

Jun 28 00:05:02 proxmox kernel: ACPI: button: Power Button [PWRF]
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Local Variables are initialized for Method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: No Arguments are initialized for method [_CPC]
Jun 28 00:05:02 proxmox kernel:
Jun 28 00:05:02 proxmox kernel: ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Jun 28 00:05:02 proxmox kernel: thermal LNXTHERM:00: registered as thermal_zone0
Jun 28 00:05:02 proxmox kernel: ACPI: thermal: Thermal Zone [TZ0] (-263 C)
Jun 28 00:05:02 proxmox kernel: thermal LNXTHERM:01: registered as thermal_zone1
Jun 28 00:05:02 proxmox kernel: ACPI: thermal: Thermal Zone [TZ00] (28 C)
Jun 28 00:05:02 proxmox kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jun 28 00:05:02 proxmox kernel: hpet_acpi_add: no address or irqs in _CRS

Jun 28 00:05:02 proxmox systemd[1]: Finished Load Kernel Module fuse.
Jun 28 00:05:02 proxmox systemd[1]: Mounted RPC Pipe File System.
Jun 28 00:05:02 proxmox kernel: EXT4-fs (dm-1): Unrecognized mount option "umask=0" or missing value
Jun 28 00:05:02 proxmox systemd[1]: modprobe@drm.service: Succeeded.
Jun 28 00:05:02 proxmox systemd[1]: Finished Load Kernel Module drm.
Jun 28 00:05:02 proxmox systemd[1]: Mounting FUSE Control File System...
Jun 28 00:05:02 proxmox systemd[1]: Mounting Kernel Configuration File System...
Jun 28 00:05:02 proxmox systemd[1]: Mounted FUSE Control File System.
Jun 28 00:05:02 proxmox systemd[1]: Mounted Kernel Configuration File System.
Jun 28 00:05:02 proxmox kernel: Loading iSCSI transport class v2.0-870.
Jun 28 00:05:02 proxmox systemd[1]: Started Device-mapper event daemon.
Jun 28 00:05:02 proxmox kernel: iscsi: registered transport (tcp)
Jun 28 00:05:02 proxmox systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
Jun 28 00:05:02 proxmox systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
Jun 28 00:05:02 proxmox systemd[1]: Failed to start Remount Root and Kernel File Systems.
Jun 28 00:05:02 proxmox systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Jun 28 00:05:02 proxmox systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
Jun 28 00:05:02 proxmox systemd[1]: Starting Load/Save Random Seed...
Jun 28 00:05:02 proxmox systemd[1]: Condition check resulted in Create System Users being skipped.
Jun 28 00:05:02 proxmox systemd[1]: Starting Create Static Device Nodes in /dev...
Jun 28 00:05:02 proxmox kernel: iscsi: registered transport (iser)
Jun 28 00:05:02 proxmox systemd[1]: Finished Load/Save Random Seed.
Jun 28 00:05:02 proxmox systemd[1]: Condition check resulted in First Boot Complete being skipped.
Jun 28 00:05:02 proxmox kernel: spl: loading out-of-tree module taints kernel.
Jun 28 00:05:02 proxmox kernel: znvpair: module license 'CDDL' taints kernel.
Jun 28 00:05:02 proxmox kernel: Disabling lock debugging due to kernel taint
Jun 28 00:05:02 proxmox systemd[1]: Finished Create Static Device Nodes in /dev.
Jun 28 00:05:02 proxmox systemd[1]: Starting Rule-based Manager for Device Events and Files...
Jun 28 00:05:02 proxmox systemd-journald[426]: Journal started
Jun 28 00:05:02 proxmox systemd-journald[426]: Runtime Journal (/run/log/journal/63e2555c16da46539a99cdca00c3adc6) is 8.0M, max 78.1M, 70.1M free.
Jun 28 00:05:02 proxmox systemd-modules-load[427]: Inserted module 'iscsi_tcp'
Jun 28 00:05:02 proxmox dmeventd[439]: dmeventd ready for processing.
Jun 28 00:05:02 proxmox systemd-remount-fs[428]: /bin/mount for / exited with exit status 32.
Jun 28 00:05:02 proxmox systemd-modules-load[427]: Inserted module 'ib_iser'
Jun 28 00:05:02 proxmox systemd-random-seed[448]: Failed to remove extended attribute, ignoring: Read-only file system
Jun 28 00:05:02 proxmox systemd-modules-load[427]: Inserted module 'vhost_net'
Jun 28 00:05:02 proxmox systemd[1]: Starting Flush Journal to Persistent Storage...
Jun 28 00:05:02 proxmox systemd-remount-fs[430]: mount: /: mount point not mounted or bad option.
Jun 28 00:05:02 proxmox systemd[1]: Started Journal Service.

Jun 28 00:05:03 proxmox networking[673]: networking: Configuring network interfaces
Jun 28 00:05:03 proxmox pvefw-logger[679]: unable to open file '/var/log/pve-firewall.log': Read-only file system
Jun 28 00:05:03 proxmox systemd-tmpfiles[682]: rm_rf(/tmp): Read-only file system
Jun 28 00:05:03 proxmox systemd[1]: pvefw-logger.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 28 00:05:03 proxmox systemd[1]: pvefw-logger.service: Failed with result 'exit-code'.
Jun 28 00:05:03 proxmox systemd[1]: Failed to start Proxmox VE firewall logger.
Jun 28 00:05:03 proxmox systemd-tmpfiles[682]: Setting access ACL "u::rwx,g::r-x,g:adm:r-x,m::r-x,o::r-x" on /var/log/journal failed: Read-only file system
Jun 28 00:05:03 proxmox systemd-tmpfiles[682]: Cannot set file attribute for '/var/log/journal', value=0x00800000, mask=0x00800000, ignoring: Read-only file system
Jun 28 00:05:03 proxmox systemd-tmpfiles[682]: Setting access ACL "u::rwx,g::r-x,g:adm:r-x,m::r-x,o::r-x" on /var/log/journal/63e2555c16da46539a99cdca00c3adc6 failed: Read-only file system
Jun 28 00:05:03 proxmox systemd-tmpfiles[682]: Cannot set file attribute for '/var/log/journal/63e2555c16da46539a99cdca00c3adc6', value=0x00800000, mask=0x00800000, ignoring: Read-only file system
Jun 28 00:05:03 proxmox systemd-tmpfiles[682]: Setting access ACL "u::rw-,g::r-x,g:adm:r--,m::r--,o::---" on /var/log/journal/63e2555c16da46539a99cdca00c3adc6/system.journal failed: Read-only file system
Jun 28 00:05:03 proxmox systemd[1]: Finished Create Volatile Files and Directories.
Jun 28 00:05:03 proxmox systemd[1]: Starting RPC bind portmap service...
Jun 28 00:05:03 proxmox systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Jun 28 00:05:03 proxmox systemd-update-utmp[703]: Failed to write wtmp record, ignoring: Read-only file system
Jun 28 00:05:03 proxmox systemd[1]: Finished Update UTMP about System Boot/Shutdown.
 
Last edited:
Jun 28 00:05:02 proxmox systemd-remount-fs[430]: mount: /: mount point not mounted or bad option.
try to mount the root manually after boot:
mount -o rw,remount /

if that works, comment our the fstab root line and enter something like:
/dev/pve/root / ext4 errors=remount-ro 0 1


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
try to mount the root manually after boot:
mount -o rw,remount /

if that works, comment our the fstab root line and enter something like:
/dev/pve/root / ext4 errors=remount-ro 0 1


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thanks - Is that first line just 1 command? I get the below output:

Code:
root@proxmox:~# mount -o rw,remount /
mount: /: mount point not mounted or bad option.

actually just remove this, just noticed it.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Unfortunately I get the same issue with editing /etc/fstab as I do with /etc/hosts (unwritable / read only file system)
 
Last edited:
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!