@Tom-Elliott said in Ubuntu is FOG's enemy:
apt-get -y remove unattended-upgrades
This saved my bacon, thank you very much, first command failed but second one worked, i have also run the unattended-upgrades command, once again thank you.
@george1421 After having a chat session with @jeremyvdv which we had to cut short I discovered somethings.
I asked him to post the output of the kernel parameters from a debug session.
loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.16.3.129/fog/ consoleblank=0 rootfstype=ext4 mac=00:00:00:00:00:00 ftp=10.1.5.8 storage=10.1.5.8:/volume1/images2/dev/ storageip=10.1.5.8 osid=5 irqpoll hostname=LP0045 chkdsk=0 img=test10 imgType=n imgPartitionType=all imgid=5 imgFormat=5 PIGZ_COMP=-10 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up
Where we can see the storage path for NFS is 10.1.5.8:/volume1/images2/dev but looking on the nas via FTP there is no reference to /volume1/images2 its just /images2, yet there is data in /images2/dev/<mac_address> directory. So NFS is working and FTP is not.
If we looked at what he posted as a screen shot of the nas storage node
We can see that he is clearly calling out /volume1/images2
When he connected via ftp to the nas the path was /images2/dev/<mac_address> like we see from the top picture here.
So what I’m thinking is that we leave storage path at /volume1/images2 and set the FTP path to /images2 then it should work. I think NFS is looking at it form the filesystem view where ftp is looking at the path from a logical view. They technically point to the same location, just how they get there is via two different paths.
@mikmatcr Just to be clear you want to store to both disks in your fog server or do you just want to add to your usable total space?
One method is to add an additional “fake” storage node configuration to your fog server it will need to be in a different storage group. When you create your image definitoin you would pick storage node 1 on disk 1 or storage node 2 on disk 2.
Another method is if your fog server host OS uses LVM (logical volume manager). What you would do is just add the new disk to the LVM pool and the OS will just magically use the additional space.
The third option is if you wanted to abandon the space on the original hard drive and then use only the new hard drive for image storage.
I do have some tutorials that are a few years old on how to do this. The decision on the path depends on how you want to use the space. I can tell you if you can add the space on the file system level that keeps the fog configuration clean and sane.