I know what's wrong, I just don't know how to fix it!

[Julianh]

I tried to put as much information in as possible, and forgot the actual error! Sorry it’s

Failed to mount NFS volume

Thanks for replying.

[ch3i]

@Julianh said:

I tried to put as much information in as possible, and forgot the actual error! Sorry it’s

Failed to mount NFS volume

Thanks for replying.

It’s seem to be an error in your export file ? How do you add that new storage in FOG ? Could you post your export and where is mounted your new hdd.

[Julianh]

I added an extra disk locally to the fog server, I’m not using an NFS server. It 4Tb disks in it was the only disk, that had the OS and images on it. It’s now full, hence the need for a new disk.

Tom kindly pointed out the disk was full, as the sql server didn’t initialise.

Thanks for your help

Julian

[Wayne Workman]

Double check you made the .mntcheck files inside the new /images and /images/dev directories ??

Also, assign 777 recursively to your new storage node location?

[CODE]chmod -R 777 /path/to/your/new/storage/node[/CODE]

[Julianh]

I’ve attached a photo of the servers screen, it shows the error better. By doing this I also noticed a fail to mount error. I’m not sure I didn’t mess up the mounts from the new disk, so I’ve pasted the fstab

I’ve also issued the “sudo chmod -R 777 /images2” command, the new disk is mounted as images2.

Mod edited to use code box
[CODE]image@fog1:/etc$ cat fstab

/etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a

device; this may be used with UUID= as a more robust way to name devices

that works even if disks are added and removed. See fstab(5).

<file system> <mount point> <type> <options> <dump> <pass>

/dev/mapper/fog1–vg-root / ext4 errors=remount-ro 0 1

/boot was on /dev/sda2 during installation

UUID=7fb5c067-98c2-45bf-88c7-66e39f3f149e /boot ext2 defaults 0 2
/dev/mapper/fog1–vg-swap_1 none swap sw 0 0
/dev/sdb1 /images2 ext3 defaults 0 0

image@fog1:/etc$[/CODE]

Thanks for your help, its late here, UK 23:52, and I have to go. If you have any suggestions I’ll look at tomorrow morning, I’d be grateful and thanks in advance.

I still think I have the username / password wrong, where would you recommend I get the
correct ones from?

Julian

[Julianh]

Don’t know what happened with the font there, sorry, here’s the photo

https://www.dropbox.com/s/75rigpzcy2b52mf/fogerror.jpeg?dl=0

[Wayne Workman]

@Julianh

On your FOG server, what is the output of these two commands?

[CODE]cat /etc/exports
ls -laR /images2 | grep .mntcheck[/CODE]

[Julianh]

Thanks for your help, much appreciated.

I issued the commands, and realised the /images2 and /images2/dev directories were not being exported. I then edited the /etc/exports file to do so. The new 4tb disk is mounted on /images2

I’ve taken a photo, now the Nfs error has gone. One down one to go.

Here’s the url of the photo;
https://www.dropbox.com/s/34lgv7b3f7fkzpc/fogerror2 (1).jpeg?dl=0

This is the result of the commands, after editing the file;

image@fog1:~$ cat /etc/exports
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2)
/images2 *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=3)
/images2/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=4)
image@fog1:~$ ls -laR /images2 | grep .mntcheck
-rwxrwxrwx 1 root root 0 Jun 1 16:30 .mntcheck
image@fog1:~$

So it’s getting there, I’m still not sure about the password, so I’m using the “password” from the /opt/fog/.fogsettings. Is that correct? What username should I use?

Thanks

[Wayne Workman]

@Julianh You’re missing one .mntcheck file.

You need one in both images and dev folders

[CODE]touch /images2/.mntcheck
touch /images2/dev/.mntcheck[/CODE]

After that, restart the NFS service and portmap/RPC (or reboot the machine).

Let us know what it does then.

[Julianh]

Thank you Wayne, your suggestion has made a big step forward.

The machine now uploads an image, but unfortunately it’s created an image in the /images2/dev directory, in a directory that is the MAC address of the machines lan card.

The image size is also 0 in the list of images
The command ls - l gives

root@fog1:/images2/dev# ls -l
total 4
drwxrwxrwx 2 root root 4096 Jun 2 22:03 e03f49af16b2
root@fog1:/images2/dev#

I thought it may be permissions, so issued

chown -R root.root /images2

But that didn’t fix it

Its the final stage that moves it from the /images2/dev to /images2 and renames it. So close…

Anyone know the next step?

Julian

[Wayne Workman]

Sounds like you now need to troubleshoot FTP.

Take a look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Let us know if you figure it out, or if you need more help.

Here’s a hint… Credentials

[Julianh]

I’ve spent 5 hours going through this, and still can’t see it.
I’ve read through the guide Wayne suggested, and can’t seem to find the problem,

My .fogsettings are; (passwords changed)

ipaddress=“10.10.1.5”;
interface=“eth0”;
routeraddress=" option routers 10.10.1.1;“;
plainrouter=“10.10.1.1”;
dnsaddress=” option domain-name-servers 8.8.8.8; “;
dnsbootimage=“8.8.8.8”;
password=“11111”;
osid=“2”;
osname=“Debian”;
dodhcp=“y”;
bldhcp=“1”;
installtype=“N”;
snmysqluser=”"
snmysqlpass=“22222”;
snmysqlhost=“”;
installlang=“0”;
donate=“0”;
fogupdateloaded=“1”
image@fog1:/opt/fog$

