Mounting File System Failed
-
@Wayne-Workman Attaches is the last part of another capture. Just like previous, the PXE gets an ip, immediately downloads undionly.kpxe but then
“iPXE initialising devices”
tftp://10.0.0.51/default.ipxe… <<- This is where you see the ARP broadcasts start again.
After several seconds, it gives up and boots the HDD
-
I did another capture/filter with ip.src==10.0.0.51 || ip.dst==10.0.0.51 for curiosity. This capture is from immediatly after the download of undionly.kpxe to when PXE gives up and boots the HDD.
-
@Rusty Packet 328 and 329 in the last capture you posted looks interesting. It happens again at 559 and 560. What name was it trying to resolve?
Looks like it was trying to find a PTR record for 51.0.0.10 ??? Is that right? Can we see more?
-
What is happening at this stage ?
to get undionly.kpxe tftp needs to have worked ? which means the option66/67 is working on the DHCP server
but now it seems to not be working… -
@Wayne-Workman Sure, whats a PTR record?
-
It just worked again, so I uploaded an image. Then it worked a second time.
Now its not working again (trying about 6 times now) -
A PRT record is a reverse lookup for DNS. Basically it asks DNS for this IP address what is its conical host name.
While I haven’t read this entire thread, for DHCP its best for option 66 to be an IP address and not a conical host name. Some PXE clients are just not that smart enough to know how to look up a name for option 66, so set it to the IP address of the FOG server.
Also I know they have been working on the boot image (in the last 3-4 days) where it was getting stuck at the initialing devices. You may want to try to update to the latest SVN. It sounds like you are almost there.
-
@george1421 Thanks.
My DHCP options use the IP of the fog server, so I’m not sure why that is the case then…OK thanks
-
after updating SVN, I re-run the installer ?
Anything need to be backed up/recorded etc ? -
yes after you do the svn up then cd to the bin folder and run setup again.
-
Not to send you down a rabbit hole here, but I take it you don’t have a reverse lookup zone created for your DNS server. Because looking at the capture its looking for the 10.0.0.51 address but the reply from DNS is name not found. Can I guess that 10.0.0.51 is your FOG server? Outside of the scope of this project you should ensure you have a reverse lookup zone created in DNS.
Here is a how to for 2012. http://www.tomshardware.com/faq/id-1954333/create-reverse-primary-dns-zone-windows-server-2012.html
-
@Rusty said:
Anything need to be backed up/recorded etc ?
If it’s virtualized, I recommend taking a snapshot before updating Trunk versions of fog.
If it’s not virtualized (and a production server), do a DB export (FOG Configuration -> Configuration Save -> Export) and a Host export (Host Management -> Export hosts -> Export) at minimum. Append the file names with the SVN version you’re using.
IF you decided to blast away the current build you have and start over, copy your images and grab a copy of /opt/fog because it has your SSL keys in it.
-
@george1421 Ok. So this isn’t contributing to my issues*?
Also excuse my ignorance, why should I add the reverse DNS lookup zone ? (what does it do for me practically?)
Thanks !
*Its possible there is a compatibility issue with the notebook I was using to image. I grabbed another old Dell and it seems to work everytime. I swapped back and Dell1 didnt work with several attempts, back to Dell2 and It is working 100%.
-
@Rusty Trade out patch cables, if you have more than one of these problematic dells I would suggest trying with another just to see what happens.
Are you using a managed switch?
Are DHCP Helper addresses set on the managed switch?
Is portfast enabled on the managed switch?What if you created a reverse lookup zone and it worked more reliably?
A lot of things use PTR records. There’s no conformity. Printers sometimes, computers finding printers, computers with IP printers installed and drivers that want to use the FQDN, some client / server software uses PTR records. the list goes on.
I wouldn’t be surprised at all if the firmware on the device you’re using is trying to querry for the PTR record just to fill some internal system variable (whether it’s used or not).
as @george1421 said, it is good practice to have a reverse lookup zone. More stuff will work and you’ll have less mysteries.
-
@Rusty Some systems will try to do a two way match between conical name->IP address -> conical name. This is a standard function of DNS. I’m kind of surprised that this issue (not having a reverse lookup zone) hasn’t been a problem.
-
Updating to SVN 4367 didn’t help with this Dell Inspiron I have here. The second laptop I have here boots into FOG menu everytime.
-
@Rusty try undionly.
kkpxe -
@Rusty said:
Updating to SVN 4367 didn’t help with this Dell Inspiron I have here. The second laptop I have here boots into FOG menu everytime.
Not to fork this thread, but just so I can get this clear in my head.
You have two computers that are exactly alike. They are the same models, with the same bios release and the same bios settings. But one boots to the fog menu and the other hangs at the init devices?
Have you tried to reset the bios back to defaults on the one that doesn’t work, save and reboot, then make any changes necessary for your image (uefi, legacy, roms, etc.) save then pxe boot. If it still hangs. Power it off, remove the battery and charging cable. Then power everything back up. If it still hangs then I might consider the mobo has issues. There may be a way (kernel parameter) that the developers can set to tell exactly where its hanging.
-
@george1421 No they are not the same, I do have another one the same as the problem one I think, Ill try that when I find it and its available. We have a high mix of different machines here, mostly Dell though.
Actually the first instance of FOG I got going (Thanks @Wayne-Workman ) DID work with this machine, and I never saw an instance of this problem. Not exactly sure what version it was, and I just deleted those VMs this morning
@Wayne-Workman I made the change to undionly.kkpxe still no worky
-
@Rusty said:
Actually the first instance of FOG I got going (Thanks @Wayne-Workman ) DID work with this machine, and I never saw an instance of this problem.
If you can get a date for that, it would help out. We can install that old version and see what happens.
