I constructed an hddimg image (core-image-fullcmdline) and flash it into a USB stick. Then boot a NUC system and chose to install (boot options works fine). Once the installation process starts, 'sda' is type (HD device name) and it hangs there. I can provided more details if necessary. This happened using sumo release. One extra bit is that I included the meta-openembedded/meta-oe layer, and include a single target from it: phoronix-test-suite. I believe the latter is not required to reproduce the issue.
Leo, I tried this but couldn't reproduce. Can you share more details please? When the installer shows: 'Please select an install target or press n to exit ( sda ):' did you type sda and then enter? Does the script hang after that?
(In reply to comment #1) > Leo, I tried this but couldn't reproduce. Can you share more details please? > > When the installer shows: > > 'Please select an install target or press n to exit ( sda ):' > > did you type sda and then enter? > > Does the script hang after that? Right. Actually I am using other non-oe-core layers, but I doubt this can affect the resulting image. Attached are the steps to reproduce it. Just ignore the meta-pnp part (meta-pnp is an layer that we are using to measure performance on a Poky OS, the latter just adds some meta-oe and meta-python packages).
Created attachment 4329 [details] detailed steps
(In reply to comment #2) > (In reply to comment #1) > > Leo, I tried this but couldn't reproduce. Can you share more details please? > > > > When the installer shows: > > > > 'Please select an install target or press n to exit ( sda ):' > > > > did you type sda and then enter? > > > > Does the script hang after that? > > > Right. Actually I am using other non-oe-core layers, but I doubt this can > affect the resulting image. Attached are the steps to reproduce it. Just > ignore the meta-pnp part (meta-pnp is an layer that we are using to measure > performance on a Poky OS, the latter just adds some meta-oe and meta-python > packages). The steps mention that you're using wic create and are using your own wks file and then flashing the wic created image to usb? That image won't have install target. Aren't you using the .hddimg that is created for you when building core-image-pnp with intel-corei7-64 MACHINE name?
(In reply to comment #4) > (In reply to comment #2) > > (In reply to comment #1) > > > Leo, I tried this but couldn't reproduce. Can you share more details please? > > > > > > When the installer shows: > > > > > > 'Please select an install target or press n to exit ( sda ):' > > > > > > did you type sda and then enter? > > > > > > Does the script hang after that? > > > > > > Right. Actually I am using other non-oe-core layers, but I doubt this can > > affect the resulting image. Attached are the steps to reproduce it. Just > > ignore the meta-pnp part (meta-pnp is an layer that we are using to measure > > performance on a Poky OS, the latter just adds some meta-oe and meta-python > > packages). > > The steps mention that you're using wic create and are using your own wks > file and then flashing the wic created image to usb? > Basically I worked around it booting the wic, then dd from stick to hard disk. > That image won't have install target. Aren't you using the .hddimg that is > created for you when building core-image-pnp with intel-corei7-64 MACHINE > name? The problem is with the hddimg, not wic. Once I dd a sick with the hddimg and boot the NUC, choose the installer, shortly after, it will hang.
I noticed that you're setting the rootfs size to exact 4gb. Can you try setting IMAGE_ROOTFS_SIZE to something less than 4 GB? You're probably hitting the FAT 4GB limit. Current code checks if rootfs size is greater than 4 GB and you're right on the edge. You can also check your 'tmp/work/intel_corei7_64-poky-linux/core-image-pnp/1.0-r0/temp/log.do_bootimg' file and see if you are getting this warning: File "rootfs.img" too big.
(In reply to comment #6) > I noticed that you're setting the rootfs size to exact 4gb. > > Can you try setting IMAGE_ROOTFS_SIZE to something less than 4 GB? You're > probably hitting the FAT 4GB limit. > > Current code checks if rootfs size is greater than 4 GB and you're right on > the edge. You can also check your > 'tmp/work/intel_corei7_64-poky-linux/core-image-pnp/1.0-r0/temp/log. > do_bootimg' file and see if you are getting this warning: > > File "rootfs.img" too big. I am not getting that error. the 4GB value is on the standard documentation (mega manual, IMAGE_ROOTFS_SIZE) is documented. There is something strange here: The only partition size that must be "small" is the boot partition, but for the main rootfs, which is ext4, does not have to be this way, right? Anuj, I do not have much time right not to reduce size & flash & install. Can you try for me?
(In reply to comment #7) > (In reply to comment #6) > > I noticed that you're setting the rootfs size to exact 4gb. > > > > Can you try setting IMAGE_ROOTFS_SIZE to something less than 4 GB? You're > > probably hitting the FAT 4GB limit. > > > > Current code checks if rootfs size is greater than 4 GB and you're right on > > the edge. You can also check your > > 'tmp/work/intel_corei7_64-poky-linux/core-image-pnp/1.0-r0/temp/log. > > do_bootimg' file and see if you are getting this warning: > > > > File "rootfs.img" too big. > > I am not getting that error. > > the 4GB value is on the standard documentation (mega manual, > IMAGE_ROOTFS_SIZE) is documented. It is, but the document should probably less than 4GB. > > There is something strange here: The only partition size that must be > "small" is the boot partition, but for the main rootfs, which is ext4, does > not have to be this way, right? No, hddimg is a fat fs. Individual files inside it should be less than 4 GB. > > Anuj, I do not have much time right not to reduce size & flash & install. > Can you try for me? I did and that's when I saw the error.
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > I noticed that you're setting the rootfs size to exact 4gb. > > > > > > Can you try setting IMAGE_ROOTFS_SIZE to something less than 4 GB? You're > > > probably hitting the FAT 4GB limit. > > > > > > Current code checks if rootfs size is greater than 4 GB and you're right on > > > the edge. You can also check your > > > 'tmp/work/intel_corei7_64-poky-linux/core-image-pnp/1.0-r0/temp/log. > > > do_bootimg' file and see if you are getting this warning: > > > > > > File "rootfs.img" too big. > > > > I am not getting that error. > > > > the 4GB value is on the standard documentation (mega manual, > > IMAGE_ROOTFS_SIZE) is documented. > > It is, but the document should probably less than 4GB. > > > > > There is something strange here: The only partition size that must be > > "small" is the boot partition, but for the main rootfs, which is ext4, does > > not have to be this way, right? > > No, hddimg is a fat fs. Individual files inside it should be less than 4 GB. > > > > > Anuj, I do not have much time right not to reduce size & flash & install. > > Can you try for me? > > I did and that's when I saw the error. I was not clear. Did you try to installer from the hddmi file? also, make sure you are in sumo branches.
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > I noticed that you're setting the rootfs size to exact 4gb. > > > > > > > > Can you try setting IMAGE_ROOTFS_SIZE to something less than 4 GB? You're > > > > probably hitting the FAT 4GB limit. > > > > > > > > Current code checks if rootfs size is greater than 4 GB and you're right on > > > > the edge. You can also check your > > > > 'tmp/work/intel_corei7_64-poky-linux/core-image-pnp/1.0-r0/temp/log. > > > > do_bootimg' file and see if you are getting this warning: > > > > > > > > File "rootfs.img" too big. > > > > > > I am not getting that error. > > > > > > the 4GB value is on the standard documentation (mega manual, > > > IMAGE_ROOTFS_SIZE) is documented. > > > > It is, but the document should probably less than 4GB. > > > > > > > > There is something strange here: The only partition size that must be > > > "small" is the boot partition, but for the main rootfs, which is ext4, does > > > not have to be this way, right? > > > > No, hddimg is a fat fs. Individual files inside it should be less than 4 GB. > > > > > > > > Anuj, I do not have much time right not to reduce size & flash & install. > > > Can you try for me? > > > > I did and that's when I saw the error. > > I was not clear. > typo, sorry: Did you try the installer from the hddmi? That is the one that hangs.
> I was not clear. > > Did you try to installer from the hddmi file? > > also, make sure you are in sumo branches. I followed the exact steps listed and installed to SSD using the bootloader 'install' option that I got after booting up the hddimg image flashed to a usb. I get errors while installing (or even booting) core-image-pnp hddimg with poky-kpi layer because the image wasn't generated correctly (because of the error I mentioned in my last comment). I don't get any error (while installing or generating image) if I remove poky-kpi layer and generate/flash/install core-image-full-cmdline image. I also don't get any error if I reduce the rootfs size in core-image-pnp.bb and then generate image and flash and install. At this point, I'd request you to try to get the logs next time you see an error or if you get time, please try out core-image-full-cmdline image without the rootfs_size specified. You can pass the parameter 'init_fatal_sh' to kernel boot line to drop to a shell in case something is failing while live booting before install script is invoked. Also, listing contents of hddimg would be helpful: $ wic ls tmp/deploy/images/intel-corei7-64/core-image-pnp-intel-corei7-64.hddimg:1
Thanks Anuj, for your investigation. So I hit an error following the docs, which this is not good. I will send a patch correcting this (<4GB). I will come back to this next week and update bug asap.
Merged: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ebbd1e4a94c675c1669860d7cd554d18f010e5b5