I’ve checked the storage node, and the management username and management password are fog and “11111”

I’ve ftp’d from windows to the fog server, and sent a file from windows to the fog server, using the credentials fog and 11111. The file transferred fine.

I’ve reset the folders with

sudo chmod -R 777 /images2
sudo chown -R fog:root /images2.

The results of the command

ls -laR /images2 are below;

drwxrwxrwx 4 fog root 4096 Jun 1 22:32 .
drwxr-xr-x 28 root root 4096 May 28 23:13 …
drwxrwxrwx 3 fog root 4096 Jun 2 21:47 dev
drwxrwxrwx 2 fog root 16384 May 28 20:16 lost+found
-rwxrwxrwx 1 fog root 0 Jun 2 17:43 .mntcheck

/images2/dev:
total 12
drwxrwxrwx 3 fog root 4096 Jun 2 21:47 .
drwxrwxrwx 4 fog root 4096 Jun 1 22:32 …
drwxrwxrwx 2 fog root 4096 Jun 2 22:03 e03f49af16b2
-rwxrwxrwx 1 fog root 0 Jun 2 17:43 .mntcheck

/images2/dev/e03f49af16b2:
total 34999444
drwxrwxrwx 2 fog root 4096 Jun 2 22:03 .
drwxrwxrwx 3 fog root 4096 Jun 2 21:47 …
-rwxrwxrwx 1 fog root 512 Jun 2 21:47 d1.mbr
-rwxrwxrwx 1 fog root 212396255 Jun 2 21:47 d1p1.img
-rwxrwxrwx 1 fog root 10085091757 Jun 2 22:03 d1p2.img
-rwxrwxrwx 1 fog root 512 Jun 2 22:03 d2.mbr
-rwxrwxrwx 1 fog root 25506898197 Jun 2 22:40 d2p1.img

/images2/lost+found:
total 20
drwxrwxrwx 2 fog root 16384 May 28 20:16 .
drwxrwxrwx 4 fog root 4096 Jun 1 22:32 …
image@fog1:/images$

The only thing I can find is I have no storageftppass= line, but if this was the fault, wouldn’t it affect the creation of images on the original disk, which works fine.

I have to build images next week, or my company won’t be able to run a course, and I’ll really be in trouble.

Can anyone help me out?

[Wayne Workman]

@Julianh

You are likely running FOG 1.2.0 ? You wouldn’t have storageftppass= I think. That’s a more recent thing in FOG Trunk.

When you say you “added a disk”, could you please elaborate?

Did you physically add another hard drive into the server itself?

Or are you using a NAS ?

[Julianh]

I had a 4tb disk in the server, that I installed fog on. The OS and images are on this disk. I ran out of space, and added another 4 Tb disk to the fog server. It’s this new disk I’m having problems with, the old disk works fine.
The new disk is mounted as /images2.
There is no NAS involved, it’s all local, which it has to be. I’m not allowed to use anything except the 1 server, and must keep it on the network the clients are on, it’s not allowed to connect outside, to another NAS box for example.

Thanks

Julian

[Julianh]

The problem is now, how do I get the images named correctly and in the images2 directory instead of being named the MAC address and in the /images2/dev directory.

Thanks

Julian

[Wayne Workman]

Well, a simple work around would be something like this:

[CODE]mv /images2/dev/MacAddressHere /images2/EXACT_Image_Name_You_Chose[/CODE]

And when I say exact, look at the path in your image definition (in the web UI). Normally, stuff like underscores and whatnot are truncated, the actual file name that it should be will be in the PATH section.

But, can you verify that when you used FTP to transfer a file, can you verify you were accessing the correct storage node?

Did you ECHO some text to /images2/dev/text.txt and then try to move that via FTP to /images/text.txt ??

[Julianh]

I have to get it working with the front end, although the mv command would work, In the long term I won’t be the only one using this so it needs to work fine, unfortunately.

Here’s the text from the windows ftp to the fog server,

ftp> open 10.10.1.5
Connected to 10.10.1.5.
220 (vsFTPd 3.0.2)
User (10.10.1.5:(none)): fog
331 Please specify the password.
Password:
230 Login successful.
ftp> pdw
Invalid command.
ftp> pwd
257 “/home/fog”
ftp> cd /images2
250 Directory successfully changed.
ftp> put test.txt
200 PORT command successful. Consider using PASV.
425 Failed to establish connection.

I redid this, I noticed that it didn’t transfer the file, but logged in. This suggests file/directory permissions, but my previous post shows what they were set to, are they wrong? Or should the directories be set to root root, rather than fog root?

Incidentally the machines being imaged have 2 drives in them
I’m getting desperate, I’ll have to explain to my boss why this isn’t working tomorrow, any suggestions?

[Wayne Workman]

Dumb question but, your Windows firewall is off, right? Like… totally off? Exceptions for stuff like TFTP don’t really work… I couldn’t get them to work anyways… maybe FTP might be the same… best to turn it off.

Also,

Can you try to use FTP from the FOG server itself? If it works, then that is a valuable troubleshooting piece.

[Julianh]

This post is deleted!

[Julianh]