Conversation

Notices

1. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 27-Jun-2023 22:21:43 EDT Clarissa Walker
   Going through the older 2TB storage drives and comparing some of the data with the current NAS data, it is safe to assume the data corruption event started around mid-March 2023 and ended around early April 2023, months after the September 2022 upgrade. May 2023 is when the bad sectors were reallocated.
   
   Seen this behavior on a suspect hard drive with pending bad sectors in August 2021: on a test Windows XP install using a suspect Seagate 320GB HDD, I copied a large archive to the NAS, then I copied that file to the test system. On the test system, the file was corrupt, even after a few retried copy attempts from the NAS. Of course, on the NAS, it was perfectly fine; hashes matched the one on the laptop but not on the test system. Final attempt was to copy that file to the test system using a USB stick, and that eventually worked.
   
   Of course, without file system integrity checks, this is the result. I'm just usually very good at catching these so far.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 28-Jun-2023 12:34:26 EDT Clarissa Walker

     in reply to
     To be fair, the original NAS4Free/XigmaNAS build had no data integrity, either.
     
     --
     
     New note on the file server, as written:
     
     WARNING: THERE IS ZERO FILE INTEGRITY WHEN TRANSFERING [sic] FILES TO THIS FILE SERVER!
     
     RECOMMENDED PROCEDURE IS TO CHECK FILE HASH BETWEEN SRC/DEST!
     
     --
     
     Yes, transferring is misspelled; I only noticed an hour after I wrote the note! http://cwcyrix.nsupdate.info/gnu-social/public/url/34
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 28-Jun-2023 16:26:42 EDT Clarissa Walker

     in reply to
     Seems some of Sis's video collection have different file hashes between her old laptop and the file server.
     
     This happened before the NAS upgrade in September 2022, so I can rule out my RAID5 setup there. The original copies are still on the old laptop, so I am retrieving those now. But, something's up with the drive installed in the laptop.
     
     I have since changed the RAM somewhere around April 2023. I have also found out that I can use unbuffered ECC RAM on the ASUS P5N-E SLI board; however, it may not actually use ECC on the system.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 28-Jun-2023 17:45:22 EDT Clarissa Walker

     in reply to
     Retrieved the data from the laptop drive and am now copying that data to the server as Unsorted.
     
     Will leave a note at that directory regarding the new directory and the existing three: that some of the files have different checksums during transfer in 2021 (what we know so far, anyway).
     
     I now suspect it was possibly RAM related somehow, as there were no known issues with these disks at that time.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 28-Jun-2023 20:28:21 EDT Clarissa Walker

     in reply to
     I also remembered: I also changed the SATA cables as well, though that was before the RAM upgrade, and there were still file corruption issues (though lessened) after the SATA cable replacements.
     
     Probably a coincidence re: the cables. However, no more noticeable issues after the RAM upgrade. Seems the board has some odd memory quirks...