Can backup, but not deploy on 1 machine.... [video inc].
-
update : Just swapped the harddrive of the trouble laptop with another one, and the good laptop deployed a treat, the trouble one froze at same place.
I’ve just gone through the bios to ensure that both are identical and still can’t figure it out. :S
-
bump
-
Ok, I didn’t forget about you. Hopefully others can respond with better options, but I want to get everything straight in my head. You have multiple laptops of the same make and model. All of them will image just fine except for one. When you swap the hard drive from the one that will not image to one that will image, the laptop that has no problem still has no problem, but the one with a problem fails even with the other hard drive. All of the bios settings are the same on all laptops. The bad laptop is getting to fog, reading out a report about the bios and all, but then freezes? I know this is redundant, but I don’t want you to think we are giving up on this, I just hate having little issues like this that seem to never go away.
-
It’s all good jason. Thanks for the reply.
but yeah. what you wrote is completely correct.
Also, I might add that all laptops can upload. Even the ‘bad’ one. It will upload an image just fine. it just can’t deploy anything.
-
Alright so Bios update did nothing, but a kernel change made the error message change. I am doing something new which is using the tutorial to build a custom kernel. I’ll test it beforehand, but if it works for me on my troublesome Dells and Toshibas then I’ll let you have it. Maybe it’ll work for you, idk though. I’ll keep you posted, it’s compiling right now.
-
Is there anything plugged into the usb ports or flash card in the laptop? I keep seeing that this error is generally another media device that is not able to be cached.
-
ok two things;
first - no. no usb in laptop.
second - on closer inspection two laptops (1xworking and 1xshitty) have different harddrive hardware ids. I don’t know if that makes a difference. I assume not as two working laptops also have different id’s - AND - i swapped harddrives between laptops.everything else, settings and hardware wise, is the same.
Still scratching my head over this one.
-
for the record, this was never solved/fixed.
I’ve literally no idea wtf is wrong with this unit. After tax time, I’ll just buy some new laptops and use this line as ‘backup’.
-
Just revisited this - I set up a brand new ubuntu desktop and installed nothing but Fog on it - I reformatted the problem laptop and did nothing but put 1 txt document on desktop. I also reset the toshiba bios.
To check fog was working, I took a working laptop and did a quick host, an upload, and a deploy all successfully.
I then took the problem laptop, managed to get the PXE to boot to fog menu, did a ‘quick host’ first time, completed an upload (to a new image file) first time also, went to deploy it - and it got stuck at the same place as the video. Just dispays a ‘#’ when it should go to the blue screen.
I’m about to throw it all out the window.
-
[quote=“Blackbook, post: 14121, member: 2681”]Just revisited this - I set up a brand new ubuntu desktop and installed nothing but Fog on it - I reformatted the problem laptop and did nothing but put 1 txt document on desktop. I also reset the toshiba bios.
To check fog was working, I took a working laptop and did a quick host, an upload, and a deploy all successfully.
I then took the problem laptop, managed to get the PXE to boot to fog menu, did a ‘quick host’ first time, completed an upload (to a new image file) first time also, went to deploy it - and it got stuck at the same place as the video. Just dispays a ‘#’ when it should go to the blue screen.
I’m about to throw it all out the window.[/quote]
we had a problem child machine we just chose an older kernel for fog and magicly it worked… Our problem child was a Brand New Dell Vostro 2420 brand new out of box one Deployed fine the other we had to change to an older kernel to get to it deploy… Same Bios versions and Ethernet Firmware versions. Identical hardware. Go figure. we stepped back all the way to the 2637 kernel. Hope that helps?