baremetal deplyments fail when /dev/sda isn't the right device for /

What device are the disks on the LSI card listed as ? /dev/sdaXXX?

disk has been listed as /dev/sdc

sda and sdb being virtual floppy and cd/dvd devices

regards
Emil

On May 26, 2013, at 8:07 PM, Robert Collins <email address hidden> wrote:

> What device are the disks on the LSI card listed as ? /dev/sdaXXX?
>
> ** Changed in: nova
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1183940
>
> Title:
> baremetal deplyments fails on sas disks attached to LSI Controller
> card
>
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> Upon deploying a Ubuntu 12.10 created image to a Cisco C200 M2 server
> via Grizzly nova-baremetal, deployment fails with:
>
> tgtadm: can't send the request to the tgt daemon. Transport endpoint is not connected.
> Could not find disk to use.
> Then it drops to troubleshooting shell where I can see that the LSI 1064E Controller card driver: mptsas is actually loaded by issuing lsmod.
>
> Seems like the tgt iscsi target is unable to see the LSI attached disk
> and present it to the nova-baremetal service.
>
> Same deployment on another server without LSI card works fine.
>
>
> Regards,
> Emil
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1183940/+subscriptions

the disk is listed as /dev/sdc

So, this is an instance-side code issue; retargeting it to diskimage-builder.

If you want to work with the standard deploy ramdisk, you need your / to be /dev/sda or one of a number of other well-known devices. Or you can build a custom ramdisk. We should make that easier.

Thanks
Making my hd to be: /dev/sda got things working.
Had to disable the virtual cd and floppy drives in order for the hd to become
/dev/sda