luisv

Members
  • Posts

    195
  • Joined

  • Last visited

Posts posted by luisv

  1. 9 minutes ago, Frank1940 said:

    @luisv, the preclear function is strictly optional.  It is not required for your server to run properly.  If the drive requires clearing, the unRAID OS WILL clear the disk before it is put into use.

     

    Now a quick bit of history.  Several generations of unRAID version ago, the array was not mounted while the preclear the operation was being performed.  This probably was not to long a period when drive capacities were small but as drive captivity increased so did the time when the array was offline until the preclear was finished.  It was proposed and a shell script was written to do this prior to adding the drive to array which reduced the time from a many hours to couple of minutes.  

     

    Now for the tricky part.  Disk drives have a failure curve that follows the 'bathtub failure' mode (Google for details)  and it was decided that doing a bit of testing would probably catch many cases of infant morality on a drive before it was placed in service.  (The first couple of computers that I purchased were burned in for 72 hours before the vendor would ship it to prevent returns for this class of failures.  I don't think that many vendors are doing this today.)  Thus, the preclear script evolved...

     

    It is really your choice.  Many of us old timers would really like some assurance that the drive is not going to fail a couple of days after it goes into service.  (Just read the forums and the number of questions from users when a drive does have problems and some of the situations which folks have gotten themselves into when they panic a bit!)  How many defective (or soon to be defective) drives are caught by running a few preclear cycles.  I would say it is probably less than 1%.  BUT, If you should get one of the one-percent, would you prefer to deal with the issues before or after you put it in an array?  Your choice. 

     

     

    Thanks for the history and details, much appreciated.  I understand it's not needed for unRAID to function, but I for one would like to at least have some sort of warm and fuzzy feeling that a drive was tested and therefore shouldn't fail shortly after placed into operation.  I know it might not be 100% perfect, and placebo or not, it provides a warm and  fuzzy feeling. 

  2. 23 minutes ago, johnnie.black said:

    The script is supported, just needs to be patched, though there are multiple other disk tools to burning disks before use for users that want to do that, badbocks for example which is also included with unRAID.

     

    I'm certainly not a seasoned unRAID user, but this is the first I'm hearing about badblocks, so that's part of the frustration and confusion.  If there are multiple ways to perform this, what are they?

  3. On 2/4/2018 at 8:15 AM, Frank1940 said:

    Yes, there is.  It is Joe L.'s preclear script which you can find here:

     

           https://lime-technology.com/forums/topic/2732-preclear_disksh-a-new-utility-to-burn-in-and-pre-clear-disks-for-quick-add/

     

     I don't believe that it is being actively supported at this time.  However, Joe L. did issue a patch which allows it to work on recent releases.  You can find that here.

     

    On 2/4/2018 at 5:31 AM, dlandon said:

    It's not really necessary.

     

    On 2/4/2018 at 5:30 AM, bonienl said:

    Many users live happily without the preclear plugin...

     

     

    The plugin isn't supported, the script isn't supported and many users live happily without the preclear plugin?  Can someone explain and recommend what the process should be to a new or relatively new unRAID user like myself?   Is the consensus of developers and or recommendation from @limetech not to run a test on new drives before adding them to the array?    Or is the consensus to hold off using the preclear plugin and script until they are updated and ready for use?   

     

    Sorry, but I'm a little confused as there are numerous forum posts, wiki instructions, videos, etc. recommending and indicating how important it is to use the preclear plugin and or running a script before adding a disk to the array.  If those recommendations and or processes have changed, shouldn't someone update the documentation, videos, etc. to indicate what the new recommended process is?   Isn't the purpose of plugins to make certain tasks easier and more foolproof for the end user?  Keep in mind that some users might not be as comfortable navigating and or running command line type scripts.

     

    Please don't take my comments / questions the wrong way, I appreciate everything that the community, developers and @limetech do... I'm just looking for some clarity and direction in regards to what the new process should be.

  4. 2 minutes ago, killeriq said:

    ive put BIOS 3803 for the ASUS Prime X370-PRO and 6.4.1 today - set C-States to Enabled *from auto....10h stable so far, even BIOS before with 6.4.0 was asl so issues,couple of days

     

    Great, please keep us posted as this would be good news under the latest BIOS and 6.4.1 for other Asus Prime X370-Pro owners.    I'm at 6hrs 44mins with it disabled.   Previous to 6.4.1 longest uptime I got was 30 - 32 days, restarted due to a BIOS / unRAID updates. 

  5. Upgraded from 6.4 and no apparent issues other than this error in the log, which I think is an NTP server error or is it something else?

    Feb 3 13:10:28 DaVault ntpd[1933]: receive: KoD packet from 45.127.112.2 has inconsistent xmt/org/rec timestamps. Ignoring.
    Feb 3 13:11:33 DaVault ntpd[1933]: receive: KoD packet from 45.127.112.2 has inconsistent xmt/org/rec timestamps. Ignoring.
    Feb 3 13:12:40 DaVault ntpd[1933]: receive: KoD packet from 45.127.112.2 has inconsistent xmt/org/rec timestamps. Ignoring.
    Feb 3 13:13:47 DaVault ntpd[1933]: receive: KoD packet from 45.127.112.2 has inconsistent xmt/org/rec timestamps. Ignoring.
    Feb 3 13:14:52 DaVault ntpd[1933]: receive: KoD packet from 45.127.112.2 has inconsistent xmt/org/rec timestamps. Ignoring.
    Feb 3 13:15:57 DaVault ntpd[1933]: receive: KoD packet from 45.127.112.2 has inconsistent xmt/org/rec timestamps. Ignoring.

    https://ipinfo.io/45.127.112.2


    I have these NTP servers listed, are others recommended?

     

    Screen Shot 2018-02-03 at 1.29.40 PM.png

  6. 31 minutes ago, ljm42 said:

     

    I'll see what I can do, this already feels too long and I don't want to scare people away.

     

    For now, you can go to the release thread and then type "preclear" in the search box. When your cursor is in the search box, a new dropdown will appear, choose "this topic" and hit the search button.  Other preclear support requests are all over the forum.

     

     

    We'll need @limetechto weigh in on the Ryzen ideas. rcu_nocbs isn't mentioned in the release notes so I thought it was old information
     

     

    Agreed, I didn't mean nor want to make the Update Notes longer than necessary; however, was curious about clarification as I believe folks would want a quick and simple guide instead of having to read through multiple threads for the info they need.  

     

    I reviewed the thread for preclear before posting and didn't see any specific evidence that it was a hard and fast rule that preclear needed to be removed by all.  Seemed like a few instances where removing it helped.  I guess I'm looking at it as instead of saying it needs to be removed, that it might need to be removed if a user sees XYZ issue.

     

     

    • Like 1
  7. This is a great thread and idea... thanks for taking the time to do this @ljm42!  Couple of questions / suggestions:

    • Is it possible to include explanations, links or additional details as to why those plugins should be removed prior to updating?  I ask as I upgraded prior to the creation of this thread and never removed the Preclear plugin; however, I didn't have any issues upgrading.   Should users remove it now or if no issue was discovered, they can reinstall or continue using Preclear or the other plugins mentioned.  I think this needs a little more clarification.  
    • As @pederm indicated, is it best to leave the rcu_nocbs setting in place or remove it and use the zenstates --c6-disable in the go script?  Potentially add rcu_nocbs as an additional stability measure?  
    • Add a link to this forum post from the first post of the 6.4.0 release thread?  Possibly indicating this is a work in progress?
  8. On 12/18/2017 at 5:05 PM, saarg said:

     

    V2 is still in beta, so not sure when that will be released. As soon as the developer moves v2 to master, this container will be updated. 

     

     

    Great, thanks for the info.  Curious if there will; be a new support thread or will this thread be renamed and stay active?

  9. On 1/6/2018 at 9:51 AM, Blindsay said:

    Hey all,

     

    curious what the general concensus on a ryzen build is right now? Over the past few days i have been migrating data from my old intel build and my ryzen build has crashed a few times

     

    Running 6.4.0_rc19b

     

    I was using the build a desktop before and it was running great so i know the hardware is good.

     

    Ryzen 5 1600

    16GB DDR4

    Gigabyte AX370-Gaming K5

     

    Could just be a coincidence but so far it has not crashed while doing something (it ran through the parity check, copying over all the data etc. fine.) it only seems to crash when idle, but i thought i read that bug was fixed?

     

    I upgraded to rc20a as well as the upgraded the BIOS to v3402 this morning.  Prior to that, with C-State disabled, my system was stable for 30 days.  

     

     

     

    unraid.png

  10. Welcome to the forums!  Not sure if you have read the forum thread below, but most Ryzen issues have been related to C-State.  If disabled within the BIOS, the system remains stable.  Some have been fine running with the latest BIOS updates with C-State enabled; however, I have had to keep it disabled to remain stable.  Only other instability issues I've read about have been due to memory... make sure it's on your motherboards approved list.    

     

    https://forums.lime-technology.com/topic/55150-anybody-planning-a-ryzen-build/

     

    • Upvote 1
  11. On 9/22/2017 at 9:40 AM, Popple2000 said:

     

    So, is this particular unit plug&play? or is more setup required?

    Thanks

     

    On 9/22/2017 at 10:01 AM, Frank1940 said:

    I just plugged it and it worked.  It does add a few extra seconds to the boot time and it does have a control key combination to get to the card's BIOS but I have never even looked at it.  I did order it with the P20 firmware.  (I contacted them and they responded quickly with instructions on how to request that version when I placed the order.)  Don't forget that you have to get cables...

     

    Is the P20 firmware required or is P19 ok?    Any difference between these cables?

     

    https://www.amazon.com/Cable-Matters-Internal-Mini-SAS-Breakout/dp/B018YHS8BS/ref=as_li_ss_tl?_encoding=UTF8&psc=1&refRID=DZD42M5Z36H2R4GR309H&linkCode=ll1&tag=orf0f-20&linkId=c3bab21c2c2bc7ba96b86d6729fcb651

     

    https://www.amazon.com/gp/product/B000FBYS2U/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=ll1&tag=orf0f-20&linkId=06f97486c1b60e0bf2573dabff7f3b02

     

    1st time using one of these cards, so pardon my lack of knowledge / experience.   I have 8 ports on my motherboard and looking to add 4 more drives.  Any issues with running both the card and on-board SATA ports?