ken-ji

Members
  • Content count

    370
  • Joined

  • Last visited

Community Reputation

29 Good

About ken-ji

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Philippines
  1. If I Remember Correctly, the drive number limit is a technical one. unRAID was kinda stuck for a long time with 26 Drives max including the flash drive simply because LT was a one man operation and weren't ready to support the case where the drive names under the hood exceeded the sda-sdz naming (it wrapped around to sdaa) There is no such thing as a custom distro underneath. unRAID is primarily based on Slackware - one of the oldest surviving distro's which is rock stable and simple. Of course some components are bumped up to meet user needs and demands, the but the core principles of the distro are all there.
  2. Just to clear some misconceptions on @tucansam None of the LSI cards have a SAS expander. all of the cards have enough chips and PCIe Lanes to properly drive all the interfaces. An external SAS port (SFF-8088) is electrically the same as an internal port (SFF-8087), the only difference being the shielding requirements and the rigidity of the connector. There are adapters for converting back and forth passively. That said. looks like you have a rotten lemon
  3. Yep. Unfortunately I've already left the server behind for the week (This is at my relative's place and I have access during the weekends) I can try to see if it can be replicated on my server.
  4. Hey got a USB flash drive giving this in the UI. Its a Samsung Flash Drive Fit 128GB. exFAT formatted, (I manually mounted it in /tmp/usb as UD was going to try to mount it to /) Any logs or command outputs you need? UD's log says: Tools - System Devices has this:
  5. I'm curious - which unraid partitioning scheme are we referring to? the "old" start at 63 MBR? the "new" start at 64 MBR? (AFAIK gpt always starts at 64)
  6. my bad. I've forgotten how to do the computations... the diagram you've quoted above is exactly the case for a single 9200-8e card. There will be no speed disadvantage with a 16e (however, the 16e might be a PCIe 3.0 card - thus possibly giving you better bandwidth) So you need to take this into account: Is your server populated with PCIe3.0 capable Xeon(s)?
  7. Sorry, just realized I wasn't clear. A single 9208e card your getting has 2x 4x ports. Each EXP3000 ESM only requiring a single 4x port to work with. Thus a single 9208e card should be able to access each EXP3000 at 4.8Gb/s - of course 12 drives in a EXP3000 would mean a theoretical max speed of 40MB/s. @johnnie.black would have better numbers for the actual real world performance.
  8. Sorry if it wasn't clear (or I omitted the info) With the share set to "Private", the default rule is *(ro,async,wdelay,insecure,root_squash,all_squash,no_subtree_check,fsid=100,anonuid=99,anongid=100,sec=sys,ro,root_squash,all_squash) When you set something in the rule field, that rule takes over and the default is completely superseded. So in my previous post, there are two rules stated in the field. one for 192.168.2.* the next for * (everybody else) If you omitted the second rule, everybody would get access denied.
  9. Hmm. It seems the EXP3000 has built-in expanders and only needs a minimum one a single link to each EXP3000. so a single LSI9208e should be enough... unless EXP3000 has dual ESMs... in which case another LSI9208e may be necessary.
  10. Here's a sample that will only allow the 192.168.2.* machines write access to the NFS share. Everybody else gets readonly Additionaly, the options allow root user access from the 192.168.2.* machines. Everybody else gets mapped to uid=99 192.168.2.0/24(sec=sys,rw,no_root_squash,insecure) *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash) So, if the client IP fails to match whatever you have listed, they don't get access.
  11. This works both ways. Just be careful to use a cache-only or share-only location with the Dropbox mount point.
  12. Ok , but the Docker data folder should be cache only... or array only. Otherwise Dropbox will delete your files when the mover kicks in...
  13. That's a permission issue, but AFAIK with no way to isolate which file dropbox is having issues with.
  14. Refer to this topic as this explains the correct way of using the Private NFS shares
  15. Actually it seems that while the array is stopped, unRAID continuously rescans the controllers for device changes. When the array is running, no new devices will be detected, unless the UD plugin (or is it the preclear plugin?) is installed and the UD tab is open in a browser - or you manually run the controller rescan from a shell. I have a hotswp external enclosure and I do the hotswap all the time I need it.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.