• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

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

calvinandh0bbes's Achievements


Rookie (2/14)



  1. ? Isn't a parity check pointless as it will calculate parity using the contents of the failed drive, which is now emulated....using parity. Kind of like checking to see if the answer in the back of the book is correct using a photocopy of the answer in the back of the book.
  2. I just updated my hardware a month ago from an Intel E6600 with 2 Gb ram (DDR2 baby!). 😎 Ran fine for a decade with unraid, but I just used it as a NAS. Cache_dirs was literally the only program I ran (well, and pre_clear). Now I'm with the cool kids like you with 32 Gig.
  3. Can't speak to the X570 taichi, but I just recently upgraded to a used X370 taichi and it's been great. stable, overclocked the memory just fine, 10 sata ports (none of which get deactivated when using either of the M2 slots). Only thing I can't attest to is passthrough, as I'm not running any VM's yet, but i've read others saying it wasn't an issue. I couldn't justify the new price tag for an X570 version when I came across the $85 used x370. Pcie 4.0 and 2 less SATA ports for $200 extra.
  4. Looking for some help with the Autofan plugin. My autofan setup is finally working for the most part and it's no longer shutting off my CPU fan (really problematic, especially since I use a small cooler). Anyways, I have "25" entered in for the "Minimum PWM value", and I'm assuming that means, if the temperatures are all below the low threshold, the fan will spin at it's given rate for a PWM input of 25%. That doesn't seem to be working as my Low and High hard drive temp thresholds are 30 C and 45 C respectively, but as soon as my temps get into the 20's, my fans shut off. I'd like to keep my fans running at some minimum to help cool things other than the hard drives (CPU, LSI controller, GPU, MB, etc). Unrelated, It would be nice to have a little guidance on how to set this up as it isn't intuitive, IMO. There is no "help" if you click the "?" in unraid. It took me quite a while to figure out that the "PWM fan" field isn't unique between PWM controllers. I kept hitting DETECT for each PWM controller (I have 5), and some would come up with one of three /long_path/fan0_input, fan1_input, or fan2_input (ie, 3 fan inputs over 5 PWM controllers, thus some had to be repeated). Also, my biggest issue is after hitting apply, it keeps going back to "PWM1." That's annoying when you are playing around with the settings, you inevitably end up making changes to 1 when you are meaning to make a change to one of the others past 1, and then wonder why the change didn't do what you thought it would.
  5. Doesn't sound like it. Just started 3 preclears (internal drives) and they went from starting to the first step in a few seconds which has always been the case. Haven't ever done any externals.
  6. I built my unraid server somewhere around 2008. I got some old hardware (circa 2006) off craigslist for crazy cheap and I still run that hardware today for exactly what you are saying you want to do...a big array of discs (17 in my server). Core 2 Duo with a whopping 2 GB of RAM (now considered bare minimum). Only thing I spent real money on other than drives was the case (to hold tons of drives) and the power supply. If you aren't planning on running dockers and VMs and such any time soon, i'd save on the guts, only making sure you can support a lot of SATA ports. If you decide in a few years you want to run more, upgrade the hardware then. You'll have faster and/or cheaper hardware at that point than if you buy good stuff now only to really put it to use years down the road. I'm looking at finally updating my hardware to add specific capability. Glad I didn't invest $$$ in 2008 to just do home file storage/serving for over a decade.
  7. I have two on my AOC-SASLP-MV8 (notice the missing "2" in SASLP) and they work just fine. Can't comment on the "2", but I would certainly imagine the newer version handles it at least as well as the older version.
  8. I avoided newegg as their drive shipping has been unimpressive in terms of packing (and I have prime). My drives from Amazon were well packed. Obviously neither was doa.
  9. Two weeks ago, my case was full (drives, all 2 TB and under). Finally replaced the parity and one of my 1 TB's data drives with SMR 8 TB archive drives. On parity rebuild, once I got past 2 TB, speed was not an issue (the first 1 TB was obviously very slow). Rebuild time was in the 20 hour range. I read the entire thread on those drives before my purchase and didn't have any performance concerns after that. I'm happy with my decision. We'll see how they do long term, that's my only concern.
  10. Yeah, looking at an esata dock. My mb's esata port likely won't support >2 tb, so I'll need to get a cheap esata pcie card. Any I should avoid or lean towards?
  11. im fine with it running slower. i don't really have any other hardware to run it on (all laptops that I can't tie up preclearing).
  12. Quick, probably simple question. My unraid server has no more free ports or bays, and I am going to start the process of replacing the original small drives (1 TB) with some larger ones. I'd like to preclear my replacement parity drive and data drive before I put them in as replacements. My desktop is an old Ubuntu box (running 12.04). Motherboard won't support > 2 TB. Looking at installing a 2 port PCI sata card that will support the bigger disks. Can I run the preclear script on an Ubuntu box (ie, not a machine running unraid)?
  13. Hey all, I searched and couldn't find an answer, though I'm sure it's been covered. WD replaced a failed 2 TB drive with a 2.5 TB drive. I'm still on unraid 4.7 (ie, no support for drives bigger than > 2TB). While I'm fine moving to 5.x, I don't want to make this my parity drive as I'm sure it's refurbished (it replaces a previous replacement drive, so I personally believe it is more likely to fail). Is this something I can do in preclear or do I have to do this beforehand and then preclear it? thanks for any help (and sorry that it's likely been gone over, I promise I searched). Calvin
  14. I as out of town on vacation for 0 days and started a parity check when I left since they take forever. When I got home, the system told me zero parity errors (yay), but no my disk 9 of 12 is coming up red. I shutdown the server, checked the wiring and everything seems fine there. Did a smart test (before and after reboot) smartctl -a -d ata /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3886684 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Aug 12 19:57:33 2012 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x85) Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (37980) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 184 163 021 Pre-fail Always - 5766 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 866 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 12311 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 24 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3795 194 Temperature_Celsius 0x0022 122 105 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 10 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 7 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 21 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 12311 1062384488 # 2 Short offline Completed: read failure 90% 12311 1062384490 # 3 Short offline Completed: read failure 90% 12311 1062417667 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Syslog attached. What I don't get is there are no red lines in the syslog page, and no occurrence of the word "error", yet the drive is red. I can access the files, but I would think that could merely be parity calculating the missing data and running from there. Any help? Thanks in advance. c+h syslog-2012-08-12.txt
  15. ok, solved my problem. apparently, choosing to operate the USB as a hard drive wasn't the right choice, but rather as a forced fdd. that and disabling quick boot enabled me to select a removable drive as a boot device, thus i could set the flash drive as the boot device there. maybe this will help someone else. took way too long to figure this out.... cal