You are not logged in.

Pages: 1

#1 2017-06-06 10:00:03

philipW
Member
Registered: 2017-03-21
Posts: 145

[SOLVED] my partition made itself read only

Hi,
I have a shared partition on my dualboot laptop that is ntfs to do this i use ntfs-3g.
The partition is shared between arch and windows 10
It used to always work but when i wanted to start a virtual machine VMware said that it was in a read only file system.
It already happened once and because there was not much of vallue on the the partition i just recreated it.
I was thinking it was because i created the virtual machine in windows and thats why it made the permissions weird or something.
So this time i reinstalled my virtual machines in arch.
They worked for a few days and now i get the read only filesystem error again.
This is my fstab.

 
#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda6
UUID=482cf21a-99a7-4a0a-9ad4-9049a19896b7       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sdb2
UUID=b46017d2-5532-4840-b964-a23ae09e5869       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sda5
UUID=bfa0fff3-2b92-4cdb-8f8c-9098814e500d       none            swap            defaults        0 0

/dev/sdb3                                       /home/philip/vmwware   ntfs-3g        rw,permissions,auto                0 0

I tried putting rw, in front of permissions.
And i also tried putting this in options : rw,user,exec,umask=000
This is what i get if i type the 

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8189640k,nr_inodes=2047410,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda6 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
/dev/sdb2 on /home type ext4 (rw,relatime,data=ordered)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sdb3 on /home/philip/vmwware type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1638908k,mode=700,uid=1000,gid=100)
[philip@FlipArch ~]$

If i try chmod 777 -R vmware/ (i use the shared partition for virtual machines i have it mounted on a folder called vmware in my home folder this is not where my vmware is installed)

[philip@FlipArch ~]$ sudo chmod 777 -R vmwware
chmod: changing permissions of 'vmwware': Read-only file system
chmod: changing permissions of 'vmwware/$RECYCLE.BIN': Read-only file system
chmod: changing permissions of 'vmwware/$RECYCLE.BIN/S-1-5-21-632418407-3825348931-1567441455-1001': Read-only file system
chmod: changing permissions of 'vmwware/$RECYCLE.BIN/S-1-5-21-632418407-3825348931-1567441455-1001/desktop.ini': Read-only file system
chmod: changing permissions of 'vmwware/.directory': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/directorysizes': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde-s001.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde-s002.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde-s003.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde-s004.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde-s005.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde-s006.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde.nvram': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde.vmsd': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde.vmx': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/Kali linux kde.vmxf': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/vmware-0.log': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/vmware-1.log': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/vmware-2.log': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/files/Kali linux kde/vmware.log': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/info': Read-only file system
chmod: changing permissions of 'vmwware/.Trash-1000/info/Kali linux kde.trashinfo': Read-only file system
chmod: changing permissions of 'vmwware/kali linux': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/kali linux.nvram': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/kali linux.vmdk': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/kali linux.vmsd': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/kali linux.vmx': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/kali linux.vmxf': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/vmware-0.log': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/vmware-1.log': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/vmware-2.log': Read-only file system
chmod: changing permissions of 'vmwware/kali linux/vmware.log': Read-only file system
chmod: changing permissions of 'vmwware/kali-linux-kde-2017.1-amd64.iso': Read-only file system
chmod: changing permissions of 'vmwware/metasploitable-linux-2.0.0.zip': Read-only file system
chmod: changing permissions of 'vmwware/System Volume Information': Read-only file system
chmod: changing permissions of 'vmwware/System Volume Information/Chkdsk': Read-only file system
chmod: changing permissions of 'vmwware/System Volume Information/Chkdsk/Chkdsk20170601104059.log': Read-only file system
chmod: changing permissions of 'vmwware/System Volume Information/IndexerVolumeGuid': Read-only file system
chmod: changing permissions of 'vmwware/System Volume Information/tracking.log': Read-only file system
chmod: changing permissions of 'vmwware/System Volume Information/WPSettings.dat': Read-only file system

It didnt help :
This is the output of 

