Pnp 00:06: Can't evaulate _CRS: 1
-
First, Packard Bell is now back in business?
Second, The php 00:06 Can’t evaluate _CRS: 1 sounds like it’s a driver issue in the kernel, not that the error really means anything from FOG’s standpoint.
FOG uploaded the image, and deployed it right?
The question I have, what are the settings for this image? (Multi Part, Resizable, etc…)
For your particular use case, it sounds to me like Multipart - Single disk is the way you want to go.
The tftpd-hpa/tftp-hpa issue is rather known about. You can setup so you don’t have to restart, there’s a ton of posts on the forums here on how to do that.
-
[quote=“Tom Elliott, post: 37875, member: 7271”]First, Packard Bell is now back in business?
Second, The php 00:06 Can’t evaluate _CRS: 1 sounds like it’s a driver issue in the kernel, not that the error really means anything from FOG’s standpoint.
FOG uploaded the image, and deployed it right?
The question I have, what are the settings for this image? (Multi Part, Resizable, etc…)
For your particular use case, it sounds to me like Multipart - Single disk is the way you want to go.
The tftpd-hpa/tftp-hpa issue is rather known about. You can setup so you don’t have to restart, there’s a ton of posts on the forums here on how to do that.[/quote]
Hi Tom,
Thank you for the quick reply.
I am in South Africa. Acer is distributing Packard Bell.
Fog did upload the image and deployed it succesfully. Note that I uploaded the image from one laptop and downloaded it to a second laptop. Same make, same config, etc.
Also to confirm :
Operating System : Windows 8.1
Image type :Multiple Partition Image - Single Disk (Not Resizable) -
Some more info :
There are 5 partitions on the disk. Have no idea why but it is clearly how Windows distribute it.
-
This sounds, to me, like the disks are setup in GPT.
To verify, can you take a look at the size of the d1.mbr file created?
[code]cd /images/<imagename>
ls -lart d1.mbr[/code] -
Here is the files :
-rwxrwxrwx 1 root root 243250350 Oct 14 16:17 d1p1.img
-rwxrwxrwx 1 root root 24911777 Oct 14 16:17 d1p2.img
-rwxrwxrwx 1 root root 53511435 Oct 14 16:18 d1p3.img
-rwxrwxrwx 1 root root 13969164726 Oct 14 17:34 d1p4.img
-rwxrwxrwx 1 root root 13904164021 Oct 14 18:02 d1p5.img -
Apologies :
-rwxrwxrwx 1 root root 17920 Oct 14 16:16 d1.mbr -
So my suspicions are correct. Your disk is layed out in GPT.
When you re-deploy nothings working right?
-
Correct.
When you reboot the latop after you activated the task, it comes up with the above error message but carries on with the deployment of all the partitions succesfully.
When you then restart the latop, you get a message that it cannot boot and that there is a device missing.
-
Can you disable Secure Boot on the systems?
The proper way to image these things is to:
(Upload Tasks)
- Disable Secure Boot
- Upload the image
- Re-enable Secure boot
- Boot the system
(Download Tasks)
- Disable Secure Boot
- Download the image
- Re-enable Secure boot
- Boot the system
-
There are two Boot Modes : UEFI and Legacy.
Secure Boot [Enabled] appear under that menu but you cannot change it. Let me look around and see if I can find a way to disable it. -
I cannot seem to find a way to disable secure boot.
One other thing, I changed the boot mode to legacy when I uploaded the image.
I also changed the boot priority order. I moved “Windows Boot Manager” down and moved network boot up.
I wonder if that could have caused the problem ?
Would it make a difference if I choose UEFI and leave the boot manager as the main option ? I missed the fact that network boot was disabled, so the only way I could get it to enable PXE boot was to use legace boot mode.
-
I cannot get IPXE to boot with UEFI. It gives the error in the pic. Under Legacy, if I press enter once or twice, it comes up with the FOG menu.
Under UEFI it comes up with the IPXE menu but goes straight into windows after the error.
[url=“/_imported_xf_attachments/1/1435_IMG_3339.JPG?:”]IMG_3339.JPG[/url]
-
if your systems have a legacy boot option, use it. configure your windows to work under that mode. it will save you many headaches
-
Thank you. Will have a go and let you know.
-
Some more questions :
When I use the recovery disk and I look at the size of the partitions, the primary partion 0 is 449 GB when I do a list volume with Diskpart. However, during the deployment of that partition from FOG, which is indicated as /dev/sda4, the Device size is indicated as 482.2 GB.Furthermore, the recovery fails on both the recovery disks I made on the two separate Laptops. So not sure if we have a disc failure. It resets until about 78% and then just stops saying there was an error. On both repartition and just restore files.
