* Atom-pc, usb installation - NO BOOTABLE DEVICE
@ 2015-01-09 9:31 Simon Bolek
2015-01-09 9:38 ` ChenQi
2015-01-09 20:52 ` Chris Tapp
0 siblings, 2 replies; 4+ messages in thread
From: Simon Bolek @ 2015-01-09 9:31 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
Hi,
The following is the case:
1) atom-pc with ssd 80 GB hard drive(the only one, no optical, no usb,
etc.) as a target device
2) core-image-sato bitbaked and moved to usb device successfully
3) usb 'install' to atom-pc successfull (so the install script says)
4) after removing the usb device, pressing enter the boot says NO BOOTABLE
DEVICE
WHY?
At the same time, ISO image (generated at the same bitbake run) is working
in virtual box like a charm. 'Install' was successfull and booting fine - i
get GRUB menu with one 'Linux' entry as expected.
On the Atom-pc this is not working. So something has to be missing. Maybe
you will have a clue.
Here are the details:
The SSD HDD is /dev/sda with the partition table:
/dev/sda1 - boot
/dev/sda2 - rootfs
/dev/sda3 - swap
there is no asterix at boot partition
under /dev/sda1/grub there is grub.cfg with:
menuentry "Linux" {
set root=(hd0,1)
linux /vmlinux root=/dev/sda2 rw
}
- so first HDD, first/boot partition
- it points to /vmlinuz and /dev/sda2
It looks fine for me.
I already tried to dd if=/dev/zero of=/dev/sda bs=4M, and 'install' from
usb again, but no luck.
I already tried to put asterix on the boot partition, but than BOOT gets me
to *grub rescue>*
If you have any ideas, where to look for, please let me know.
thank you and best regards
simon :-)
[-- Attachment #2: Type: text/html, Size: 1821 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Atom-pc, usb installation - NO BOOTABLE DEVICE 2015-01-09 9:31 Atom-pc, usb installation - NO BOOTABLE DEVICE Simon Bolek @ 2015-01-09 9:38 ` ChenQi 2015-01-09 20:52 ` Chris Tapp 1 sibling, 0 replies; 4+ messages in thread From: ChenQi @ 2015-01-09 9:38 UTC (permalink / raw) To: yocto [-- Attachment #1: Type: text/plain, Size: 1738 bytes --] On 01/09/2015 05:31 PM, Simon Bolek wrote: > Hi, > > The following is the case: > 1) atom-pc with ssd 80 GB hard drive(the only one, no optical, no usb, > etc.) as a target device > 2) core-image-sato bitbaked and moved to usb device successfully > 3) usb 'install' to atom-pc successfull (so the install script says) > 4) after removing the usb device, pressing enter the boot says NO > BOOTABLE DEVICE > > WHY? > The minimal installer in OE has the problem of hardcoding disk names in grub configuration file instead of using UUID. So it's possible that you may experience boot failures due to the change of disk names. //Chen Qi > At the same time, ISO image (generated at the same bitbake run) is > working in virtual box like a charm. 'Install' was successfull and > booting fine - i get GRUB menu with one 'Linux' entry as expected. > > On the Atom-pc this is not working. So something has to be missing. > Maybe you will have a clue. > Here are the details: > The SSD HDD is /dev/sda with the partition table: > /dev/sda1 - boot > /dev/sda2 - rootfs > /dev/sda3 - swap > there is no asterix at boot partition > > under /dev/sda1/grub there is grub.cfg with: > menuentry "Linux" { > set root=(hd0,1) > linux /vmlinux root=/dev/sda2 rw > } > - so first HDD, first/boot partition > - it points to /vmlinuz and /dev/sda2 > It looks fine for me. > I already tried to dd if=/dev/zero of=/dev/sda bs=4M, and 'install' > from usb again, but no luck. > I already tried to put asterix on the boot partition, but than BOOT > gets me to /grub rescue>/ > > If you have any ideas, where to look for, please let me know. > > thank you and best regards > simon :-) > > [-- Attachment #2: Type: text/html, Size: 3580 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Atom-pc, usb installation - NO BOOTABLE DEVICE 2015-01-09 9:31 Atom-pc, usb installation - NO BOOTABLE DEVICE Simon Bolek 2015-01-09 9:38 ` ChenQi @ 2015-01-09 20:52 ` Chris Tapp 2015-01-11 9:38 ` Simon Bolek 1 sibling, 1 reply; 4+ messages in thread From: Chris Tapp @ 2015-01-09 20:52 UTC (permalink / raw) To: Simon Bolek; +Cc: yocto [-- Attachment #1: Type: text/plain, Size: 2087 bytes --] On 9 Jan 2015, at 09:31, Simon Bolek <simon.bolek@googlemail.com> wrote: > Hi, > > The following is the case: > 1) atom-pc with ssd 80 GB hard drive(the only one, no optical, no usb, etc.) as a target device > 2) core-image-sato bitbaked and moved to usb device successfully > 3) usb 'install' to atom-pc successfull (so the install script says) > 4) after removing the usb device, pressing enter the boot says NO BOOTABLE DEVICE I've seen this is the past with an eSata device. Changing the BIOS emulation mode for the device fixed it - I can't remember exactly what I had to do, but I think I needed to set it to "IDE" mode to get the install to work (it would then boot using either mode). > WHY? > > At the same time, ISO image (generated at the same bitbake run) is working in virtual box like a charm. 'Install' was successfull and booting fine - i get GRUB menu with one 'Linux' entry as expected. > > On the Atom-pc this is not working. So something has to be missing. Maybe you will have a clue. > Here are the details: > The SSD HDD is /dev/sda with the partition table: > /dev/sda1 - boot > /dev/sda2 - rootfs > /dev/sda3 - swap > there is no asterix at boot partition > > under /dev/sda1/grub there is grub.cfg with: > menuentry "Linux" { > set root=(hd0,1) > linux /vmlinux root=/dev/sda2 rw > } > - so first HDD, first/boot partition > - it points to /vmlinuz and /dev/sda2 > It looks fine for me. > I already tried to dd if=/dev/zero of=/dev/sda bs=4M, and 'install' from usb again, but no luck. > I already tried to put asterix on the boot partition, but than BOOT gets me to grub rescue> > > If you have any ideas, where to look for, please let me know. > > thank you and best regards > simon :-) > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Chris Tapp opensource@keylevel.com www.keylevel.com ---- You can tell you're getting older when your car insurance gets real cheap! [-- Attachment #2: Type: text/html, Size: 4927 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Atom-pc, usb installation - NO BOOTABLE DEVICE 2015-01-09 20:52 ` Chris Tapp @ 2015-01-11 9:38 ` Simon Bolek 0 siblings, 0 replies; 4+ messages in thread From: Simon Bolek @ 2015-01-11 9:38 UTC (permalink / raw) To: Chris Tapp; +Cc: yocto [-- Attachment #1: Type: text/plain, Size: 3271 bytes --] Chris, Thanks for your hint. In my BIOS there is no way to set such a mode. However, all of a sudden it had started to boot ok. It was after I reseted the /dev/sda a couple of times. It is strange and I will try it with another hardware. I know best how that sounds, when you hear: "i really did nothing in between", but i really did nothing. I just reseted the disk 3-4 times installing the system from usb every time after reset like this: 1) plug-in usb and choose 'boot' option (boot is automatic, so no TAB needed at startup) 2) after system booted up, clean target disk with dd if=/dev/zero of=/dev/sda bs=4M 3) reboot, but this time use TAB to choose 'install' option from USB 4) installing.... (in my case SSD HDD /dev/sda) 5) optional step for me: parted /dev/sda set 1 boot on - as this is not set by install.sh script Interesting was that, there is no need to set boot partition for ISO image in VBox to run fine, but hey! i adjusted initrd and DONE! I can test my image now! thank you and best regards simon :-) On Fri, Jan 9, 2015 at 9:52 PM, Chris Tapp <opensource@keylevel.com> wrote: > > On 9 Jan 2015, at 09:31, Simon Bolek <simon.bolek@googlemail.com> wrote: > > Hi, > > The following is the case: > 1) atom-pc with ssd 80 GB hard drive(the only one, no optical, no usb, > etc.) as a target device > 2) core-image-sato bitbaked and moved to usb device successfully > 3) usb 'install' to atom-pc successfull (so the install script says) > 4) after removing the usb device, pressing enter the boot says NO BOOTABLE > DEVICE > > > I've seen this is the past with an eSata device. Changing the BIOS > emulation mode for the device fixed it - I can't remember exactly what I > had to do, but I think I needed to set it to "IDE" mode to get the install > to work (it would then boot using either mode). > > WHY? > > At the same time, ISO image (generated at the same bitbake run) is working > in virtual box like a charm. 'Install' was successfull and booting fine - i > get GRUB menu with one 'Linux' entry as expected. > > On the Atom-pc this is not working. So something has to be missing. Maybe > you will have a clue. > Here are the details: > The SSD HDD is /dev/sda with the partition table: > /dev/sda1 - boot > /dev/sda2 - rootfs > /dev/sda3 - swap > there is no asterix at boot partition > > under /dev/sda1/grub there is grub.cfg with: > menuentry "Linux" { > set root=(hd0,1) > linux /vmlinux root=/dev/sda2 rw > } > - so first HDD, first/boot partition > - it points to /vmlinuz and /dev/sda2 > It looks fine for me. > I already tried to dd if=/dev/zero of=/dev/sda bs=4M, and 'install' from > usb again, but no luck. > I already tried to put asterix on the boot partition, but than BOOT gets > me to *grub rescue>* > > If you have any ideas, where to look for, please let me know. > > thank you and best regards > simon :-) > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > > -- > > Chris Tapp > opensource@keylevel.com > www.keylevel.com > > ---- > You can tell you're getting older when your car insurance gets real cheap! > > [-- Attachment #2: Type: text/html, Size: 5750 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-01-11 9:38 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-01-09 9:31 Atom-pc, usb installation - NO BOOTABLE DEVICE Simon Bolek 2015-01-09 9:38 ` ChenQi 2015-01-09 20:52 ` Chris Tapp 2015-01-11 9:38 ` Simon Bolek
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.