@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)??

I’m wondering now if the database backup failure was caused by the bloating of the history table like I experienced on another server? hmm …

Too bad I didn’t check for that.

@FiskTechLV What exactly is the PXE rom reporting as an error code? It should be a EXX-XXXX like error code.

The next step is going to be a little involved, but it will give us a better idea of what is going on in your network. As long as the fog server and target computer are on the same subnet you can run this command from the fog server. Make sure tcpdump is installed on your fog server then run this command.

tcpdump -w /tmp/bootup.pcap port 67 or port 68 or port 69

Then pxe boot that target computer until you get the pxe boot failure. Once you reach the error then stop tcpdump and post the pcap file here. I might also suggest if you have some networking skills, load the pcap file into wireshark and see if you can spot the error. But also post the pcap here.

You betcha. thx again!

@Sebastian-Roth Oh, I’m silly. You are correct. That page returns:

{"dev":"unknown","rx":0,"tx":0}

I can confirm that the interface is set correct in storage nodes for this server, if that’s related.

@Tom-Elliott Thank you… that’s good to know!

Good catch man! Marking this solved.

I was able to help via Team Viewer.

The FOG server’s IP address changed. The server is probably set to receive DHCP and maybe the reservation was deleted or something - not sure. It had a very weird IP, not one you’d normally set as static or as a reservation.

Also - Connie has fog 0.29 installed on Ubuntu 10.04

The root partition has around 30-40GB of free space now - but it will surely run out of space again.

Images and DB need backed up, and a new server needs built, honestly.

@ITCC upgrading FOG will maintain its identity, so long as you don’t use --recreate-CA

@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)???

@Wayne-Workman
Ok…I,ll try to update my server. Thanks for your time and your answers.

I appreciate!!

Yes, when I installed FOG, I clicked Y for the, “Would you like to use the FOG server for dhcp service? [Y/n]” option.

Most likely these are partially (or fully captured that were unable to move) capture images hanging out in /images/dev

Thank you very much! I got it!

Thanks for all the suggestions, we tried all the mount scenarios, its like Tom said you cannot NFS share an NFS/CIFS share.

It would be awesome if Wayne’s idea can be implemented in Fog so everything can be stored on the NAS, so the virtual Fog server disk space will be as small as possible.

We think the whole community will be very happy with it… at least we will be 🙂

Peter

Cheers Wayne, you live and learn.

That sorted the issue. Please mark this as resolved.

Regards. Kiweegie.

@MacGeek83 The images are not gone, just the image definitions are - because you deleted the node, which contains all the image definitions. You can recreate these manually if you like.

@Tom-Elliott That worked! I believe the issue lies in the fact that we have some customizations in the bootmenu.class.php file. When I removed those directories and reran the installer, I didn’t copy that file over and everything worked like a charm.

I’ll be copying our custom file over, and trying it again and if it breaks, I will know for certain the issue lies there. I can then compare the two and make changes to the new file being pulled down by the installer.

Thanks for your fast help!

Confirmed fixed (again) in r7174. 🙂

@Tom-Elliott I don’t think it’s a mysql error but a php error, php for centos tends to be a little tricky and some things are missing on the redhat builds, the apache logs point out that same php error, maybe we could try an alternative for mysqli->query