disParity » General Discussion

Testing Failures

(3 posts)
  1. Klaatou
    Member

    Hello !
    I'm glad of my data reorganization, my disks are almost full and parity creation was OK , the 67MB log file ends with :
    "6,19 TB protected in 53 798,42s (120,65 MB/sec)"
    The Verify command gave me : "Verify complete. Errors: 0"

    Then I tried the testing feature on one of the disk and got some lines as this one :
    "Testing STE\STE-S1\_STE-S1-V6-par2...Verify FAILED!"

    With that at the end :
    "Tested 5785 files (903,24 GB) in 70222,98 sec. Failures: 64

    Verify complete. Errors: 0"

    I don't understand why there is some failures and at the end 0 error.
    I tried then the HashCheck command and got the same kind of response.

    I did no modification to my data before or during the tests so I don't understand, what do you think of that ?
    I don't see the differences between all the commands "test, verify, HashCheck" and didn't found an answer in the forum, where can I find it please ?

    Thenk you !

    Posted 4 months ago #
  2. Roland
    Key Master

    I can't understand how you would get both the "Test 5785 files" line and the "Verify complete" line in the same log. Those are from two different commands. You should *only* see the "Verify complete" line at the end of a verify command, and not at the end of a "test" command.

    Can you zip and send me the log that contains the output of the "test" command? Send it to rolandv@gmail.com. Thanks.

    Posted 4 months ago #
  3. Klaatou
    Member

    Yes it is strange as I don't find that in the logs, I copy pasted the results in the disParity center were I can assure you that it was as you see above ... So the mixe is a disParity center issue ... sorry to "affraid" you with that but as I had all in the center windows I didn't thaught it not could be the real logs.

    But I still don't understand the verify command gave 0 errors and the test one gave 64 failures for one disk.

    Posted 4 months ago #

RSS feed for this topic

Reply

You must log in to post.