fsck.ext3 error

English Install/Boot/Login
#1

I trying to restore my system from one VM Server to another identical VM Server. I have restored the MBR, created the partitions and restored the system using tar. After I rebooted I get the following error:

fscj.ext3 /dev/sda4 failed (status 0x8) Run manually. Any idea why I am getting this error. I am thinking it has to do with the way I created my ext3 partitions.

Thanks
Will

#2

I’m presuming you are trying to rebuild a guest VM on a running VMServer…

Couple of thoughts:
How did you create and format the partitions? I think your thought is right that the problem comes from that step.
As note: openSUSE 11 uses an default inode setting of 256. As you are unzipping the tar as restore I don’t think it’s relevant, but just thought I’d mention it :wink:

Also ‘who’ is /dev/sda4? Are all the partitions ext3?

Cheers,
Wj

P.s. Cool way of moving a system btw :slight_smile:

#3

Wj,

First of all thanks for the reply. See answers to your questions below

I’m presuming you are trying to rebuild a guest VM on a running VMServer…

Answer:
Yes I am running VMServer on a windows box and I have a SLES 9 server. I am running SLES 10 64 in production but I don’t have a 64 bit version (I need to download) to test with so I am using SLES 9 for now.

How did you create and format the partitions?

Answer:
I used th mkfs.ext3 command to created my /boot and / parition.

Also ‘who’ is /dev/sda4? Are all the partitions ext3?

Answer:
/dev/sda4 is my / partition. I do have one reiserfs partition that is a data partition.

I have run into quite a few issue trying to restore the system using tar but I have solved as them have come up. I hope this is my last issue to solve

Thanks
Will

#4

Well, thanks in return for answering in a clear fashion! :slight_smile:

to take one step back, I would suggest to restart the restore process (maybe using a new vm disk). Restore the mbr and create the ext3 and other filesystems. Before restoring anything create a file or two, restart the VM guest and run a fsck on the partitions, mount/unmount, etc.
That should give an indication if the partitions ar ok.

See where that takes us :wink: