HP Stream 11 pro
-
@Tom-Elliott @Wayne-Workman @Sebastian-Roth
Hey guys. Sorry to bug but as I continue to tackle these HP streams I ran into another problem that popped up. The specs are the same, I’m still running
svn 5293
(had to reinstall fog because i had a HHD totally fail)
same boot ipxe.efi
same kernel 4.2.3
same kernel arg and host disk.
I can pull images just fine using undionly.kkpxe on my lenovosyet the streams just wont pull an image (sorry for potato quality)
-
For some reason when I changed the image to a RAW image (4) it decided to pull it.
I’ve tried option (2) and (3) and it didn’t work.
In the past I had it set up to use Multiple Partition Image Single Disk-(2) yet its crapping out on me using that option.
I guess maybe some clarification is all I’m asking for at this point. -
Is it just this one or are others doing it too?
-
@Wayne-Workman Haven’t tried other ones yet. The way I have the HP’s working is that they use the MAC of the usb adapters. Unfortunately I only have 4 adapters soo they are just simple hosts with the valid arguments and such. When this image is done being pulled I’ll try to use option (2) on it and see what happens. I can try another adapter on a different HP or the same, doesn’t matter.
BTW I want to upgrade trunk but i’m afraid that I’ll lose functionality for the HP’s.
In the other school building I keep trunk updated and it runs awesome! but at this particular building I’m keeping fog where it is for the HP’s. at the other school building I don’t need it for the HP’s. -
@drc0nc I’m not asking you to update. it’s fine to leave it as is. I was asking you try with a different HP to see whether or not it’s an issue with that specific HP or some larger issue.
-
@Wayne-Workman lol i didn’t mean it like that.
I’ve just tried 2 other HP’s and different adapters. Same deal… If i do RAW then it’ll work to capture and deploy. Otherwise it’ll give me theThe protective MBR's 0xEE partition is oversized! Auto-repairing.
then proceed to reboot. -
@drc0nc What are you using for DHCP in that building you’re in?
-
@Wayne-Workman a windows server 2012 r2. options 66 and 67 are set to the appropriate ip and option 67 is ipxe.efi on global and scope options.
-
@drc0nc Please boot into debug mode on this client and run
fogpartinfo --list-parts /dev/sda
This is what FOG did (in the older versions, Tom changed that in the last week) to get the partitions. I guess this will fail. Please let us know which error you see.
-
@Sebastian-Roth the output was
/dev/mmcblk0 179:0 /dev/mmcblk0boot0 179:8 /dev/mmcblk0boot1 179:16 /dev/mmcblk0p1 179:1 /dev/mmcblk0p2 179:2 /dev/mmcblk0p3 179:3 /dev/mmcblk0p4 179:4 /dev/mmcblk0rpmb 179:24
-
@drc0nc Sorry, updated my last post as I remembered that Tom changed this not long ago. Please try
fogpartinfo --list-parts /dev/sda
and see if you get any errors. -
@Sebastian-Roth fogpartinfo isn’t a valid command
-
@drc0nc I was going to suggest creating a DHCP Reservation for one of the adapters, and point it’s option 066 (for the reservation only) to the FOG server in the other building that is running FOG Trunk.
See what luck you have…
That’ll cause it to use that fog server.
-
@Wayne-Workman I’ll be heading over to one of the other schools today. I’ll bring a couple HP’s and try it from there and see if an updated trunk will let me boot. I’m just curious as to why I can’t image using anything other than RAW when it was letting me before. (on the HP’s)
-
@drc0nc Well if you’re using 1.2.0 stable - it’s not changed. Something else must have changed.
-
@Wayne-Workman I’m running version 5293 currently
-
@drc0nc said:
BTW I want to upgrade trunk but i’m afraid that I’ll lose functionality for the HP’s.
Oh. I interpreted that line as if you were on 1.2.0.
-
@Wayne-Workman lol no sorry. I meant update the revision. I know that 5293 was a working release with the streams so I only installed that one again
-
@drc0nc Hey man, sorry again. I am getting a little confused here. Clearly you are using a newer kernel (bzImage/init.xz) than rev5293 as fogpartinfo is not included anymore. This is not a problem! Just means that the output of lsblk is relavant.
@Tom-Elliott Changing from fogpartinfo to lsblk - have you tried special things like
mmcblk
yet? Fram what I can see in the code the major ID 179 is not being taken care of. Could you update the script? -
@Sebastian-Roth I guess, sorry. I know my bzImage and bzImage32 file versions are 4.2.3 (that’s what allowed me to get these babies going.)