MX Linux Forum

Posted: **Sat Jun 11, 2022 12:25 pm**

Reason unknown, time frame unknown. Dual boot system Mx linux W/ Win7. First noticed this problem using VirtualBox on host Mx-Linux W/Client Win7iso. Kept getting error message. Which VBox now boots without the error (can not screen shot now). Error said could not access the shared folders due to * not available*. They where there, but could not change anything or save to them. This is when I tried system reboot and VirtualBox machine reboot, Always boot up VBox and shutdown never save running state. Have now noticed that when Mx boots all other ntfs H-drives are auto mounted. Can not change this and can not change permissions on drives, not even when using root. Now, I also have one H-drive that is vfat and the permissions have not changed and I can add it to VBox as shared folder and can access it as before and make mods to files. But none of the ntfs H-drives can be modified now. I can unmount all drives but the Win7 H-drive which will stay mounted. I can not copy to or paste to any ntfs systems. Which I could before "THIS" whatever happened, happened. I suspect it had to do with some update around the end of May. I have been searching for fixes and have tried chmod with root privileges but no go. Anybody got any Ideas?? I am not all that linux savvy, use it as installed, have had other problems with VBox after updates. Just formatted and reinstalled everything. Lost much good stuff. Do not want to do that at this time.

Code: Select all

Snapshot created on: 20200915_1434
System:    Kernel: 4.19.0-20-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-20-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm 4.14.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-19.4_x64 patito feo May 31  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: M5A97 R2.0 v: Rev 1.xx serial: <filter> 
           BIOS: American Megatrends v: 2603 date: 06/26/2015 
