• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

SMB setup for external storage

Scheduled Pinned Locked Moved Solved
Linux Problems
5
22
12.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    Tim.Trageser
    last edited by Jun 12, 2015, 12:28 PM

    I had that error the other day when trying to image from my USB connected External Drive. Issue was the exports file. Might be worth looking at.

    1 Reply Last reply Reply Quote 0
    • C
      cmcleod
      last edited by Jun 12, 2015, 2:42 PM

      Ok, I’ll go back to my original NFS configuration and maybe I’m doing something wrong and you guys will be able to pick up on it.

      On the Terastation - I have enabled NFS. I assigned the fog server as a client on nfs via it’s IP address. I’ve created a fog user with it’s UID set to match the UID of the fog user on the fog server - 1001. The NFS mount point on the terastation is //mnt/array1/images

      First, I logged into fog and tried to mount the storage server through NFS.
      Name: Terastation
      IP: 192.168.142.176
      Max clients:10
      Storage Group: default
      Image path: /mnt/array1/images – path specified on the NAS
      Interface: eth0
      Username: fog user and same password as on the NAS
      I add it and then I go to the home screen. I click under Disk info to change to Terastation. The response: No error, but no data was return. So, my guess is that means it didn’t work.

      On the fog server, I ran the following commands:

      1. mkdir /mnt/nfs/images
      2. mount 192.168.142.176:/mnt/array1/images /mnt/nfs/images
      3. mount - shows that it was mounted successfully. However, there is no rw after the mount. Does that mean it is not read/write?
      4. vi /etc/fstab
      5. line added:
        192.168.142.176:/mnt/array1/images /mnt/nfs/images nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0
      6. mkdir /mnt/nfs/images/dev
      7. touch /mnt/nfs/images/.mntcheck
      8. touch /mnt/nfs/images/dev/.mntcheck
      9. reboot now
      10. confirm the mount point was successful - output of the mount command is:
        192.168.142.176:/mnt/array1/images on /mnt/nfs/images type nfs (rw,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800,addr=192.168.142.176)
      11. ls -alh /mnt/nfs/images - the .mntcheck file is there with the following permissions:
        -rwxrw-rw- fog:52
        /dev - drwxrwxrwx fog:52
        /images/dev/.mntcheck - same permissions as the other file
        **so I’m not sure if those permissions are correct or not
      12. I login to fog. I go back to the Terastation storage I created earlier. This time I create a storage group called Terastation and change the storage node for terastation’s IP to the fog server. I change the Image path to: /mnt/nfs/images
      13. I go back to the Home screen and change to terastation and I can now see the space available on the Terastation.
      14. I go to Images and create an image:
        Name: Win7-64-Pre-Sysprep
        Storage Group: terastation
        OS: Windows 7
        Image Path: /images/Win764PreSysprep
        Image Type: Multiple Partition Image - all Disks (Not Resizable)
        I click Add
      15. I boot up and register a host computer.
      16. I go to the hosts in fog and choose to upload for the computer to upload an image to fog.
        I reboot the host and I get this error:
        mounting 192.168.142.72:/mnt/nfs/images/dev on /images failed: Permission denied.
        An error has been detected!
        Fatal Error: Failed to mount NFS Volume
        Computer will reboot in 1 minute.

      Any ideas? Thanks so much for your help.

      1 Reply Last reply Reply Quote 0
      • C
        cmcleod
        last edited by Jun 12, 2015, 2:56 PM

        Update - When I went back into Image Management after it failed, there was an error:
        FOGFTP: Login failed. Host: 192.168.142.72, Username: fog, Password: (my password), Error: ftp_login(): Login incorrrect.

        1 Reply Last reply Reply Quote 0
        • C
          cspence Developer
          last edited by Jun 12, 2015, 3:12 PM

          Sounds like a dirty install. If you reinstalled FOG, you will need to delete the fog user.

          1 Reply Last reply Reply Quote 0
          • C
            cmcleod
            last edited by Jun 12, 2015, 3:40 PM

            @cspence

            I tried deleting fog from the forum instructions and I deleted the fog user. I re-installed following the same specifications I listed earlier and I’m still receiving the same error message.

            1 Reply Last reply Reply Quote 0
            • W
              Wayne Workman
              last edited by Jun 12, 2015, 4:09 PM

              @cmcleod said:

              ftp_login(): Login incorrrect

              https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
              Daily Clean Installation Results:
              https://fogtesting.fogproject.us/
              FOG Reporting:
              https://fog-external-reporting-results.fogproject.us/

              1 Reply Last reply Reply Quote 0
              • C
                cmcleod
                last edited by Jun 16, 2015, 7:27 PM

                So, here is how I resolved this issue.

                First, on the Terastation, NFS was setup incorrectly. It was running in User Mode and it needed to be running in Kernel Mode. After this was set, we could then go back into the Fog server and removed the Terastation node. We changed the settings for the DefaultMember to point to the Terastation. After doing this, we were still receiving FTP errors. However, we could see the mount point and the files within.

                We fixed the FTP issues by going to Fog Configuration, Fog Settings, TFTP server and changing the Fog account password. Also, the Terastation was joined to our Windows domain. After some research, we found out that if it is joined to the domain, FTP will not work. After unjoining from the domain, FTP started working immediately.

                The only issue, and this may not be able to be solved, is that when we go to the Home page of Fog and look at the Disk Information, it just reports “No error, but no data was return.”
                If you run df -h in the terminal, you can see the data returned for the total space and free space available. Is there a way to have this show up for the NFS mount in Fog?

                Thanks so much for your help!

                W 1 Reply Last reply Jun 16, 2015, 10:18 PM Reply Quote 0
                • W
                  Wayne Workman @cmcleod
                  last edited by Jun 16, 2015, 10:18 PM

                  @cmcleod Fog uses FTP to determine disk usage. Is the ‘size’ (or relevant command) supported by the buffalo terastation?

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                  Daily Clean Installation Results:
                  https://fogtesting.fogproject.us/
                  FOG Reporting:
                  https://fog-external-reporting-results.fogproject.us/

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmcleod
                    last edited by Jun 17, 2015, 4:58 PM

                    It appears to support it. I ran the command size but that appears to only work for file sizes. I ran the command:
                    size /mnt/array1/images/Win7Master/d1p1.img and it returned a response
                    213 8553337

                    W 1 Reply Last reply Jun 17, 2015, 5:31 PM Reply Quote 0
                    • W
                      Wayne Workman @cmcleod
                      last edited by Jun 17, 2015, 5:31 PM

                      @cmcleod

                      Well… I’m not sure…

                      Most people don’t even get NAS to work right with FOG so… you should feel lucky lol. I guess just use the Buffalo Terastation’s web interface to keep an eye on your space usage?

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                      Daily Clean Installation Results:
                      https://fogtesting.fogproject.us/
                      FOG Reporting:
                      https://fog-external-reporting-results.fogproject.us/

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 2 / 2
                      2 / 2
                      • First post
                        22/22
                        Last post

                      173

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.3k

                      Posts
                      Copyright © 2012-2024 FOG Project