Jump to content

Popple2000

Members
 View Profile  See their activity

  • Posts

    109

  • Joined

  • Last visited

 Content Type 

Posts posted by Popple2000

    Dockers missing after update.

    in General Support

    Posted

    5 hours ago, itimpi said:

    You could also have fixed the templates for the affected containers.

    Thanks for the reply :)

    I'm not sure how to do that. I try not to muck around too much without guidance in fear of breaking something.

     

    Dockers missing after update.

    in General Support

    Posted

    Hey guys,

     

    I just updated a bunch of dockers and plex/tailscale etc have vanished.

    I went to the apps tab to reinstall them, but when I do, I get "docker: invalid spec: :/downloads:rw: empty section between colons."

    Can anyone help please?

     

    Thanks

    Letsencrypt/SWAG Stopped working after last update

    in General Support

    Posted

    Hey guys,

     

    After I last updated the container I was no longer able to connect to ombi etc from outside the network.

    When I checked the logs I'm getting this over and over.

    "nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3"

    Is there a quick fix for this?

    Please let me know if more info is required.

     

    Thanks!

    Your flash drive has possible corruption

    in General Support

    Posted

    On 3/13/2022 at 3:47 PM, Popple2000 said:

    Hey,

    I had no sync errors.

    I'll go ahead and update to UDP.

    I was emptying the drive to convert it to XFS and then swap in a 14tb i have sitting here.

    As far as sdj1 is concerned, can I do anything to remedy the trim error? Should I be concerned?beafy-diagnostics-20220313-1624.zip

    *edit* Perhaps you were talking about the critical target error... I assume this is bad? Should I replace the drive?

    *edit 2* I ran a scrub and balance, updated everything, cleaned up the errors I could, rebooted the server and attached a new diag.

    @trurl

    I moved the second cache drive off the LSI HBA and onto the onboard sata and i think that solved the trim issue(I read somewhere that could be the culprit)

    Im pretty sure the rest of my issues are solved for now as well.

     

    Thanks for your help!

    Cheers

    beafy-diagnostics-20220315-0838.zip

    Your flash drive has possible corruption

    in General Support

    Posted · Edited by Popple2000
    *edit*

    44 minutes ago, trurl said:

    Looks like you let it complete the automatic parity check after the unclean shutdown. Do you have any sync errors? The reason I ask is because of another warning from FCP. 

    Mar 13 15:01:37 Beafy root: Fix Common Problems: Warning: Docker Update Check not enabled ** Ignored
