limetech

Administrators
  • Posts

    10185
  • Joined

  • Last visited

  • Days Won

    196

Report Comments posted by limetech

  1. I would not use windows 'hosts' file since that is ignored by many browsers and if you forget about that entry and your IP address changes in the future it can be very puzzling what's happening.

     

    A question to those seeing this issue:  How did you access the server webGUI before?

    That is, what URL was used?

    eg, http://tower.local/

    eg, http://<ip-address>/

    eg, https://<hash>.unraid.net/

    something else?

     

    How about booting in GUI mode - do you see webGUI there?

     

    We created a command to unlock keys from the car.  If you can ssh/telnet into server, or use local webGUI Terminal, type the command:

    use_ssl no  # this will set enable http protocol on your LAN

    or

    use_ssl yes  # this will enable https with self-signed cert on your LAN

    • Thanks 1
  2. 14 hours ago, Tucubanito07 said:

    Is there anything different from the stable to RC8?

     

    Yes, here are the changes (-rc9 was never published):

     

    ## Version 6.10.0-rc9 2022-05-16 (vs. 6.10.0-rc8)


    ### Base distro:

    - curl: version 7.83.1 (CVE-2022-27778 CVE-2022-27779 CVE-2022-27780 CVE-2022-27781 CVE-2022-27782 CVE-2022-30115)
    - intel-microcode: version 20220510

     

    ### Linux kernel:

    - Linux 5.15.40-Unraid

     

    ### Management:

    - emhttpd: fix: changing any user password too enthusiastically logged out all browser sessions
    - emhttpd: for 'domains' and 'system' shares, change 'Enable Copy-on-write' default setting from 'No' to 'Auto'
    - emhttpd: change poll_attributes tunable default value from 30 min to 30 sec.
    - webgui: Wireguard: strip ListenPort from file input
      - ListenPort must be unique, let WG generate a random local port instead
    - webgui: Font files update:
      1. Restore clear-sans font
      2. Update bitstream font
      3. Cleanup font files, use only woff format
      4. Adjust css settings

    • Like 1
  3. I don't see anything unusual in the diags.  Starting a parity check on spun-down drives will cause them to spin up via I/O, meaning there is no explicit "spin up" command sent to the drive, instead it spins itself up due to I/O.  The 'Spin-up All' button sends an explicit spin-up command to each drive, well actually it tells the drive to exit 'standby' state.  Maybe the controller or those drives, has some kind of power saving feature whereby spin-up by I/O leaves drive in an "in between" state where it's not at full performance in an effort to save power? - but that doesn't make much sense to me.

     

    Has anyone else seen this issue?

  4. 17 hours ago, Titan84 said:

    @limetech Just wondering, would it make sense if you could please update the default setting to 30 seconds in your next Unraid release and then if users wanted a higher value then they can increase the value. In my case i wasn't aware of the default polling interval being so high and i would guess that many others dont know about this either. I have just gone ahead and changed this to 30 sec now.

    ok

    • Thanks 1
  5. Default poll interval dates back a number of years.  It was chosen to minimize video "glitching" in lower-performance servers - Atom processors, 4G or less of RAM, older hard drives with small caches.

     

    These days I think something like 30 seconds would be better.  Then if someone posts that they are seeing video glitches every 30 sec we can suggest raising the value.

    • Like 1
    • Thanks 2
  6. I've looked at about as much eudev/kernel code as I have appetite for ...

     

    The source of the problem is this:

    On 4/27/2022 at 10:30 AM, JorgeB said:
    root@Tower1:~# cat  /sys/block/nvme1n1/device/serial
            664S107XTPGV

     

    In constructing the /dev/disk/by-id symlink, eudev forms:

    "model" + "_" + "serial"

     

    Then there is additional code in eudev that looks at the overall symlink string, and then it collapses any internal white space to a singe "_" character (this was to fix a different bug).  This is why you see two underscores.

     

    I can see in the nvme device driver where trailing white space is removed, but nothing about leading white space.  Sometime between Linux kernel 5.10.x and 5.15.x there is a nvme driver change that quit trimming leading white space in a serial number.  Probably this is also device-specific, meaning most nvme devices don't have leading white space, and no one noticed the bug which was introduced except for resident storage guru @JorgeB :)

     

    Here's what I'm going to do about this:  In the next release, -rc8, I'm going to look at the './by-id' string and collapse multiple underscores into a single underscore.  This way anyone currently running older version of Unraid OS with an nvme device that has leading spaces in it's serial string, will continue to be identified properly.  However for you, @JorgeB it means you'll have to edit your cfg files to remove that extra underscore...

  7. Thank you for the reproduction details.  Fixed in next release.

    The issue is not that device assignment not saved, rather the device status for single-slot pool was not being handled properly resulting in confusing webGUI.

     

    > P.S. this is somewhat related to this issue, I though the cache config wasn't being saved because of the extra spaces in the device name but it was this issue, so now that I saved the new config I don't really care that the device name has an extra underscore.

     

    Totally unrelated.  Would like to get to the bottom of that one since once 6.10 stable is published issue will probably crop up again.

     

    • Like 1
  8. 1 hour ago, netsrot303 said:

    After upgrading from RC5 to RC7, my wireguard tunnel no longer starts. When I try to activate the inactivity button the display immediately jumps back to inactive.

     

    May  6 17:53:38 Server wireguard: Tunnel WireGuard-wg0 started

    A wireguard process is not running either.

    Please open separate Bug Report for this.

  9. re: ixgbe: there is a build issue with 6.10.0-rc6.

     

    What's happened is both the Intel out-of-tree driver and the Linux in-tree driver are present:

    ./kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko.xz   <- the in-tree driver

    ./updates/drivers/net/ethernet/intel/ixgbe/ixgbe.ko.xz  <- the out-of-tree driver

     

    Not only that, the out-of-tree driver is not for the current kernel version.

     

    Obviously something amiss in our build procedure.  We're working on a -rc7 with the correction.  If you don't use Intel 10Gbit networking, this does not impact your server.

    • Thanks 3
  10. 7 minutes ago, Driconis said:

    Unsuccessfully attempted to upgrade once again from rc3. System appears to boot normally, but after booting it appears as if the array does not start. No drive activity and the WebGUI and SSH is not accessible. I can log in via command line on connected monitor and keyboard. Was previously not able to upgrade to rc4 and rc5 as well. System is a Supermicro A2SDi-8C+-HLN4F with 64 GB with 4 Disk data array and SSD cache drive.

     

    A quick read through the diagnostics indicates that the ethernet is still dropping in and out. Two other flash drives give the same result. Went for a hail mary and tried disabling IPMI as I had a hunch it might be interfering but no luck there as well.

    diagnostics-20220505-1729.zip

     

    Diags show 'ixgbe' is out-of-tree - does not make sense.  Maybe bzmodules did not update?  very odd

  11. 7 hours ago, JorgeB said:

    For now it's only enable for pools, you can have a single device "pool" as long as pool slots are set to >1, though I agree it should be enabled for everything.

     

    The mount options for a btrfs pool are:

    noatime,space_cache=v2,discard=async

     

    We can apply those same options to a btrfs unRAID device - would be better?