paperclip

Members
  • Posts

    57
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

paperclip's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Thanks for the response BRiT. Unfortunately I don't have a cache drive and no slot available to add one.
  2. I'm using the great cache_dirs script to keep folders and files listings in memory. I have a situation where I need to keep one file and its contents always in memory for a particular NFS share: \\TOWER\Videos\settings.txt The file itself is under 60 bytes. I have a media player that will attempt to read this file whenever the "Videos" share is accessed and I don't want it to end up spinning up the drive that contains the file just so that 60 bytes of material need be read. Thanks.
  3. Thanks again to @Helmonder and @trurl for your help. The "CORRECT" parity check completed and now reports 0 errors.
  4. Thanks for catching that. I didn't realize the second time was running the CORRECT parity check. Thanks you @trurl for looking into the syslog and discovering this. I would have never noticed it. I should have followed @Helmonder original recommendation and let the second parity check run its course. I'm running the third parity check right now and will report what occurs after it's done. One thing I've already noticed with this third parity check, is that the GUI is showing "Sync errors: 0" When I ran the second, incomplete parity check this morning it immediately showed "Sync errors: 3", so perhaps that means the second parity check I previously cut short did infact correct the errors and this currently running third check will just confirm that? Thanks again.
  5. Will do. I've attached it. Includes instances of both parity checks (the first fully completed one, and the second one I stopped). Thanks. syslog.txt
  6. Hi @trurl. When I ran the parity check a second time, it reported the same three errors a minute or so after beginning, so it looks like it's doing a non-correcting (e.g., NOCORRECT) parity check by default. It looks like I'm going to have to figure out how to run a "CORRECT" parameter parity check via the command line instead of the GUI. It does look like the option/parameter does exist within v4.6, but it's just not an available option within the GUI. That option/checkbox must have been added as a later option. Thanks.
  7. I just started another parity check, and the log file at the outset is showing the same three errors. It's showing "3 sync errors": Aug 2 00:57:12 Tower kernel: md: recovery thread woken up ... Aug 2 00:57:12 Tower kernel: md: recovery thread checking parity... Aug 2 00:57:12 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Aug 2 00:57:34 Tower kernel: md: parity incorrect: 7680 Aug 2 00:57:34 Tower kernel: md: parity incorrect: 7688 Aug 2 00:57:34 Tower kernel: md: parity incorrect: 7696 I stopped the parity check after 15 minutes, as it looks like it's reporting the same 3 errors a minute or so after starting. @Helmonder I did want to respond to the first part of this. I don't believe I've experienced any recent unclean shutdowns. I've always stopped the array, then chose power down. The computer is attached to an APC backup battery. It also has a clean auto-power down script that properly shuts down if the APC battery is close to running out of juice. As far as I know, there hasn't been any power outages recently. I was looking at the package manager in unmenu, and it shows the following for the monthly parity check scheduler: So the option to run a CORRECT instead of default NOCORRECT parity check does appear to be available in v4.6 of UNRAID. There's a similar post of something discussing NOCORRECT with their 4.6 setup: http://lime-technology.com/forum/index.php?topic=11972.0 So, it seems clear to me, based on what @Helmonder originally recommended -- that I run a parity check with "CORRECT" option/flag chosen, but how do I do this? There's no option within the GUI. Is there a command I could execute via command line? Thanks.
  8. Helmonder, thanks for responding. With my version of unraid (4.6) I don't see an option to run a correcting parity check. I've attached a screenshot of the admin area to show you what I mean. Thanks.
  9. I'm on an old Unraid, version 4.6. I know this is the v5.0 forum, but I didn't know a more appropriate sub-forum to put this in. Moderator(s), please feel free to move this if appropriate. Thanks. For today's monthly parity run, it reported 3 errors. All drives are green. Here are lines from the log file. You can see the scheduled parity check start at 4am, and it appears the 3 errors are occurred back to back 22 seconds after the parity check began. Jul 31 20:30:10 Tower dhcpcd[2628]: dhcpIPaddrLeaseTime=86400 in DHCP server response. (Routine) Jul 31 20:30:10 Tower dhcpcd[2628]: DHCP_ACK received from (192.168.1.1) (Routine) Aug 1 04:00:01 Tower kernel: mdcmd (39): check NOCORRECT (unRAID engine) Aug 1 04:00:01 Tower kernel: (Routine) Aug 1 04:00:01 Tower kernel: md: recovery thread woken up ... (unRAID engine) Aug 1 04:00:01 Tower kernel: md: recovery thread checking parity... (unRAID engine) Aug 1 04:00:01 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine) Aug 1 04:00:22 Tower kernel: md: parity incorrect: 7680 (Errors) Aug 1 04:00:22 Tower kernel: md: parity incorrect: 7688 (Errors) Aug 1 04:00:22 Tower kernel: md: parity incorrect: 7696 (Errors) Aug 1 07:11:18 Tower dhcpcd[2628]: sending DHCP_REQUEST for 192.168.1.102 to 192.168.1.1 (Routine) Aug 1 07:11:18 Tower dhcpcd[2628]: dhcpIPaddrLeaseTime=86400 in DHCP server response. (Routine) Aug 1 07:11:18 Tower dhcpcd[2628]: DHCP_ACK received from (192.168.1.1) (Routine) Aug 1 13:13:49 Tower kernel: md: sync done. time=33228sec rate=58791K/sec (unRAID engine) Aug 1 13:13:49 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine) By the way, the parity drive does report the following: reallocated_sector_ct=1 reallocated_event_count=1 current_pending_sector=1 But it's been showing those 3 values for years, and they've never incremented. I've had 100% successful rebuilds for two failed drives while those three issues have been reported. I've posted about it a few years back here: http://lime-technology.com/forum/index.php?topic=15521.msg145003 All my data drives show zero for the following within their quick SMART reports: reallocated_sector_ct reallocated_event_count current_pending_sector offline_uncorrectable multi_zone_error_rate I really don't know what 3 errors Unraid is referring to. The last red ball replaced drive was about a month ago, and the follow-up parity check reported no errors. The only out of the ordinary thing I've done since then was power down the drives/computer two to three times in the past 30 days. I've read about running a parity check again and choosing the "correct" option, but it appears that option is unavailable to me because I'm on v4.6 of Unraid. I understand I'd have to upgrade to 4.7 then 5.0 (or above), but I'd like to avoid upgrading for now if possible. I'm not really confident I won't mess things up, and if it's not broke, I want to avoid unnecessarily fixing something. So, these 3 errors? Significant, worth ignoring for now? I'm wondering if the next parity check is going to keep reporting it. Thanks.
  10. I have an old Unraid version 4.6 where the parity drive is a 2tb WD20EARS and the data drives are also WD20EARS? Unfortunately, the last drive I added (which is actually model WD20EADS) has shown 500+ errors during the monthly parity run. The drive is marked as failed and disabled (DISK_DSBL). Would it be ok to swap it with the WD20EZRX model even though it's a sata III drive and the parity is the much older sata II WD20EARS? Thanks.
  11. Same as any linux command you start on the comand line: type Control-C (hold down the "Control" key and press the letter "C") Thanks Joe. And thanks for your great script.
  12. I've got preclear disk running on one disk. Is there a way to cleanly cancel its process? I want to restart preclear again later.
  13. Thanks for confirming this. You're right. The other disk are all showing green and unmenu doesn't report any smart errors for the rest, so I'll just have to hope the others won't go bad during the eventual rebuild. As I understand it, a rebuild takes as long as a parity check, so I should be up and running after about 11 hours. Even though the parity disk is showing current_pending_sector=1 I don't think I have any choice but to keep it there and hope it can successfully rebuild the replaced data disk. I've put in an RMA with Western Digital and should be receiving the replacement in a few days. I decided not to go with the Seagate as it's too cost-prohibitive to make a new drive purchase at the current price levels. Thanks for your help.