Posts made by arduinoAndMore

@Wayne-Workman Ah. Thank you. In hindsight I probably could have saved some trouble by copying the dev folder out of the previous /images (now /oldImages) directory. I just copied the image I knew I needed to keep and then created a new dev directory. Just should’ve copied both

Troubleshoot NFS

@Tom-Elliott …So apparently the .mntcheck file goes inside /images/dev and not just under /images? Was that really what I did wrong? facepalm

Is it just that .mntcheck should be under /images/dev or should it be in both /images/dev and /images?

It works now.

Thank you both so much for your valuable assistance! Keep up the good work!

@Wayne-Workman said in Trouble after adding storage to /images:

find /images | grep .mntcheck

Output of find /images | grep .mntcheck is

/images/.mntcheck

Out put of ls -lahRt /imagesis

/images:
total 36K
drwxr-xr-x  6 fog  root 4.0K Jun 15 14:55 .
drwxrwxrwx  2 fog  root 4.0K Jun 15 14:55 dev
drwxr-xr-x 26 root root 4.0K Jun 15 14:07 ..
-rwxrwxrwx  1 fog  root    0 Jun 15 14:04 .mntcheck
drwxrwxrwx  2 fog  root  16K Jun 15 13:56 lost+found
drwxrwxrwx  2 fog  root 4.0K May 26 09:34 MultiKiosk
drwxrwxrwx  2 fog  root 4.0K May 11 10:32 postdownloadscripts
/images/dev:
total 8.0K
drwxr-xr-x 6 fog root 4.0K Jun 15 14:55 ..
drwxrwxrwx 2 fog root 4.0K Jun 15 14:55 .
/images/lost+found:
total 20K
drwxr-xr-x 6 fog root 4.0K Jun 15 14:55 ..
drwxrwxrwx 2 fog root  16K Jun 15 13:56 .
/images/MultiKiosk:
total 1.8G
drwxr-xr-x 6 fog root 4.0K Jun 15 14:55 ..
-rwxr-xr-x 1 fog root   47 May 26 09:34 d1.original.swapuuids
-rwxr-xr-x 1 fog root  512 May 26 09:34 d1p2.ebr
drwxrwxrwx 2 fog root 4.0K May 26 09:34 .
-rwxr-xr-x 1 fog root 1.8G May 26 09:34 d1p1.img
-rwxr-xr-x 1 fog root  512 May 26 09:27 d1p5.ebr
-rwxr-xr-x 1 fog root  250 May 26 09:27 d1.minimum.partitions
-rwxr-xr-x 1 fog root 1.0M May 26 09:27 d1.mbr
-rwxr-xr-x 1 fog root    0 May 26 09:27 d1.has_grub
-rwxr-xr-x 1 fog root   16 May 26 09:27 d1.original.fstypes
-rwxr-xr-x 1 fog root  250 May 26 09:27 d1.partitions
-rwxr-xr-x 1 fog root    4 May 26 09:27 d1.fixed_size_partitions
/images/postdownloadscripts:
total 12K
drwxr-xr-x 6 fog root 4.0K Jun 15 14:55 ..
drwxrwxrwx 2 fog root 4.0K May 11 10:32 .
-rwxr-xr-x 1 fog root  233 May 11 10:32 fog.postdownload

As you can see I do have one small image called MultiKiosk that is stored here already. I’m trying to capture a new Windows7 image right now.

@george1421 @Tom-Elloitt

Content of /etc/exports

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

Output of showmount -e 127.0.0.1

Export list for 127.0.0.1:
/images/dev *
/images     *

I still get the message from the client saying:
“Could not verify mount point. Check if .mntcheck exists (/bin/fog.upload)”
Computer will reboot in 1 minute

@george1421

My output is as follows. Note that I changed the second line from /images/dev to /images. I assume that’s not what I was supposed to do.

fogadmin@fogserver:~$ cat /etc/exports
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1) 

As you mentioned in your reply I should probably see the /images/dev share in the output of showmount. How should I go about adding that new share?

@george1421 This makes sense. What is the proper way to add the share? Thanks

@Tom-Elliott

I did a screenshot and coped the text from the picture using OneNote. OCR’s fault I updated the output of sudo mount (reply below) using copy-paste over ssh.

Output of sudo mount /dev/sdb1 /images is

mount: /dev/sdb1 already mounted or /images busy
mount: according to mtab, /dev/sdb1 is already mounted in /images

@Tom-Elliott

Output of sudo mount

