Jump to content

tlrmcknz

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by tlrmcknz

  1. On 4/21/2023 at 2:43 PM, KluthR said:

    I need some clarification…

     

    do we talk about ca.backup2? If yes, your exclusion works as expected.
     

    if not, then we talk about appdata.backup. Post in the right thread with the debug log attached, please

    Referring to this post: 

    Where I had an exclusion of "/mnt/user/appdata/data" but that was causing "/mnt/user/appdata/ms-sql-server/data" to be excluded from the backup.

  2. On 4/13/2023 at 10:37 AM, KluthR said:

    Hmm.

     

    cant tell. I dont think it has a bug. In any case, I ask you to try it within the new appdata.backup plugin as soon as Unraid 6.12 is done. If the issue persists, Ill check it.

    Update on this: Checked the backup after removing that path exclusion and it had the data folder as expected. So looks like there's a bug in the path matching, applying the data subfolder exclusion to all other folders.

  3. I seem to be having an issue with entire appdata subfolders missing.

     

    [03.04.2023 03:03:06] Stopping MS-SQL-Server...  done! (took 1 seconds)
    ...
    [03.04.2023 03:12:40] Backing Up: ms-sql-server
    [03.04.2023 03:13:38] Verifying Backup ms-sql-server
    ...
    [03.04.2023 03:24:53] Starting MS-SQL-Server... (try #1)  done!

     

    But inside the archive, there's no ms-sql-server\data folder, yet one exists on the filesystem and has the same permissions as ms-sql-server\log (which does get backed up in the archive properly)
     

    Filesystem:

    drwxrwxr-x 1 root   root    28 Dec 12 14:30 ./
    drwxrwxrwx 1 nobody users 2076 Mar 10 15:46 ../
    drwxrwxr-x 1 root   root   832 Mar 21 11:37 data/
    drwxrwxr-x 1 root   root  5234 Apr 10 03:27 log/
    drwxrwxr-x 1 root   root    22 Dec 12 14:30 secrets/

     

    Archive:

    image.png.1f87e2431fa6911872d732207443766c.png

     

    Any idea what's going on here?

  4. Would like a second opinion on the health of this drive and whether or not I should rebuild it onto itself.

     

    Currently doing a read check on the array after an unplanned power outage. The read check stopped on it's own at about 50% and that's when I noticed the disk was disabled. I resumed the read check and it's now at about 58%.

     

    Attached is the short test log. The extended test seemed to still be at 10% after 30-60mins, so I didn't let it complete or run it again (yet).
    Also attached diagnostics that logged when the parity check errors started occuring.

     

    Thanks muchly.

    ryzen-smart-20220201-1447.zip

    ryzen-diagnostics-20220201-1514.zip

    ryzen-smart-20220201-2221.zip

  5. Did you ever make any headway on this? Saw something extremely similar today for me:

     

    Short hardware list:

    MB: ASRock B450 Pro4

    CPU: AMD Ryzen 7 1800X

    GPU1: Nvidia GeForce GTX 1650

     

    My BIOS cstate = DISABLED

    Slightly truncated kernel log from remote syslog:

    general protection fault: 0000 [#1] SMP NOPTI
    CPU: 3 PID: 21050 Comm: nzbget Tainted: P        W  O      4.19.107-Unraid #1
    Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.20 06/18/2020
    RIP: 0010:nf_nat_setup_info+0x365/0x666 [nf_nat]
    Code: ed 75 23 45 8b 17 48 8d 7c 24 58 b9 0a 00 00 00 48 8d 74 24 30 f3 a5 41 f6 c2 01 0f 85 c4 00 00 00 e9 25 02 00 00 8a 44 24 56 <41> 38 45 46 74 15 4d 8b ad 98 00 00 00 4d 85 ed 74 c7 49 81 ed 98
    hrtimer: interrupt took 2467865 ns
    RSP: 0018:ffff88881e6c36d8 EFLAGS: 00010206
    general protection fault: 0000 [#1] SMP NOPTI
    CPU: 3 PID: 21050 Comm: nzbget Tainted: P        W  O      4.19.107-Unraid #1
    Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.20 06/18/2020
    RIP: 0010:nf_nat_setup_info+0x365/0x666 [nf_nat]
    Code: ed 75 23 45 8b 17 48 8d 7c 24 58 b9 0a 00 00 00 48 8d 74 24 30 f3 a5 41 f6 c2 01 0f 85 c4 00 00 00 e9 25 02 00 00 8a 44 24 56 <41> 38 45 46 74 15 4d 8b ad 98 00 00 00 4d 85 ed 74 c7 49 81 ed 98
    hrtimer: interrupt took 2467865 ns
    RSP: 0018:ffff88881e6c36d8 EFLAGS: 00010206
    RAX: ffff88813f034906 RBX: ffffffff81e91080 RCX: 0000000086ee2de1
    RDX: ffff8887d1180000 RSI: 0000000045680e5d RDI: 0000000087f6373f
    RBP: ffff88881e6c37b0 R08: ffff88881e6c3708 R09: ffffffff81c8a6e0
    R10: ffff8884c1518388 R11: 0000000000000000 R12: 0000000000000000
    R13: 04fa37f2f9f462ee R14: ffff888050b64b40 R15: ffff88881e6c37c4
    FS:  0000153f3737bb20(0000) GS:ffff88881e6c0000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 0000153f36cc6fd0 CR3: 00000005711c0000 CR4: 00000000003406e0
    Call Trace: 
    ...

     

  6. I have a Vega 56 gpu in my secondary pcie slot, with an nvidia card in the primary. Up until recently, I never got the reset bug. I can't explain why not, because I don't recall applying any of the patches or scripts that would fix/prevent it. I could start and stop the vm 20 times a day without issues. 

     

    I decided I wanted to try the amd gpu in the primary slot since I got a new case that would fit it better, so I flipped them around. I couldn't get this to work, even after dumping the bios and supplying it, so I reverted it all back. 

     

    After doing that, I am now getting the reset bug every time. About 30 mins after shutting down the vm, the gpu fans go full tilt and I get the error 127 trying to start the vm again. 

     

    Anyone have any ideas how I can get back to that initial state? I'm clueless. 

  7. Currently facing an issue where hardware transcoding isn't working after a random amount of time. On my samsung tv, the logs were showing that the transcoder was dead. Streaming from a pc, I don't see anything relevant in the logs. Thought it might be due to the transcoding directory being full, but checked and changed a couple ways and that doesn't seem to be related.

    Seemed to occur out of the blue on 6.8.2 with no relevant changes on my end, so I upgraded to 6.8.3 but the issue still occurs.
    Attaching log file from session when streaming to pc where the video just halts (like it was paused, no errors on screen)

     

    GPU is a GTX 1650. This is out output of "watch nvidia-smi" even when the video is halted:
     

    +-----------------------------------------------------------------------------+
    | NVIDIA-SMI 440.59       Driver Version: 440.59       CUDA Version: 10.2     |
    |-------------------------------+----------------------+----------------------+
    | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
    | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
    |===============================+======================+======================|
    |   0  GeForce GTX 1650    Off  | 00000000:0C:00.0 Off |                  N/A |
    | 40%   35C    P0    19W /  75W |     76MiB /  3903MiB |      0%      Default |
    +-------------------------------+----------------------+----------------------+
    
    +-----------------------------------------------------------------------------+
    | Processes:                                                       GPU Memory |
    |  GPU       PID   Type   Process name                             Usage      |
    |=============================================================================|
    |    0      3355      C   /usr/lib/plexmediaserver/Plex Transcoder      64MiB |
    +-----------------------------------------------------------------------------+

     

    When streaming from the TV, the nvidia-smi doesn't show anything after the video stops / error is shows on the tv.

     

    Any help would be appreciated.

    Plex Media Server Logs_2020-03-16_12-40-26.zip

×
×
  • Create New...