Jump to content

John_M

Members
  • Posts

    4,729
  • Joined

  • Last visited

  • Days Won

    12

Report Comments posted by John_M

  1. 21 minutes ago, sittingmongoose said:

    So you're saying my most recent diag looks better but still has segfaults?  Can you explain what a segfault could indicate?

    The most recent diagnostics don't have the "conflicting memory types" errors but it has segfaults. A Segmentation Fault is an access violation, i.e. an attempt to access an area of memory in an illegal way, such as trying to write to read-only memory or trying to read memory that belongs to another process. It could be a programming bug or I suppose some table of pointers could be getting corrupted, or a hardware problem. Since your other errors are memory related I'd ask about your RAM. Have you run a MemTest on it? Are you operating it within spec?

  2. 19 minutes ago, sittingmongoose said:

    I am including my diags to see if there are still all the errors you previously saw.

    FWIW, your latest syslog doesn't have any of this

    Nov  4 14:32:07 9900K kernel: x86/PAT: CPU 3/KVM:5062 conflicting memory types a2000000-a3000000 uncached-minus<->write-combining
    Nov  4 14:32:07 9900K kernel: x86/PAT: reserve_memtype failed [mem 0xa2000000-0xa2ffffff], track uncached-minus, req uncached-minus
    Nov  4 14:32:07 9900K kernel: ioremap reserve_memtype failed -16

    which flooded your previous one, but it still conatins segfaults:

    Nov  4 14:51:02 9900K kernel: ffdetect[25520]: segfault at 38 ip 00000000004042af sp 00007ffdde2eeda0 error 4 in ffdetect[403000+c000]
    Nov  4 14:51:02 9900K kernel: Code: 0f b6 6d 00 40 84 ed 75 b7 48 8b 14 24 48 8d 35 ce ad 00 00 bf 01 00 00 00 31 c0 ff 15 92 59 01 00 48 89 df ff 15 c1 5a 01 00 <41> 0f b6 2c 24 40 84 ed 0f 84 9a 00 00 00 4c 8d 35 2c b1 00 00 eb

    Did you ever boot into safe mode?

  3. 1 hour ago, JasonJoel said:

    Microsoft was right on this one.

    This kind of debate is pointless in a section whose purpose is for reporting bugs. It's the way it is because Unraid is a Linux distribution. It is not a bug. If you would prefer it some other way then make a feature request in the appropriate place.

    • Like 1
  4. 6 hours ago, limetech said:

    Probably you have a plugin that is installing perl and along with it an old version of lm-sensors.

    It looks like the Dynamix System Temperature plugin (current version is dated 2019-01-12) is replacing the stock version of sensors-detect with its own:

    Oct 21 19:32:09 Lapulapu root: Verifying package dynamix.system.temp.txz.
    Oct 21 19:32:09 Lapulapu root: Installing package dynamix.system.temp.txz:
    Oct 21 19:32:09 Lapulapu root: PACKAGE DESCRIPTION:
    Oct 21 19:32:09 Lapulapu root: Package dynamix.system.temp.txz installed.
    Oct 21 19:32:09 Lapulapu root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/sensors-detect already exists
    Oct 21 19:32:09 Lapulapu root: plugin: creating: /usr/sbin/sensors-detect - copying LOCAL file /boot/config/plugins/dynamix.system.temp/sensors-detect
    Oct 21 19:32:09 Lapulapu root: plugin: setting: /usr/sbin/sensors-detect - mode to 0755
    Oct 21 19:32:09 Lapulapu root: plugin: running: anonymous
    Oct 21 19:32:09 Lapulapu kernel: it87: Found IT8603E chip at 0x290, revision 1

    I'll try safe mode.

     

    EDIT: Without the plugin I see a different output from sensors-detect

    root@Lapulapu:~# sensors-detect 
    # sensors-detect revision $Revision$

     

  5. 1 hour ago, Johan1111 said:

    there is any way to forward the local ip trough DMZ and access Unraid from the internet or from a domain name. that would be awesome!

    If you want a safe way of accessing your server from outside, scroll to the top of this page and read the section entitled WireGuard support, then follow the link to the guide.

  6. 13 minutes ago, testdasi said:

    I think the scaling on your MacBook affects it too. When I zoom out to 90%, it's back to 3 columns.

    There isn't any scaling. It isn't a Retina display. It's 1:1.

    jbartlett says he's using -rc1. I'm using -rc3, which is the subject of this thread,

  7. 40 minutes ago, testdasi said:

    I run Firefox so the width of the window is a certain number of pixels smaller than 1920px (closer to 1800 or so).

    My screen grab was from Firefox on a 1280 pixel wide display (non-Retina 13-inch MacBook Pro) with a vertical scrollbar on the right of the window, so significantly narrower than 1920. Which theme are you using?

     

    EDIT: I switched temporarily to Gray theme and saw two columns, as you describe. Now back on White theme, with three columns.

     

    • Thanks 1
  8. 26 minutes ago, testdasi said:

    Bug on UI:

    When the browser window is maximised, the Docker Containers section used to display 3 columns of icons but now only displays 2, aligned to the left margin of the box. Perhaps each docker icon is a little wider or something?

    Are you referring to the Dashboard page? Perhaps you need to give more detail because I'm seeing three columns, using the White theme.

     

    1330561096_ScreenShot2019-10-22at20_12_45.png.5b05be7b16ea735e4bd9523e709c839b.png

     

     

  9. 8 hours ago, Benson said:

    Those with "user-set" means changed, I simple set all in 10x ( no evaluate ). Some discussion post your may ref. too.

     

    s.PNG.0ef8e2388955c575f3392ba15735748d.PNG

    The value of 800 doesn't make sense for md_queue_limit. According to the GUI Help the valid range is 1 to 100 as it's specified as a percentage.

  10. 1 hour ago, Frank1940 said:

    Any chance one of you MAC users who have solved the problem could start a thread in the General Support sub-forum and explain the ins-and-outs of what is going on, the gotcha's and the way to set it up.. That way, it could be made a 'sticky'... 

    I already wrote one for AFP some time ago and if anyone wants to use SMB there's a guide here: https://wiki.unraid.net/UnRAID_6/Configuring_Apple_Time_Machine

    and it's stickied here:

     

    • Thanks 2
  11. 6 minutes ago, meep said:

    I note deprecation of AFP from 6.9.

    Is there any impact on maintaining TimeMachine volumes?

    You'll need to use SMB instead of AFP and turn on Enable enhanced macOS interoperability. It should be fine for modern Macs running recent versions of macOS (Sierra and later). Not for old Macs running old versions of OS X though. It affects me but I'm not complaining as I knew it was coming and I've switched over to using dedicated USB-connected 2.5-inch hard disks for Time Machine purposes. That has improved Time Machine reliability and also freed up server space.

    • Thanks 1
  12. 2 minutes ago, jbartlett said:

    Just as a FYI, I can't actually tell what's bolded and what's not.

    I find it easier to tell the difference with the light theme. That's what I normally use but I switched to dark temporarily and found that it's difficult to see the difference between bold text and regular.

    • Like 1
  13. 3 minutes ago, Niklas said:

    The release notes say 1 hour but seems to not work. 

     

    In the future, I would also like to see "keep me signed/logged in" selection to always be logged in. 

    I don't recall doing anything to stay logged in. I would find it very annoying to be logged out automatically after 1 hour.

  14. 22 minutes ago, eagle470 said:

    In 6.7.2 when powering on the system, I have the array set to auto start. It always took less than 30 seconds for the array to auto start, I had to wait for more than a minute after upgrading to 6.8-rc1 for everything to come online. It's not a HUGE issue per say, but I thought the change was worth noting. Let me know what trouble shooting steps you'd like to see.

    It wouldn't surprise me if the first start-up immediately after an upgrade takes a little longer. Are subsequent start-ups the same or faster?

  15. 8 minutes ago, Darqfallen said:

    No I didn't.

    Don't worry. I don't see anything incriminating in there. What I do see is that sdb (a MyPassport drive - connected by USB?) is causing a few problems by not responding when it's expected to. Unplugging it might help. Other than that random restarts could be caused by overheating, power supply problems or bad hardware.

  16. What should the disk tunables enable_NCQ and nr_requests be set to in this version? I made notes before I upgraded and they were previously set to Auto and 128, respectively. Now they are set to Auto and Auto. The GUI help suggests that Auto NCQ uses the disks' default (which amounts to a queue length of 32) but I always thought that Unraid preferred NCQ to be off (a queue length of 1) because Linux handles queueing better than the disks' firmware. So has the meaning of Auto changed for that tunable?

×
×
  • Create New...