Databases
StackOverflow2013
Postsdbo
POAdd EBS to Ubuntu EC2 Instance
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAdd EBS to Ubuntu EC2 Instance
    text
    copied!<p>I'm having problem connecting EBS volume to my Ubuntu EC2 Instance.</p> <p>Here's what I did:</p> <ol> <li><p>From the Amazon AWS Console, I created a EBS 150GB volume and attached it to an Ubuntu 11.10 EC2 instance. Under the EBS volume properties, "Attachment" shows: "[my Ubuntu instance id]:/dev/sdf (attached)"</p></li> <li><p>Tried mounting the drive on the Ubuntu box, and it told me "mount: /dev/sdf is not a block device"</p> <p><code>sudo mount /dev/sdf /vol</code></p></li> <li><p>So I checked with fdisk and tried to mount from the new location and it told me it wasn't the right file system.</p> <p><code>sudo fdisk -l</code></p> <p><code>sudo mount -v -t ext4 /dev/xvdf /vol</code></p> <p>the error:</p> <blockquote> <p>mount: wrong fs type, bad option, bad superblock on /dev/xvdf, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so</p> </blockquote> <p>"dmesg | tail" told me it gave the following error:</p> <blockquote> <p>EXT4-fs (sda1): VFS: Can't find ext4 filesystem</p> </blockquote></li> </ol> <p>I also tried putting the configurations into /etc/fstab file as instructed on <a href="http://www.webmastersessions.com/how-to-attach-ebs-volume-to-amazon-ec2-instance">http://www.webmastersessions.com/how-to-attach-ebs-volume-to-amazon-ec2-instance</a>, but still gave same not the right file system error.</p> <p>Questions:</p> <p>Q1: Based on point 1 (above), why was the volume mapped to 'dev/sdf' when it's really mapped to '/dev/xvdf'?</p> <p>Q2: What else do I need to do to get the EBS volume loaded? I thought it'll just take care of everything for me when I attach it to a instance.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload