Unable to use an NFS share to store images

[vpt]

@george1421 Thanks for that trick. It looks like it is failing on the “Preparing backup location” tasks. On your recommendation, I hit Ctrl+C to abort, I went to the /images directory in FOS Linux, and I attempted to mkdir test. It told me that it couldn’t create the directory and that it was a read-only file system.

Does this mean that FOS can’t write to the directory on the QNAP?

[george1421]

@vpt Yes, you don’t have the permissions set right, either you shared the nfs share as read-only or its the file level permissions on that directory on the qnap that blocking the write. So once you get the permissions right then you should be able to create that directory.

[george1421]

I realize that you are using a qnap, but here is the tutorial for the synology NAS devices: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node You should review the permissions for the directories.

And I’m sure you seen this qnap tutorial: https://forums.fogproject.org/topic/10973/add-a-nas-qnap-ts-231-as-a-storage-node-fog-v1-4 the same rules apply for 1.5.x as 1.4.x

[vpt]

@george1421 Thanks for these guides. I’m going through the QNAP one step-by-step, and I’m just waiting for the advanced folder permissions to apply. Based on how quickly it’s going, it probably won’t finish today, but I will follow up with my results once it finishes.

I appreciate everyone sticking with this and helping out.

[vpt]

@george1421 I was able to complete your QNAP guide finally (been out sick the last few days), and I get a bit further in the process now. However, I still get an error when I get to the Partclone part of the process. See this image for the error in Partclone:
https://meridiannatl-my.sharepoint.com/:i:/g/personal/mzarvalas_vptitle_net/ERHZpkPVz7NAtaerPQsvHNAB0qBUmJMNskhfgvGlTrcpGw?e=Nx1shP

And see this message for the error afterwards back in FOS Linux:
https://meridiannatl-my.sharepoint.com/:i:/g/personal/mzarvalas_vptitle_net/EdicD0QitxBDsyIuY3JemsoB0XlA97xNczYbRhv_o5rDFw?e=7MQ0AU

I tried researching the error in partclone, and I attempted to run ntfsfix against both sda1 and 2, but not luck. I also tried capturing an unsysprepped image with shutting down Windows using the “shutdown /s” option to avoid the Fast Startup issues with windows, but my results were unchanged.

The second error back in FOS Linux seems to indicate that there isn’t enough space to capture an image, but if FOS is using the NAS share as it seems to be indicating in the error message, there should be more then enough space.

Let me know if you have any further troubleshooting advice to try. Thanks a bunch for you help so far.

[george1421]

@vpt That first error is saying that windows was probably shutdown incorrectly for image cloning. This happens when someone just uses the shutdown start menu button. With fast boot enabled in windows, shutdown is really an enhanced sleep state. Its really not “shutdown” what we would think it is.

So what can you do?
Shutdown the windows computer properly for cloning by:

1. If you use sysprep add the /shutdown switch to properly power off the computer for image cloning.
2. If you don’t use sysprep then key in shutdown.exe -s -t 0 from a command window.

To understand what is happening here you can google “windows dirty bit”.

[vpt]

@george1421 I have tried both shutting down the system using shutdown.exe -s -t 0 as well as sysprep with the /shutdown switch. I’ve also tried hitting Shift + F10 when it boots to the setup screen of the sysprepped image to launch the command prompt and shutdown from there. I still got the same error.

I also tried running through this guide:
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

I completed all three steps in that guide and I still get the same error in partclone

[george1421]

@vpt So did you boot the image you are trying to capture and run check disk “chkdsk /f”? There is something wrong with the structure of that disk you are trying to capture.

[vpt]

@george1421 I did not let the full chkdsk complete. I tried method 3 in that guide which says to try to capture the image as soon as chkdsk reboots the system. I will try to let chkdsk run through to completion and see if that works

[vpt]

@george1421 I ran a full chkdsk on that machine, and I still received the same error.

To see if the issue was isolated to that machine I grabbed another one, inventoried it, and ran a capture task without issue. I think we can safely call this issue solved at this point.

To all interested, Following the below guide solved my initial NFS issue with my QNAP:
https://forums.fogproject.org/topic/10973/add-a-nas-qnap-ts-231-as-a-storage-node-fog-v1-4

Thanks to everyone for their help with this project!