Attaching a ebs volume to ec2 instance at /dev/sdh doesn't appear to attach

  • Question
  • Updated 5 years ago
I created a debian ami here, launched it and logged in just fine. I then attached an ebs volume at /dev/sdh and it shows as attached in the console/command line. But when I try to list the volume it is not in /dev...this works on all my other instances except this one that I built here? Anyone have any ideas?
Photo of

  • 4 Posts
  • 0 Reply Likes
  • confused

Posted 5 years ago

  • 1
Photo of Yan Pritzker

Yan Pritzker

  • 65 Posts
  • 5 Reply Likes
Hi there. We have been able to build ec2 images that mount ebs just fine in the past. If you could please email support AT elasticserver DOT com with information about your server (ip, login & password), we could try to ssh in and take a look. I won't rule out that the issue is on our side, but we've never seen it before...

Please also let us know exactly the command you used to attach your EBS drive (or whether you did it through something like aws console). I would recommend detaching it, and then again reattaching it, making sure to properly specify /dev/sdh as the device.

hope to resolve this for you right away...
Photo of

, Official Rep

  • 95 Posts
  • 11 Reply Likes
Official Response
I think I understand what you're asking. If you're asking why you don't see a device /dev/sdh then it's because we don't ship the VMs with every single device pre-made. This is due to slight differences between the distros we support and their use of udev and larger differences between the various virtualization environments that we support.

What you can try to do is log on to your server and type the following:
$ cd /dev
$ sudo /sbin/MAKEDEV sdh

At this point you should be able to see /dev/sdh and possibly (if the EBS volume has been partitioned) things such as /dev/sdh1, /dev/sdh2, etc.

Hope this helps.

Nicholas
Photo of

  • 4 Posts
  • 0 Reply Likes
Tried your suggestion but it appears udev is running...

sudo /sbin/MAKEDEV sdf
.udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.

maybe that is the source of the issue...
Photo of

, Official Rep

  • 95 Posts
  • 11 Reply Likes
Okay, try this:

$ cd /dev
$ sudo mv .udev .udev.X
$ sudo /sbin/MAKEDEV sdh
$ sudo mv .udev.X .udev
Photo of

  • 4 Posts
  • 0 Reply Likes
That may have done, it I sent my login info, but Ignore that for now and I will let you know here in a bit..
Photo of

  • 4 Posts
  • 0 Reply Likes
that did it, I was trying to convert to an ebs boot, with this article:

http://www.elastician.com/2009/12/cre...

I finished it, but the ami won't boot now...anyone ever tried this?
Photo of

, Official Rep

  • 95 Posts
  • 11 Reply Likes
I've not tried booting from an EBS image that way, but it looks interesting. I'll start playing with it in the next couple of days (got a new release of ElasticServer to complete first).

Thanks for letting us know that the fix worked.

Nicholas