NAS DRIVE :: Showing READ-ONLY Error after few days

phoneme

New Member
May 19, 2020
10
0
1
29
We are using the common storage pool which is attached as the Network storage and then we are making the Volumes and allocating to the Virtual Machines .
The Common Storage Volume named Hartron-EDU is attached to the PVE Node as storage pool . as shown in image named " Hartron-EDU-Disk-Common-Storage.png "

This pool is then mounted on the Hartron-EDU-Disk-Common-Storage.png

Now this storage is further used as a disk in VM named Hartron 221 as shown in Hartron-EDU-Disk-Common-Storage.png

NFS-Mounted-VDA-VM.png



Now once it is mounted as a volume in the disk in VM then after running for few days it is giving the error . 221-VM-Snapshot.png

221-VM-Snapshot.png

I would request you to suggest if it is the right way of using the NAS based storage drive ?
How to remove the error in the same ?

Rg
 
how is that volume mounted? a 'mount' and 'df' should show more info.

also check your logs and dmesg why its getting mounted readonly
 
DMESG OUTPUT :---


[2905552.754540] device veth10eecd8 entered promiscuous mode
[2905552.759815] IPv6: ADDRCONF(NETDEV_UP): veth10eecd8: link is not ready
[2905552.759818] br-6ef4542e0242: port 1(veth10eecd8) entered blocking state
[2905552.759819] br-6ef4542e0242: port 1(veth10eecd8) entered forwarding state
[2905553.260455] br-6ef4542e0242: port 1(veth10eecd8) entered disabled state
[2905553.828818] eth0: renamed from vethe8e8c1d
[2905553.846012] IPv6: ADDRCONF(NETDEV_CHANGE): veth10eecd8: link becomes ready
[2905553.846061] br-6ef4542e0242: port 1(veth10eecd8) entered blocking state
[2905553.846063] br-6ef4542e0242: port 1(veth10eecd8) entered forwarding state
[3050273.739330] br-6ef4542e0242: port 1(veth10eecd8) entered disabled state
[3050273.745494] vethe8e8c1d: renamed from eth0
[3050273.803692] br-6ef4542e0242: port 1(veth10eecd8) entered disabled state
[3050273.811051] device veth10eecd8 left promiscuous mode
[3050273.811054] br-6ef4542e0242: port 1(veth10eecd8) entered disabled state
[3050274.099358] br-6ef4542e0242: port 1(veth27bbefd) entered blocking state
[3050274.099361] br-6ef4542e0242: port 1(veth27bbefd) entered disabled state
[3050274.099427] device veth27bbefd entered promiscuous mode
[3050274.099536] IPv6: ADDRCONF(NETDEV_UP): veth27bbefd: link is not ready
[3050274.099538] br-6ef4542e0242: port 1(veth27bbefd) entered blocking state
[3050274.099539] br-6ef4542e0242: port 1(veth27bbefd) entered forwarding state
[3050274.757051] br-6ef4542e0242: port 1(veth27bbefd) entered disabled state
[3050275.185707] eth0: renamed from veth600bd10
[3050275.211873] IPv6: ADDRCONF(NETDEV_CHANGE): veth27bbefd: link becomes ready
[3050275.211921] br-6ef4542e0242: port 1(veth27bbefd) entered blocking state
[3050275.211923] br-6ef4542e0242: port 1(veth27bbefd) entered forwarding state
[3808738.459478] sd 2:0:0:2: [sdb] tag#52 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[3808738.459486] sd 2:0:0:2: [sdb] tag#52 Sense Key : Aborted Command [current]
[3808738.459487] sd 2:0:0:2: [sdb] tag#52 Add. Sense: I/O process terminated
[3808738.459632] sd 2:0:0:2: [sdb] tag#52 CDB: Write(10) 2a 00 0a eb cb a0 00 00 08 00
[3808738.459871] print_req_error: I/O error, dev sdb, sector 183225248
[3808738.460715] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 52559983 (offset 0 size 4096 starting block 22903157)
[3808738.460718] Buffer I/O error on device sdb1, logical block 22902900
[3808738.632442] sd 2:0:0:2: [sdb] tag#63 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[3808738.632445] sd 2:0:0:2: [sdb] tag#63 Sense Key : Aborted Command [current]
[3808738.632447] sd 2:0:0:2: [sdb] tag#63 Add. Sense: I/O process terminated
[3808738.632449] sd 2:0:0:2: [sdb] tag#63 CDB: Write(10) 2a 00 0a eb cb a8 00 00 08 00
[3808738.632450] print_req_error: I/O error, dev sdb, sector 183225256
[3808738.632458] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 42730098 (offset 0 size 4096 starting block 22903158)
[3808738.632461] Buffer I/O error on device sdb1, logical block 22902901
[3808739.418993] sd 2:0:0:2: [sdb] tag#82 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[3808739.418996] sd 2:0:0:2: [sdb] tag#82 Sense Key : Aborted Command [current]
[3808739.418997] sd 2:0:0:2: [sdb] tag#82 Add. Sense: I/O process terminated
[3808739.418999] sd 2:0:0:2: [sdb] tag#82 CDB: Write(10) 2a 00 38 07 1b f8 00 00 68 00
[3808739.419001] print_req_error: I/O error, dev sdb, sector 939990008
[3808739.419031] Aborting journal on device sdb1-8.
[3808739.506909] sd 2:0:0:2: [sdb] tag#82 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[3808739.506911] sd 2:0:0:2: [sdb] tag#82 Sense Key : Aborted Command [current]
[3808739.506912] sd 2:0:0:2: [sdb] tag#82 Add. Sense: I/O process terminated
[3808739.506914] sd 2:0:0:2: [sdb] tag#82 CDB: Write(10) 2a 00 38 04 08 00 00 00 08 00
[3808739.506917] print_req_error: I/O error, dev sdb, sector 939788288
[3808739.506920] print_req_error: I/O error, dev sdb, sector 939788288
[3808739.506923] Buffer I/O error on dev sdb1, logical block 117473280, lost sync page write
[3808739.506959] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[3808763.586819] sd 2:0:0:2: [sdb] tag#53 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[3808763.586821] sd 2:0:0:2: [sdb] tag#53 Sense Key : Aborted Command [current]
[3808763.586822] sd 2:0:0:2: [sdb] tag#53 Add. Sense: I/O process terminated
[3808763.586824] sd 2:0:0:2: [sdb] tag#53 CDB: Write(10) 2a 00 00 00 08 00 00 00 08 00
[3808763.586826] print_req_error: I/O error, dev sdb, sector 2048
[3808763.586830] print_req_error: I/O error, dev sdb, sector 2048
[3808763.586834] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[3808763.587047] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
[3808763.587170] EXT4-fs (sdb1): Remounting filesystem read-only
[3808763.587274] EXT4-fs (sdb1): previous I/O error to superblock detected
[3808763.674727] sd 2:0:0:2: [sdb] tag#53 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[3808763.674729] sd 2:0:0:2: [sdb] tag#53 Sense Key : Aborted Command [current]
[3808763.674731] sd 2:0:0:2: [sdb] tag#53 Add. Sense: I/O process terminated
[3808763.674732] sd 2:0:0:2: [sdb] tag#53 CDB: Write(10) 2a 00 00 00 08 00 00 00 08 00
[3808763.674735] print_req_error: I/O error, dev sdb, sector 2048
[3808763.674739] print_req_error: I/O error, dev sdb, sector 2048
[3808763.674742] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[3900975.092299] EXT4-fs (sdb1): error count since last fsck: 2
[3900975.092304] EXT4-fs (sdb1): initial error at time 1602045692: ext4_journal_check_start:61
[3900975.092305] EXT4-fs (sdb1): last error at time 1602045692: ext4_journal_check_start:61
[3910990.957423] scsi 2:0:0:1: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[3910990.959277] sd 2:0:0:1: Power-on or device reset occurred
[3910990.959519] sd 2:0:0:1: Attached scsi generic sg2 type 0
[3910990.959665] sd 2:0:0:1: [sdc] 1887436800 512-byte logical blocks: (966 GB/900 GiB)
[3910990.959853] sd 2:0:0:1: [sdc] Write Protect is off
[3910990.959854] sd 2:0:0:1: [sdc] Mode Sense: 63 00 00 08
[3910990.960083] sd 2:0:0:1: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[3910990.964303] sd 2:0:0:1: [sdc] Attached SCSI disk
[3911024.588031] sdc: sdc1
[3911024.589626] sdc: sdc1
[3911101.669681] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[3912334.557961] RPC: Registered named UNIX socket transport module.
[3912334.557962] RPC: Registered udp transport module.
[3912334.557963] RPC: Registered tcp transport module.
[3912334.557964] RPC: Registered tcp NFSv4.1 backchannel transport module.
[3912334.591421] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[3912334.648434] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[3912334.648448] NFSD: starting 90-second grace period (net f0000099)
[3926124.124681] EXT4-fs error (device sdb1): ext4_lookup:1594: inode #42730541: comm du: deleted inode referenced: 42730098
[3926124.124709] EXT4-fs (sdb1): previous I/O error to superblock detected
[3926124.775774] EXT4-fs error (device sdb1): ext4_lookup:1594: inode #52560217: comm du: deleted inode referenced: 52559983
 
Mount

pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14212)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /run/user/108 type tmpfs (rw,nosuid,nodev,relatime,size=3216596k,mode=700,uid=108,gid=114)
/dev/sdb1 on /datavol type ext4 (ro,nosuid,nodev,relatime,data=ordered)

 

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!