Hi,
First I would like to clarify one thing. the creation of a new user doesn't create a new user in the debian system first with useradd right? because the creation of a user in the gui is something totally different?
Second what's the key IDs for a user in linux pam in the GUI? ssh keys...
So Long story short, I had a problem with my logical volume on my adaptecRAID 10 so I've lost all the disk images but fortunately my automatic backup have been running this same day so I was able to recover nearly all the data but some of the containers wasn't been backed up in the backup task...
yes but the upstart job is before the launching of the VM. and the VM are starting from a RAID 10 on a adaptec 6405E with RE4 class HDD from WD.
anyway it seems that it doesn't do it anymore and I don't know why either
here it is:
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext4 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
#vm
/dev/vm/vm /vm ext4 defaults 0 2
So the waiting and notification for upstartjob is it the filesystemcheck working?
no way to do...
I don't even know how can I do a fsck on proxmox since it always answer to me:
fsck /dev/mapper/pve-root
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/mapper/pve-root is mounted.
e2fsck: Cannot continue, aborting.
Yeah I don't think that I change a thing, I mean I think I use the default installation but not sure anymore. What precise information can I give you and where to find it?
I've seen that it was answered here https://forum.proxmox.com/threads/fsck-failure-on-reboot-with-fix.961/
but I guess it's not up-to date, so how can I verify the integrity?
Hi,
I hve a strange thing at start. Several startjob have some difficulties to start apparently.
dev-pve-swap or dev-pve-data etc...
My system is on a ssd. How should I check if the swap partition is activated or if the partition table is damaged somehow?
So I have different type of backup and none of your qmp command works and I would like to know why, so what have I have to give you to investigate this problem?
in snapshot mode you have this kind of error: qmp command 'guest-fsfreeze-freeze' failed - got wrong command id '19572012' (expected...
@dietmar always the same problem about the timeout. Especially on a planified task which run every week.
what do you want me to give you as information? Seems to happen on several vm or maybe all of them.
INFO: starting new backup job: vzdump 100 101 102 104 105 106 107 111 --mode suspend...
I have the same problem than that 100:
Feb 13 01:00:19 ERROR: VM 100 qmp command 'guest-fsfreeze-freeze' failed - got timeout
100: Feb 13 01:00:30 ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
everything is up to date and it's on a debian 8.2
but the backup seems to be...
Hi, I have the same error. So I tried to uninstalled the thing but seems impossible too:
[3360:3164][2016-01-25T14:12:53]i326: Removed dependency: {15b28e32-5594-45e4-8386-60e363c78769} on package provider: {10043E6A-A6D2-40A5-8D38-59019AC776D2}, package qemu_ga_x64.msi...
thanks didn't know if there was a link between the two concepts since on your youtube tutorial you specifically put virtio disk as the primary disk in the windows installation:)
thanks again
best regards
Hi,
I would like to know if virtIO disk is necessary for qemu-agent to work? is it necessary for all kind of VM or jsut for windows vm or something else?
thanks
thanks Cdracer because the wiki of qemu was speaking about another file.
for the guest-ping command I have a {"return":{}}
is that correct? or is it a problem with my installation?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.