SMB Discover

[Arvi LEFEVRE]

Hello!

I made my Freenas about 2 weeks ago, 3 HDD of 3 TB, which gives me 5.2 TB of storage, 16 GB of RAM, it's really fast (I copied files from my PC at 110 MB/s, network limit.

But now that I have almost 1 TB of data on the NAS, I noticed that, if I restart the NAS or my computer, often it won't work or it will take a lot of time to discover the shared folder when I click on my nas in the network Area (from win 7), it just says connection timed out (or something like that). Do you think it could come from the NAS ?
Because from my raspberry pi, that runs KODI, now I have to reboot 10-20 times maybe to finally have, maybe, the SMB shares (I can use the plex share when it doesn't work, it's much better when I can check "Movies" or "TV shows" directly.

What do you think that could be?

Last question, I still have 3 empty racks for HDD, I want to add more in the future, do you think it will be OK? My MB only accepts 16 GB of RAM, so I can't add more :(

Thanks :)

 

[Robert Trevellyan]

I can offer a general answer to your 2nd question. I assume your pool is configured as RaidZ1. With 3 slots available for more hard drives, you could add another 3-disk RaidZ1 pool. However, there are at least 2 reasons why you'd probably be better off destroying your first pool and making a new 6-disk pool:

1. If you have to replace a disk in a RaidZ1 pool, you will be at high risk of data loss while your pool re-silvers. The more data you have in the pool, the higher the risk.
2. Managing 1 pool is simpler than managing 2 pools.

Whether or not 16GB of RAM will be a limiting factor depends entirely on how you plan to use your NAS.

 

[Robert Trevellyan]

I should probably mention that if someone shows up on this thread who might be in a position to help with your main issue, they will expect you to follow forum rules.

 

[Bidule0hm]

I'll just add that he's not forced to create a second pool, he can add a second vdev to the existing pool (but a RAID-Z1 of 3TB drives isn't recommended, let alone 2 of those in the same pool...).

We need more info to debug the main issue (list of hardware, share type, service & share settings, ...).