installing my server

R

ressel

Well-Known Member
Proxmox Subscriber
Mar 7, 2010
74
0
46
Hello,

Im going to install proxmox on my server, is there a way to NOT let proxmox play with one of my haddrives?

This is my setup
HD1+2 is 2 discs with 750 gb

Atm. i also got a 500gb harddrive connected with copy of my vm's from vmware that i will convert to kvm.

So what i want proxmox to is install it on HD 1+2, and don't touch HD3 is this possible?
 
ressel said:
Hello,

Im going to install proxmox on my server, is there a way to NOT let proxmox play with one of my haddrives?

This is my setup
HD1+2 is 2 discs with 750 gb

Atm. i also got a 500gb harddrive connected with copy of my vm's from vmware that i will convert to kvm.

So what i want proxmox to is install it on HD 1+2, and don't touch HD3 is this possible?
Click to expand...
Hi,
with a normal installation proxmox take only one disk. You can simply add the second disk to the volumegroup and expand the logical volume /dev/pve/data (its mounted to /var/lib/vz) on the console - leave min. 4GB free in the volumegroup for backup (snapshot).
Perhaps you should use the bootparams maxroot, to limit the space for the root-volumgroup.

Udo
 
Hello,

I have found a bit problem.
When i converted my vmware machines to to HD3, i copied the vmdk file for first vm, but i didn't get the newest, i had some snapshots, the version have have copied was from last year.

Before HD 1+2 was in software raid with centos.

I have installed proxmox on HD1, is there any chance to rescue data on HD2 ? i havn't mounted it, after i did the reboot with HD 1+2 raided as raid 1.
All i have done i use HD1 for the proxmox.
I have never worked with raid before, i didn't unraid the harddrives.

Please help, if you need any information to help me, please write the commands i shall run.
 
ressel said:
Hello,

I have found a bit problem.
When i converted my vmware machines to to HD3, i copied the vmdk file for first vm, but i didn't get the newest, i had some snapshots, the version have have copied was from last year.
Click to expand...
You had to delete the snapshort first... but now is to late.
Before HD 1+2 was in software raid with centos.

I have installed proxmox on HD1, is there any chance to rescue data on HD2 ? i havn't mounted it, after i did the reboot with HD 1+2 raided as raid 1.
All i have done i use HD1 for the proxmox.
I have never worked with raid before, i didn't unraid the harddrives.
Click to expand...
I understand not all. Right, that with vmware-server HD1+2 runs as softwareraid?
Then you install proxmox on HD1 and make a new Softwareraid (HD1+2)? If this is true, then you have no chance to get data back, becourse the raidbuilding process sync all data from HD1 to HD2. Or have you proxmox on HD1 and HD2 is the broken mirror from centos-raid? Then all data are on HD2.

Udo
 
Hello Udo,

This is the outpot.

Code: 
v1:~# fdisk -l /dev/sdb

Disk /dev/sdb: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00093dc1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          36      289138+  fd  Linux raid autodetect
/dev/sdb2              37         765     5855692+  fd  Linux raid autodetect
/dev/sdb3             766       91201   726427170   fd  Linux raid autodetect
v1:~#
 
ressel said:
Hello Udo,

This is the outpot.

Code: 
v1:~# fdisk -l /dev/sdb

Disk /dev/sdb: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00093dc1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          36      289138+  fd  Linux raid autodetect
/dev/sdb2              37         765     5855692+  fd  Linux raid autodetect
/dev/sdb3             766       91201   726427170   fd  Linux raid autodetect
v1:~#
Click to expand...
Hi ressel,
try following:
Code: 
apt-get install dmraid
modprobe raid1
fdisk -l
Do you see raid-devices? (/dev/md0 ... /dev/md1)
Try to mount the raid-devices (perhaps one is swap).

Udo
 
reply of commands:
Code: 
v1:~# modprobe raid1
v1:~# fdisk -l

Disk /dev/sda: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdb: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00093dc1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          36      289138+  fd  Linux raid autodetect
/dev/sdb2              37         765     5855692+  fd  Linux raid autodetect
/dev/sdb3             766       91201   726427170   fd  Linux raid autodetect

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       60801   488384001   83  Linux

Disk /dev/dm-0: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

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

Disk /dev/dm-1: 103.0 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

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

Disk /dev/dm-2: 636.8 GB, 636879896576 bytes
255 heads, 63 sectors/track, 77429 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table
v1:~#
 
Hi,
you can also try following:
Code: 
apt-get install mdadm # leave dialog with root... empty - default is all
mdadm -C /dev/md3 -l 1 -n 2  missing /dev/sdb3
# perhaps the same with /dev/md1 and /dev/sdb1
mount /dev/md3 /mnt

Udo
 
v1:~# mdadm -C /dev/md3 -l 1 -n 2 missing /dev/sdb3
mdadm: /dev/sdb3 appears to contain an ext2fs file system
size=726427072K mtime=Sun Mar 28 20:25:49 2010
Continue creating array?

is it safe to click yes here?
 
ressel said:
v1:~# mdadm -C /dev/md3 -l 1 -n 2 missing /dev/sdb3
mdadm: /dev/sdb3 appears to contain an ext2fs file system
size=726427072K mtime=Sun Mar 28 20:25:49 2010
Continue creating array?

