On Wednesday 01 November 2017 10:24:00 Jose M Calhariz wrote: > Hi > > I am using amanda 3.5 on my personal server and started to investigate > a strange problem on my amanda installation. > > Since around 10 days ago when it runs the amdump during the nigth, it > flush the holdingdisk, by starting allways with the same big DLE. > This means after the DLE is on vTape is not deleted from the > holdingdisk and will be flushed on the next night. > > I found an interesting error message in amdump.20171101031517, I think > this error is related to the problematic DLE. And I noticed that the > file on vTape is broken too, it generates an error from gzip. > > driver: result time 549.166 from taper0: PARTIAL worker0-0 00-00001 > INPUT-ERROR TAPE-GOOD "6828c030:54131462843" "[sec 548.000000 bytes > 54131462843 kps 96464.883212 orig-kb 53706460]" "source server crc > (6828c030:54131462843) and input server crc (b8d66d3d:54131462843) > differ)" "" > > This problem possibly was caused by an error on SATA that caused the > system disk to became read-only. > Is the sata cable bright red plastic?
Replace it. The red cables in my experience since about 1970, when the J.A. Pan company started using it in CB radio mic cables, have a liketime of 3 to 4 years. Something in the red dye attacks the copper wire, turning it into a brownish powder. Acid test, take a pencil, and move the cable 1/2 an inch while tailing the system log. If the log blows up with drive resets, bad cable. Replace it with any OTHER color of cable. Also, go to the drive makers site, and get that drives latest firmware, put it on a cd as an image, not as a file, reboot to the cd, it should find the drive and update it. The drive will be faster, sometimes dramaticly, like from a write speed of 22 megs/second, to about 135 megs/second. I have been using a 1TB Seagate for vtapes and when I did the firmware update, it was only 2 weeks old and had already marked 25 bad sectors out. Most of a decade later, its still running with the same re-allocated sector count, but now has 70,000 spinning hours on it. But I'm about to replace it as I've outgrown it, and have put off adding the last 2 machines I've added to my home network to the disklist as df reports its hovering in the 87% range and I got a disk full error from one big DLE 3 nights back. The drive is still a 100% usable drive. If it weren't for SSD's getting to be dirt cheap, like $33 for a 64GB thats 3x faster than spinning rust, which I've already put in two of my milling machines and intend to do to the rest of my machinery as time permits. For that duty, a 64GB SSD is only 28% used. gcode to carve a part is not a huge file, so it will handily outlast me since I'm already 83. > What logs should I investigate? Because this is a personal > installation with private data, I will send the logs to the interested > persons, not to the list. > > > Kind regards > Jose M Calhariz Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
