Topics created by lawrence1997

In the reports section there is an imaging log. Go to report management and on left side column there is Imaging Log. It should show all the relevant data and you can even export it to csv or pdf.

It’s possible you need a current version. I am running Fog 1.4.0.

Jason

@Tom-Elliott

Hi Tom

Running the installation again with sudo-i worked

Thanks for your help

Kind Regards

Lawrence

@lawrence1997 I know. Did you read what I wrote?

@lawrence1997 On this model, have you run through the FOG compatibility tests from the iPXE menu?

@lawrence1997 Getting errors is not helpful to anyone. What kind of errors are you getting?

I’m seeing, now, that something recently changed on ondrej repository again :(.

George is right. The devs have made strides in supporting upgraded systems where all sorts of things are off/wonky due to migration not being perfect. That said, most people fail at this process because it’s perhaps beyond their skill level to fix, and when they ask for help on the forums, we have to start from zero with troubleshooting because it could be anything if it’s not obvious, and there have been a lot that haven’t been obvious fixes. I’d always recommend a clean build as George said.

@Wayne-Workman It had nothing to do with PHP. It had to do with the FOG Services not being properly picked up. PHP code had nothing to do with any of these problems. (Not saying there wasn’t a coding problem, just want people to more properly know what/where a problem is.)

The php not installing proper wasn’t something I’ve been able to replicate. But after this, a fresh install didn’t start the proper portions of the services which has been addressed.

Try different hdd exit types. Look up the host in Host Management, and on it’s general page you’ll see two drop downs towards the bottom for hdd exit types, one is BIOS the other is UEFI. so the mode that the computer is operating in determines which of these settings will apply. I would first recommend trying Grub, then if that doesn’t work just try one at a time - do a full reboot between each try.

@Tom-Elliott All fixed and working thanks all can be marked as solved!

@george1421 So sorry for the late reply (2 months even) but this sorted my issue out

Thanks

@lawrence1997 said in A Disk Read Error Occured after imaging:

A Disk Read Error Occurred

Are you able to fix this by using fixboot/fixmbr tools from a windows boot CD (http://answers.microsoft.com/en-us/windows/forum/all/a-disk-read-error-occurred-press-ctrlaltdel-to/adc36c93-1aed-487e-8511-5246417e4f0e)??

@lawrence1997 What is the exact error you see? As Wayne said, please post a picture!

As well the partition layout would be very helpful! See if you have d1.partitions for that machine in your /images directory (or possibly /images/dev - if the upload did not finish). Good question coming up. Does this error occur on capture (upload) or deploy (download)???

@Tom-Elliott

Cheers Tom it worked!