ldrax

Members
  • Content Count

    93
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ldrax

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I probably should do the Preclear again, because for reason that escaped me, I opted to 'Skip pre-read' and 'Skip post-read' when I started the preclear that night.
  2. This is the 'Disk Log Information' from unassigned devices menu. Note that this log only after the Reboot described at point 7) above. The errors at the Nov 21 23:26 - 23:27 was just after the Preclear started (point 9 above). sdu-log.txt
  3. I need to find a way to get a cleaner diagnostics. Currently a bunch of DIY scripts are contributing to syslog messages that are not exactly public. I can post the 'Disk Log information' if that helps.
  4. Hi all, I got a situation as below. Basically I want to know if I should be confident enough to use the disk in question going forward, at its current exact location and SATA slot? My plan was to shrink the array, unassign disk10, and use it as unassigned device. 1. During non-correct parity check, disk10, /dev/sdu, reported rapid UDMA CRC errors (going from 0 to 3000+ count). 2. Turned off system, replaced SATA cable (actually it's a 4-ways branch-out cable from a jbod pcie controller, the order is preserved, i.e. the "3rd cable"). 3. Parity check finished without error, and wit
  5. Done reposted there. I will delete this post shortly. Thanks @johnnie.black!
  6. Recently I noticed many occurrences of many processes were 'unable to fork, resources not available' errors, and these processes failed to execute. Suspecting out of memory issue (I have 32GB), I watch the top command for a while when these errors occurring, but it doesn't look that way. 'ps' command surprisingly shows there are 30k+ processes of nv_queue. -- truncated -- 32757 ? S 0:00 [nv_queue] 32758 ? S 0:00 [nv_queue] 32759 ? S 0:00 [nv_queue] 32760 ? S 0:00 [nv_queue] 32761 ? S 0:00 [nv_queue] 32762 ? S 0:00 [
  7. Recently I noticed many occurrences of 'unable to fork' errors. I watch the top command for a while, suspecting out of memory issue, but it doesn't look that way. 'ps' command surprisingly shows there are 30k+ processes of nv_queue. -- truncated -- 32757 ? S 0:00 [nv_queue] 32758 ? S 0:00 [nv_queue] 32759 ? S 0:00 [nv_queue] 32760 ? S 0:00 [nv_queue] 32761 ? S 0:00 [nv_queue] 32762 ? S 0:00 [nv_queue] 32763 ? S 0:00 [nv_queue] 32764 ? S 0:00 [nv_queue] 32765 ? S 0:00 [nv_queue]
  8. I see. So possible cause is because it's underloaded. Thanks @Benson
  9. I noticed a strange behaviour of my PSU (Silverstone Stridec 1200W Platinum ST1200). The PSU is installed with its fan facing downwards, taking air from the bottom of the case (Corsair 760T has the intake honeycomb with filter at this bottom position). For a long time I always had the HDDs spindown delay to 'Never', i.e. disabled it. Recently I enabled it. When those disks stay spun down, the PSU would periodically ramp up its fan speed for about 10-20 seconds before it goes quiet again. When I spun the HDDs up again, the PSU is quiet all the way again. This is rather strange, as
  10. Done, looks like all errors are corrected. Thanks! scrub status for 3c12a05c-3bba-493e-98e5-d2d3a2c7e107 scrub started at Mon Mar 30 16:21:50 2020 and finished after 00:26:03 total bytes scrubbed: 1.87TiB with 300965 errors error details: csum=300965 corrected errors: 300965, uncorrectable errors: 0, unverified errors: 0
  11. BTRFS Scrub command (non repairing, yet), however, shows a lot of errors found: scrub status for 3c12a05c-3bba-493e-98e5-d2d3a2c7e107 scrub started at Mon Mar 30 15:52:07 2020, running for 00:01:21 total bytes scrubbed: 121.53GiB with 14191 errors error details: csum=14191 corrected errors: 0, uncorrectable errors: 0, unverified errors: 0 (in progress)
  12. So before I did the --clear-space-cache command, I started the array in normal mode to be able to backup some selective files from the cache pool. While doing this, there were a lot of errors message (including message to correct them) on syslog, and rebuilding space cache message as well: Mar 30 15:18:56 gpt760t kernel: BTRFS warning (device sdh1): failed to load free space cache for block group 4907223482368, rebuilding it now Mar 30 15:18:56 gpt760t kernel: BTRFS warning (device sdh1): failed to load free space cache for block group 4158791876608, rebuilding it now Mar 30 15:18:56 g
  13. Thank you @johnnie.black I'll do that shortly and update again here. You've been very helpful each time.