insufficient permission to write to disk  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Forum rules
Post Reply
Message
Author
ancer
Posts: 28
Joined: Mon May 31, 2021 12:09 pm

insufficient permission to write to disk

#1 Post by ancer »

In my desktop I have a SSD with multi-boot operating systems and another HD drive for storing data. Until 3 days ago I experienced no problem writing to HD (which is formatted in NTFS, because I access it from MS Windows too). Yesterday I experienced a strange thing - I wanted to erase some files from HD with Dolphin - after "erasing" the files were still there. Later I wanted to copy some files from SSD disk to HD - Couldn't do it. Last try - I simply wanted to save a picture from some web site - Instead of saving it - there is a messsage: "Failed - Insufficient permissions". Just 3 days ago HD was available for all this actions - write, erase, read etc - now I can only read files from it. What to do to restore permissions for HD disk?
Thank You

Code: Select all

System:
  Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64 
  root=UUID=<filter> ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.4_kde_x64 patito feo March 31  2021 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <filter> 
  Mobo: ASUSTeK model: PRIME A520M-K v: Rev X.0x serial: <filter> 
  UEFI: American Megatrends v: 1004 date: 08/13/2020 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 PRO 4650G with Radeon Graphics bits: 64 
  type: MT MCP arch: Zen family: 17 (23) model-id: 60 (96) stepping: 1 
  microcode: 8600106 L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 88635 
  Speed: 1848 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1848 
  2: 2691 3: 2014 4: 3459 5: 2259 6: 2657 7: 1890 8: 3489 9: 2030 10: 3035 11: 2046 
  12: 3232 
  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: Full AMD retpoline, IBPB: conditional, IBRS_FW, 
  STIBP: conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 08:00.0 
  chip ID: 1002:1636 
  Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.0-5mx-amd64 LLVM 11.0.1) 
  v: 4.6 Mesa 20.3.4 direct render: Yes 
Audio:
  Device-1: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 08:00.1 
  chip ID: 1002:1637 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK PRIME B450M-A 
  driver: snd_hda_intel v: kernel bus ID: 08:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.10.0-5mx-amd64 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.14 TiB used: 325.00 GiB (27.8%) 
  ID-1: /dev/nvme0n1 vendor: Apacer model: AS2280P4 256GB size: 238.47 GiB 
  block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
  serial: <filter> rev: S0614B0 scheme: GPT 
  ID-2: /dev/sda vendor: Toshiba model: HDWD110 size: 931.51 GiB block size: 
  physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
  serial: <filter> rev: A8R0 scheme: MBR 
Partition:
  ID-1: / raw size: 97.66 GiB size: 95.62 GiB (97.92%) used: 11.52 GiB (12.0%) 
  fs: ext4 dev: /dev/nvme0n1p3 
Sensors:
  System Temperatures: cpu: 44.5 C mobo: N/A gpu: amdgpu temp: 31 C 
  Fan Speeds (RPM): N/A 
Repos:
  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://it.mxrepo.com/mx/repo/ buster main non-free
  2: deb http://it.mxrepo.com/mx/repo/ buster ahs
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
  1: deb https://deb.opera.com/opera-stable/ stable non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 287 Uptime: 33m Memory: 7.16 GiB used: 2.21 GiB (30.9%) Init: SysVinit 
  v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
  running in: quick-system-in inxi: 3.0.36
Top
Huckleberry Finn

Re: insufficient permission to write to disk  [Solved]

#2 Post by Huckleberry Finn »

Disable Fast Startup on Windows.

Do files & folders look with "padlocks" in File Manager?

viewtopic.php?p=599920#p599920

While you're at it: it would also be good to chkdsk /f on command prompt
you can also state the drive like chkdsk /f E:

Also on MX, Menu => GSmartControl: check disk's health ... )
Last edited by Huckleberry Finn on Tue Jun 15, 2021 1:29 pm, edited 1 time in total.
Top
ancer
Posts: 28
Joined: Mon May 31, 2021 12:09 pm

Re: insufficient permission to write to disk

#3 Post by ancer »

No, they look exactly the same as the ones from my system's SSD partition.
Top
Huckleberry Finn

Re: insufficient permission to write to disk

#4 Post by Huckleberry Finn »

Ok, no harm to remove readonly (on both Linux & Windows, whichever works) , you can apply them.

Also viewtopic.php?p=595808#p595808
Top
User avatar
jeffreyC
Posts: 532
Joined: Mon May 27, 2019 10:39 am

Re: insufficient permission to write to disk

#5 Post by jeffreyC »

When Windows 10 updates it will reset Fast Startup to enabled, so you will need to disable it again.... and again...
Top
User avatar
entropyfoe
Posts: 627
Joined: Thu Apr 19, 2007 11:42 am

Re: insufficient permission to write to disk

#6 Post by entropyfoe »

If you right click the files or folders in Thunar,to view the properties, and go to the permissions tab, what does it say for the owner and user's permissions (read/write etc?).
MX 23.6 AHS on Asus PRIME B650
AMD Ryzen 9700X (16 threads @ 3.8 GHz)
64 Gig DDR4 6400 (Crucial)
Integrated Radeon graphics
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =2TB Data, plus 4TB WD =backups
on-board ethernet & sound
Top
ancer
Posts: 28
Joined: Mon May 31, 2021 12:09 pm

Re: insufficient permission to write to disk

#7 Post by ancer »

Thank You both-
Huckleberry Finn - Yes, simply run chkdsk and repair the errors worked.
and JeffreyC - this "Fast Startup" I'll need to disable every time I run windows 10? Because it seems that every time I run it, which luckily is not very often, It installs some updates.
Top
ancer
Posts: 28
Joined: Mon May 31, 2021 12:09 pm

Re: insufficient permission to write to disk

#8 Post by ancer »

Thank You, entropyfoe, I have to install Thunar first - which one? there seems to be many thunar related packages in stable debian repo
Top
ancer
Posts: 28
Joined: Mon May 31, 2021 12:09 pm

Re: insufficient permission to write to disk

#9 Post by ancer »

Ok, I installed thunar, and me (owner) have permissions to read and write, while "group" has only permission to read folder content. Luckily (for now at least) the problem is solved.
Thank You
Top
Huckleberry Finn

Re: insufficient permission to write to disk

#10 Post by Huckleberry Finn »

I guess @entropyfoe just thought you were using the default (or AHS) MX (Xfce), that's why he said "Thunar" .. :)
Top
Post Reply

Return to “MX KDE Official Release”