[SOLVED] Cannot delete drive files

[thelonghop]

New to LInux and built a Linux PC and I moved some HDDs over from my previous Windows PC. I can read files on the drives just fine but can't delete the files. I found a way to access the files using root and updated the permissions and was able to delete files, but after a restart I'm not able to again. How do I go about fixing this and giving me full access to the files on the drive?

[RIH]

Are you dual booting with Windows?

If so it is a Windows issue & you need to disable fat boot in Windows.
https://www.passfab.com/windows-10/disa ... ws-10.html

Windows does not release the disk completely & so Linux is unable to perform some actions on the disk..

[motoryzen]

RIH meant " fast" boot. xD

[RIH]

RIH meant " fast" boot. xD

Ha, ha.. Freudian slip sorry..

[motoryzen]

RIH meant " fast" boot. xD

Ha, ha.. Freudian slip sorry..

Hey..now..don't apologize. There is nothing wrong with a fat boot..Fat boot= more stability for running up mountains. xD Keep sense of humor sharp

[ricardogroetaers]

I can read files on the drives just fine but can't delete the files.

Assuming that the hard drives remain fixed, I ask you to post the output of the commands:
id
lsblk -fi
cat /etc/fstab

I ask you to mention which volumes (file systems), shown in "lsblk -fi", with which you are having problems.

[thelonghop]

Are you dual booting with Windows?

If so it is a Windows issue & you need to disable fat boot in Windows.
https://www.passfab.com/windows-10/disa ... ws-10.html

Windows does not release the disk completely & so Linux is unable to perform some actions on the disk..

No, not dual booting. The Linux mint was install on a new drive, then after I confirmed everything was running I pulled some data drives out of the Windows PC. They don't have Windows installed on them.

[thelonghop]

I can read files on the drives just fine but can't delete the files.

Assuming that the hard drives remain fixed, I ask you to post the output of the commands:
id
lsblk -fi
cat /etc/fstab

I ask you to mention which volumes (file systems), shown in "lsblk -fi", with which you are having problems.

Code: Select all

uid=1000(mint) gid=1000(mint) groups=1000(mint),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),114(lpadmin),134(sambashare)

Code: Select all

NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0
     squash                                                  0   100% /snap/mono
loop1
     squash                                                  0   100% /snap/core
loop2
     squash                                                  0   100% /snap/snap
sda                                                                   
|-sda1
|                                                                     
`-sda2
     ntfs   Backup
                  6CEE119FEE11631E                      863.4G    69% /media/mat
sdb                                                                   
`-sdb1
     ntfs   Data1 9424CDFC24CDE17A                      612.6G    34% /media/mat
sdc                                                                   
`-sdc1
     ntfs   Data2
                  0C3910DC0C3910DC                      252.1G    86% /media/mat
nvme0n1
|                                                                     
|-nvme0n1p1
|    vfat         DF1C-DC0B                             503.2M     2% /boot/efi
`-nvme0n1p2
     ext4         43d8d77d-cecc-48a8-9e12-b7ec77e56ed6    1.7T     2% /run/times

Code: Select all

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=43d8d77d-cecc-48a8-9e12-b7ec77e56ed6 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=DF1C-DC0B  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

It's the Backup, Data1, and Data2 drives that have the permission issues.

[AndyMH]

The Linux mint was install on a new drive, then after I confirmed everything was running I pulled some data drives out of the Windows PC.

Still relevant, if that win PC did not have fast start disabled, then the chances are that the ntfs partitions are locked and read-only. Plug them back into the win PC, disable fast start and then shut down.

[ricardogroetaers]

It's the Backup, Data1, and Data2 drives that have the permission issues.

I understand, thank you.
I ask you to confirm that your username on this computer is really "mint".

[thelonghop]

It's the Backup, Data1, and Data2 drives that have the permission issues.

I understand, thank you.
I ask you to confirm that your username on this computer is really "mint".

nope

[ricardogroetaers]

I ask you to confirm that your username on this computer is really "mint".

nope

You probably posted the output of the "id" command using a Linux Mint installation medium. Am I right or am I wrong or was it just a coincidence?
There it appears to be "mint" as your username.
Mystery?

I don't need to know your username on that computer to suggest an attempt at a solution, but it would help a lot if you did.
It is up to you to inform or not.

[thelonghop]

The Linux mint was install on a new drive, then after I confirmed everything was running I pulled some data drives out of the Windows PC.

Still relevant, if that win PC did not have fast start disabled, then the chances are that the ntfs partitions are locked and read-only. Plug them back into the win PC, disable fast start and then shut down.

That was probably it! I did as suggested, but then also used the 'safely eject' option for each of them as well. Added them back to the Linux PC and I have full control over the files. Thanks!

[AndyMH]

Just one of the things we have to live with alongside win. Fast start = win never shuts down, just gives the user the illusion that it has shut down so that it can appear quick to boot. That together with 'disable secure boot' are the two things you need to do if dual booting or working with win. If you are not sharing those drives with any win PC, you would be better off converting them to ext4, i.e. a native linux filesystem.

[motoryzen]

Indeed Andy is correct. This is just one of the many reasons why I don't dual boot Windows and Linux worlds within the same storage drive. There is just too much to have to remember/keep up with to ensure things work correctly. It's just not worth the headache. That's why whenever I absolutely must do something within the Windows world on the same machine I use to run LM 20.1 Cinnamon with...I power it down completely..disconnect all Linux-only involved drives, connect only Windows-coherent drives and then power it on.

This way, I keep the two worlds as separated as possible and keep my sanity. xD