tax

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

tax's Achievements

Noob

Noob (1/14)

0

Reputation

  1. one thing i am missing in SF on 5.0 is the UI to manage the sharing options for disk shares. now I'm not sure if that's: a) a bug in SF with 5.0 b) something SF just doesnt (yet) provide c) me being blind and simply not seeing it with the stock UI you can manage these settings by clicking on the devices on the main screen, afair can anyone confirm that?
  2. Thanks lostwebb, i just tried. I followed the steps just as you posted and it works perfectly - fix confirmed!
  3. 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.
  4. I first (discovered and) installed simpleFeatures on top of the updated webGUI and found many of the pages mostly empty. looking in the forum quickly brought up the idea that this is because of incompatibility with the newer webgui. So i removed the two files of the updated webgui from the plugins folder and rebooted -> it's mostly working now (and some feature are very cool). Though I still feel it's missing some of its proposed functionality. e.g.: - the temp. display in the right part of the menubar doesn't show values at all (only the icons/labels) - can't get the webserver plugin to start. switching it to enabled (of course with some unused port like 8888 or 8088) still gives me a "stopped" status (cant find any valuable log/debug information on that either) - the "stats" tab only shows "disk stats" (according to the screenshots, there should also be a CPU graph to switch to) cheers tax
  5. that was exactly the reason for me trying to go with a reader where i could independently swap out the SDcard in case it really resigns ... also i figured a rather swift sdcard would also have a better boot-performance than a standard thumbdrive (but thats really just a nice bonus ... how often do you really boot your NAS once its setup and running) I ended up registering my license on a good old 8G flash drive i initially tried unRAID with (Kingston DataTraveler G3) ... i didnt have any problems with that one so far.
  6. Alright then, back to flash drives it is So for the record: don't go for "Kingston MobiLite G3" SD card reader as boot device, doesn't work thanks guys for saving me more trial and (even more) errors
  7. - you mean to simply disable all other boot devices? - and what is meant by "a mini" - could you elaborate? thanks for your quick help here, really appreciate it!
  8. I'm using a standard SD card (no micro/mini). "Transcend Ultimate-Speed SDHC Class 10 UHS-1 8GB" (thats how its listed in the shop)
  9. Hi guys I bought the mentioned Kingston card reader in order to use it as boot device for my unraid system. Due to the lack of availability for the Kingston mobilite G2 - which i have read here on the forum would work fine - I just took the risk of buyin the G3, hoping it would work in the same manner. I prepared the SDCard/Reader as usual (copied the system, ran the make-bootable script) and moved it over to my NAS (being a HP N54L btw.) to boot from it. It boots just fine, but when it tries to finally mount the partition via the label, it can't find it and therefore cannot load the config. It seems to me, that it doesn't see the SD-Card as a device (looking into /dev/disk/by-ID i only see the reader device, but no partition, which would have the label information). But how can it even boot from it, if that's the case?! I'm not linux-savvy enough to confirm that's the issue and if it is fixable or if i am just out of luck with that particular card-reader-device (in which case this post could be seen as a warning against buying that device for that purpose). cheers tax