Jump to content

tjb_altf4

Members
 View Profile  See their activity

  • Posts

    1,388

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Report Comments posted by tjb_altf4

    Unraid OS version 6.10.0-rc5 available

    in Prereleases

    Posted · Edited by tjb_altf4

    2 hours ago, fat_flying_pigs said:

    Has rc4/5 changed the behaviour of ctrl+clicking the unraid tabs? Seems like now on all browsers I use (windows chrome, mac firefox/safari), it opens the target link in a new tab (as it should), but the original tab also navigates to that link (as opposed to staying on the same tab).

    Looks like the onclick behaviour has been changed slightly, looks like its trying to manage cookies better when navigating links, but maybe browser security setting aren't liking it?

     

    My popup blocker stops ctrl+clicks for those links, even though the unraid ui is greenlit in adblocker

    [6.10.0-rc4] - docker console and log window no longer simultaneously available

    in Prereleases

    Posted · Edited by tjb_altf4

    8 hours ago, bonienl said:

    This is expected behavior, due to the ttyd implementation we use, not a bug.

    Seems to be a limitation due in how we are calling ttyd?
    If we add a salt (time) to the object name like the vanilla webterminal does (which allows multiple sessions), that should get around the issue?

      

    openTerminal('ttyd','Web Terminal '+d.getTime(),'');

     

    If that's not possible, I did find a workaround, it looks like you can use simply use the URL to create as many new sessions as you want, i.e. http://jaskier.local/logterminal/DiskSpeed/ creates a new terminal session, its just not as elegant as using the GUI as we do now.

    • Like 1

    Docker templates revert when docker checks for update.

    in Prereleases

    Posted

    has stung me many a time, I thought I was going nuts for a while... deleted fields will return on docker update or if author updates template (I think those were the scenarios).

     

    Workaround: edit the template XML and delete the <TemplateURL> field or set to false 

     <TemplateURL>false</TemplateURL>

     

    Make sure to ignore FCP if it asks you to add a missing URL from template, or it will be readded.

     

     

    • Thanks 1

    Windows VM much slower after upgrade 6.10.RC[1-2] - Cyberpunk 2077 Videos

    in Prereleases

    Posted

    I noticed in the libvirt log that it is repeatedly trying to open remote connections from your other server, this only happens in the 6.10rc2 logs. 

    This might not resolve your issue, but worth removing these isos from the VM to rule it out in any case.

      

    2021-11-03 10:36:32.851+0000: 5854: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 10:36:32.851+0000: 5858: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 10:36:34.697+0000: 5855: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 10:36:34.697+0000: 5854: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 10:36:34.714+0000: 5858: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 10:36:34.715+0000: 5857: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 11:40:38.970+0000: 5858: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 11:40:38.971+0000: 5857: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 11:40:39.724+0000: 5856: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 11:40:39.725+0000: 5855: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 11:40:39.742+0000: 5854: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 11:40:39.743+0000: 5858: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 20:29:30.344+0000: 5857: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 20:29:30.345+0000: 5856: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 20:29:30.991+0000: 5858: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 20:29:30.991+0000: 5857: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 20:29:31.009+0000: 5856: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 20:29:31.010+0000: 5855: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 20:29:35.271+0000: 5854: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 20:29:35.272+0000: 5858: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory
2021-11-03 20:29:35.288+0000: 5857: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/AOMEI_Windows.iso': No such file or directory
2021-11-03 20:29:35.289+0000: 5856: error : virQEMUFileOpenAs:11262 : Failed to open file '/mnt/remotes/BABYBUS-GREEN_isos/template/iso/virtio-win-0.1.189-1.iso': No such file or directory

     

    [6.9.2] Creating new pool - cannot be named with share name error?

    in Stable Releases

    Posted

    Renaming 'system' share to something else allowed me to create the 'system' pool.

    From there I could migrate the files in the existing system share to system pool, and delete the original 'system' share.

     

    This wasn't really a bug, but just an annoying series of steps and my lack of understanding on collisions this warning was protecting me from.  I believe @trurl was spot on with the assessment of it being an SMB export conflict IF the pool was used as a disk share.

     

    Thanks.

    [6.9.2] BTRFS raid0 pool not showing full capacity

    in Stable Releases

    Posted

    44 minutes ago, JorgeB said:

    For some reason that I can't find the 2 new devices weren't added to the pool, it's just 2 devices, hence the capacity, stop array, unassign both new pool members, start array, stop array, re-assign both new members, start array and post new diags.

    They were added on the previous boot, but array wasn't started (related to the other bug report I guess).

     

    Still, this log entry seems to know it should have been 4 devices, maybe some weirdness due to reboot and possible drive allocation changes? 

    Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool TotDevices: 2
Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool NumDevices: 4
Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool NumFound: 2
Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool NumMissing: 0
Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool NumMisplaced: 0
Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool NumExtra: 2
Oct  9 17:12:24 fortytwo emhttpd: /mnt/chiapool LuksState: 0

     

    Thanks for the suggestion, I'll do that as soon as I have the chance.

    [6.9.2] - CPU usage stuck at 100% (2 core/thread)

    in Stable Releases

    Posted · Edited by tjb_altf4

    So while this is still an ongoing issue (still on 6.9.2), it seems to have settled down since I started using my VMs a lot recently (even once they are shutdown).

    Current usage with VM running:

    image.png.097f0c64992ec6c95cb659d0dfd0daa8.png

     

    All I can think is that there is some hardware that isn't being initialised properly until the VM starts... kind of like what we see with GPUs.

     

    My theory is the 100% usage should return on next Unraid reboot, and then disappear again once I start a VM... I'll try and test this theory out in the next week.

    [6.9.2] - User share drive calculations includes pools not participating in user shares

    in Stable Releases

    Posted · Edited by tjb_altf4

    28 minutes ago, jonathanm said:

    The only exception is if the disk is globally excluded from user shares.

    It's a disk share (pool share technically lol) as it has been globally excluded from user shares. 

    image.png.3df48e4dba521d2cdfab8ba19bde426e.png

    The disk share happens to have a folder on it of the same name as a user share.

    The files in the folder "chia" on the Scratch pool do not appear in the user share "chia" (expected behavior), however it is included for "chia" user share size calculations (unexpected behavior).

    [6.9.2] - CPU usage stuck at 100% (2 core/thread)

    in Stable Releases

    Posted

    8 minutes ago, SyberWraith said:

    i'm experiencing this as well, since i'm running a ryzen i made sure to add the lines to the go file, and i did try a couple things suggested about finding the interrupt that has high usage, but none showed up. Also tried setting the "CPU Scaling Governor" to On demand, haven't tried performance yet, but so far nothing seems to help. it's making reboots/shutdowns difficult as it seems to hang on properly shutting down the array.

     

    i've attached my diag file in case it has something that might help

    titan-fs-diagnostics-20210505-1516.zip 137.71 kB · 0 downloads

    Do you still see the 100% usage when the array is stopped?

×
×
  • Create New...