Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- From: Ivan Voras <ivoras@xxxxxxxxxxx>
- Date: Mon, 10 Sep 2007 11:14:13 +0200
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 (motherboard, controller) or software (geli).
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?)
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- From: Thomas Hobbes
- Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- References:
- GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- From: Thomas Hobbes
- GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- Prev by Date: Re: nvidia-driver rebooting machine on X startup
- Next by Date: Re: Net-snmp dying with an "ld-elf" error at start on brand new FreeBSD install
- Previous by thread: Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- Next by thread: Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f
- Index(es):