<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Archie,<br>
<br>
I came across the same problem and it turned out to be due to the
volume not being partitioned although it was formatted correctly.<br>
<br>
This documentation on Stardev covers manually partitioning and
formatting:<br>
<a class="moz-txt-link-freetext" href="http://web.mit.edu/stardev/cluster/docs/create_volume_manually.html#partitioning-and-formatting-the-new-volume">http://web.mit.edu/stardev/cluster/docs/create_volume_manually.html#partitioning-and-formatting-the-new-volume</a><br>
<br>
Try the following steps to create the volume on 'myInstance', a
separate (e.g., non-Starcluster) EC2 instance then detach it ready
for incorporation into your new Starcluster instance. (NB: Expected
output is indented - you should see something like it when you run
the commands.) <br>
<br>
1. ON myInstance, CREATE A VOLUME (using your volume name as an
example):<br>
<br>
ec2-create-volume --availability-zone us-east-1a --size 40<br>
<br>
VOLUME vol-521d803a 40 us-east-1a
creating 2011-01-05T15:34:28+0000<br>
<br>
ec2-attach-volume vol-521d803a -i i-b42f3fd9 -d /dev/sdz<br>
<br>
ATTACHMENT vol-521d803a i-b42f3fd9 /dev/sdz
attaching 2011-01-05T15:36:28+0000<br>
<br>
ec2-describe-volumes<br>
<br>
<br>
2. PARTITION THE VOLUME WITH ONE LINUX ext2 PARTITION USING THE
WHOLE VOLUME<br>
(NB: ext2 is the format of starcluster AMI partitions but in theory
ext3 is fine) <br>
<br>
echo ",,L" | sfdisk -L /dev/sdz<br>
<br>
Checking that no-one is using this disk right now ...<br>
OK<br>
<br>
Disk /dev/sdz: 5221 cylinders, 255 heads, 63 sectors/track<br>
Old situation:<br>
Units = cylinders of 8225280 bytes, blocks of 1024 bytes,
counting from 0<br>
<br>
Device Boot Start End #cyls #blocks Id System<br>
/dev/sdz1 0+ 5220 5221- 41937682 83 Linux<br>
/dev/sdz2 0 - 0 0 0 Empty<br>
/dev/sdz3 0 - 0 0 0 Empty<br>
/dev/sdz4 0 - 0 0 0 Empty<br>
New situation:<br>
Units = cylinders of 8225280 bytes, blocks of 1024 bytes,
counting from 0<br>
<br>
Device Boot Start End #cyls #blocks Id System<br>
/dev/sdz1 0+ 5220 5221- 41937682 83 Linux<br>
/dev/sdz2 0 - 0 0 0 Empty<br>
/dev/sdz3 0 - 0 0 0 Empty<br>
/dev/sdz4 0 - 0 0 0 Empty<br>
Warning: no primary partition is marked bootable (active)<br>
This does not matter for LILO, but the DOS MBR will not boot
this disk.<br>
Successfully wrote the new partition table<br>
<br>
Re-reading the partition table ...<br>
<br>
If you created or changed a DOS partition, /dev/foo7, say, then
use dd(1)<br>
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7
bs=512 count=1<br>
<br>
<br>
3. FORMAT THE NEWLY CREATED PARTITION (NB: ***/dev/sdz1*** ):<br>
<br>
mkfs.ext3 /dev/sdz1<br>
<br>
mke2fs 1.39 (29-May-2006)<br>
Filesystem label=<br>
OS type: Linux<br>
Block size=4096 (log=2)<br>
Fragment size=4096 (log=2)<br>
5242880 inodes, 10484420 blocks<br>
524221 blocks (5.00%) reserved for the super user<br>
First data block=0<br>
Maximum filesystem blocks=4294967296<br>
320 block groups<br>
32768 blocks per group, 32768 fragments per group<br>
16384 inodes per group<br>
Superblock backups stored on blocks: <br>
32768, 98304, 163840, 229376, 294912, 819200, 884736,
1605632, 2654208, <br>
4096000, 7962624<br>
<br>
Writing inode tables: done <br>
Creating journal (32768 blocks): done<br>
Writing superblocks and filesystem accounting information: done<br>
<br>
This filesystem will be automatically checked every 36 mounts or<br>
180 days, whichever comes first. Use tune2fs -c or -i to
override.<br>
<br>
<br>
4. MOUNT THE NEWLY CREATED PARTITION ON myInstance (NB:
***/dev/sdz1*** ):<br>
mount -t ext2 /dev/sdz1 /scvol<br>
<br>
5. COPY OVER DATA FROM /data TO /scvol<br>
cp -rp /data/* /scvol<br>
<br>
6. UNMOUNT DEVICE AND DETACH VOLUME FROM myInstance<br>
umount /dev/sdz1<br>
ec2-detach-volume vol-521d803a<br>
<br>
<br>
7. ADD [volume ...] SECTION TO STARCLUSTER CONFIG<br>
(You can call it anything you like but I used 'data' mounting to the
folder '/data'.)<br>
<br>
[volume data]<br>
DEVICE=/dev/sdz<br>
MOUNT_PATH=/data<br>
PARTITION=1<br>
VOLUME_ID=vol-521d803a<br>
<br>
8. LAUNCH YOUR STARCLUSTER INSTANCE <br>
(E.g., 'smallcluster')<br>
<br>
starcluster -c /full/path/to/config start smallcluster<br>
<br>
<br>
Hope that helps?<br>
<br>
Cheers,<br>
<br>
Stuart<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 2/3/2011 5:13 PM, Archie Russell wrote:
<blockquote
cite="mid:AANLkTimOgynFZmhkx5Q2dt-AqvCOu6KTuyiqzEWFzuFc@mail.gmail.com"
type="cite"><br>
Hi,
<div><br>
</div>
<div>Thanks for the help so far guys, I got starcluster to fire
up an AWS cluster (config file needed a strategic " ")</div>
<div><br>
</div>
<div>I am trying to mount a volume now and getting this error:</div>
<div><br>
</div>
<div>
<div>clustersetup.py:200 - WARNING - Cannot find partition
/dev/sdz1 on volume vol-521d803a</div>
<div>clustersetup.py:202 - WARNING - Not mounting vol-521d803a
on /bioreference</div>
<div>clustersetup.py:204 - WARNING - This either means that the
volume has not beenpartitioned or that the partition
specifieddoes not exist on the volume</div>
</div>
<div><br>
</div>
<div>I've mounted this volume before and it worked OK, but never
dealt with partitions. What should I do?</div>
<div><br>
</div>
<div>
<div>Thanks,</div>
<div>Archie</div>
<div><br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
StarCluster mailing list
<a class="moz-txt-link-abbreviated" href="mailto:StarCluster@mit.edu">StarCluster@mit.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/starcluster">http://mailman.mit.edu/mailman/listinfo/starcluster</a>
</pre>
</blockquote>
<br>
</body>
</html>