Jump to content

shanecole

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by shanecole

  1. I've always appended checksums to my files and I think you are forgetting that XBMC is using the filename of the MKV to create the other files including the checksum you had appended to the end of the MKV... so those files are never going to have a valid CRC32 as it's not their CRC, it's the MKVs.
  2. Thank you for the suggestion! So far, all corrupt files have been to one disk, but thats the most empty disk and has been taking the majority of writes. I will keep track of whenever it happens and see if it is common to one drive or if on different drives to one controller. In any case I bought a set of new SATA cables and am ready to replace willy nilly!
  3. I am faced with an intermittent issue where a file that I move to my server when read back from the server no longer has the correct CRC32. Having noticed it happen a few times (more often on larger files) paranoia has set in and I started including CRC32 in the filenames as well. When a file compares bad, I can re-check it's CRC32 multiple times from the server and it is always wrong. Last night for example 2 out of about 300 files that I moved had bad CRC. I copied both of the bad copies back to my machine and compared them using HxD file compare to the source local files. In both cases, a single bit was toggled wrong in a random place within the file. This happens when running normal with a parity drive, out of curiosity, I moved a ton of files with no parity drive in place and still had the problem occur, albeit the files moved a lot quicker. Interestingly, if I grab all the files that I have tagged with a CRC32 in the filename and read them back from unRAID, always check out ok, if the file copies correctly, it seems to stay good on the server. Now before I include logs and specs, this has been happening since my first unRAID server, and I have replaced my server board/case/cooling/cables/memory/cpu three times since I first bought a key some 4 years ago and have experienced it from version 4.x until the last version 5. I had always attributed it to maybe a dodgy network card and resigned myself to always performing writes to the array using a write/test approach. I now want to get to the bottom of it because this has persisted through different motherboards, PSU, hard drives that were 1TB and 1.5TB that are now all 2, 3 and 4TB drives. I thought it may have something to do with drives spinning up/down as it would seem that when I browsed to a new share, the current copy would pause for a number of seconds (I assume while a drive spun up) and sometimes that file would end up being corrupt, but I couldn't reproduce it often. So - I can't afford to keep my drives spinning at all times to avoid the problem, any suggestions? One thing that is common to my servers is the adaptec 1430 4 port sata cards. As a test, all the files that had successfully copied, I have for the last two nights just been reading all files sequentially that have a CRC32 in the filename and not a single error reading these files that were successfully copied. At my wits end. I thought ethernet did CRC32 on each packet, is it possible unRAID is not checking the packets at all? Even the gigabit switch has been changed out for a different model.
  4. I have one disk that has show some errors (read, not write) and they are slowly going up. All my disks are currently the same size and I would rather put a larger one in place of the suspect disk. If I remove the suspect disk, put in the larger disk, does anyone have first hand experience of if UNraid will move parity first to the new disk, and then use the old parity disk to rebuild the missing disk? I'm reticent to replace the parity disk first in case I get another read error on my suspect one when it goes to rebuild it, but at the same time I don't want to buy a smaller size drive to replace the current suspect one without needing to move parity. Could anyone give me some advise?
  5. I'm using 5.0 beta 2 and my Popcorn Hour C200 just can't seem to connect over NFS like it used to with 4.5.6. I removed and re-added the shares but it never finds them. I can browse on the network and it fines my unRAID and then the shares are visible but no further. How did you get on with your TVIX 6500 with the new beta? Does anyone else have a PCH and unRAID 5.0b2 using NFS ?
×
×
  • Create New...