/dev/mapper/fogserver--vg-root on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sdb1 on /images type ext3 (rw)
/dev/sda1 on /boot type ext2 (rw)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
nfsd on /proc/fs/nfsd type nfsd (rw)
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,default_permissions,allow_other)```

@george1421

The output of showmount -e 127.0.0.1 is

Export list for 127.0.0.1
/images *

@Tom-Elliott Thank you for your reply. I looked in /etc/exports and it was pointing at /images and /images/dev I’m pretty sure there’s nothing on /images/dev but the new drive is mounted at /images.

I tried changing both to point at /images and got the same result. I’m not sure if I did that right or not, but you’re right about the /etc/exports file.

I wasn’t sure if I should post this under Linux or under Fog since I don’t know where the issue lies exactly, but here we are.

I recently ran out of space on my FOG 7589 VM. I added a new disk to the VM and mounted it at /images following instructions here. Now when I try to capture an image, the client fails to check the mounted file system and says to check and make sure that .mntcheck exists (and it does, with the correct permissions).

The disk space pie chart in FOG itself shows the correct space in the new disk. I know FOG sees its new images directory, but for some reason clients just don’t like it after it’s mounted. Please advise. Thanks!

UPDATE: I wound up having the same issue again trying to capture an updated image under the same conditions. I set the folder permissions again and tried to capture before running a check from a live USB stick. This also failed, which means that permissions were not the problem (important, but not the cause of this issue)

I booted to Slacko Puppy Linux and ran gparted and did right-click /dev/sda1 and clicked check. It takes a few seconds and then everything works. Hope that helps.

Bottom line: Do a check on the drive from a live USB

@Wayne-Workman Here’s what I did: I booted to Puppy (live) and tried to check the drive. It didn’t take more than 10 seconds and it returned nothing. I’m not sure it actually did anything useful. (Might have, just no confirmation)

I also discovered that the directory I had created to save the image to on my server (inside /images) was owned by someone besides root. I chowned it to root and tried again. The image seems to be going up just fine now. I hope this is useful to someone down the line.

sudo chown root:root /images/<imagename>

@Wayne-Workman This is my golden machine, so it would take some effort to redo the image. I suppose that might be best at this point. It’s better than hacking this one into working and then spreading problems further by imaging. Thanks for the help. I’ll plan to redo the image.

@Wayne-Workman Everything looks perfectly happy until that first screenshot in my last response. Hope that helps

@Wayne-Workman https://onedrive.live.com/redir?resid=BD4D5D336B75EB86!12042&authkey=!AIebEm7G2UuGnWI&v=3&ithint=photo%2Cjpg

That message pops up briefly before receiving the following:

https://onedrive.live.com/redir?resid=BD4D5D336B75EB86!12043&authkey=!ALF3ccl2Vs2wGgc&v=3&ithint=photo%2Cjpg

Thanks

I’m receiving an error from FOG when I try to capture an image. I captured this image once last week and realized I forgot to add a config file to the machine, so I tried to capture again after I added the file. Now I am receiving the following error:

Partclone fail, please check /var/log/partclone.log !

An error has been detected!
Failed to complete upload (savePartition)
Args Passed: /dev/sda1 1 /images/0015c547b279 all

Computer will reboot in 1 minute

Other notes: I am capturing a single partition which has Lubuntu 15. I’m on a dedicated imaging network running FOG 7589. The image type is currently multiple partition single disk. I have tried the others, and raw is the only format that works currently. That’s not what I want to use of course. Image size should be around 2-5GB or so. If I’ve left any details out, let me know.

Like I said, this worked once last week, and I haven’t done anything drastic since then. I assume the fix should be pretty simple. I just haven’t found it yet. Thank you for any help you can give.

@Wayne-Workman That did the trick. It said something about “file not found” but I know it got its address. I’ll get all the files worked out later. Thank you for your help!!

@Wayne-Workman I’m on build 7581 (downloaded today) my ip addr show output is below.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:38:d4:b1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.1/23 brd 192.168.3.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe38:d4b1/64 scope link 
       valid_lft forever preferred_lft forever

Upon restoring the config to the original file, I’m now able to run sudo service isc-dhcp-server restart successfully. I’m still not able to boot that machine however. No IP was handed out.

Here is my dhcpd.conf file. It’s pretty much the basic configuration as far as I can tell.

#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.
option broadcast-address 192.168.3.255

subnet 192.168.2.0 netmask 255.255.254.0 {
	range 192.168.2.1 192.168.2.254
	range 192.168.3.3 192.168.3.254
}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#    option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#    option routers rtr-29.example.org;
#  }
#  pool {
#    allow members of "foo";
#    range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#    deny members of "foo";
#    range 10.0.29.10 10.0.29.230;
#  }
#}