Recent content by ors_86

Any ideas why this has happed only at elastix and not at windows server 2003 either windows xp that were at the same storage that wasn't at lvm group?

Any ideas why that has happened?

Elastix: vzdump --dumpdir /media/samba/DiskB2000/Backup/ --compress -mailto ktsimaris@pc2help.gr --snapshot 301 INFO: starting new backup job: vzdump --dumpdir /media/samba/DiskB2000/Backup/ --compress -mailto ktsimaris@pc2help.gr --snapshot 301 INFO: Starting Backup of VM 301 (qemu) INFO...

Yes, the issue was that, the volume where the virtual machine disk was, was not at a lvm group. Now it works fine. But why that issue was not at server 2003 and win xp machine where both of them was at the same volume? thanks Udo, Orestis

Here is the output: proxmox:~# cat /etc/qemu-server/301.conf name: Elastix_1.6_v2 ide2: cdrom,media=cdrom bootdisk: ide1 ostype: l26 ide1: LocalDiskA1000:301/vm-disk-ide0.raw memory: 1024 sockets: 1 onboot: 0 cores: 2 description: qm start 301<br>qm monitor 301<br>device_add...

Here is the log: Nov 20 18:25:01 INFO: Starting Backup of VM 301 (qemu) Nov 20 18:25:01 INFO: running Nov 20 18:25:01 INFO: status = running Nov 20 18:25:01 INFO: mode failure - unable to detect lvm volume group Nov 20 18:25:01 INFO: trying 'suspend' mode instead Nov 20 18:25:01 INFO: backup...

This is the new output: proxmox:~# dmsetup info Name: pve-swap State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 251, 0 Number of targets: 1 UUID...

I run again the command "lvscan" and the output is the following: proxmox:/var/lib# lvscan ACTIVE '/dev/pve/swap' [4.00 GB] inherit ACTIVE '/dev/pve/root' [74.50 GB] inherit ACTIVE '/dev/pve/data' [215.09 GB] inherit

I have run the command: lvremove /dev/pve/vzsnap-proxmox-0 And removed the snapshot. The virtueal machines are still working fine. Then i run the command you mentioned to me, and the output is the following: proxmox:~# ls -l /dev/mapper total 0 crw-rw---- 1 root root 10, 59 Nov 16 12:53...

Hi e100 and Udo, Thanks for the quick replys both of you. I am not very familiar with proxmox, so i need your help. Here are the outputs of the commants you mentioned to me: proxmox:~# lvscan /dev/dm-5: read failed after 0 of 4096 at 0: Input/output error ACTIVE...

Thanks for the quick reply. I have run that command, and found that with minor number 5, is was the first. How can we fix that?

Hi, Thanks for the reply. Im sorry but i didn't understand what i should do. The proxmox installation is at a 250GB hdd. What i should do? Thanks in advance, Orestis

The strange this is that this issue happend from nowhere. I mean that everthing was working smooth for about 6 months now. Here is the output of the pvs command: proxmox:~# pvs /dev/dm-5: read failed after 0 of 4096 at 0: Input/output error PV VG Fmt Attr PSize PFree...

Here is the log, please inform what whats is wrong. Nov 19 15:40:01 INFO: Starting Backup of VM 301 (qemu) Nov 19 15:40:01 INFO: running Nov 19 15:40:01 INFO: status = running Nov 19 15:40:06 INFO: mode failure - unable to detect lvm volume group Nov 19 15:40:06 INFO: trying 'suspend' mode...

I have done many attempts to replicate that issue, and i noticed that if any backup jod run, the virtueal elastix machine is okay. When i run a backup jod, after it complets then the virtueal machine is at offine state. Can anyone inform me for that issue? Thanks