Re: StarCluster not mounting EBS volume correctly
This archive was generated by
There is a command that will create volumes for you:
starcluster createvolume 30 us-east-1b
Have you tried that? Starcluster expects a partition, thats probably
why its failing. I'd use the command unless I had some specific reason
I couldn't. I was unaware of it for about 3 months though :)
On 10/27/2010 03:29 PM, Dan Tenenbaum wrote:
> Hi all,
> I created a 30GB EBS volume, formatted it with the ext3 filesystem,
> and detached it.
> Then I set my cluster config to use this volume.
> VOLUMES = sharedhome
> [volume sharedhome]
> VOLUME_ID = vol-70e6f719
> MOUNT_PATH = /home
> I start my cluster and see the following output:
> >>> Waiting for cluster to start.../>>> The master node is
> >>> Attaching volume vol-70e6f719 to master node on /dev/sdz ...
> >>> Setting up the cluster...
> >>> Mounting EBS volume vol-70e6f719 on /home...
> ssh.py:77 - WARNING - specified key does not end in either rsa or dsa,
> trying both
> >>> Using private key /Users/dtenenba/.ec2/bioc-keypair.pem (rsa)
> clustersetup.py:201 - WARNING - Cannot find partition /dev/sdz1 on
> volume vol-70e6f719
> clustersetup.py:203 - WARNING - Not mounting vol-70e6f719 on /home
> clustersetup.py:206 - WARNING - This either means that the volume has
> not beenpartitioned or that the partition specifieddoes not exist on
> the volume
> I formatted my volume according to these instructions:
> Was there something else I need to do? How do I put a named partition
> such as /dev/sdz1 on the volume?
> BTW, I don't want to partition the volume, but I want to use the whole
> I have set up volumes before using this procedure and not run into any
> BTW, after I ssh into the master, and do fdisk /dev/sdz, I see this:
> # fdisk /dev/sdz
> Device contains neither a valid DOS partition table, nor Sun, SGI or
> OSF disklabel
> Building a new DOS disklabel with disk identifier 0x5cde0278.
> Changes will remain in memory only, until you decide to write them.
> After that, of course, the previous content won't be recoverable.
> The number of cylinders for this disk is set to 3916.
> There is nothing wrong with that, but this is larger than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old versions of LILO)
> 2) booting and partitioning software from other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
> Warning: invalid flag 0x0000 of partition table 4 will be corrected by
> Not sure if that is relevant or not.
> Please let me know how I am supposed to configure the volume. Thanks
> StarCluster mailing list
Received on Wed Oct 27 2010 - 15:36:56 EDT