ls -l
[philip@FlipArch vmwware]$ ls -l
total 844820
drwxrwxrwx 1 philip users      4096 Jun  2 10:00 'kali linux'
-rw------- 1 philip users         0 May 30 12:44  kali-linux-kde-2017.1-amd64.iso
-rwxrwxrwx 2 root   root  865084584 Apr 29 12:55  metasploitable-linux-2.0.0.zip
drwxrwxrwx 1 root   root          0 Jun  1 10:37 '$RECYCLE.BIN'
drwx------ 1 root   root       4096 Jun  2 07:25 'System Volume Information'
[philip@FlipArch vmwware]$

Last edited by philipW (2017-06-06 10:55:10)

Offline

#2 2017-06-06 10:13:28

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOLVED] my partition made itself read only

Check in "journalctl -b" to see what ntfs-3g says when it's trying to mount it.

Make sure you still have that "fast start-up" thingy in Windows disabled so that it does a full shutdown instead of its normal half-shutdown-half-hibernate thing. Maybe Windows 10 enabled it again after some update? You might not have noticed immediately as it won't use it when you choose to reboot to go from Windows to Arch. You'll only notice if you power-off, then choose Arch on next power-on.

Offline

#3 2017-06-06 10:34:53

tick1020
Member
Registered: 2017-04-22
Posts: 26

Re: [SOLVED] my partition made itself read only

yeah, i know this issue very well. Try

sudo mount -t ntfs-3g -o remove_hiberfile /dev/sdb3 /home/philip/vmwware

It wont hurt anything but you will loose any date you didnt have saved when you "shut down"/hybernated in windows.

You can turn off hybernate in windows and you wont ever have the problem again, but even if you select shut down from the list sometimes windows 10 will still hybernate your pc. The purpose is to make your startup times faster. If you were only running windows you would never know and just think your pc turns on super quick. That is, if you have it enabled in control pannel.

Last edited by tick1020 (2017-06-06 10:41:25)

Offline

#4 2017-06-06 10:45:44

philipW
Member
Registered: 2017-03-21
Posts: 145

Re: [SOLVED] my partition made itself read only

This is what "journalctl -b" says about ntfs-3g:

Jun 06 12:36:36 FlipArch ntfs-3g[430]: Version 2017.3.23 external FUSE 29
Jun 06 12:36:36 FlipArch ntfs-3g[430]: Mounted /dev/sdb3 (Read-Only, label "SHARE", NTFS 3.1)
Jun 06 12:36:36 FlipArch systemd[1]: Mounted /home/philip/vmwware.
Jun 06 12:36:36 FlipArch ntfs-3g[430]: Cmdline options: rw,permissions

I have the fast startup disabled in my bios im gonna look if there is a function in windows .
The strange thing is that i never used this partition in windows after creating it.
I am gonna try 

sudo mount -t ntfs-3g -o remove_hiberfile /dev/sdb3 /home/philip/vmwware

Now.

Offline

#5 2017-06-06 10:48:52

philipW
Member
Registered: 2017-03-21
Posts: 145

Re: [SOLVED] my partition made itself read only

Oke i tried this 

[philip@FlipArch ~]$ sudo mount -t ntfs-3g -o remove_hiberfile /dev/sdb3 /home/philip/vmwware
[sudo] password for philip: 
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
[philip@FlipArch ~]$ 
[philip@FlipArch ~]$ sudo umount /dev/sdb3/
[philip@FlipArch ~]$ sudo mount -t ntfs-3g -o remove_hiberfile /dev/sdb3 /home/philip/vmwware
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sdb3': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
[philip@FlipArch ~]$

Seems like my windows is not shutdown propperly.
Really weird because i shut it down completely before i tried this.

Offline

#6 2017-06-06 10:54:32

philipW
Member
Registered: 2017-03-21
Posts: 145

Re: [SOLVED] my partition made itself read only

Problem solved:
Turns out i have to hold shift when clicking shutdown to make it fully shutdown.
Have to do some research how i can enable it by default.


EDIT: this is how to turn off fast startup in windows if anyone is interested: http://windowsten.info/tutorials/5767-h … windows-10

Last edited by philipW (2017-06-06 11:02:10)

Offline

Pages: 1

Board footer

Powered by FluxBB