You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Hieu Le <hi...@gmail.com> on 2012/09/13 10:23:30 UTC
System VM corrupt (fsck return code 4)
Hi guys,
My CS always have System VMs error. The error is corrupt disk and while
booting System VMs always display fsck code 4.
Can you show me the problem ? Can it be caused by NFS ?
Re: System VM corrupt (fsck return code 4)
Posted by Gavin Lee <ga...@gmail.com>.
The md5sum is the same as mine. But not tried KVM cluster with this
template yet.
On Thu, Sep 13, 2012 at 6:11 PM, Hieu Le <hi...@gmail.com> wrote:
> I download system VM template following the install guide, here is my
> template info
>
> filename=57489dc1-76cf-4c21-96f7-d366b353e362.qcow2
> description=SystemVM Template
> checksum=
> hvm=false
> size=725811200
> qcow2=true
> id=3
> public=true
> qcow2.filename=57489dc1-76cf-4c21-96f7-d366b353e362.qcow2
> uniquename=routing-3
> qcow2.virtualsize=725811200
> virtualsize=725811200
> qcow2.size=725811200
>
> the md5sum value is: ab52eae5e112683a1e14f14d7c1e6101
>
> On Thu, Sep 13, 2012 at 5:01 PM, Gavin Lee <ga...@gmail.com> wrote:
>
>> You can get quick help if you put system vm template version info and
>> md5sum value.
>>
>> On Thu, Sep 13, 2012 at 4:23 PM, Hieu Le <hi...@gmail.com> wrote:
>> > Hi guys,
>> >
>> > My CS always have System VMs error. The error is corrupt disk and while
>> > booting System VMs always display fsck code 4.
>> >
>> > Can you show me the problem ? Can it be caused by NFS ?
>>
>>
>>
>> --
>> Gavin
>>
>
>
>
> --
> ..:: Hieu LE ::..
>
> Class: Information System - Course 52
> School of Information and Communication Technology
> Hanoi University of Technology
> No 1, Dai Co Viet street - Hai Ba Trung district - Hanoi
>
> High Performance Computing Center
> Cloud Computing Group
> Gmail: hieulq89@gmail.com
--
Gavin
Re: System VM corrupt (fsck return code 4)
Posted by Hieu Le <hi...@gmail.com>.
I download system VM template following the install guide, here is my
template info
filename=57489dc1-76cf-4c21-96f7-d366b353e362.qcow2
description=SystemVM Template
checksum=
hvm=false
size=725811200
qcow2=true
id=3
public=true
qcow2.filename=57489dc1-76cf-4c21-96f7-d366b353e362.qcow2
uniquename=routing-3
qcow2.virtualsize=725811200
virtualsize=725811200
qcow2.size=725811200
the md5sum value is: ab52eae5e112683a1e14f14d7c1e6101
On Thu, Sep 13, 2012 at 5:01 PM, Gavin Lee <ga...@gmail.com> wrote:
> You can get quick help if you put system vm template version info and
> md5sum value.
>
> On Thu, Sep 13, 2012 at 4:23 PM, Hieu Le <hi...@gmail.com> wrote:
> > Hi guys,
> >
> > My CS always have System VMs error. The error is corrupt disk and while
> > booting System VMs always display fsck code 4.
> >
> > Can you show me the problem ? Can it be caused by NFS ?
>
>
>
> --
> Gavin
>
--
..:: Hieu LE ::..
Class: Information System - Course 52
School of Information and Communication Technology
Hanoi University of Technology
No 1, Dai Co Viet street - Hai Ba Trung district - Hanoi
High Performance Computing Center
Cloud Computing Group
Gmail: hieulq89@gmail.com
Re: System VM corrupt (fsck return code 4)
Posted by Gavin Lee <ga...@gmail.com>.
You can get quick help if you put system vm template version info and
md5sum value.
On Thu, Sep 13, 2012 at 4:23 PM, Hieu Le <hi...@gmail.com> wrote:
> Hi guys,
>
> My CS always have System VMs error. The error is corrupt disk and while
> booting System VMs always display fsck code 4.
>
> Can you show me the problem ? Can it be caused by NFS ?
--
Gavin
RE: System VM corrupt (fsck return code 4)
Posted by Edison Su <Ed...@citrix.com>.
How this error happened? Is it happened all the time, even in the first starting of system vms?
> -----Original Message-----
> From: Hieu Le [mailto:hieulq89@gmail.com]
> Sent: Thursday, September 13, 2012 1:24 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: System VM corrupt (fsck return code 4)
>
> Hi guys,
>
> My CS always have System VMs error. The error is corrupt disk and while
> booting System VMs always display fsck code 4.
>
> Can you show me the problem ? Can it be caused by NFS ?