Transmission not able to write data to mounted HDD

Hi Guys,

I mount my Harddrive in /mnt/data.
I am able to access my Harddrive from ssh.
Then i unmounted the drive.
I changed owner of data to osmc and gave 777 to /mnt/data.


I have installed Transmission from App Store and from the web interface i added the torrent file.
But i am getting the Error saying it is unable to access the folder.

Can somebody help me as what am missing.<img

might be better to chown

http://pubs.opengroup.org/onlinepubs/9699919799/utilities/chown.html

and use 666 instead of 777 or better yet 664 or something :slight_smile:

hope that helps :slight_smile:

@Toast since the folder was already with osmc, I didn’t used the chown command.
I will change the permissions and will report back

What does ls -l of /mnt/data look like when the drive is mounted? I can see you chmodded /mnt/data but that was unmourned, what do the subdirectories look like?

Ohh forgot that OSMC has a transmission package but make sure that it has recursive permission in that folder so that new folders get the same permissions.

usually dont rely on custom packages when i set up my stuff :slight_smile:

I guess this is what is causing issues.
After I unmounted the HDD, I changed the ownership and permissions.
But when I mount the HDD again. It is getting changed.

Can someone help me as how to make it persistent.

Cheers

OK I was able to make it persistent by adding a record in /etc/fstab.
And now it is showing properly owner and permissions.
Still I am not able to write anything.


Can somebody guide me as what am trying wrong

“Read-only file system”

I guess either your filesystem is corrupted (the input/output error indicates that) or you have a wrong fstab line (which should not be necessary anyhow if everything is running normal automount will mount it as osmc/osmc.

Check/post your dmesg/journal output also post your fstab

@fzinken should i post the dmesg | grep sd* output? and also this command journalctl. Am i correct?

Just use grab-logs -J - K -f

@fzinken am getting the below.

osmc@osmc:~$ grab-logs -J - K -f
usage: grab-logs [-h] [-A] [-T FILENAME] [-C] [-P] [-I] [-p] [-v] [-k] [-r]
                 [-s] [-f] [-O] [-o] [-a] [-J] [-l] [-i] [-d] [-K] [-m] [-D]
                 [-b] [-X]
grab-logs: error: unrecognized arguments: - K
osmc@osmc:~$

One space sneaked in, correct is
grab-logs -J -K -f

@fzinken logs are present grab-logs

[ 8.854017] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Suggest to run
umount /mnt/data
sudo fsck.vfat /dev/sdb1

Ok. i unmounted and i ran the fsck command.

osmc@osmc:~$ sudo umount /mnt/data/
osmc@osmc:~$ sudo fsck.vfat /dev/sdb1
fsck.fat 3.0.27 (2014-11-12)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corru                                                                             pt.
1) Remove dirty bit
2) No action
? 1
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:02/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
/FOUND.000
  Contains a free cluster (1410). Assuming EOF.
/DSLR Pics/Ernakulam pics/DSC_0232.JPG
  Contains a free cluster (453469). Assuming EOF.
/DSLR Pics/Ernakulam pics/DSC_0232.JPG
  File size is 8223095 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Reclaimed 141 unused clusters (4620288 bytes).
Free cluster summary wrong (28404809 vs. really 28404950)
1) Correct
2) Don't correct
? 1
Leaving filesystem unchanged.
/dev/sdb1: 81120 files, 2111349/30516299 clusters
osmc@osmc:~$ sudo fsck.vfat /dev/sdb1
fsck.fat 3.0.27 (2014-11-12)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:02/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
/FOUND.000
  Contains a free cluster (1410). Assuming EOF.
/DSLR Pics/Ernakulam pics/DSC_0232.JPG
  Contains a free cluster (453469). Assuming EOF.
/DSLR Pics/Ernakulam pics/DSC_0232.JPG
  File size is 8223095 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Reclaimed 141 unused clusters (4620288 bytes).
Free cluster summary wrong (28404809 vs. really 28404950)
1) Correct
2) Don't correct
? 2
Leaving filesystem unchanged.
/dev/sdb1: 81120 files, 2111349/30516299 clusters

But after i mounted the drive, i am still seeing the same error. Did i do anything wrong? Or if i just deleted that one pic which in fsck will this issue be solved ?

Well my gut feeling is something serious wrong with that drive. Is it getting enough power? How is it powered?
Suggest to backup all files and format the drive. Or maybe connect to a windows PC and check what that says.

@fzinken sorry for the late reply… i got struck with some work. I connected the drive to Windows and fixed the errors. There were some boot error.
Now Transmission is able to access the drive. Thanks for your help. :slight_smile:

Avoid NTFS if you can

@sam_nazarko My drive is vfat only. Is there any particular problem with NTFS and Pi3, as i have another hard drive in NTFS format?

Use exFAT if you need access on a Windows PC.