My SUSEStudio buit EC2 AMI wont stop "initializing"

[druonysus]

I have built an image with SUSEStudio (http://susestudio.com/a/y1G68N/thisnext-basicserver). I have gone through several different images and this one I am several revisons in... I started by selecting an openSUSE 12.1 server image... I would not boot on EC2 so I replaced the standard kernel with the Amazon ec2 kernel. The image is still not booting once I get the AMI uploaded to EC2 the instance just says "initializing" and never boots. I don't know if this is an issue with Studio or my image.

[dmayer]

Am Freitag, 17. Februar 2012, 15:21:05 schrieb druonysus:

> I have built an image with SUSEStudio
> (http://susestudio.com/a/y1G68N/thisnext-basicserver). I have gone through
> several different images and this one I am several revisons in... I started
> by selecting an openSUSE 12.1 server image... I would not boot on EC2 so I
> replaced the standard kernel with the Amazon ec2 kernel. The image is still
> not booting once I get the AMI uploaded to EC2 the instance just says
> "initializing" and never boots. I don't know if this is an issue with Studio
> or my image.
>
> --
> View this message in context:
> http://suse-studio-users.1598176.n2.nabble.com/My-SUSEStudio-buit-EC2-AMI-w
> ont-stop-initializing-tp7295802p7295802.html Sent from the SUSE Studio Users
> mailing list archive at Nabble.com.

I'm looking into this. Thanks for reporting it.

Dominik

[Randomsense]

Anyone have an update on this yet by chance? It looks like I have the same issue and I can provide some additional details.

Built a openSUSE 12.1 Server configuration with minor adjustments. Had the system generate builds for EC2 and VMware. The VMware testdrive works fine but after having the studio upload the image to Amazon I ge the same results as the post mentions... The status checks never go through and you can't connect to the instance.

Checking the system log through EC2 I'm seeing this at the bottom.

FATAL: Module scsi_dh_emc not found.
FATAL: Module scsi_dh_hp_sw not found.
FATAL: Module scsi_dh_rdac not found.
FATAL: Module scsi_dh_alua not found.
Setup multipath devices: ok.
Waiting for device /dev/sda1 to appear: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Could not find /dev/sda1.
Want me to fall back to /dev/sda1? (Y/n)


Thanks and any help would be appreciated!

[Randomsense]

Putting this in here for reference in case it helps anyone else.
I got a reply from Drew Adams that worked around the issue - thanks! Here is his reply...

====

Yes there is a work around for now: Just remove the package
yast2-firstboot and it will work no problem on EC2. There seems to be
a bug in that package that trips up EC2 but that package isn't really
needed when booting in EC2. Just remove it and all is well.

--
Drew Adams
Member & Ambassador,
openSUSE Project

====

[James T.]

Hi there,

Apologies for the inconvenience - we have tracked down the root cause
and are now working on a proper fix. Meanwhile you can use the
yast2-firstboot removal workaround.

--
James Tan
Engineering Manager, SUSE Studio
Maxfeldstr. 5,
90409 Nürnberg, Germany
SUSE


On 03/01/2012 01:10 AM, Randomsense wrote:

> Putting this in here for reference in case it helps anyone else.
> I got a reply from Drew Adams that worked around the issue - thanks! Here is
> his reply...
>
> ====
>
> Yes there is a work around for now: Just remove the package
> yast2-firstboot and it will work no problem on EC2. There seems to be
> a bug in that package that trips up EC2 but that package isn't really
> needed when booting in EC2. Just remove it and all is well.

[dmayer]

This problem has since been resolved. No need for the workaround anymore.