Bug 1257

Summary:	[crownbay] broken grub due to wrong root path
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Jiajun Xu <jiajun.xu>
Component:	bsps-configuration	Assignee:	Tom Zanussi <tom.zanussi>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	High	CC:	dvhart, ke.yu, sgw, wenhuax.fan, yp.bsp.watcher, yp.watcher
Version:	unspecified
Target Milestone:	1.1 M3
Hardware:	TunnelCreek
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Jiajun Xu 2011-07-19 00:27:31 UTC

Tree/Branch : Poky/1.1_M2
Poky Commit : fa4bcfdb73167f8159b88e5a4d711c0d37627a70
Meta Branch : 1.1_M2
Meta Commit : 738d2bc6d1a0d7ff6589000893c1c8b4f983d76f

image location: http://autobuilder03.jf.intel.com/crownbay-1.1_M2/nightly/20110717-1/machines/crownbay/x86_32/core-image-sato-sdk-live-crownbay-20110717223745.hddimg.bz2

With Yocto 1.1 M2 RC3 build, default installation of crownbay emgd image could not boot up with a error that "Error 2: Bad file or directory type".

The issue is that, by default the grub of crownbay is like following:
####
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 rw quiet
####

We should modify the "root (hd0,1)" to "root (hd0,0)" to make system boot up.

The grub used by crownbay is 0.97, instead of version 1.98 on sugarbay and jasperforest.

Comment 1 Darren Hart 2011-07-21 15:53:42 UTC

There seems to be some kind of issue surrounding the creation of the grub.cfg or menu.lst files, depending on which grub version is being used (0.97 for Crownbay as it is 32 bit iirc). It looks to me that the menu.lst should be generated using (hd0,0) instead of (hd0,1) but I'm not sure why hd0,1 would be used for the grub2 config, nor why this is only coming up now.

Tom, I think you have more experience with the grub recipes, could you have a look?

Comment 2 Tom Zanussi 2011-07-25 06:50:13 UTC

Yes, it's strange that it just started happening, and also that it only affects crownbay.  Will look into it.

Comment 3 Tom Zanussi 2011-07-26 11:20:28 UTC

I just tried this on sugarbay, which uses grub2, and saw the same problem, which is suprising and points to a grub non-version-specific problem or some change outside of grub that elicits a common problem or assumption in both versions.

Comment 4 Tom Zanussi 2011-08-02 12:32:05 UTC

The problem is that the wrong init-install.sh is getting pulled in and causing grub2 to be installed for crownbay.

I'm also no longer seeing the problem on sugarbay, which may have actually been operator error.

Will check in a fix for crownbay as soon as I finish testing.

Comment 5 Tom Zanussi 2011-08-02 15:31:57 UTC

Fixed by meta/intel commit: 724b13a74e068b7cd018cd8b2e18c2a762881d1d

Comment 6 wenhua.fan 2011-08-07 22:37:51 UTC

This issue not reappear in Yocto1.1 M3 RC3 20110806 building.

Image location:

http://autobuilder03.jf.intel.com/crownbay-1.1_M3/nightly/20110806-1/machines/crownbay/x86_32/core-image-sato-sdk-crownbay-20110807054857.hddimg.bz2

Comment 7 wenhua.fan 2011-08-07 22:49:55 UTC

Tree/Branch: Poky/1.1_M3
Poky Commit id: abdec68876ac7ce1a6d5c223d1757b7e8a14b85f
Meta Branch: 1.1_M3
Meta Commit id: da93dc24fd73079b4dbb6811b83e44a2036d54ef