Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

2007-09-11 Thread Thomas Hobbes
> It's impossible to tell which one of these is more likely without more > information (e.g. did you receive any other messages, such as CRC errors > on the drive?) No, I didn't receive more information. Can I exclude that a combination of gmirror and geli is responsible for this error? Because one

Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

2007-09-10 Thread Ivan Voras
Thomas Hobbes wrote: Hi, what is this kind of error's meaning? Usually it means your data is corrupted. Some possible reasons are: - bad sectors or media deficiencies - power failures or fluctuations that affected the drive and/or the controller - bad cables - bugs, either in hardware (moth

Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

2007-09-10 Thread Thomas Hobbes
> It means that metadata (in the last provider's sector) is in an > inconsistent state. Someone/something changed it. The error occurs while attaching a device on a gmirrored disk. Am I right assuming that the responisble change happens right between initialisation and attachment?

Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

2007-09-10 Thread Pawel Jakub Dawidek
On Sun, Sep 09, 2007 at 08:07:49PM +0200, Thomas Hobbes wrote: > Hi, > > what is this kind of error's meaning? It means that metadata (in the last provider's sector) is in an inconsistent state. Someone/something changed it. -- Pawel Jakub Dawidek http://www.wheel.pl [EMAI