is it safe to click yes here?
Click to expand...
Hi,
if you want to use the md-device you must answer "y" here. Size, mount date and filesystem type looks good - but this must you known better.

Udo
 
Here is the folder with my vmware disks.

Can anyone see wich file i should use?

v1:/mnt2/var/lib/vmware/Virtual Machines/Virtual Machines/web1.ybnet.dk_1# ls -l
total 222343564
-rw-r--r-- 1 root root 866902 Mar 28 17:44 vmware-0.log
-rw-r--r-- 1 root root 83092 Mar 27 11:28 vmware-1.log
-rw-r--r-- 1 root root 227939 Mar 26 22:40 vmware-2.log
-rw-r--r-- 1 root root 71793 Mar 28 20:11 vmware.log
-rw------- 1 root root 68417880064 Nov 25 21:54 web1.ybnet.dk-000001.vmdk
-rw------- 1 root root 19461832704 Mar 28 20:11 web1.ybnet.dk-000002.vmdk
-rw------- 1 root root 5016387584 Nov 25 21:30 web1.ybnet.dk-Snapshot2.vmem
-rw------- 1 root root 1155378 Nov 25 21:30 web1.ybnet.dk-Snapshot2.vmsn
-rw------- 1 root root 8684 Mar 28 20:11 web1.ybnet.dk.nvram
-rw------- 1 root root 131649175552 Nov 25 21:54 web1.ybnet.dk.vmdk
-rw------- 1 root root 2919235584 Mar 3 21:12 web1.ybnet.dk.vmem
drwxrwxrwx 2 root root 4096 Mar 3 21:30 web1.ybnet.dk.vmem.lck
-rw------- 1 root root 911 Nov 25 21:30 web1.ybnet.dk.vmsd
-rw------- 1 root root 1136958 Mar 3 21:30 web1.ybnet.dk.vmss
-rwxr-xr-x 1 root root 2309 Mar 28 20:06 web1.ybnet.dk.vmx
-rw------- 1 root root 268 Dec 5 15:02 web1.ybnet.dk.vmxf

it was web1.ybnet.dk.vmdk i used for first convertion.
 
post the content of 'web1.ybnet.dk.vmx':

Code: 
cat web1.ybnet.dk.vmx
 
Hello Tom,

Here is the content:

Code: 
v1:/mnt2/var/lib/vmware/Virtual Machines/Virtual Machines/web1.ybnet.dk_1# cat web1.ybnet.dk.vmx
#!/usr/bin/vmware
.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "7"
floppy0.present = "FALSE"
mks.enable3d = "TRUE"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
nvram = "web1.ybnet.dk.nvram"
virtualHW.productCompatibility = "hosted"
ft.secondary0.enabled = "TRUE"
tools.upgrade.policy = "useGlobal"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"

displayName = "web1.ybnet.dk"
extendedConfigFile = "web1.ybnet.dk.vmxf"

numvcpus = "1"
scsi0.present = "TRUE"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsilogic"
memsize = "2784"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "web1.ybnet.dk-000002.vmdk"
scsi0:0.writeThrough = "TRUE"
ide1:0.present = "TRUE"
ide1:0.fileName = "/usr/lib/vmware/isoimages/linux.iso"
ide1:0.deviceType = "cdrom-image"
ide1:0.allowGuestConnectionControl = "FALSE"
ethernet0.present = "TRUE"
ethernet0.allowGuestConnectionControl = "FALSE"
ethernet0.virtualDev = "e1000"
ethernet0.features = "1"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.networkName = "Bridged"
ethernet0.addressType = "generated"
guestOS = "debian4-64"
uuid.location = "56 4d c4 5d 7a fc 60 f8-1f 65 48 e4 68 74 b7 e1"
uuid.bios = "56 4d 0a ed 4a b7 8f b5-1b 18 56 68 14 9d e1 f6"
vc.uuid = "52 f3 4f 63 50 a9 ac 18-05 da c4 f6 24 11 25 b4"

ide1:0.startConnected = "FALSE"
ethernet0.generatedAddress = "00:0c:29:9d:e1:f6"
tools.syncTime = "TRUE"
scsi0:0.redo = ""
vmotion.checkpointFBSize = "16777216"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "345891318"

debugStub.linuxOffsets = "0x0,0xffffffff,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0"

tools.remindInstall = "TRUE"

checkpoint.vmState = ""
v1:/mnt2/var/lib/vmware/Virtual Machines/Virtual Machines/web1.ybnet.dk_1#
 
as far as I see, the disk is defined in this line:
Code: 
scsi0:0.fileName = "web1.ybnet.dk-000002.vmdk"
also, you should use the same MAC in the KVM to eliminate network issues. see this line:
Code: 
'ethernet0.generatedAddress = "00:0c:29:9d:e1:f6"'
 
Hello Tom,

But if i use web1.ybnet.dk-000002.vmdk will it then have all files?

see filesize:
-rw------- 1 root root 68417880064 Nov 25 21:54 web1.ybnet.dk-000001.vmdk000001
-rw------- 1 root root 19461832704 Mar 28 20:11 web1.ybnet.dk-000002.vmdk000002
-rw------- 1 root root 131649175552 Nov 25 21:54 web1.ybnet.dk.vmdkybnet
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back