11.2 RC1 Ubuntu VM has problems accessing its disk

[daeda]

I don't know if this is a specific release candidate problem. But if ssh into the vm and try this in the user's home directory it get:

Code:

touch test
touch: cannot touch 'test': Read-only file system

The machine has the following settings:

Code:

Type Bhyve
Autostart: false
Virtual CPUs: 4
Memory: 4096
BootLoader: UEFI
Com Port: /dev/nmdm10B

When I connect to the machine via vnc while it is booting I can see several message telling me that it cannot write to the file system.
The first message I get is:

Code:

failed to start remount root and kernel file system

After a wile I get the following python errors in vnc (see attached file)

The volume is a zvol

how do i fix this

 

[kdragon75]

zvols for the most part don't have permissions. This would tend to make me suspect the VM. from inside your VM please run mount and provide the output. Also please take a moment to review the forum rules about posting for help and the information you should include.
https://forums.freenas.org/index.php?threads/updated-forum-rules-8-3-16.45124/

 

[daeda]

zvols for the most part don't have permissions. This would tend to make me suspect the VM. from inside your VM please run mount and provide the output. Also please take a moment to review the forum rules about posting for help and the information you should include.
https://forums.freenas.org/index.php?threads/updated-forum-rules-8-3-16.45124/

Here is the output from inside the vm

Code:

 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,nosuid,relatime,size=1988980k,nr_inodes=497245,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=403920k,mode=755)
/dev/sda2 on / type ext4 (ro,relatime,stripe=8,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
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)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
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/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
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/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15372)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
/var/lib/snapd/snaps/core_5328.snap on /snap/core/5328 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_5548.snap on /snap/core/5548 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/docker_179.snap on /snap/docker/179 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_4917.snap on /snap/core/4917 type squashfs (ro,nodev,relatime,x-gdu.hide)
configfs on /sys/kernel/config type configfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 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)
tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,noexec,relatime,size=403920k,mode=755)
//192.168.66.242/Tausch on /home/angus/Tausch type cifs (rw,relatime,vers=default,cache=strict,username=paperless,domain=,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.66.242,file_mode=0660,dir_mode=0770,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=403916k,mode=700,uid=1000,gid=1000)

Thank you for the link to the forum rules, but these rules tend to be the same all over. So why don't you tell me what rule exactly am I not following?

 

[kdragon75]

So why don't you tell me what rule exactly am I not following?

Given the short list of rules and your response to this, the one that says to read the rules...

/dev/sda2 on / type ext4 (ro,relatime,stripe=8,data=ordered)

This is your issue. The device /dev/sda2 mounted to / (your root filesystem) is 'ro' or read only. Now we need to find out why its read only. Reboot the VM, check to see if its read only, and check /var/log/syslog

 

[daeda]

Given the short list of rules and your response to this, the one that says to read the rules...

Ok I got it :)

This is your issue. The device /dev/sda2 mounted to / (your root filesystem) is 'ro' or read only. Now we need to find out why its read only. Reboot the VM, check to see if its read only, and check /var/log/syslog

When rebooting I get several messages scrolling by concerning that mount problem I was not yet able to find out where these messages are stored as I don't know how to scroll back in the vnc browser window. But running dmesg seems to show some info.


dmesg | grep sda
[ 11.548112] sd 0:0:0:0: [sda] 200000000 512-byte logical blocks: (102 GB/95.4 GiB)
[ 11.550002] sd 0:0:0:0: [sda] 32768-byte physical blocks
[ 11.551843] sd 0:0:0:0: [sda] Write Protect is off
[ 11.564251] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 11.565661] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 11.732744] sda: sda1 sda2
[ 11.735373] sd 0:0:0:0: [sda] Attached SCSI disk
[ 20.041952] EXT4-fs (sda2): recovery complete
[ 20.043674] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 36.788788] EXT4-fs (sda2): Couldn't remount RDWR because of unprocessed orphan inode list. Please umount/remount instead
[ 72.585590] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 332.768755] EXT4-fs (sda2): error count since last fsck: 14
[ 332.768858] EXT4-fs (sda2): initial error at time 1538679656: ext4_reserve_inode_write:5761
[ 332.768901] EXT4-fs (sda2): last error at time 1538679659: ext4_do_update_inode:5232


Googling for some of the messages led me to running sudo e2fsck /dev/sda2, fixing the problems it finds leads to the system running fine again after another reboot. But it would be interesting what led to those problems in the first place.