dgaschk

Moderators
  • Posts

    8920
  • Joined

  • Last visited

Everything posted by dgaschk

  1. So once Blue Iris writes a file it never has to access that file again?
  2. I'm not sure I understand the question. Blue Iris is keeping the disk busy.
  3. I agree. "Disabled" should stay in the title until the procedure no longer requires a disabled disk. Although, what is the point of this procedure if a disk is not disabled?
  4. Run reiserfsck -check again. reiserfsck --check /dev/md5
  5. Run with check again to confirm success. You may want to run "new permissions" to make the lost and found share accessible.
  6. Blue indicates a new disk. Disk 2 cannot be rebuilt unless all of the other disks are green. Was parity installed previously? Reinstall the original disk 2 and post its SMART report.
  7. Run with rebuild tree. Always follow the instruction given by reiserfsck. I can think of no circumstances when the advise given by a file recovery program should be ignored.
  8. Memtest needs to run at least overnight. The longer the better. If it will only run once a RAM issue is indicated.
  9. Is the disk XFS? root@rack:/mnt/disk8# ls root@rack:/mnt/disk8# du -a 0 . root@rack:/mnt/disk8# fallocate -l 50GB stor.img root@rack:/mnt/disk8# ls -l total 48828128 -rw-r--r-- 1 root root 50000000000 Sep 13 12:58 stor.img root@rack:/mnt/disk8# du -a 48828128 ./stor.img 48828128 . root@rack:/mnt/disk8#
  10. See here: http://lime-technology.com/wiki/index.php?title=FAQ#How_To_Troubleshoot_Recurring_Parity_Errors
  11. Ask in application specific forum or thread.
  12. Ask in application specific thread.
  13. I suspect BinHex-Deluge is not setting correct permissions. Show the output of ls -al /mnt/cache and ls -la /mnt/cache/Movies to confirm. Select Tools->New Permissions and run it on the cache disk to repair.
  14. http://lime-technology.com/forum/index.php?topic=13432.0
  15. This should not be an issue. Check for MB BIOS and SATA card firmware updates.