Timeline for Cannot see files from DSM I made with Transmission on NFS share on Synology NAS
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2019 at 13:08 | comment | added | goldilocks♦ | "they were just somewhere on the sdcard of the Pi" -> Pretty sure you mean not in the mount directory, but if you mean it was the storage mounted on the wrong place, note that you can mount stuff on a directory with content -- what happens then is you can't access that content until you remove the mount. So if you only ever use the directory as a mount, it's easy to at one point copy stuff into the dir by mistake when nothing is mounted, then not notice it for months because normally something is always mounted there. Hope that makes sense... | |
| Oct 21, 2019 at 20:55 | answer | added | FenderBender | timeline score: 1 | |
| Oct 21, 2019 at 17:57 | comment | added | Ingo | Please just write an answer. That will finish the question and show others that is has a solution. Seems you can just move your comment with the solution into the answer field. It is nothing wrong with answering the own question. | |
| Oct 21, 2019 at 16:35 | comment | added | FenderBender | Can I close a question? Or how do I handle this, pretty new to StackExchange so no clue. | |
| Oct 21, 2019 at 16:32 | comment | added | FenderBender |
@goldilocks Man oh man, finally found what went wrong. I made an error in the path of the mount target, so the files never reached the share, they were just somewhere on the sdcard of the Pi. When I corrected the error, I got a new NFS error. Couldn't solve that one, so had another go as to why my CIFS entry in /etc/fstab worked fine in the CLI, but continued to have Permission Denied error in Transmission. Turns out I had vers=3.0 specified, which aparently Transmission did not like at all. When I removed that everything worked just fine. Anyway, really appreciate your help!
|
|
| Oct 21, 2019 at 12:18 | comment | added | goldilocks♦ | I'm actually not a Windows user, so I can't comment further on all that. The actual storage here is attached to the Pi, right? So you can check locally what is really in the NFS exported directory. Chances are it is the same view as from the Pi, and the stuff you are supposedly putting in it from the Windows side isn't there at all. If you can reboot the Windows machine and it is still there from that end, then whatever it supposed to be the NFS mount obviously isn't, it's stored on the Windows machine somewhere. I would guess instead it isn't anywhere, but that's just a guess. | |
| Oct 21, 2019 at 9:40 | comment | added | FenderBender |
Could it be because DSM has no clue as to who user pi:pi is? (Sorry if this sounds stupid, am learning as I go here and I'am just getting started)
|
|
| Oct 21, 2019 at 9:20 | history | edited | FenderBender | CC BY-SA 4.0 |
Changed Windows in title to DSM, as it better reflects issue
|
| Oct 21, 2019 at 9:01 | comment | added | FenderBender | @goldilocks Indeed, but I still don't understand why the the DSM file browser cannot see the files. DSM understands NFS out of the box, right?. It's the other way arround too: files and folders created from my Windows PC or from the DSM file browser are not visible to the Pi3. I can even make a folder called 'TORRENT' on the PI3 and make a folder 'TORRENT' in the DSM file browser in the same share without getting a conflict. | |
| Oct 21, 2019 at 8:25 | comment | added | Jaromanda X | Windows 10 Pro supports NFS if you enable it. Which Windows version do you have | |
| Oct 20, 2019 at 22:20 | review | Close votes | |||
| Nov 4, 2019 at 3:05 | |||||
| Oct 20, 2019 at 21:48 | comment | added | goldilocks♦ | Pretty sure you need to add some software to Windows in order for it to read NFS. | |
| Oct 20, 2019 at 17:19 | history | asked | FenderBender | CC BY-SA 4.0 |