April 25, 20188 yr Am I dealing with a corrupt share or permissions issue? Unraid shows no files in a media folder of mine on the User Share. However, when I explore the individual disks, the files are still there. tower-diagnostics-20180425-0455.zip
April 25, 20188 yr Community Expert Could you give us screenshots of what you see? A screenshot of "Unraid shows no files in a media folder" and another screenshot of "explore the individual disks, the files are still there"
April 25, 20188 yr Community Expert Also, those diagnostics were taken just after reboot and without the array started so not much to go on.
April 25, 20188 yr Author Sorry , here are the screen shots and the diagnostics after the array was started. tower-diagnostics-20180425-0506.zip Disk Medis Folder.pdf Media Share Folder.pdf
April 25, 20188 yr Community Expert Are you sure you don't have disk1 excluded from user shares in Global Share Settings? You do have corruption on disk5 though which might break user shares. Apr 25 05:06:15 Tower kernel: XFS (md5): Corruption detected. Unmount and run xfs_repair Stop array and restart in Maintenance mode to repair disk5.
April 25, 20188 yr Author Thank you, I'm now running the repair on disk 5, as for the disk 1 no shares have no excluded disks and it is the same issue across all the disks.
April 25, 20188 yr Community Expert 16 minutes ago, guyver76 said: no shares have no excluded disks I wasn't referring to a particular user share excluding disk1. In Settings - Global Share Settings, it is possible to exclude specific disks from ALL user shares.
April 26, 20188 yr Author Here is the global share setting all drives are included, I also ran the repair on disk 5 and that didn't fix the main problem of being able to access the media folder share. Tower_ShareSettings.pdf
April 26, 20188 yr Community Expert 2 hours ago, guyver76 said: I also ran the repair on disk 5 Can you give more details about this?
April 26, 20188 yr Unrelated, but a problem nevertheless, your Parity(1) disk's SATA connection keeps being reset. You'll need to check/replace its cable. There's also a lot of "wrong csrf_token" junk in your syslog from having a stale browser window open.
Archived
This topic is now archived and is closed to further replies.