• Posts

  • Joined

  • Last visited


  • Gender

Marky's Achievements


Rookie (2/14)



  1. Thanks for the info guys. I was thinking it was a glitch myself also. Going to replace it anyway and work on it outside of unraid. A possibility (that I read online so not sure if true) is that its a spare sector that has not been brought into use but the drive firmware has seen it as potentially bad. May call HGST and see if they have an explanation. Will report back if I find out anything. Mark
  2. Just recently upgraded to unraid 6 from 5 and immediately saw that one if my disks has 8 pending sectors. Since this is an AF drive I understand that to mean there is 1 4k sector pending to be reallocated. I've run both smart short and long tests and they both pass. I see no errors and there is no LBA of where this bad sector is. Would like to find that out to see if it was in use and what file might be affected. I've copied all the data off the drive to another machine as a failsafe and again I had no read errors. Anyone have any ideas why if there is indeed a bad sector why the smart reports don't show the LBA. The drive is a HGST 6TB NAS. Any help would be appreciated. Mark
  3. So wanted to give an update on this as it is strange. I compared all the files and only one file was different, so replaced the bad file on the new disk. Ran a correcting parity check to fix anything. Did a non correcting check to make sure and no sync errors. Here's where it gets strange. I've upgraded another disk and the same thing happened. Re-built fine, no errors. Did a non correcting check and again 5 sync errors. Compared all the files and again only one file is different. This time I had a look at the contents of the bad file. There was a whole section of zero's but in part of that block was the string EFI PART. This seems odd to me as though wrong data was written on the rebuild. Wonder if I'm hitting an edge case somehow of a bug? Before I update any more drives I'm going to move to V6 I think. Mark
  4. Have just found that there is a Linux Reader plugin for Total Commander. This will be perfect for me as the diff tool in TC is really good. Mark
  5. Am I doing something wrong as I can't access anything from outside the Linux Reader interface. Also read online of a comparision of these mount utils and it also said you couldn't. Mark
  6. Its Reiser. I've just been looking at Linux reader, unfortunately it does not look like you can use any external tools. No driver letter or mount point externally. I'm thinking of the network route, safest to leave the new drive where it is. Easier I think to just mount the old drive in a Linux install read only. Any recommend utility on Linux to do the full directory compare of all files? Thanks for your help. Mark
  7. I have no spare SATA ports so the unassigned devices plugin is not really an option. With both drives in a different box wether it be Windows or Linux the drives would be mounted read only for sure. Mark
  8. Hard to know the exact cause I guess. Parity was good before the rebuild. No read errors shown on any disk after rebuild. They only showed after a non-correcting check after the rebuild was complete. Parity should only be read during rebuild so not sure how there would be parity errors. I think my plan to be safe is to put old and new disks in a different box and binary diff the files. If all files match then I guess there are parity errors so I can do a correcting parity. If they don't match then a do another rebuild, check parity and then also binary diff again. Anything wrong with this plan?
  9. I did run a full preclear on the new disk, all clear. SMART checks on all drives are good. It was my assumption that the rebuild had a glitch as parity would not be written to on a rebuild unless there were errors. No errors shown on UI after the rebuild on any disk. First time I have seen this happen and upraded many disks in the same system over the years. Mark
  10. After some advice on the best way to procede. Here is what I did. 1) Ran a parity check, all fine no errors. 2) Upgraded data disk to a larger one and rebuilt data. 3) Ran a non-correcting check to make sure everything was good, 5 sync errors. No errors showing in the ui on any disk so I'm wondering what caused these. Never had it happen before. Would it be best to do another data rebuild and run the parity check again? Also thinking of connecting the old and new disk to another box and running a binary diff on the files to check them. Any advice would be appreciated. Mark
  11. 2 work fine together. I've used 2 with 4tb drives without a problem, larger drives should work ok too. Mark
  12. I just got one of these yesterday. $60 + $12 shipping. Like others have said came complete with 6 cables. Really great deal. Maybe have to order another one for future use. Mark
  13. Why are you doing an RMA if you only got them in the last week? Take it or send it back to where it was purchased and get a new replacement. If you RMA your likely to just get a refurb as a replacement. Personally I don't trust refurb drives. Mark
  14. I agree with garycase, these are great drives. I would not have posted the link if I did not use them myself. I bought another couple of them and luckily got my local Fry's to pricematch. For me the speed difference between these and 7200rpm drives has not been noticeable. They have the advantage because of spinning slow of lower power use and less heat generation. What you want in a box with many drives close together. Mark