I have a minor problem; I've just decided to use that extra storage, that I had lying around my linode, but -- I can find where the drives are. I mean; The drives in the /etc/fstab are like this:

/dev/xvda / ext3 defaults 0 0
/dev/xvdb swap swap defaults 0 0
/dev/xvdc /backup ext3 defaults 0 0
proc /proc proc defaults 0 0

So, basically; the next logical drive would be /dev/xvdd, right? But, it's not. When I try to unleash a cfdisk on /dev/xvdd, it returns "FATAL ERROR: Cannot open disk drive".

Where can I find the additional disk?

However; I've recently updated from Debian 4.0 to 5.0 via apt-get, and everything is working flawlessly, except for that... Any ideas, what's going on?

Probably need to edit the profile to add your new disk image and reboot. Then you can mount it or whatever

Edit: or just shut down your node and add the space to /dev/xvda using the resize feature.

Hi.

Hm... I've already added the drive as Ext3 partition, and the drive *SHOULD* be available there, but it's not...

However; I want to use external partition for the repository rather than just cram everything in one single partition. Aesthetical reasons, probably.

IIRC; in the older versions of the Manager, you could pick a suitable device for the drive, and there is no such thing in the current one. Should I open a ticket for this?

It's not clear from this if you mean adding the drive as in creating a new disk image in the Linode Manager, or as in selecting the drive from one of the drop down lists in the device setup section of the configuration profile editing page. You pick the partition type (ext3) when creating the disk image, but "add the drive" sounds like the device setup step.

Given that your running system doesn't see the new device, and especially since you mention not seeing an option to perform the mapping, it sounds like you haven't edited your configuration profile, as suggested by the earlier responder.


Completely reasonable. Plenty of reasons for multiple partition schemes on Linux systems. With Linode, I also use separate disk images for stuff like /home, which lets me use the same disk image with multiple linux distributions by just having multiple configuration profiles all of which mount the same separate disk image as /home.


You pick the device as part of the appropriate configuration profile (e.g., you get to pick which /dev/xvd[ah] device it will appear as when that configuration profile is booted).

Other than some initial assignments if you create a profile through the "Deploy a Linux distribution" option, assigning disk images to devices for a configuration profile is a distinct operation from creating the disk image in the first place. You have to specifically go into your configuration profile and edit the device assignments.

You will also need to reboot your configuration profile if you made changes to the device assignments in order for those assignments to appear in the running system.

If you've done all this (and double checked that the configuration profile you have edited is the same one you have then rebooted into, just in case you have more than one configuration profile), not sure what to say. I've added and changed many disk images without any problems. I suppose a support ticket might be a next step.

-- David

Heh. I'm officially an idiot.

Thanks for the help. Adding the drive to the profile actually did what I wanted