Search results

It was indeed!!!! I was getting number blind... Well, it sets the route, but it still won't bloody work. Grrrrrr! I must be missing a trick somewhere. Ahhh - sussed it. Route was still not quite right This did it: route add -net 10.90.114.192/26 gw 10.90.44.1 dev eno2 (other IP is on...

Thanks for responding. Hmm. Less than happy but no idea why One end is seemingly OK but the other not. Any suggestions appreciated: Box 1 - Settings from provider 10.90.44.13 Reverse MAC address 20:47:47:8f:70:00 network mask 255.255.255.192 IPv6 SLAAC Unavailable status...

Had a look around here but still not sure of the answer - keep getting stuck :-( Using Prox 6. I have a 'real' server with an online provider which has an 'external' interface plus an 'internal' one so I can theoretically connect to another server I have in their space. I can happily set the...

Well, to follow up, all good. Created a 750G qcow2 file Ran with gparted and both partitions and copied the partitions over with sfdisk eg sfdisk -d /dev/vda > sfdisk_vda.output sfdisk /dev/vdb < sfdisk_vda.output So I now have the right partitions. Ran clonezilla and very gingerly copied...

I should be ok. Current qcow2 is 700Gb but only contains 500Gb data. I'd have space to cope with a 750Gb raw drive to copy to.

Mate just had an idea. Create new HD at size required. Boot vm with clonezilla (or live disk with say dd) Clone old partitions (not entire drive) to new drive. Reboot with new drive to check it is ok. Should now be my new 750Gb drive with 500Gb data and space to resize the partition. Boot...

NP !! Damn. I don't have enough disk space to do that. No, I've not changed anything, but as per my test when converting to raw it will create an image of the New disk size. So. Qcow2 = 700Gb Convert to raw = 1342Gb Resize down to 750Gb Convert to qcow = 500Gb (current vm data size) That's...

Yes, but I am not sure that is the case here. I need to shrink the size of the disk the OS *thinks* it has. Yes, I am sure it has some overhead - hence the OS has a drive of about 488Gb and the qcow2 file is about 700Gb The problem is the VM now thinks it has a 1342Gb disk with a load of free...

Except damn - it doesn't loo like you can qm resize <vmid> <disk> <size> [OPTIONS] The disk you want to resize. <size>: \+?\d+(\.\d+)?[KMGT]? The new size. With the + sign the value is added to the actual size of the volume and without it, the value is taken as an absolute one. Shrinking disk...

Addendum Whist playing about I did set the config directly to 750G qm list VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 100 Home running 8192 750.00 1270 So qm thinks it is 750, but the OS and gparted can see 1342. Question...

I needed to resize the disk in a VM. I went to resize and mistakenly entered the required size, and not the increase in size. Doh.... it's way to easy to do that.... :-( The original was about 450gb and I added 750Gb by mistake - I actually wanted it to be 750Gb but the OS now can see 1342Gb ...

https://support.hpe.com/hpesc/public/km/product/1156881/HPE-Smart-Array-P400-Controller#t=DriversandSoftware&sort=relevancy&layout=table&f:@kmswsoftwaretypekey=[swt8000029,swt8000193]&f:@source=[cdp-km-software-pro-h4-v1] Use FW1010.2012_0530.49.iso and use the USB utility in the ISO to make a...

Hmmm - just noticed now I have usb-sdc1 as a drive in the manager. I never had that before ! That is clearly added by the pvesm add command. You can see the auto added usb-sdc1 and the added manually 'Directory' USB-Backup (/media/Backup) I have also noticed that if I leave it set as automount...

Can I make a suggestion for an improvement? Each drive gets mounted to its own mount point based on the drive label. So we get: sdc1-usb-BackupDrive_1 sdc1-usb-BackupDrive_2 Is it possible to override this behaviour and always mount at the same point regardless of the label ? Yes, I can...

Backup with new settings as above with same kernel worked for me last night

Ok - thanks. I'll give it a whirl tonight as is and see what happens (always helps to test these things) and I can give the kernel a try tomorrow B. Rgds John

Similar issues here since upgrading on 1st Jan - which I presume relate to the updated updated the kernel. Crash ocurs shortly after a backup runs. Linux proxmox 4.4.35-1-pve #1 SMP Thu Dec 22 14:58:39 CET 2016 x86_64 GNU/Linux I have done the following to see what happens: cat >...

Vtiger devs listening...? Don't even go there..... :(

I said I didn't like it as it was a totally unconventional layout that no one else uses. I suggested that you should look at a theme manager so new themes could be introduced to test. What else can I say ? And see my bug, as I said above which you choose to ignore. I didn't ask to change it...

Sorry - so what are bug reports for if not for raising issues ? You said nothing 'explicit' about 'don't ask to change it back' as far as I can see. In any case, if you bother to read VERY carefully you will see that I didn't. The bug was entitled "Add theme manager" and yes, I chose my words...