Jump to content

xrqp

Members
  • Posts

    247
  • Joined

  • Last visited

Posts posted by xrqp

  1. Now I see "how" to do it.  It is in Settings tab (Settings/ Docker).  Found help here Docker Mgmt, down at "Re-Create the Docker image file".  

     

    I was incorrectly looking in the Docker tab.  I was confused about docker image file described here  ***OFFICIAL GUIDE*** RESTORING YOUR DOCKER APPLICATIONS IN A NEW IMAGE FILE

     

    I do not know if I should do this, but I don't know what else to try, so I will try.  

  2. I may be misunderstanding the posts and the guides, about re-installing containers, vs reinstalling the docker engine (or docker service).  I had a problem with a container, so I reinstalled it, but it did not help.  Then the same happened again with a second container.  

     

    Should I now try to re-install the Docker Engine (and all the containers since they are under the engine) ? 

     

    How?

     

    I read this ***OFFICIAL GUIDE*** RESTORING YOUR DOCKER APPLICATIONS IN A NEW IMAGE FILE

    but it seems it only for the containers, I am not sure.

  3. OK.  I did not know if reboot shut off power briefly.  I guess not.  Thanks.

     

    I remember the South Park episode, where the internet went off all around the world, causing porn to be unavailable and many other problems, until they power cycled the router.

    • Haha 1
  4. Yes.  It makes no sense that I can see files, can not see, can see, can not see - assuming that is what you are referring to.  I have never experienced this before.  But I repeated it over and over to be sure what i was seeing, and had to repeat it to narrow down what container triggered it.

     

    I think i had disk problems before i noticed this behavior.  Then I replaced the disks, but the see, don't see problem remained.  But it seems possible the bad disks caused this by doing something to nzbget, or to docker img, or to the files, that remains, even though disks were replaced. 

     

    Regarding when i did the container re-install, is was done the way you suggested, but it still auto filled many settings.  Is that weird too?  Maybe a nzbget file stayed behind after i did "removal" of the container, and was somehow used when i did re-install.

  5. The WD bare drive is in my main case with all the other unraid HDDs, with a fan and with proper airflow over every drive.

     

    The WD external hard drive has the vent openings unrestricted for natural convection.  No fan in this WD My_Book.

     

    They both run hot, and both were purchased in 2021.  I did not purhase any other WDs in the last 3 years.  I got 2 or 3 Seagate 8TB in the last 3 years, and they stayed under 40C.

    • Haha 1
  6. The last 2 WD HDDs I got run about 57°C when doing preclear. this is when my room is 72°F . 

    One is a 8TB My_Book_25ED, still in the USB3 external enclosure.

    One is a 8TB  WDC_WD80EDAZ shucked bare on SATA.

     

    I think WD is saying up to 70C is OK, but that does not make me feel as good as when my Seagate drives only get to 38C during preclear.  

     

    15 years ago, I started a bias to WD over Seagate.  But now  I am thinking of preferring Seagate.  What are you experiencing?

  7. My container, binhex Nzbget, seems to be the culprit of my problem, which is when it runs, my file browser (windows file explorer) looses visibility of 70% of the stored media files (plus Nzbget seems to not work).  If i reboot unraid with Nzbget off, then I can see 100% of the media files.  As soon as I run Nzbget, 70% are not visible.  I can repeatedly loose, then bring back file visibility this way. 

     

    I tried removing and reinstalling Nzbget, but the problem remains.  It seems it is not a full reinstall because unraid remembered the settings and put them in automatically.

     

    What do you think i should do?  

    1. should I reinstall the whole docker image?
    2. or is there a way to reinstall just Nzbget where the old settings are not automatically put back?
    3. or something else?
  8. I took this drive out of my array, as it was suspect.  Put it into unassigned and ran 1 preclear.  The 5 steps all show Success.  The smart status shows:

    ATTRIBUTE                INITIAL  CYCLE 1  STATUS                                                                      #
    #   Reallocated_Sector_Ct    0        0        -                                                                           #
    #   Power_On_Hours           1767     1776     Up 9                                                                        #
    #   Runtime_Bad_Block        5        5        -                                                                           #
    #   End-to-End_Error         0        0        -                                                                           #
    #   Reported_Uncorrect       6        6        -                                                                           #
    #   Airflow_Temperature_Cel  40       33       Down 7                                                                      #
    #   Current_Pending_Sector   0        0        -                                                                           #
    #   Offline_Uncorrectable    0        0        -                                                                           #
    #   UDMA_CRC_Error_Count     20       20       -     

     

    Should I be concerned that:

    • Runtime_Bad_Block is 5
    • Reported_Uncorrect is 6    ?

     

    Below that the report says "SMART overall-health self-assessment test result: PASSED" so does that mean I can ignore the rest of the smart report, like bad blocks?

     

  9. Does it mean, if i am offline it is uncorrectable, but when i went online it was then able to correct? 

     

    For SMART 198 wikipedia says:
    0xC6 (Offline) Uncorrectable Sector Count.  

    The total count of uncorrectable errors when reading/writing a sector. A rise in the value of this attribute indicates defects of the disk surface and/or problems in the mechanical subsystem.

     

    Wikipedia does not mention "returned to normal", but it does say there is some inconsistency in what each smart code means. 

  10. Here are diagnostic in reverse chronological. 

    Here is just now May 6, while my Disk 3 replacement is doing parity rebuild (45% done). 

    tower-diagnostics-20210506-1912.zip

     

    Here is my diagnostics May 4, before I replaced 3, but I think before i replaced Disk 1 (not sure).

    tower-diagnostics-20210504-2333.zip

     

    Here is my diagnostics from May 3, before I replaced any disks.

    tower-diagnostics-20210503-0046.zip

  11. For Disk 1 and 3, Yes, I have backups.  Most of it is not too important.  

    For the rest of the 6 disks, the data is important, and is backed up.

    I am guessing 115 errors could all be in one sector (if I am lucky), or in up to 115 sectors.  

     

    It didn't tell me which drive, or is it saying it is the parity drive?

     

    If I can figure out which drive it is, Should I replace it, or just keep an eye on it and see if errors increase?

×
×
  • Create New...