Jump to content

PeteAron

Members
  • Posts

    265
  • Joined

  • Last visited

Posts posted by PeteAron

  1. Well I am running a second parity check and, as expected, I see these 5 errors again.  Hopefully this means they are corrected; but is it possible they are scrambled?  I am writing corrections to parity; I dislike doing this because eventually I need to replace a disk, and i worry about the potential for these errors to corrupt my rebuild.

     

    Is it possible this is a memory-related error?  I will replace my sas-sata breakout cables this weekend and run a third parity check.  Any input here is welcome.

  2. No, Jorge, It has been fine.  The one unusual issue i have had is an st800dm drive has been throwing crc errors- enough that i am going to return it.  I dont see others, so i assumed that isnt the issue.  

     

    How do i find where the errors are?  Maybe its time to replace my 2 year old sas to sata cables?

  3. I used to use a SASLP-MV8 in my array, for about 7 years.  I would occasionally get 5 parity errors as you have done.  I replaced that controller with an LSI SAS2008 (PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) ) and have had good service from it.  However, just yesterday I had a parity check complete, and I have 5 errors. 

     

    Since this pattern has been related to the SAS controller, does anyone think I have something to worry about with this one?  I think I will run a second parity check.  In the past, when I did this, the same 5 errors would show up, and a third check would show no errors, as if they had been corrected.

     

    Any ideas?

  4. I have been using UNRAID strictly as a NAS for 10 years?  11?  not sure.  still on the same hardware but second replacement PS, LOL.  And of course, all of the disks have been replaced.  

     

    I have just built a new server to start using a docker VM, and am already thinking about how best to upgrade my NAS, and use another docker or three.  I'd like to replace the functionality of a couple of windows boxes and my two servers will be on all the time anyway, so i am trying to put that wasted power to good use.

     

    As a NAS, i am unable to imagine a better solution than Unraid for an individual moron like myself.

     

     

    And can I just say that guys like Hoopster and JorgeB are just great to have around?  You guys are so helpful, really appreciated :)

  5. I appreciate JorgeB, Hoopster, and others trying to raise this to a higher priority level.  

     

    I am going to review everything in my setups, and even though i have a pretty good idea of what to do, some sort of primer on server security would be helpful, no doubt to many others.  I am wondering, after i have opened a port for my server to accept connections, what is necessary to prevent any unintended access to that port or ports.

     

    Any guidance, from general to specific, from our most experienced users, should go a long way to helping the Luddites among us (me included).

    • Like 1
  6. On 9/1/2018 at 12:33 PM, CHBMB said:

    You've changed the port on the docker side, you should change the port on the host side and leave the docker port alone.

    Sent from my Mi A1 using Tapatalk
     

    This doesnt work.  even though virtual 6881 is mapped to a server port number xxxxx, the qbit reports 6881 to the tracker, and that port is banned at more than one tracker.  canyouseeme can see my server using my servers port number xxxxx (mapped to docker port 6881) when the docker port number, 6881, is entered in the web gui.  unfortunately qbit reports the 6881 instead of the actual port being used.

     

    when i put port xxxxx into the webgui, canyouseeme says the port xxxxx is blocked.

     

    port 6881 being banned stops me even though i am not even using it.   jesus why cant we edit the container port number?  this is a very simple networking issue and it seems it is not solvable.

     

    Is there any way to change this?  I am ready to give up on unraid dockers <frustrated>

  7. I had this new second server working and was trying to get deluge or delugevpn up and running - i could not get it to download.  Something went wrong so i reconfigured the network settings and rebooted.  My router sees my server but it cant connect to the internet.

     

    Here are the diagnositics.

     

    I am not able to start the array (it says too many devices) and it cant connect to the key server.  I tried to install my purchased key and it fails with ERROR (4)

     

    I would appreciate help with this as soon as possible.  Should i message Lime directly?  How do i do that?

     

  8. You can get an iso from microsoft without a license.  you can even use it legally.  without an activated install you wont be able to customize the interface or get tech support, but ms will allow you to use an unlicensed copy.  In my process of moving a physical pc onto my server, i will be using the unlicensed copy of windows to run what i need on that VM.

  9. I dont hold a candle to itimpi, but reading through this I would follow exactly what he suggests.  Since you built parity with a disk giving read errors, you very likely have invalid parity.  Luckily the data on that disk isnt important to you, so if it were me i would shut down my array now, do a new config, remove that drive from the array, and let fresh parity build.

     

    It makes no difference how many parity disks you have or how many drives fail right now - you cant trust your existing parity with that failing disk in place because parity is based on "bad bits" from that disk, or at least, you can't be sure that it isnt.  

     

    remove the drive and do new config asap IMO

  10. In my case i believe i have a failing drive but it's odd.  I am getting CRC errors even though i am sure it isnt the connections.  I mention it because i was using this drive to replace another disk in my array, and my rebuild speeds were varying from 10 Mb/s to the more normal 130-160 while trying to rebuild the disk.  I took it out of the array and replaced it with another.  

     

    I am going to rma the drive, even though the only issue is crc errors - it is up to 1475 crc errors now.  You may have a similar issue.

     

    Edit:  This drive had been precleared immediately before trying to put it into the array.

×
×
  • Create New...