We are currently running a digital jukebox using 1.4 GB WORMs with DiskXtender 200 version 5.60.049 and one of our original data disks is giving us a 16042 error and will not copy its data over to its backup disk due to the maximum number of errors being exceeded. It was functioning for the first few months I was present, and for an indeterminate amount of time beforehand. Any suggestions on how we could get this running again?
The error translates to "A drive hardware error was encountered" which in return seems to indicate you should run some check on disk and replace it if faulty.
It may be worth attempting to read the data using another drive if you have one.
There is an EMC kb article (esg75752) on this error. It does not look promising:
"Customer sees an error-popup containing amongst other things the following : 'Drive device error encountered (16042)' It is not drive specific, since other disks are able to read successfully in the same drive. The same disk also appears to give the same problem on different drives."
"The disk was received for testing, and would not inventory in the EMC lab. The disk appears 'healthy' on a block level, even though it is impossible to determine the integrity of the data written to it. It is presumed that the disk and/or the written data is damaged. Customer was advised to revert to backup and/or to consult with Data Recovery specialists."
ble1
6 Operator
•
14354 Posts
•
56186 Points
580
0
Posted September 7th, 2007 00:00