Hello, I've received an io-error. I would like to know how to pinpoint what the cause of the problem is, to address the correct issue and avoid repeats.
I ran some tests
I'm guessing the hard drive is faulty, but would like to confirm which hard drive, before physically replacing.
Also, how do I check all the hard drives in the server without physically opening up the machine?
I would like to confirm harddrives running Proxmox and if or what hard drives are running the servers, such as CentOS where the io-error appeared on the GUI. The Proxmox GUI also showed the CPU usage at 101.5%, but was running fine, until I logged in and saw the io-error.
I ran some tests
Code:
Proxmox > /var/logs/messages:
Mar 13 06:25:01 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 14 06:25:01 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 15 06:25:01 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 16 06:25:02 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 17 06:25:02 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 18 06:25:02 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Mar 18 21:31:46 proxmox kernel: vmbr0: port 5(tap145i0) entering disabled state
Mar 18 21:31:58 proxmox kernel: vmbr0: port 4(tap144i0) entering disabled state
Mar 18 21:33:10 proxmox kernel: device tap144i0 entered promiscuous mode
Mar 18 21:33:10 proxmox kernel: vmbr0: port 4(tap144i0) entering forwarding state
Mar 19 06:25:02 proxmox rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2481" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Code:
root@proxmox:/var/log# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 pve lvm2 a-- 111.29g 13.87g
root@proxmox:/var/log# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz--n- 111.29g 13.87g
root@proxmox:/var/log# lvs
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
data pve -wi-ao--- 55.79g
root pve -wi-ao--- 27.75g
swap pve -wi-ao--- 13.88g
root@proxmox:/var/log# dmsetup ls --tree
pve-swap (253:1)
└─ (8:3)
pve-root (253:0)
└─ (8:3)
pve-data (253:2)
└─ (8:3)
root@proxmox:/var/log# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=2045157,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1638148k,mode=755)
/dev/mapper/pve-root on / type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=0,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3276280k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
/dev/sda2 on /boot type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
/dev/sde1 on /mnt/backup type ext4 (rw,relatime,barrier=1,data=ordered)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
beancounter on /proc/vz/beancounter type cgroup (rw,relatime,blkio,name=beancounter)
container on /proc/vz/container type cgroup (rw,relatime,freezer,devices,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,relatime,cpuacct,cpu,cpuset,name=fairsched)I'm guessing the hard drive is faulty, but would like to confirm which hard drive, before physically replacing.
Also, how do I check all the hard drives in the server without physically opening up the machine?
I would like to confirm harddrives running Proxmox and if or what hard drives are running the servers, such as CentOS where the io-error appeared on the GUI. The Proxmox GUI also showed the CPU usage at 101.5%, but was running fine, until I logged in and saw the io-error.