How to image to (or from) a machine with an unsupported bios?
Is it possible?
I have a laptop and a desktop (first 2 machines I tried) and both say unsupported bios / error and it reboots when I tried to initiate a pull of an image. They inventoried fine in to the server, but then after I told it to pull an image and rebooted the machine again, it showed that error. I checked the problematic devices list, and in fact both machines are on that list.
Does that mean there is NO option for those machines, or is there some other way I can use fog, for example via a boot disk, or something else?
I’ll bet it’s in GPT as I stated before.
0.32, you said that might be the problem - what version is better (newer or older)?
tried bzImage220.127.116.11.KS and it is not able to mount nfs / network unreachable so likely does not support the nic
also tried bzImage3.8.8core - same errors - unsupported bios, but by the way is also showing no partitions found. I think the stock 0.32 bzImage shows that same message.
so in fact maybe something to do with the disk format or mode?
You don’t need to use a different kernel, as you were able to successfully register the host. The kernel is NOT your issue. If you wish to use a different, please feel free. I’d normally give you my web address to the kernel, but right now my network is down and I’m not at home to fix the problem.
What version of FOG are you using though?
[quote=“Tom Elliott, post: 23664, member: 7271”]The bios error you’re seeing is not the issue. There’s something else causing the issue, and with my recent knowledge of what’s been happening, my guess is you’re using 0.32 and the hdd’s are formatted in GPT format.[/quote]
How do I use a different kernel / what version should I be using? (this is a windows 7 machine I am trying to image)
The bios error you’re seeing is not the issue. There’s something else causing the issue, and with my recent knowledge of what’s been happening, my guess is you’re using 0.32 and the hdd’s are formatted in GPT format.
Try a different kernel, those bios errors don’t mean beans.