Cannot connect to my FreeNas Server

[Al Slitter]

Hello All;
I am hoping that someone might be able to help me with this issue that has frustrated me for many months now.
A couple of years ago I built a FreeNas server using (9.10.2U1). At that time I was a Windows 7 user and was able to access the server and store backup's etc. on the drives located on this server. The configuration of the server contained a SuperMicro X10SLM-F motherboard with 16 GB’s of ECC memory and a celeron processor. In addition it contains 3-WD Red 2GB hard drives in a Raid 5 configuration,
Everything worked well it seems until I made the jump from Windows 7 to Linux Mint 19.2 . The situation might have worsen when my ISP removed my ADSL connection and installed a Fiber Optic solution ?
As it now stands my network consists of 3-workstation and my FreeNas server. The server seems to be booting up correctly and provides a IP address of 192.168.1.xxx which worked well in the past but now after months of trying I am unable to connect to the server from my main station or another station on the network. My thinking was that this was a Samba issue which it might well be but I am exhausted from trying so many fixes that have not worked.

Can someone slowly work with me as I am getting old and have limited system knowledge and get me back to point where I can see my server?

Thank You!

 

[garm]

God day sir,

Are you able to access the Web UI at http://192.168.1.xxx (no need to anonymizes local IPs)?

 

[Al Slitter]

No I am not that is the problem.
Regarding no need to anonymizes local IPs, just trying to be safe.
The address is http://192.168.1.200

 

[garm]

That’s an indication of something bigger then a SMB issue. Do you have a monitor attached to the system?

 

[Al Slitter]

Yes I have a monitor connected to the system. I have a monitor always available so I might manage and or down the system in case of an issue.

 

[melloa]

The situation might have worsen when my ISP removed my ADSL connection and installed a Fiber Optic solution ?

What else changed on your ISP equipment?

Let's do some troubleshooting on your network:

- On your Mint, open a shell and type

Code:

ifconfig

. What is the IP on the inet line? Please don't provide your inet6 for security.

Code:

ifconfig
enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.10.60  netmask 255.255.255.0  broadcast 10.10.10.255

It must be on the same subnet as the NAS (192.168.1.xxx).

If it is on the same subnet, try to ping the NAS:

Code:

ping 192.168.1.200

.

- From the NAS

Open a shell (Option 9)
Type

Code:

ping yahoo.com

. That will test your NAS access to the internet.
Type

Code:

ping x.x.x.xxx

, where x.x.x.xxx is your Mint IP from previous step.

 

[Al Slitter]

First Off I want to thank you for taking the time to assist me in getting my server back into an operating condition. I have listed below the results which I received from my desktop system and the server.
What else changed on your ISP equipment?
The ISP ran Fiber Optical cable directly into my home, they removed the ADSL modem and replaced it with a Fiber Optic modem, they then removed my single band WiFi router and replaced it with a dual band WiFi router.
As mentioned earlier my current configuration has the Fiber optic cable coming into the modem then a single cable running to the dual band WiFi router. I have a eithernet cable running from the WiFi router to a DLink 1GB switch where all of the networking cabling is attached too including the NAS.

ifconfig
enp10s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255

ether 60:a4:4c:63:bf:83 txqueuelen 1000 (Ethernet)

