limetech

Administrators
  • Content count

    6544
  • Joined

  • Last visited

  • Days Won

    11

limetech last won the day on September 22

limetech had the most liked content!

Community Reputation

160 Very Good

About limetech

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. That's some great analysis, thank you. We'll try to figure out the best place to post this issue, either with btrfs developers (probably) or samba developers. I think you're right, though for the sake of data integrity, we should disable samba async i/o for now. The reason it was added was to experiment with "multi-channel" feature, cf: https://blog.chaospixel.com/linux/2016/09/samba-enable-smb-multichannel-support-on-linux.html
  2. unRAID OS version 6.4.0-rc9f available

    Please break this out into it's own topic since as you can see, it is getting lost here. The 'longhexidecimal' is not derived from any IP address.
  3. Replacing Data Drive Error

    Thanks for helping out. Hey what's that "code" in your sig? Something to do with the Illuminati perhaps?
  4. Hard Crashs rc9f

    But no messages on console get output just prior to crash? Anything change with your h/w? Run memtest lately? Overclocking (hope not)? Added storage devices?
  5. Hard Crashs rc9f

    What do you mean by "hard crashes"?
  6. Hard Crashs rc9f

    Thank you for the info, however I see nothing out of the ordinary. Since you can make it crash "at will", please boot server, and then open a telnet/ssh window using, e.g., putty, or if not available, click 'Log' button on webgui menu bar. Now make it crash and select/copy/paste the content of the logging window into a post, hopefully that will show the origin of the crash.
  7. Yes this is possible and UI design specifically allows for this. If you are really intent on using your USB boot flash, maybe try out f2fs instead of xfs? But in general we are against this because your license key file is tied to your USB flash device. In fact we are trying to go the other direction: get everything that's read/write off the USB flash except the most basic/critical config data. Sure it seems "wasteful" to have hundreds of Gigs of unused space, but this is only the case because the devices are so cheap. On the other hand, the size of unRAID OS download is continuing to grow. If you want to keep the current release along with a couple 'previous' releases, you have to ensure enough space is available in partition 1 to accommodate. To answer another question, why does chbmb have to maintain the "dvb edition"? Well adding all the required drivers greatly increases the download size (and time to download) and we don't want to require the large majority of users to have to download a great deal of stuff they will never use. Also presents problems having the GPU drivers present for those who want to use GPU pass through to VM's because once the host 'binds' a device, in our experience, unbinding and then assigning to a VM is not always reliable. To solve this we have to implement some kind of module blacklisting UI - again a pain-in-the-neck for majority of users. Where this is going is that we want to implement "editions" of each release, where you can select what you need. For example, maybe you don't use the console-GUI, ok you could select a download version that omits this. Maybe you want the dvb-edition, ok you could select that. Astute observers might recognize that the Flash Creator tool provides the foundation on which we could add this capability.
  8. unRAID OS version 6.4.0-rc9f available

    docker in -rc9f is the same as -rc8q ...
  9. unRAID OS version 6.4.0-rc9f available

    Can you test something for me? Look at the device identifier for your nvme device, let's say it's "nvme0n1". Please see if output of this command: smartctl -A /dev/nvme0n1 Looks identical to output of this command: smartctl -A /dev/nvme0 (we just dropped the 'n1' from end of the device). Also please include vendor/model of your NVMe device. Nevermind, I see yours. Thanks!
  10. unRAID OS version 6.4.0-rc9f available

    Can you test something for me? Look at the device identifier for your nvme device, let's say it's "nvme0n1". Please see if output of this command: smartctl -A /dev/nvme0n1 Looks identical to output of this command: smartctl -A /dev/nvme0 (we just dropped the 'n1' from end of the device). Also please include vendor/model of your NVMe device. Thanks!
  11. unRAID OS version 6.4.0-rc9f available

    Can you test something for me? Look at the device identifier for your nvme device, let's say it's "nvme0n1". Please see if output of this command: smartctl -A /dev/nvme0n1 Looks identical to output of this command: smartctl -A /dev/nvme0 (we just dropped the 'n1' from end of the device). Also please include vendor/model of your NVMe device. Thanks!
  12. Mover ignoring split level

    This is being caused by same bug.
  13. Is this really with -rc8q? I think this is fixed in -rc9f.
  14. unRAID OS version 6.4.0-rc9f available

    We get it from here: https://www.kraxel.org/repos/jenkins/edk2/ You want the file that begins with: edk2.git-ovmf-x64 These are automatically rebuilt every time there is a commit to the ovmf git repo.
  15. Well you know there are lots of reports of Ryzen instability. That makes it hard to separate what might be a cpu/hw issue vs. some kind of s/w issue in unRaid. That's the main reason we try and keep up with latest kernels. In release notes for -rc9f I wrote: We wanted to move to 4.13 asap in order to see if Ryzen issues got better, but I made the decision to stick on 4.12 where it's last patch release corresponded with this release of unRAID. We go through a lot of testing after updating kernel minor releases and I didn't want to delay this unraid release further. I guess the bottom line is: we'll try and get these -rc's out faster with updated components.
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.