CPU:       Info: Quad Core model: AMD FX-4300 bits: 64 type: MCP arch: Bulldozer family: 15 (21) 
           model-id: 2 stepping: 0 microcode: 6000852 cache: L2: 2 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 30500 
           Speed: 2827 MHz min/max: 1400/3800 MHz boost: enabled Core speeds (MHz): 1: 2827 
           2: 2191 3: 2105 4: 2095 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GT218 [GeForce 210] vendor: ASUSTeK driver: nouveau v: kernel 
           bus-ID: 01:00.0 chip-ID: 10de:0a65 class-ID: 0300 
           Display: x11 server: X.Org 1.20.10 compositor: xfwm4 v: 4.14.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.0x9.4") 
           s-diag: 449mm (17.7") 
           Monitor-1: VGA-1 res: 1440x900 hz: 60 dpi: 90 size: 408x255mm (16.1x10.0") 
           diag: 481mm (18.9") 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 20.3.4 direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 00:14.2 chip-ID: 1002:4383 class-ID: 0403 
           Device-2: NVIDIA High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus-ID: 01:00.1 chip-ID: 10de:0be3 class-ID: 0403 
           Sound Server-1: ALSA v: k4.19.0-20-amd64 running: yes 
           Sound Server-2: PulseAudio v: 12.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8 series driver: r8169 v: kernel port: d000 bus-ID: 02:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Ralink RT5572 Wireless Adapter type: USB driver: rt2800usb bus-ID: 5-2:2 
           chip-ID: 148f:5572 class-ID: 0000 serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 1.58 TiB used: 1.08 TiB (68.0%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Silicon Power model: SPCC Solid State Disk 
           size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
           serial: <filter> rev: 08.2 scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Silicon Power model: SPCC Solid State Disk 
           size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
           serial: <filter> rev: 08.2 scheme: MBR 
           ID-3: /dev/sdc maj-min: 8:32 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: A750 temp: 26 C scheme: MBR 
           ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD10EACS-00ZJB0 
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A 
           serial: <filter> rev: 1B01 temp: 27 C scheme: MBR 
Partition: ID-1: / raw-size: 102.02 GiB size: 99.92 GiB (97.94%) used: 40.91 GiB (40.9%) 
           fs: ext4 dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 9.77 GiB used: 512 KiB (0.0%) priority: -2 
           dev: /dev/sda2 maj-min: 8:2 
Sensors:   System Temperatures: cpu: 17.4 C mobo: N/A gpu: nouveau temp: 43.0 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     Packages: note: see --pkg apt: 2254 lib: 1149 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ buster main contrib non-free
           2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/testrepo/ buster test
           3: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 224 Uptime: 2h 44m wakeups: 1 Memory: 3.76 GiB used: 1.41 GiB (37.6%) 
           Init: SysVinit v: 2.93 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 8.3.0 
           alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 running-in: quick-system-in 
           inxi: 3.3.06

Posted: **Sun Jun 12, 2022 9:35 am**

Is this just a crazy problem or do I need to install Mx21 due to Mx19 no longer being supported?

Posted: **Sun Jun 12, 2022 9:52 am**

post out put of

Code: Select all

cat /etc/fstab

and the output of

Code: Select all

cat /proc/mounts

If I understand correctly, you have a dual-boot with windows 7 and mx linux, in addition the mx machine has a virtuabox setup with win7 on it, which used to be able to access your original ntfs partitions but now cannot.

Posted: **Sun Jun 12, 2022 12:46 pm**

Yes, I have a dual boot system, Mx linux 19.4 Buster, W/ Win7. Boot is Via grub menu loaded on sdb1 . No my VirutalBox does not access my Hard drive win7. But is a separate smaller win7 iso. But I could exchange files through a Disk partition "/media/Data" before. As of today V-Box boots and runs fine, I can access shared folder "/media/Saved" to exchange files. But is a bit wonkey as I have to save and move files to data. Not a big problem but wonkey, and I have forgot a few times which is the currant file, i Know my bad.. My main problem is from boot, Mx now auto mounts all my drives. and I can not change permissions on all ntfs drives but Saved which is vfat system. Permissions are locked as read only, even as root can not be changed. By any method I have tried.
I could from the Linux side save files on to Data drive to access from the Win side, and vis-versa. If needed could make files in win V-box and do the same. So I could stay on one side or the other and access same files. As I have programs which will not run on the V-Box win but will run on the hard Drive win system. I know this sounds a bit much, but all was well with the way things worked. I have a game on win side I play, I have security, updates and such on Linux side. Have had to format the whole works about a year and a half ago lost some very valuable paid for programs on win side. And at this point do not want to try and upgrade to Mx21 due to possible loss of stuff I have yet to move from my V-Box win7, and it has become a major hassle to reinstall the V-Box win7, as it can not be made genuine now. Here are the outputs you asked for.

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>

#Entry for /dev/sda1 :
UUID=c833b25a-1d9d-476f-882c-467c969ffd37 / ext4 defaults 1 1
#Entry for /dev/sdb1 :
UUID=6264705C12C62F5C /media/Win7 ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdb2 :
UUID=503C331847755AE1 /media/Data ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdc1 :
UUID=269C4B8F9C4B5907 /media/Echo ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdc2 :
UUID=EAC2412AC240FBF7 /media/Echo_XP ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdd1 :
UUID=16EC-DEA6 /media/SAVED vfat defaults,utf8,umask=0 0 2
#Entry for /dev/sda2 :
UUID=3ed22df5-a971-4113-995b-9ada9456e714 swap swap defaults 0 0

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=1902928k,nr_inodes=475732,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=393792k,mode=755 0 0
/dev/sda1 / ext4 rw,relatime 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=2835580k 0 0
rpc_pipefs /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
cgroup /sys/fs/cgroup tmpfs rw,relatime,size=12k,mode=755 0 0
systemd /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/run/cgmanager/agents/cgm-release-agent.systemd,name=systemd 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=393788k,mode=700,uid=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
/dev/fuse /run/user/1000/doc fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
/dev/sdb1 /media/Win7 fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sdb2 /media/Data fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sdc1 /media/Echo fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sdc2 /media/Echo_XP fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/sdd1 /media/SAVED vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0

Posted: **Sun Jun 12, 2022 12:59 pm**

looking at your fstab

Code: Select all

UUID=6264705C12C62F5C /media/Win7 ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdb2 :
UUID=503C331847755AE1 /media/Data ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdc1 :
UUID=269C4B8F9C4B5907 /media/Echo ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdc2 :
UUID=EAC2412AC240FBF7 /media/Echo_XP ntfs defaults,nls=utf8,umask=0222 0 0
#Entry for /dev/sdd1 :
UUID=16EC-DEA6 /media/SAVED vfat defaults,utf8,umask=0 0 2

these are all set to automount. so if you don't want them to automount, add "noauto" after "defaults". one of the "defaults" is to automount.

I would also suggest setting options for the ntfs parititions to UID= your $UID and gid=users.

vfat doens't actually store in permissions. its not part of the fat specification. ntfs *can* but most of the time ntfs partitions, ntfs being a fuse filesystem, are mounted with a "spoofed" user ID and group ID.

you might change "ntfs" to "ntfs-3g" but that actually shouldn't matter. I think ntfs-3g is linked to ntfs these days.

as an example, my ntfs data partition in /etc/fstab looks like this:

Code: Select all

UUID=4AAA433BAA4322B5	/media/datapart	ntfs-3g	uid=1000,gid=users,dmask=002,fmask=113,auto,comment=x-gvfs-show,locale=en_US.UTF-8	0	0

Posted: **Sun Jun 12, 2022 1:03 pm**

not sure about this. Is this a file I can modify with "noauto" and then can I change permissions from within same file mod?

Posted: **Sun Jun 12, 2022 1:04 pm**

mckneb wrote: Sun Jun 12, 2022 1:03 pm not sure about this. Is this a file I can modify with "noauto" and then can I change permissions from within same file mod?

check out my edited post. I was typing up some permissions information while you were responding.

Posted: **Sun Jun 12, 2022 1:06 pm**

Looking at the format of the /etc/fstab file, I presume you set the file up by working in disk-manager originally. you can make edits with that if you wish.

Posted: **Sun Jun 12, 2022 1:43 pm**

I'll try and use your line as a guide. Ill try and modify the file in a bit as I have to run to store in a few. I'll be back and do it by 3:00 pm. my time EST

Posted: **Sun Jun 12, 2022 3:37 pm**

Great, this advise has been, so far so good. The edit of my fstab seems to have worked. I studied the man page for fstab to get a feel for what means what, used your line as a guide and now can change permissions as I think I should. I have not Cked my V-Box usage but I am confident I'll be good to go. I'll mark this as solved as soon as I figure out how. Thank you for your time, patients and help. Thank you.

Posted: **Sun Jun 12, 2022 3:38 pm**

mckneb wrote: Sun Jun 12, 2022 3:37 pm Great, this advise has been, so far so good. The edit of my fstab seems to have worked. I studied the man page for fstab to get a feel for what means what, used your line as a guide and now can change permissions as I think I should. I have not Cked my V-Box usage but I am confident I'll be good to go. I'll mark this as solved as soon as I figure out how. Thank you for your time, patients and help. Thank you.

little checkmark in the header of any of your posts will mark as solved.

and I'm glad it worked out.

Posted: **Sun Jun 12, 2022 5:38 pm**

Had to keep at it, read many man pages, had to learn about umask, dmask, fmask. Displaying the mask in octal (0007) and letter (+rwx). Not an expert, but system is now working as before.

MX Linux Forum

ntfs system(s) drives permissions have changed and are being auto mounted on boot.

ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot. [Solved]

Re: ntfs system(s) drives permissions have changed and are being auto mounted on boot.