RX packets 343070 bytes 476784244 (476.7 MB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 176675 bytes 16837560 (16.8 MB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0



lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet 127.0.0.1 netmask 255.0.0.0

loop txqueuelen 1000 (Local Loopback)

RX packets 1625 bytes 185140 (185.1 KB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 1625 bytes 185140 (185.1 KB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


Please note I am not a systems administrator so usage of inet6 was new to me but I am familiar now with what is represents. I have removed from the above screen shots two lines which address inet6.

information.
I see the first issue: The subnets are not the same, this will of course cause an issue. Do I need to change the IP address on the server to 192.168.0.200 ??

I tried to Ping the server (PING 192.168.1.200 (192.168.1.200) 56(84) bytes of data.) but did not get any response which is what I suspected would happen.

I tried to ping Yahoo.com from the server and as expect I received the following message:

Host Name Lookup Failure

I hope that I have not missed anything and thank you so much for your time and efforts regarding my situation.

 

[Al Slitter]

I thought I would try and change the static IP address on the server .
This I did and now I am able to reach the server from my main work station.

How ever when getting into FreeNas I have now encountered two issues can you assist me on get a handle on them?

They are:

• WARNING: Feb. 20, 2020, 6:29 a.m. - The WebGUI Address could not bind to 192.168.1.200; using wildcard
  CRITICAL: Feb. 20, 2020, 6:08 a.m. - The volume RAID-Z1 (ZFS) state is UNKNOWN:

 

[Heracles]

Hi AI Slitter,

Your internal network address space changed from 192.168.1.x to 192.168.0.x. You need to re-configure your WebUI for it to listen on the 192.168.0.x address instead of the old 192.168.1.x address that does not exist anymore.

As for the pool, can you post the result of zpool status ?

 

[Al Slitter]

I will attempt to work on the issues later today, thank you again.

As a short point I was surprised to learn from my system that the server has been down for 2-years now and the installation of FreeNas was done nearly 4-years ago. As one gets older time seems to just fly bye.
Because I am retired and live in Thailand and have done so of 16 years I down the server after use due to the terrible power situation here. Yes I understand a UPS would be great but on a small retirement budget some things just fall of the tracks that we want.

 

[Al Slitter]

OK, have tried to do the tasks you mentioned.
(Re-configure your WebUI for it to listen on the 192.168.0.x) This I believe is done correctly as the error relating to this issue is now cleared.

(As for the pool, can you post the result of zpool status ?) I am sorry but I do not know how to get it, just a dummy here??
What I seem to have come upon is one of my hard drives (ada2) does now not seem to be working, if this is the case I will need to replace the drive
and hopefully rebuild my RAID 5 configuration.
The drive seems to be spinning and when the last time I used the system the pool of drives where in good shape. Strange.
I have forgotten so much about using the FreeNas system so I will need some guidance regarding the removal and replacement of the drive.
If memory serves me I actual replaced a drive due to a failure of some sort several years ago.

Thanks again for your assistance.

 

[Heracles]

Hi AI Sitter,

For the command, you do it either over SSH or using the command line from the WebUI. The command is :

zpool status

and the output looks something like this :

Code:

root@Atlas[~]# zpool status
  pool: JBCloud
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:44:29 with 0 errors on Mon Feb 10 22:44:31 2020
config:

    NAME                                            STATE     READ WRITE CKSUM
    JBCloud                                         ONLINE       0     0     0
      mirror-0                                      ONLINE       0     0     0
        gptid/42003674-d1db-11e9-94f5-a0369f858d9c  ONLINE       0     0     0
        gptid/9bca240e-d43f-11e9-9f1e-a0369f858d9c  ONLINE       0     0     0
      mirror-1                                      ONLINE       0     0     0
        gptid/529662d0-d1db-11e9-94f5-a0369f858d9c  ONLINE       0     0     0
        gptid/be00368a-d43f-11e9-9f1e-a0369f858d9c  ONLINE       0     0     0
      mirror-2                                      ONLINE       0     0     0
        gptid/633484c3-d1db-11e9-94f5-a0369f858d9c  ONLINE       0     0     0
        gptid/e7442b03-d43f-11e9-9f1e-a0369f858d9c  ONLINE       0     0     0
      mirror-3                                      ONLINE       0     0     0
        gptid/eedeafa0-d2a4-11e9-9f1e-a0369f858d9c  ONLINE       0     0     0
        gptid/699da698-d440-11e9-9f1e-a0369f858d9c  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:01:08 with 0 errors on Sun Feb 16 03:46:08 2020
config:

    NAME        STATE     READ WRITE CKSUM
    freenas-boot  ONLINE       0     0     0
      mirror-0  ONLINE       0     0     0
        da8p2   ONLINE       0     0     0
        da9p2   ONLINE       0     0     0

errors: No known data errors

 

[Al Slitter]

Regarding: ( For the command, you do it either over SSH or using the command line from the WebUI. The command is : zpool status )

I am sorry to be so ill informed, I have no experience using SSH and nothing is set up. Regarding WebUI I have looked and looked for a command line within FreeNas and have not found one. Can you please assist me with getting to a command line?
On a similar and dissimilar point I noticed when checking out my drives under "Drives" and "Reporting" it shows that my possible ada2 drive
which appears to be not part of my ZFS Raid 5 pool is in fact working or so the report shows.
This of course makes me really want to check this out by using zpool status.
I promise that as soon as my FreeNas server is stable I will hit the documentation to get my knowledge back where it should be.

 

[Heracles]

The command line is available in the WebUI in the left column, at the bottom, and it is named SHELL.

 

[Al Slitter]

Thank you I found it and learn another thing.
The results are hopefully what you need;

[root@freenas ~]# zpool status
pool: freenas-boot
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
da0p2 ONLINE 0 0 0

errors: No known data errors
[root@freenas ~]#

 

[Al Slitter]

I found this a little bit latter maybe it helps?

bash: scan:: command not found
[root@freenas ~]# config:

bash: config:: command not found
[root@freenas ~]#

[root@freenas ~]# NAME STATE READ WRITE CKSUM

bash: NAME: command not found
[root@freenas ~]# freenas-boot ONLINE 0 0 0

bash: freenas-boot: command not found
[root@freenas ~]# da0p2 ONLINE 0 0 0

bash: da0p2: command not found
[root@freenas ~]#

[root@freenas ~]# errors: No known data errors

bash: errors:: command not found
[root@freenas ~]# [root@freenas #

bash: [root@freenas: command not found
[root@freenas ~]#

 

[Al Slitter]

I have spent several hours today getting familiar with FreeNas and am slowly having somethings coming back.

It appears to me that the ada2 which appeared to at first glance be dead or damaged drive is in fact working.
I believe that my Raid Volume (Raid Z1) has become corrupt or something similar, thoughts?

I have now found another issue which I will leave until the server is back in shape. The issue relates to me not being able to view
the FreeNas server from my Linux Mint workstation.

 

[melloa]

I have now found another issue which I will leave until the server is back in shape. The issue relates to me not being able to view
the FreeNas server from my Linux Mint workstation.

Let's fix your network first, than attack the other issues. Did you configure your FreeNAS network correctly with the new IP subnet? Also, configure the gateway to the same as your desktop (I didn't see on your above messages, but usually 192.168.0.1 or 192.168.0.254 on your case).

After you have access to the gui, you will have an easy way to manage things.

 

[Al Slitter]

I am now back at it this morning, please note there is a 12 -15 hour time zone difference between our locations.

Yes I believe so, I went through the various fields and when ever I saw 192.168.1.200 I changed it to 192.168.0.200 .
This does not preclude that I missed something ? I am not sure that 192.168.0.1 is my desktop, it could be a router?
I did change the IP4v default gateway to 192.168.0.1

I have the server up an running in a window here so if there is a question please give me detailed instructions and I will gladly do them.

 

[Al Slitter]

I could be wrong but my system shows the IP4V address of my desktop computer as 192.168.0.11 with the default route and DNS as 192.168.0.1