Jump to content

2112

Members
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

 Content Type 

Posts posted by 2112

    [SOLVED] Unable to resize '/var/lib/docker': Read-only file system

    in General Support

    Posted

    @trurl I have read through the post.  I am not seeing anything in the log file about bad files that should be removed.  I ran a scrub but am getting this error in the log "scrub: not finished on devid 1 with status: -30".  

    @JorgeB I took the array offline and did a check filesystem on my cache pool.  This is what it came back with, "attempting to repair backref discrepancy for bytenr 686580432896 backrefs don't agree with each other and extent record doesn't agree with anybody, so we can't fix bytenr 686580432896 bytes 67268608 failed to repair damaged filesystem, aborting."  Earlier in the day I accidentally assigned a new drive to my cache pool then removed it.  I am not sure if that factors into any of this.  I think I am screwed lol!

    Cache: Unmountable: Unsupported or no file system (after update)

    in General Support

    Posted · Edited by 2112

    1 hour ago, JorgeB said:

    And where are they? And what is the problem?

     

    My cache drives are showing up as "unmountable:  unsupported or no file system."  I am unable to stop/start my array and assign these drives but the highlighted message below keeps showing.  Unraid will let me format these but I don't want to lose my appdata contents.  Any help or guidance would be appreciated.

     

    image.thumb.png.b727ca738bd87771b7680c5fe3aff740.png

     

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    So I also had issue w/user scripts not showing up even though I had user scripts installed.  What fixed things for me:

    • followed this SpaceInvader video 
    • installed as Big Sur (user scripts did not install)
    • went back to macinabox and selected download method 2 (user scripts did not install)
    • went back to macinabox and selected Catalina
    • user scripts could now be seen :) 
    • ran the the two user scripts
    • found the VM and launched it however it stated that I was installing macOS Monterey

    regardless, I am up and running.

    Delete contents and user share

    in General Support

    Posted

    I had this issue recently.  The root cause was that I had piHole installed and I modified my router to use piHole for DNS.  The errors showed that the TCP connection for Docker was trying to use a local IP address (192.168.1.52) which was a clue I had things configured wrong and thus Docker containers could not be downloaded from the repo.  I put my router back to default settings and everything was fixed right away.

×
×
  • Create New...