SMB setup for external storage

[ch3i]

@cmcleod said:

@ch3i
Initially I tried the NFS route with the Terastation. When I added it to the Storage Group as a second node, fog just showed an error on the Home page for that storage device.

I then mounted the NFS share within CentOS and pointed fog to the local mount point. Fog saw the additional storage with no problem. However, when I tried to upload the image, I received the same error I stated in my original post that I was receiving now with CIFS.

Wich is the mount point of your NFS share in your NAS? I think is not xxx.xxx.xxx.xxx:/images.

For example a ReadyNAS : the NFS share is >> xxx.xxx.xxx.xxx:/c/media/your_share/ (your_share can be images…)

[Wayne Workman]

perhaps… just perhaps…

Run the download in “debug” mode,

mount the SMB share manually at the CLI, and start the imaging process? (do not use the “fog” command, it tries to mount via NFS).

You’d have to dive into what the “Fog” command actually does… find it’s file and examine what is in it…

And just do everything in there except the NFS stuff (because you already mounted via SMB, right?) and cross your fingers and see if it works?

The "Troubleshoot NFS " article MIGHT assist you with some of this…
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS

And the ill-completed Fedora 21 Server article has examples of SMB mounting…
https://wiki.fogproject.org/wiki/index.php/Fedora_21_Server

and, if you can figure out the commands to issue… and it works… then modify the “fog” command so that it does those things every time, then it should work for normal image downloads?

You’d have to modify the upload processes too.

I’d totally absolutely try this like right now but my servers are down due to a dead AC adapter for my router

[Wayne Workman]

Also, it’s not necessary to use /etc/fstab to mount things… It can be done directly from the CLI.

[Tim.Trageser]

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.

[cmcleod]

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.

[cmcleod]

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.

[cspence]

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

[cmcleod]

@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.

[Wayne Workman]

@cmcleod said:

ftp_login(): Login incorrrect

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

[cmcleod]

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!

[Wayne Workman]

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

[cmcleod]

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

[Wayne Workman]

@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?