Mizerka

Members
  • Posts

    75
  • Joined

  • Last visited

Posts posted by Mizerka

  1. Hey, thanks for your work;

     

    for a about a week now (not bothered to look at it closely), delugevpn docker in unraid would fail to start, stating dns resolution errors, it'd loop through all external ip identifiers and dns resolutions until it times out eventually and starts webgui without external connection, despite it connecting to vpn (tested) and not stating any errors during it, looking at debug logs, nothing useful again other than dns resolutions failing, I tried swapping to CF, google and internal pihole with same results. It can ping external just fine from console

     

    This started happening since 6.9 rc2 update

     

    any ideas? let me know if you need logs/more info.

    ignore me, removed .ovpn and .conf files and it just started to work.

  2. You still need to enable bifurcation on the right slot, you'll want to use 4x4x4x4 in most cases if you split 8x8 you can end up not seeing both depending on how card splits lanes internally. and your nvme won't get saturated over x4 pcie3 anyway. 

     

    For booting you'll need to use a custom bios. But if it's vmware just stick it on USB and it'll be fine. 

  3. 2 hours ago, aidenpryde said:

    Just came across this thread as I'm looking to do some NVMe caching at some point here and don't want to use up multiple PCI-E slots.

     

    Are you saying that you mod the BIOS first, then you upgrade to the official 3.4 BIOS?

     

    Or does the official unmodded 3.4 BIOS allow PCI-E bifurcation?

     

    I have a X9DR3-F which is different than yours I think, not that I think it matters in this case.

    bios firmware is modded to allow for nvme boot, if you're only planning to use nvme for cache pool (like what I have), then you can use the official bios. I never bothered with nvme boot and also it's not needed for unraid since we boot from usb anyway.

     

    after all this supermicro ended up adding the official bios to their download pages so you can get it legit from them if you don't trust my links etc.

    • Like 1
  4. 18 hours ago, justjosh said:

    Where did you get this from? Have you tested it with the Asus Hyper M2 or some other card?

     

    I have already sold off my Hyper M2 but if someone can confirm this works in particular with the M2 I don't mind getting a new one.

    from Supermicro support, since then I've actually got a newer 3.4 stable, same link, subfolder "3.4 official", had some say they don't trust me or whatever, included email conversation from the tech in email.

     

    Also yeah I ran 3.3 beta which worked flawlessly with m2 hyper x4, flashed to 3.4 as well without issues, 2 weeks uptime without issues so far, with each m.2 drive saturating 1.2gbps reads (sn750 1tb)

     

    also not sure if it affects nvme, but these and samsung 250gb's I have tested don't break parity like some flash ssd's were reported to.

     

    I will add the 3.4 nvme boot modded version as well, I don't need it but I know some do want the option.

  5. On 12/11/2019 at 9:27 PM, justjosh said:

    Hi all,

     

    I currently possess a X9DRi-F board and a Hyper M.2 card but after extensive testing and research, it seems that it is impossible to make bifurcation work with this combination even though the BIOS clearly has such an option.

     

    As a result, I have decided I would need to source for another motherboard. Everything else I have runs on the X9 infrastructure so it would be great if the suggestions were for X9.

     

    I also need 3x x16 slots and 1x x8, preferably with the x16s spaced out as I am planning to install double slot width cards.

     

    Alternatively, if anyone managed to make the Hyper M.2 card show 4 drives with the X9DRi-F, I would also love to hear about it.

     

    Thanks!

    confirmed working bios for x9dr3(i)-f, beta dated Feb'20, also including nvme modded for bootable nvme.

     

    https://mega.nz/folder/q0sWiAya#ibXw5vbz08m8RXbaS3IB1A

  6. 17 hours ago, Dyon said:

    Hello, by default every 300 seconds the container sends out a ping to one.one.one.one by default. If this domain is unreachable the container will shutdown, and normally automatically restart. This normally happens if the connection with the VPN is not working anymore.

    Could you verify the following:

    Click the jackettvpn Docker, select Edit, in the top right change to slider to Advanced View and check if Extra Parameters has the following:

    `--restart unless-stopped`

     

    This makes it so that the container automatically restarts if it goes offline when the domain is unreachable.

     

     

    makes sense,

     

    can confirm, --restart unless-stopped wasn't there, I've added now and will see how it behaves.

     

    thanks

  7. okay, so I think I'm good now, ended up booting back into full array with md14 mounted, moved all data off of it without issues, then went back into maintenance and could now run -v, once complete I've started array again and seems good fine for last 20mins or so, crisis averted for now. if it didn't -v I'd probably -L and just reformat it if it corrupts the filesystem.

  8. 47 minutes ago, trurl said:

    What did it actually say?

     

    The -n (nomodify) flag means check but don't repair anything.

    After looking around forums a bit more came across similar post,

    mod advised to run against /dev/mapper/md# if drives are encrypted (all of mine are btw), then to -L it.

     

    which spits out this output, same as webui

    image.png.3626c57d8f7b855664a4f95f75d18167.png

     

    Clearly it wants me to run with -L but that sounds destructive? It's a 12tb mostly filled, I'd really hate to lose it, at this point I'd almost be better to remove it and let parity emulate it probably and move data around before reformatting and adding back to array?

  9. 1 minute ago, trurl said:

    What did it actually say?

     

    The -n (nomodify) flag means check but don't repair anything.

    running webgui with a -v flag gives this output;

     

    Phase 1 - find and verify superblock...
            - block cache size set to 6097840 entries
    Phase 2 - using internal log
            - zero log...
    zero_log: head block 6247 tail block 6235
    ERROR: The filesystem has valuable metadata changes in a log which needs to
    be replayed.  Mount the filesystem to replay the log, and unmount it before
    re-running xfs_repair.  If you are unable to mount the filesystem, then use
    the -L option to destroy the log and attempt a repair.
    Note that destroying the log may cause corruption -- please attempt a mount
    of the filesystem before doing this.

     

  10. 8 minutes ago, trurl said:

    Also, see this section on that same wiki page:

     

    https://wiki.unraid.net/Check_Disk_Filesystems#Drive_names_and_symbols

    okay, ye makes sense, so run it against md# instead, I've gone back to maintenance and I'm getting the errors in edit, md14 is saying drive busy and webui refuses to run beyond -n/-nv

     

    I've tried to run repair, but it never got past saying magic number failed and trying to find secondary superblock

     

    which outputs this if it helps

     

     

    Phase 1 - find and verify superblock...
    Phase 2 - using internal log
            - zero log...
    ALERT: The filesystem has valuable metadata changes in a log which is being
    ignored because the -n option was used.  Expect spurious inconsistencies
    which may be resolved by first mounting the filesystem to replay the log.
            - scan filesystem freespace and inode maps...
    Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x3a381e28/0x1000
    Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x74703c48/0x1000
    btree block 1/1 is suspect, error -74
    btree block 2/1 is suspect, error -74
    bad magic # 0xdaa0086c in btbno block 1/1
    bad magic # 0x2fdfba35 in btbno block 2/1
    Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x3a381e30/0x1000
    btree block 1/2 is suspect, error -74
    bad magic # 0x419e48e9 in btcnt block 1/2
    agf_freeblks 122094523, counted 0 in ag 1
    agf_longest 122094523, counted 0 in ag 1
    Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x74703c50/0x1000
    btree block 2/2 is suspect, error -74
    bad magic # 0xa8692ca5 in btcnt block 2/2
    agf_freeblks 121856058, counted 0 in ag 2
    agf_longest 121856058, counted 0 in ag 2
    Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x3a381e38/0x1000
    btree block 1/3 is suspect, error -74
    Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x74703c58/0x1000
    bad magic # 0x639e272e in inobt block 1/3
    btree block 2/3 is suspect, error -74
    bad magic # 0x796a2ce3 in inobt block 2/3
    Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0xaea85a78/0x1000
    btree block 3/3 is suspect, error -74
    bad magic # 0x15f1f03 in inobt block 3/3
    sb_ifree 59, counted 44
    sb_fdblocks 2926555418, counted 2681574888
            - found root inode chunk
    Phase 3 - for each AG...
            - scan (but don't clear) agi unlinked lists...
            - process known inodes and perform inode discovery...
            - agno = 0
            - agno = 1
            - agno = 2
            - agno = 3
            - agno = 4
            - agno = 5
            - agno = 6
            - agno = 7
            - agno = 8
            - agno = 9
            - agno = 10
            - agno = 11
            - agno = 12
            - agno = 13
            - agno = 14
            - agno = 15
            - agno = 16
            - agno = 17
            - agno = 18
            - agno = 19
            - agno = 20
            - agno = 21
            - agno = 22
            - agno = 23
            - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
            - setting up duplicate extent list...
            - check for inodes claiming duplicate blocks...
            - agno = 0
            - agno = 1
            - agno = 4
            - agno = 3
            - agno = 14
            - agno = 22
            - agno = 8
            - agno = 9
            - agno = 5
            - agno = 6
            - agno = 10
            - agno = 12
            - agno = 15
            - agno = 16
            - agno = 13
            - agno = 17
            - agno = 18
            - agno = 2
            - agno = 21
            - agno = 7
            - agno = 19
            - agno = 20
            - agno = 23
            - agno = 11
    No modify flag set, skipping phase 5
    Inode allocation btrees are too corrupted, skipping phases 6 and 7
    Maximum metadata LSN (904557511:-555599277) is ahead of log (1:6247).
    Would format log to cycle 904557514.
    No modify flag set, skipping filesystem flush and exiting.

     

  11. 5 minutes ago, trurl said:

    You can't repair the sdX device, and you shouldn't repair the sdX1 partition of a disk in the array, or you will invalidate parity. You must run it on the md# device.

    If you do it from the webUI then it will do it correctly.

    I see, the doc specifies either can be used, I'll try now with md# instead, to confirm if I want to run it from webui I should just change -nv to -v?

     

    trying to run from webui now only displays this;

    image.png.24b3d15d1f29c22cb0473588c8bd7b27.png

     

    not allowing any actions

     

    using md# also returns device is busy

     

    image.png.ac3458509b83a692e8b09f6e19b2a6cd.png

  12. xfs_repair in webgui, after 2nd run of -nv said, "just start the array up bro, it'll be good", as doubtful as I was, I tried it and so far... it seems okay. but scrubbing btrfs cache as well just in case.

     

    edit;

     

    ye okay, spoke too soon.

     

    image.thumb.png.b1953c8cc8d15c63b8afb296ec02b543.png

     

    thoughts on best action? I'll try to unmount again and repair but doubt it'll work

  13. So had some heat issues today, some disks hit 60c before I realised.

     

    Anyway, I sorted but found some strange behaviour, but primary io write errors from smb, so loaded up logs and found a lot of issues. took array down and up again, no go. rebooted in maintainence and found disk14 reported xfs_check issues, but then after leaving it for a while and checking logs it's filled with below.

     

    image.thumb.png.49052d0aaf1fe8a56b8c6357601ed6db.png

     

     

    So.... how bad is it?  looking at docs I should run xfs_check -V /dev/sdX ,which I tried with disk14 which was only one that actually reported issue in webgui using xfs check.

     

     

    But that's been running for past 15mins trying to find 2ndary superblocks in filesystem

    image.thumb.png.22ed0cbd01a74fba946aa31d5a6398c8.png

     

     

     

    So, help please :S

  14. 28 minutes ago, ich777 said:

    It will nothing happen because you have to input something and because it's a container it wouldn't work.

    You can also create it on OSX and it will work.

     

    Create a world on your windows machine named 'world' and with your preferred options, then i recommend deleting the whole container including the created directory in appdata.

    Then redownload the container from the CA App wait for it to fully startup, then stop it and delte the two files in your Worlds folder and replace it with the 'world.wld' file generated from your windows machine.

    Okay, ye so that worked, didn't know actual world name during generation mattered. got  3 instances running side by side now without issues. If you get some time it'd be nice to sort that downloading delay though, world is 2mb, but takes it good 10mins before it proceeds to extract it

    • Like 1
  15. Just now, ich777 said:

    Yes because it's broken in the game itself when you specify it in the serverconfig.txt (and that's why i had to do it that way, otherwise I had to pull the container of the CA APP).

     

    You must match the world to that name that is in the serverconfig.txt or you rename it in the serverconfig.txt.

    Hmm, so they match otherwise as you said it'd complain about it missing, but still fails to starts, fwiw I'm generating local worlds on windows client. If I just copy it over it goes back to the same error as before, when run straight parameters from container instead of using -config x.txt I get that weird n world, d <number> delete world in log, left it for 30mins and nothing happened.

  16. 2 minutes ago, ich777 said:

    I think there must be something wrong with the download of the world.

     

    Have you generated the world with the same name as in the serverconfig.txt? It has to be the same!

     

    That's likely because you've created the world with another name as in the serverconfig.txt and can't find it.

     

    I have to look into it another day...

    World generation still isn't working in any way, it only downloads it once if path is missing.

     

    World I tried with was different name originally (just renamed file to match serverconfig.txt), I'll give that a try.

  17. On 6/12/2020 at 10:56 AM, ich777 said:

    All Terraria Containers are now fixed and should be working as usual. ;)

    Thanks, however still not having it for me :(

     

    Now it it's stuck on downloading worlds, looks like it pulled a complete .zip but then does nothing with it by the looks, extracting it manually and restarting container, just goes back to the same error as before.

     

    new container from template;

     

    ---Checking if UID: 99 matches user---
    ---Checking if GID: 100 matches user---
    ---Setting umask to 000---
    ---Checking for optional scripts---
    ---No optional script found, continuing---
    ---Starting...---
    ---Version Check---
    
    ---Terraria not found, downloading!---
    ---Successfully downloaded Terraria---
    ---Prepare Server---
    ---No serverconfig.txt found, downloading...---
    ---No World found, downloading---

     

    restarted;

     

    Session terminated, killing shell...�'---Checking if UID: 99 matches user---
    usermod: no changes
    ---Checking if GID: 100 matches user---
    usermod: no changes
    ---Setting umask to 000---
    ---Checking for optional scripts---
    ---No optional script found, continuing---
    ---Starting...---
    ---Version Check---
    
    ---Terraria Version up-to-date---
    
    ---Prepare Server---
    ---Server ready---
    ---Checking for old logs---
    ---Start Server---
    Error Logging Enabled.
    
    �[?1h�=�[6n�[H�[JTerraria Server v1.4.0.5
    
    �[H�[J
    Server crash: 6/14/2020 6:09:07 PM
    System.NullReferenceException: Object reference not set to an instance of an object
    at Terraria.Main.WriteFancyWorldLoadErrorToConsole () [0x00005] in <0ebea07e9a804a06a9f1dd17904b9c9c>:0
    at Terraria.Main.DedServ () [0x00b21] in <0ebea07e9a804a06a9f1dd17904b9c9c>:0
    at Terraria.Program.LaunchGame (System.String[] args, System.Boolean monoArgs) [0x000ac] in <0ebea07e9a804a06a9f1dd17904b9c9c>:0
    
    Please send crashlog.txt to support@terraria.org
    Terminated

     

     

    edit;

     

    okay, so I just though it might be doing some magic is background and not outputting into logs, so I left it for like 15minutes and it generated 1.4.0.5 world as expected, hmmm I'll try a few more and see if it likes it.

     

    Also, master mode? can I just set difficulty 2?

     

    edit2;

    Hmm... so it didn't work again, not sure why it worked before I guess.

     

     

    edit3;

    Okay, so looks like it downloads ideantical world, named world.wld server config specifies a world1.wld, renaming makes it work. but this doesn't generate new worlds.... it just uses whatever one it downloads. Commenting out world load so it creates one doesn't work either, get's stuck with below;

     

    ---Prepare Server---
    ---Server ready---
    ---Checking for old logs---
    ---Start Server---
    Error Logging Enabled.
    
    [?1h=[6nTerraria Server v1.4.0.5
    
    1 world
    n New World
    d <number> Delete World

    Copying a locally created world doesn't work either and spams the same errors as before object reference not set

  18. 18 minutes ago, ich777 said:

    This is not an error that I get when I'm installing the container/game and also this shouldn't affect the game since this is the real problem:

    
    Server crash: 6/7/2020 7:43:38 PM
    System.NullReferenceException: Object reference not set to an instance of an object

    I will look into it as soon as possible but I'm very busy at the moment (I think i will fix it this week but give me a few days).

    To confirm, if I take your template as is, it works fine, it generates a 1.3.5.3 world, and I can just upgrade server to 1.4.0.5 but I'd like to generate a new world in 1.4 for a few reasons (and expert + medium/large but that's something else, on side topic, I assume master and journey worlds can also be created by incrementing values further?).

     

    For now I'm just running it locally, also tried creating the world locally and moving it over, which didn't work either, with same error.

     

    and yeah no rush, I appreciate your work on this.

  19. 1 hour ago, ich777 said:

    Can you please be a little bit more specific?

    Is this the normal Terraria Server or a mod server?

     

    EDIT: I tried it on my server and got almost the same error but not completely, since the last major update of Terraria almost all of my containers are messed up, i will look into it as soon as I got a little bit spare time...

    This is vanilla, I tried few more versions since, but could only get it to generate a 1.3.5.3 world. Tried few more modes, small medium large, all giving the same error, I'm not great at reading syntax but seems like it's just expecting a integer early on probably from some variable, or from initial error where some var is just not set at all.

  20. Hey, trying to run terraria server but having some issues, docker installs and created fine, but it creates a 1.3.5.3 world, I tried changing version to 1.4.0.5 or blank which updates fine to latest, but fails to create a world and crashes with this error.

     

    Tried creating multiple dockers but could only get it to create a world when the default version value is used.

     

    ---Starting...---
    /opt/scripts/start-server.sh: line 5: [: : integer expression expected
    ------------------------------------------------------------------------------------
    ---------------------------------W A R N I N G--------------------------------------
    ---The variable Prefered Version doesn't work anymore for Version 1.4.0.2 and up----
    
    ---The conatainer will always pull the latest version if set to 1.4.0.2 or higher---
    
    ------------------------------------------------------------------------------------
    ---Version Check---
    
    ---Terraria Version up-to-date---
    
    ---Prepare Server---
    ---Server ready---
    ---Checking for old logs---
    ---Start Server---
    Error Logging Enabled.
    
    [?1h=[6n[H[JTerraria Server v1.4.0.5
    
    [H[J
    Server crash: 6/7/2020 7:43:38 PM
    System.NullReferenceException: Object reference not set to an instance of an object
    at Terraria.Main.WriteFancyWorldLoadErrorToConsole () [0x00005] in <0ebea07e9a804a06a9f1dd17904b9c9c>:0
    at Terraria.Main.DedServ () [0x00b21] in <0ebea07e9a804a06a9f1dd17904b9c9c>:0
    at Terraria.Program.LaunchGame (System.String[] args, System.Boolean monoArgs) [0x000ac] in <0ebea07e9a804a06a9f1dd17904b9c9c>:0
    
    Please send crashlog.txt to support@terraria.org
    Terminated
    [?1l>[39;49m'---Checking if UID: 99 matches user---
    usermod: no changes
    ---Checking if GID: 100 matches user---
    usermod: no changes
    ---Setting umask to 000---
    ---Checking for optional scripts---
    ---No optional script found, continuing---
    ---Starting...---
    /opt/scripts/start-server.sh: line 5: [: : integer expression expected
    
    Session terminated, killin