[Ocfs2-users] Dinode signature problem

[Valan Franklin]

Dear Sunil:

I discovered what was causing the problem. It was due to problems with the
hard drive. It looks like the hard drive is defective. It is a new Maxtor
Diamond Plus 80G ATA 133 drive I bought 3 years ago and never used until
now. I ran Maxtor's PowerMax utility on the drive and it checked out OK. In
the meantime I'm testing a Maxtor 10G drive for shared storage until
everything works so far. I'll get a bigger drive after all testing is
completed.

Thank you very much for your help. I'll post results as soon as I can.

Valan
----- Original Message ----- 
From: "Sunil Mushran" <Sunil.Mushran at oracle.com>
To: "Valan Franklin" <v.franklin at sympatico.ca>
Cc: <ocfs2-users at oss.oracle.com>
Sent: Thursday, May 04, 2006 2:16 PM
Subject: Re: [Ocfs2-users] Dinode signature problem


> Valan Franklin wrote:
> > Dear Sunil:
> >
> > I tried the solution recommended solution but the problem is still
there.
> > After executing the commands, I read the device (dev/sda1) into an
output
> > file and 'KNODE01' appears on the first line. I was wondering if the
changes
> > were written to /dev/sda1 correctly. What are your thoughts?
> >
> So you dd to the device and that block still says "KNODE01". Well
> maybe you used the wrong blocksize? If so, refresh from the backup.
>
> Try bvi. http://bvi.sourceforge.net/. It will allow you to directly
> edit the block on the device.
>
> > As fr iSCSI, I'm unable to purchase a unit now because I'm in the middle
of
> > a job search. If you know what I mean.
> >
> Best of luck.
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.5.1/328 - Release Date: 5/1/2006
>
>