Proxmox 2.1 Add new Storage [How??]

[buyukweb]

Hi, I'm Ömer from Turkey.

Proxmox new version (2.1) installed.

How it 2 will introduce you to store?

fdisk -l view

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000e7ea4

Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 121602 976237568 8e Linux LVM

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/dm-0: 103.1 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 33.3 GB, 33285996544 bytes
255 heads, 63 sectors/track, 4046 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 846.1 GB, 846125334528 bytes
255 heads, 63 sectors/track, 102868 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

 

[half_life]

I think we will need a little more information before we can help you.

What is the output from the mount command?

 

[buyukweb]

Mount output :

/dev/mapper/pve-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw)
/dev/sda1 on /boot type ext3 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
container on /proc/vz/container type cgroup (rw,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)

 

[Morten]

If you just want to add a new storage channel (e.g. iSCSI or NFS) to the cluster you click on [Datacenter] in the left menu and then click the [Storage] tab in the content/right frame and then [Add]
Otherwise it would help a lot if you could explain what you mean by How it 2 will introduce you to store?

 

[buyukweb]

If you just want to add a new storage channel (e.g. iSCSI or NFS) to the cluster you click on [Datacenter] in the left menu and then click the [Storage] tab in the content/right frame and then [Add]
Otherwise it would help a lot if you could explain what you mean by How it 2 will introduce you to store?

Hi, morten



İd :
Portal :
Target :
Nodes :

What I need to write?

 

[buyukweb]

please help me !

 

[Morten]

ID: Pick a unique name for this storage
Portal: IP address or hostname for you NAS/SAN server (e.g. OpenMediaVault/Openfiler/FreeNAS or whatever you have setup)
Target: After you have entered a valid IP or hostname in Portal you just pick the LUN of the iSCSI target you want to use. If you don't see anything here you haven't configured the iSCSI services correct on you NAS.
Nodes: All (No restrictions)
Enable: Check
Use LUNs directly: Check

 

[8la]

Hi guys,

May be this is a basic but here we go: ¿Where the hell the size of the storage supouse to be filled?

 

[Morten]

Hi,

Nope, not basic. Just like everything else with virtualization storage is complex!
The size and type of a iSCSI-filesystem on a SAN server is a matter of setting up the LUN on your SAN, and is not a Proxmox matter.
If you are new to SAN concepts I suggest you download OpenMediaVault (debian based just like Proxmox, otherwise choose another) and install it on a 64 bit machine with 2 hard disks and start playing.

 

[8la]

Hi!

I mean, the LV's you can create, or you have to do it manually with lvcreate and then add it to yout storage pool ?

 

[Morten]

Well, no LV creation is not a part of Proxmox (only for locale/internal storage, but just leave that alone for now).
Go to your SAN server. Create LV with the size that you wan't the virtual harddisk have. Configure iSCSI LUN. Go to Proxmox and add storage like I explained earlier.
Now you should see the storage.
If you wan't to change the size of the LV run lvextend or lvresize on the SAN server and reload the iSCSI config.

 

[MacIT]

Hi Morten

I am new to Proxmox and would like to know how to down load the "back ups" that I have made / to external storage

step by step please

thanks

see post from other member


Hi
I would like to request new (probably very easy to fix to) features that I find missing in the new web UI in Proxmox 2.1.
Download, Rename
Simply add a Download and Rename buttons next to the upload button when you are in the contents view of your storage. Would be really nice if one could download backups and iso files as simply as one can upload them today. Even download the images files would be nice (if the vm is shutdown of course). Also a rename button so that you can rename backup and iso files if you need to.

I know it is easy to directly from cli on your storage but it would be so much easier if these options where in the web UI.