tasmaniac

Members
  • Posts

    5
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

tasmaniac's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Nice catch. Yes, bios was set to ide for a couple of sata ports. Now all AHCI. Ran parity for 10+GB, restarted parity, and the first 10GB came up clean. Doing a full parity now. Thanks for the help. I will reply one last time once complete parity check done.
  2. I replaced the RAM just to eliminate that problem and ran memtest for 8+ hours with no errors. I also rebuilt the usb boot drive (keeping /config) to eliminate that. Same error, except it does not appear to be every block. There is a large group at the beginning that seems OK. New logs attached. Ran parity for a couple of minutes, stopped, then ran it again. Same blocks having problem. Attached new diags. I am not going to swear to it but it seems like this problem started when I went to 6.8.2 or 6.8.3. tower-diagnostics-20200606-1333.zip
  3. Will do. Strange as this machine has been running unraid for many years. I will post the results.
  4. I did it twice just to make sure. No reboot. Correction always starts at 0. Looks like it is not caused by a reboot. tower-diagnostics-20200604-1225.zip tower-diagnostics-20200604-1227.zip
  5. Every time I run a parity check, it looks like every single block fails. Corrected block count is huge. Nothing is catching my attention in the logs. I replaced the parity drive, did a parity check, then ran a second parity check which showed the same problem. smartctl -a looks clean. Everything is functioning but obviously concerned about a drive failure. All drives are btrfs. Could a file system problem on one of the drives cause this problem? Attached are the diags. tower-diagnostics-20200604-1145.zip