Unsolved
This post is more than 5 years old
3 Posts
0
748
November 13th, 2007 07:00
DX Hardware Errors, spefically 16042
Hi everyone,
We've been getting a lot of support calls lately in which users are getting frequent hardware errors in DX. The scenario has been similar for several different customers, and seems to be intermittent. The error we see the most is 16042, which seems to translate to some sort of hardware error when trying to read or write. Sometimes the errors go away for a few days, sometimes rebooting everything helps, as well as clearing statistics and forcing a drive scan. But no matter what we do the same errors seem to reappear over the course of a few days/weeks/or sometimes months. We have been placing hardware calls also, but according to the vendor the hardware often checks out fine. We are mainly using Plasmon or HP jukeboxes and single disk optical devices. The issues don't seem to be common to a particular device, so we are starting to wonder if this isn't something with DX/MediaStor.
I have tried everything I can find here on the knowledgebase and we still haven't been able to resolve these problems for all affected customers. Luckily in most cases DX is still "working" (the files will eventually write) but the error messages and constant need to clear statistics is quite annoying. Has anyone encountered the same thing? Any suggestions?
We've been getting a lot of support calls lately in which users are getting frequent hardware errors in DX. The scenario has been similar for several different customers, and seems to be intermittent. The error we see the most is 16042, which seems to translate to some sort of hardware error when trying to read or write. Sometimes the errors go away for a few days, sometimes rebooting everything helps, as well as clearing statistics and forcing a drive scan. But no matter what we do the same errors seem to reappear over the course of a few days/weeks/or sometimes months. We have been placing hardware calls also, but according to the vendor the hardware often checks out fine. We are mainly using Plasmon or HP jukeboxes and single disk optical devices. The issues don't seem to be common to a particular device, so we are starting to wonder if this isn't something with DX/MediaStor.
I have tried everything I can find here on the knowledgebase and we still haven't been able to resolve these problems for all affected customers. Luckily in most cases DX is still "working" (the files will eventually write) but the error messages and constant need to clear statistics is quite annoying. Has anyone encountered the same thing? Any suggestions?
No Events found!
bmeltzer
26 Posts
0
November 28th, 2007 08:00
Are all your customers using the same drives?
Are the drives on the same rev of firmware?
Have you had the hardware vendor look at the drives and\or the Library?
jtm2
3 Posts
0
May 19th, 2009 12:00
In our implementations we are using DX to manage (mainly) image files from AX... When you are using Optical WORM media, the optical drive performs a calibration test on the media every time it receives a write command. The calibration area is finite, and once it is used up the drive can no longer calibrate. Since the files we are dealing with are very small, about 50-100k, we found it common for platters to start "failing" long before they are out of "usable space." As it turns out, the majority of the problems we were related to this, and were caused by setting the DX schedule to move files all the time rather than letting them queue up and move on a schedule.
So in essence, the calibration area was getting filled up too early and we could no longer write to these pieces of optical media. There isn't necessarily anything wrong with the hardware or the media (you can still read files) it just can't calibrate therefore it will not write. All you can do at this point is mark the media full and move to a new one.
We have changed the move schedule for most of our installs and that seems to have taken care of the issue. Hopefully this will help someone else as it took us quite a while to get to the root of the problem.