Page 1 of 1
MHDD errors
Posted: July 26th, 2010, 18:15
by Wassy
Im really trying to learn MHDD and use at as a reliable diagnostic tool, but I must admit I'm really struggling to find out what the error codes mean. I have tried searching the internet for some of them, and even tried searching the forums but havent found any list that shows what the codes mean. Or is there a way MHDD tells you and I just dont know?
Re: MHDD errors
Posted: July 27th, 2010, 7:52
by xsoliman
What error codes in particular ?
Or do you mean the
UNC
ABRT abort
IDNF
AMNF
TONF
BBK
I'm not exactly sure what they are also. but they arent good (unless theres only a few of them)
Used to know what a few of them were, but forgotten
Re: MHDD errors
Posted: August 18th, 2010, 1:59
by fzabkar
Re: MHDD errors
Posted: December 26th, 2010, 20:41
by rzr
can IDNF errors (on wdc) be fixed using a fw replacement or any software operation ?
regards
Re: MHDD errors
Posted: January 4th, 2011, 20:11
by VistaViewer
I just discovered MHDD today, and I'm trying to use it to diagnose a problem Seagate ST31500341AS
SATA drive that keeps dropping offline in a RAID system. It works OK when attached in a single-drive
configuration. This make/model drive is causing a lot of problems for many users, and Seagate has
issued some firmware updates. Mine is not on this of those with the problem firmware, yet the drive is
definately having a problem.
I am running on a dual Xeon ASUS Z8NA-D6 mobo. This is a very late design running the latest Intel CPUs.
I get the following errors when I boot MHDD from CDROM:
MHDD PCI Scan module v3.2
PCI Bus ver: 3.0
PCI Last Bus: 10
An unhandled exception occurred at 0x00036350 :
ERRORRANGE : Range Check Error
0x00036350
0x0002CE51
0x0031C0D4
Anyone have any idea what this means?
It doesn't look like MHDD is going to help me with my problem today.
VV
Re: MHDD errors
Posted: January 4th, 2011, 20:14
by drc
Looks like it is not happy with your hardware config. Try a different computer, or if this is not the system that the RAID is set up on, try changing it to IDE / ATA / Legacy mode in the BIOS