Mar 13 15:01:37 Beafy root: Fix Common Problems: Warning: Scheduled Parity Checks are not enabled ** Ignored
Mar 13 15:01:39 Beafy root: Fix Common Problems: Error: Blacklisted plugin speedtest.plg
Mar 13 15:01:42 Beafy root: Fix Common Problems: Warning: Docker application Bitwarden has moderator comments listed ** Ignored
Mar 13 15:01:42 Beafy root: Fix Common Problems: Warning: Docker application openvpn-as has moderator comments listed
Mar 13 15:01:44 Beafy root: Fix Common Problems: Warning: preclear.disk.plg Not Compatible with Unraid version 6.9.2
Mar 13 15:01:46 Beafy flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 13 15:01:49 Beafy root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed
Mar 13 15:01:50 Beafy root: Fix Common Problems: Error: /boot/config/plugins/plexmediaserver/settings.ini corrupted

    Personally, the only one of those I would set to "ignore" is the one about Unassigned Devices Plus if you don't need its functionality.

     

    Disk2 is the one you formatted. Why did you format it? Are you converting from ReiserFS?

     

    Also cache2 may have problems, maybe you noticed 

    Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 Sense Key : 0x5 [current] 
Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 ASC=0x21 ASCQ=0x0 
Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Mar 13 04:35:40 Beafy kernel: blk_update_request: critical target error, dev sdj, sector 484642784 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Mar 13 04:35:40 Beafy kernel: BTRFS warning (device sdj1): failed to trim 1 device(s), last error -121

     

     

    Hey,

    I had no sync errors.

    I'll go ahead and update to UDP.

    I was emptying the drive to convert it to XFS and then swap in a 14tb i have sitting here.

    As far as sdj1 is concerned, can I do anything to remedy the trim error? Should I be concerned?beafy-diagnostics-20220313-1624.zip

    *edit* Perhaps you were talking about the critical target error... I assume this is bad? Should I replace the drive?

    *edit 2* I ran a scrub and balance, updated everything, cleaned up the errors I could, rebooted the server and attached a new diag.

    Your flash drive has possible corruption

    in General Support

    Posted

    17 minutes ago, trurl said:

    Any idea what this is about? 

    Mar  9 21:35:39 Beafy emhttpd: unclean shutdown detected

     

    I was using unbalance to move files off a disk and I must have miss-clicked something because it started deleting everything off the disk instead and I couldn't get it to stop, so I initiated a reboot from the unraid GUI.

    When the server came back up from it's reboot it was running a parity check on it's own so I assume something went wrong with the reboot.

    Docker tab showing false updates?

    in Docker Engine

    Posted

    Hello all!

    So, I recently added a 10TB Parity drive(not sure if that has anything to do with this) and since then, my DOCKER tab when I click "check for updates" shows:

     

     

    1835674779_2019-09-07(2).thumb.png.11bf628e4213ce9f565255b2aff7231b.png

     

    This looked fairly normal to me since I hadn't updated my containers in a while.

    I ran "update all"(same outcome if I try to update individually) and all of the "pulling image" boxes looked like this:

    1717666282_2019-09-07(4).png.58ea2209c29c15f5d5251b68ac65e72b.png

     

    0 b pulled every time.(aside from when there actually is an update, as it seems to be updating if one is actually available)

     

    Once I run the updated and it finishes, all of the containers show up to date, but if I run "check for updates" again, they all show as if they need to be updated once again.

     

    Thanks in advance for any help and please don't hesitate to ask if you need more information!

    Upgrading cache drive

    in General Support

    Posted

    6 hours ago, noja said:

    As always, Spaceinvader One has a video for this.  I didn't know about the "one at a time" option, but I think you could always go with his method too if one or the other gets complicated.

     

     

    Thanks!

    Love his videos too! :)

    Upgrading cache drive

    in General Support

    Posted · Edited by Popple2000
    typo

    4 minutes ago, presence06 said:

    I would think you'd want them both hooked up and set to cache and let it build/balance.

    If i hooked them both up at the same time, there would be nothing on them.

    I was wondering if the above mentioned technique would save me a backup and restore.

    But thanks for your reply! 

    Upgrading cache drive

    in General Support

    Posted

    Hi there.

     

    I have a scenario I'd like to ask about.

    Currently I have 2x 128gb ssd's in a btrfs cache pool but I would like to upgrade to two 500gb's

    Could I pull one of the 128gb out, drop in a 500gb, let it balance.... then pull out the other 128, drop in the other 500gb and let it balance again?

    Or would this not work?

     

    Thanks in advance.

    Slow transfer to cache drive

    in General Support

    Posted

    4 minutes ago, johnnie.black said:

    Doesn't make sense that a local transfer to the cache drive is fast, while a network transfer is slow

     

    Let me ask you this...

    If someone was watching something on plex and it was transcoding... should that affect the xfer speed? I should mention that I have the transcoding going to ram, not the ssd.

    Could it be an I/O conflict?

    I am at a loss

    Slow transfer to cache drive

    in General Support

    Posted

    2 minutes ago, johnnie.black said:

    That would suggest a network issue.

    I also just transfered a file from my desktop to disk7 directly and it went at 60MB/s and the xfer to the cache slowed down to 5MB/s and then went back to 25MB's when the direct xfer finished

×
×
  • Create New...