I’ve been following the thread over here https://forums.fogproject.org/topic/7851/intel-raid0-image-capture in order to figure out how to image some hardware that I have that uses the “fake” Intel RAID. We specifically use RAID 1 on these machines. Well I found what I needed and I set the image to Single Disk Resizable and set the Host Kernal Arguments to mdraid=true and the Host Primary Disk to /dev/md126. I kick off the capture task, but then I get the error below. *Mounting partition (/dev/md126p1)...Failed *Could not mount /dev/md126p1 (removePageFile) Args Passed: /dev/md126p1 Reason: ntfs-3g-mount: mount failed: Permission denied Weird that I’m getting permission denied because if I get rid of the mdraid=true and /dev/md126 and just capture the image like a regular non-RAID machine it captures with no issue. Why would these arguments spit out a permissions error?

@Zerpie @george1421 Build is done. Please find new test binaries here 64 bit and 32 bit . Download and put in /var/www/fog/service/ipxe on your FOG server. Rename to match the original names - do not overwrite but also rename the original init’s I would say just in case. Please test and let us know. Caputre, deploy… working?

@Zerpie I am still trying to get my head around this so please bear with me. So in resizable capture you get the “mount failed: Permission denied”. What FOG is trying to do at this stage is mount the partition and remove the hibernation file as preparation for the partition to be resized before capture. Denied could either mean FOG is not able to properly access the partition on the RAID array. This I think would be a bit strange because it is able to read the partition table and find the first partition. The other thing I can think of is that the partition is somehow “locked”. Could be the partition is bitlocked [ ref ] or Win 10 fastboot is on or the NTFS filesystem is somehow not clean [ ref ] Either way, you can disable removing hibernation file under FOG Configuration -> FOG Settings -> General Settings -> CAPTUREIGNOREPAGEHIBER (uncheck this). Let’s see how far you can get with this. On debug deploy (non-resizable this time) we see that FOG was not able to put the partition layout on disk and therefore is not able to proceed. I am still not sure why this is happening. Do you capture and deploy to the very same machine or is it going to another one with slightly smaller disks (maybe only a few sectors if they are a different model).

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Permission denied when trying to capture Intel RAID1 image

Solved

FOG Problems

5.9k

S

Sebastian Roth Moderator
last edited by
@Robert-H As we have the mdmon included in the official inits I deleted the special ones now. Find the official inits here:
```
https://fogproject.org/inits/init.xz
https://fogproject.org/inits/init_32.xz
```
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
1 Reply Last reply
Reply Quote 0

242

Online

11.6k

Users

17.1k

Topics

154.6k

Posts