No access to the web interface

teknodisk

New Member
May 15, 2022
3
0
1
Hello,

No access to the web interface. If it is restarted, access to the web interface is available. But after a while I can't access it again. It gives this Error.
how can i fix continue i am having this problem.

Virtual Environment 7.1-7

HDD https://prnt.sc/u917ff0tjGaE

ss.jpg
 

Dunuin

Famous Member
Jun 30, 2020
6,749
1,571
149
Germany
Looks like either your root filesystem is full so it switched to read-only (check it with df -h) or your filesystem got corrupted (you should run a fsck then of the non-mounted root partition for example by booting into a live linux) or your disk is failing (you should check with smartctl the disk health and maybe replace the disk after backing it up).
 

teknodisk

New Member
May 15, 2022
3
0
1
my disks are not full Promox Virtual installation is installed on 256 GB nvme.

Virtual Machines are built on 500 GB nm and ssd in good health.

I take my backups on a separate hard disk, 256 GB SSD.

It works for 1 week, then the same problem occurs again, if I restart my proxmox server, it is fixed.




root@srv:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.1G 1.3M 3.1G 1% /run
/dev/mapper/pve-root 229G 5.5G 214G 3% /
tmpfs 16G 52M 16G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/nvme0n1p2 511M 328K 511M 1% /boot/efi
/dev/sda1 220G 34G 175G 16% /mnt/yedek
/dev/nvme1n1p1 458G 53G 382G 13% /mnt/pve/vm
/dev/fuse 128M 16K 128M 1% /etc/pve
tmpfs 3.1G 0 3.1G 0% /run/user/0
 

Dunuin

Famous Member
Jun 30, 2020
6,749
1,571
149
Germany
Reboot will likely run a fsck job fixing your filesystem errors. Then your ext4 corrupts again later switching to read-only to prevent further errors?
You could let memtest86+ run over night to test if maybe a bad RAM is currupting your root fs.
 
Last edited:

teknodisk

New Member
May 15, 2022
3
0
1
@Dunuin
I ran memtest and found no problems. rams not ecc


Could it be a problem with the following mount? I'm just keeping a backup here.



cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=39AB-F494 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
LABEL=YEDEKSSD /mnt/yedek ext4 defaults 0 2

Could it be a problem with the following mount? I'm just keeping a backup here.

root@srv:~# 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=16046596k,nr_inodes=4011649,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=3215876k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
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)
none 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=35687)
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/nvme0n1p2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda1 on /mnt/yedek type ext4 (rw,relatime)
/dev/nvme1n1p1 on /mnt/pve/vm type ext4 (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=3215872k,nr_inodes=803968,mode=700,inode64)
 
Last edited:

Dunuin

Famous Member
Jun 30, 2020
6,749
1,571
149
Germany
Your screenshots show that dm-1 (should be a device mapper of your LVM?) and and /var/log got O errors and those are on your NVMe.
 

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 your own in 60 seconds.

Buy now!