October 5, 201312 yr I used to use SNAP to mount a disk as TEMP drive but this doesn't seem to work very well in 5.0 final. Is there an alternative plugin or method to accomplish this?
October 5, 201312 yr Try the new version of SNAP that has been updated for 5.0 here: http://lime-technology.com/forum/index.php?topic=29519.0
October 5, 201312 yr Author Try the new version of SNAP that has been updated for 5.0 here: http://lime-technology.com/forum/index.php?topic=29519.0 Thanks for that. Didn't know it was still developed. Thought it was a dead end.
October 5, 201312 yr I revived it because it is a great plugin. Let me know if you find any bugs. I've tested it pretty well, but there may still be a few minor issues.
October 6, 201312 yr Author I installed it and gave my temp disk a name and mounted and shared the disk. That seemed to work, but after a reboot the disk wasnt available anymore. Snap was started but the disk showed as shared but not mounted. Did I do something wrong? It used to work in earlier versions.
October 6, 201312 yr That sounds like an issue that I resolved. Are you using SNAP version 5.13? Is it a usb drive? When SNAP starts it will only mount and share usb drives.
October 6, 201312 yr Author That sounds like an issue that I resolved. Are you using SNAP version 5.13? Is it a usb drive? When SNAP starts it will only mount and share usb drives. I am using 5.13. No it is not a USB drive but mounted to a SATA port. I didn't have this issue with earlier versions (ie 5.09). I need the disk available immediately after reboot and without any user intervention.
October 6, 201312 yr I am using 5.13. No it is not a USB drive but mounted to a SATA port. I didn't have this issue with earlier versions (ie 5.09). I need the disk available immediately after reboot and without any user intervention. SNAP mounts and shares usb drives only on startup. It does not mount SATA drives. If it did that before, it was unintentional. You can mount and share the drive on reboot by adding the following line to your 'go' file: /boot/config/plugins/snap/snap.sh -ms yourdrivesharename This will mount a share the drive.
October 6, 201312 yr I use an older version of bennie-chan's drive mount plugin. He is in the middle of a rewrite so the latest one is a little buggy still, but I'd recommend it for mounting an app or whatever drive. I have a slightly modified version of his old plugin that is not SF dependent if you want it... Just allows you to configure a static mount for non array drives... Simple simple.
October 11, 201312 yr I was also looking for such an "alternative" solution. My plan was to use a USB3-connected drive as TimeMachine drive for my macs on my LAN. The problem I ran into with SNAP was that it automatically mounts and shares the drive that it has assigned to manage. Now that is of course not a "problem" per se, as SNAP was designed to do exactly that, as I understand. For my TimeMachine share though, that is not what I want. I want the TM share not be exposed via smb but only via AFP as dedicated timemachine share - and thats not (yet) possible using SNAP, right? I came up with a somewhat dirty hack: I created a TM share on my cache drive (using the cache-only setting) and (since i don't want to use the cache drive as TM target itself - its only a 120G SSD) I am mounting the USB drive into that folder manually afterwards. This way i'm able to use the unRAID GUI to configure the TM share but still make the data go to an unmanaged drive directly. The remaining thing yet to be solved is that this manual mount only works, once the user shares are created. so adding the manual mount command at the end of the go script fails as the mount target doesn't exist at that point. Also when using the GUI to Poweroff/Reboot the system, I have to manually unmount the USB disk first, otherwise the usershares cannot be unmounted. Do you guys see any problem with my approach/hack in regards to the array (or the unRAID system in general) ... since i'm not that much of a linux crack.
Archived
This topic is now archived and is closed to further replies.