Jump to content

darkphox

Members
  • Posts

    5
  • Joined

  • Last visited

darkphox's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Interesting. These ports are open on my firewall (for my LAN at least), and both SMB and NFS searches are finding the shares when going through the process to add them. It's once they're added that it can't seem to see the share as 'online.' My local TLD was customized. A few months back I changed it so I could connect with a domain address instead of the server's IP to avoid the "potential security risk ahead" warning. I deleted this field, so it is now blank. Adding a share via the automated setup still shows offline, but connecting a share via manually entering its IP now shows the share online and mountable. I'm out of time tonight, but I'll do the port scans tomorrow.
  2. Hi there, I believe I'm having the exact same issue as @biologicalrobot, where the recent change in UD seem to be causing my remote shares on a second Unraid server to no longer show as online nor be mountable via either SMB or NFS. Have tried: - rebooting both unraid servers - disabling/re-enabling SMB and NFS - deleting and re-adding multiple shares with various permissions - re-adding via host name and by IP - second server successfully pings (although it looks like the change makes that no longer relevant) - shares are still accessible on other systems (several windows machines) I ran the commands @dlandon posted and got the same results of 1 and 124, respectively. Sharing my diagnostics as well in case it proves helpful. backphox-diagnostics-20240507-2016.zip
  3. Thanks Jon, I'm tracking. I use the term 'old' relatively. They're about a year old and are the drives from my raspi NAS setup. I also have another 18TB drive in the pipe for a 2nd parity disk, and I still have everything redundant on my old OMV setup. Just got confused (somehow) on the impact (or lack thereof) of mixed disk sizes. Again, loving Unraid...by far the best experience I've had with this type of thing.
  4. Thanks for the quick response! I swear I read somewhere in the past week that keeping parity while using mixed drive sizes limited all your disks to the smallest disk's capacity...but now I can't find it, lol. I appreciate the sanity check.
  5. Hey folks, I'm new to Unraid, but I totally love it. It's a big improvement, coming from OMV and generic raspi NAS's. I'm adjusting my configuration and have some concerns before I press the big red button. Bottom Line Up Front: I'm thinking I should use the 'New Config' tool to add new disks to my array that are smaller in capacity than my current disk in order to establish smaller drive capacities and maintain parity protection. I'm unsure though, whether this is the correct way forward. Details: I had an array with (1) 18 TB data drive and (1) 18 TB parity drive. Things worked great but I was nearing 15 TB of data so I decided to add some old external drives to the array as data disks. These were (1) 10 TB and (1) 8 TB drive. As I understand it, Unraid must use the smallest disk's capacity on all drives to maintain parity. So, all 3 data disks should only have 8 TB of usable space, for a grand total of 24 TB. I installed the drives, added them to the array, and Unraid cleaned and formatted them. They're now showing in my pool as usable drives, but all of my data disks still have their full capacities with a total of 36 TB showing up. Again, I think I need to run the 'New Config' tool in order to properly set the disks' max capacities to 8 TB and re-establish parity. However, I'm not sure this would work the way I think it would and I have some questions that I haven't been able to find in the manual or in other posts.... - Would Unraid avoid data loss by 'balancing' the 18 TB disk? I.e. send data to the other drives before reducing its max capacity to 8 TB? - Is there another way to do this that I'm simply not considering? I appreciate ya'lls input!
×
×
  • Create New...