HP Stream 11 pro

[Sebastian Roth]

@Tom-Elliott said:

I can add in the checks if you want.

That said, I’m kind of scared to enforce write access to this partitions.

While you are at it… See if you can add this as well. I felt kind of the same when first reading about the read only boot partitions. But on the other hand this is kind of like writing the MBR or partition layout. If we do something wrong there things can really go wrong. But we still do because we need to. Same with those boot partitions on mmcblk devices I reckon. We just won’t get around writing to those if we want to properly deploy to those kind of devices.

[Tom Elliott]

fog.download has been rewritten.

I’ve made quite a few adjustments and calculations for this and have tested the resizable download capability.

With this, i believe i fixed upload and download with multipart types (non resize) as well.

This should be the most non-assumptive init yet.

While I’m sure I could post this to the masses, I’d rather those of you with these “weird” hard drives test this and verify if the findings are correct and things are working correctly.

I have performed some decent testing, but I’d rather rely on information straight from those of you who have this issue.

[Tom Elliott]

Probably needed information.

The init’s are currently at:

http://mastacontrola.com/init.xz (64 bit)
http://mastacontrola.com/init_32.xz (32 bit)

You can use these commands:

wget -O /var/www/fog/service/ipxe/init.xz http://mastacontrola.com/init.xz
wget -O /var/www/fog/service/ipxe/init_32.xz http://mastacontrola.com/init_32.xz

I hope for the best of news, but I’m not holding my breath.

While I’m quite impressed with the fog.upload, I still worry how fog.download turned out a little bit.

[Wayne Workman]

@Tom-Elliott So they are not added into trunk yet?

[Tom Elliott]

@Wayne-Workman the scripts are. the inits are not updated with these changes yet.

[drc0nc]

@Tom-Elliott @Wayne-Workman @Sebastian-Roth Here is just a snapshot of a debug capture task. http://i.imgur.com/m2l2Nfo.jpg (sorry but chrome was giving me problems uploading into the forum.)
I will post info once the capture is done and I’m deploying an image.
It’s working so far with the inits I got from Tom.

[Tom Elliott]

@drc0nc Is this good or bad?

[drc0nc]

@Tom-Elliott It pulled an image just fine. When I go to deploy this is what happens http://i.imgur.com/Hbw7LL3.jpg

If i use the

echo 0 > /sys/block/mmcblk0boot0/force_ro
echo 0 > /sys/block/mmcblk0boot1/force_ro

and run a debug deploy this is what happens
http://i.imgur.com/YlxKwGY.jpg

It can capture just fine, deploying is having a problem (looks like a syntax issue?)

[Tom Elliott]

Teamviewer?

[drc0nc]

@Tom-Elliott sure thing

[Tom Elliott]

Remoted in and found a few more deploy bugs, but I think we finally got them worked out.

It appears that the mmcblk#boot# parts are not parts, but disks in their own right.

Because of this, I have removed the read/write code (commented really) and am not iterating through these disks in any manner.

I suppose if you wanted to, you could down the road but I would highly recommend against it.

[Sebastian Roth]

@Tom-Elliott said:

It appears that the mmcblk#boot# parts are not parts, but disks in their own right.

Because of this, I have removed the read/write code (commented really) and am not iterating through these disks in any manner.

Sounds interesting but I don’t really get what you mean by that Tom. Would you mind explaining this a bit more? From what I saw in earlier posts it seamed like mmcblk#boot# partitions where no problem if read only was disabled. But maybe I am wrong?!

[Tom Elliott]

The mmcblk#boot# are the disks, while the mmcblk#boot#p# are the partitions of those disks.

The problem occurs in that these boot volumes are incredibly tiny. However, the mbr that get’s written is not always appropriate for the volume. (Maybe somebody else can take that approach on?)

I ask because the boot partitions on these are not designed to be the same methods as you foresee on a typical volume layout. Perhaps there’s a reason they’re started in Read only to begin with? I’m guessing something along the lines of nand or something in a a similar fashion.

[Sebastian Roth]

Ohh, now I see. Have been sitting on my eye balls I suppose. You are right mmcblk#boot# are disks, not partitions. Started a new discussion on device enumeration here: https://forums.fogproject.org/topic/6372/enumerating-disks-and-partitions

[drc0nc]

@tom-elliott
I’ve updated fog to 5844 (still using Toms’ inits.) the image is setup as windows 8.1 and using option 2 for type (multiple part single disk) and when I created a simple upload task on a new image it’ll pull an image like this:

mmcblk0 will pull a full RAW rip (~39GB)
then it’ll continue using partclone for each “partition” ex: mmcblk0p1
each one being its respective sizes.

I feel that the first step of pulling a raw image is unnecessary. or is there a way i can skip it? I’ll update this as soon as it’s finished pulling the image and I deploy it.

[Tom Elliott]

@drc0nc I have found and fixed this issue on my server. It was related that the getPartitions function was only checking if the device passed ended in a number. While this works for older style disks (/dev/{h,s}d[a-z]), it doesn’t work for disks ending with a number itself. This should now be corrected for.

Please test, if you can, and let me know?

Thank you

[drc0nc]

@Tom-Elliott Ok! I’ll test today and update.
EDIT: It worked, the init skipped the main block and went to the partitions and pulls images just fine.

[drc0nc]

@Sebastian-Roth @tom-elliott New issues with enabling write cache. I can pull images fine still. Just not deploy.

[drc0nc]

@Wayne-Workman @Tom-Elliott @Sebastian-Roth
I’m not sure why but I cant get the debug deploy or capture to load up…
also, still having issues with deploying. I can capture just fine (not debug capture though)

[Tom Elliott]

@drc0nc I’ve marked this thread as solved as we were able to getting his working again. I had some relatively minor things that needed to be corrected and through teamviewer and a little time I figured out what the problem was. Hopefully this means the systems are bootable but I do know the system was taking the image and we already knew the system was able to upload.