pasgener

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by pasgener

  1. Hi all.

     

    FCP just threw up this warning: "Invalid folder rootshare contained within /mnt".  I had just restarted my Unraid server.

     

    The folder "rootshare" is indeed in /mnt and is empty.

     

    I have just replaced my parity drive with a larger drive (the parity rebuild process is complete), and I am now in the process of replacing one of my data drives with a larger drive (that data-rebuild just started and is ongoing).

     

    I have no VM running.  I have only one docker running (tonido).  I don't recall creating that folder!  I have standard shares and never tried to create an overarching "rootshare".

    tower-diagnostics-20220311-2109.zip

    Diagnostics attached.  Appreciate any thoughts/suggestions.  Should I just delete that "rootshare" folder?

     

    Thanks in advance.

  2. 12 hours ago, Frank1940 said:

     

    You are not the only one with this problem.  I have not seen a solution posted up on the forum yet. One thing which I would like to suggest is that you google the problem.  Suggested phase would be something like:      SMB/CIFS problems WIN 10 20H2   (You will get a lot of hits!!!)  IF you are getting an error message be sure to include that in your search.

     

    You also  have to realize that there are many different favors of WIN 10 version 20H2 ---  Home, Pro, Educational, Enterprise.  And I may have missed some.  They are all a little bit different when you look under the 'hood'.  For example, I believe Home does not have the Edit Group Policy app.  Settings in the registry may differ depending on which one you have.  What works for one favor may not work for another. 

     

    Now if you find a solution, PLEASE (pretty please) post back with what you found.  (I have actually locked my WIN 10 Pro to version 2004 until someone finds a solution...)

    I also have several Win10 systems on my home network, and only have problems with my Win10 Pro clients (the rest are Win10 Home).  With Win10 Pro the only solution that works to allow File Manager access to my unraid server (either with server name or with IP address) is to create a User/Password combo on Unraid that matches my Win10 system, and then manually create those credentials in Windows Credential Manager.  Then I can connect like I always used to,

     

    For some reason the tips to turn off password protected sharing, and allow SMB 1.0, and allow insecure guest no longer work with 20H2 without that account -- as far as I can determine!

    • Thanks 1
  3. 2 hours ago, Ford Prefect said:

    ...see here: 

     

    in short: ...try the beta or - unfortunately for a NUC without the ability to add a PCIe card - stay with the external  NIC until beta becomes the next stable version.

    Got it.  Thanks for the quick reply.  Thunderbolt PCIe 10GbE on the way -- will also give that a shot.

  4. Unraid (nor any Linux variant I believe) does not support the Intel I219-V Gigabit LAN built-in NIC that is part of the Intel NUC 10th generation (Comet Lake).

     

    I have an Intel NUC 10i5FNH, and Unraid would boot but could not recognize or load a driver for the gigabit ethernet NIC natively and so could not pull an IP address.

     

    I have been able to run a trial license of Unraid using a USB3 hub with gigabit ethernet (ASIX Electronics Corp. AX88179 Gigabit Ethernet) which is supported, and Unraid can pull an IP through that connection.  Obviously it would be preferable to use the built-in ethernet!  Please let me know if you are able to implement a drive for the Intel NUC 10th gen NIC (Intel I219-V Gigabit LAN).

     

    Thanks in advance.

     

     

  5. My unraid server (6.8.3) has been running for many years, and while it is old, it has served me well through memory upgrades, the addition of a cache pool, a new CPU, and 10GbE.

     

    Recently however it has been "locking up" unpredictably.  The system is on and the console works (via hardwired keyboard and VGA monitor to Supermicro mobo), but network connectivity is gone (cannot access shares or webmanager via server name or IP address).  In addition the console is basically non responsive: commands like reboot or shutdown don't work.

     

    I can hard reset and reboot and the system boots up fine and runs for 1 day or 1 week before a repeat "lock up".

     

    Reviewing the log files (attached) I notice some CPU thread errors but I am far from a Linux expert so don't know what to make of them.  Do I have a new hardware problem (like a failing CPU), or is it something else?

     

    I have attached my log file (I have it set to save all logs to the flash drive so that the errors are preserved post crash), my system profile, and my diagnostics, and appreciate any suggestions or help you can provide.

     

    tower-diagnostics-20201203-1849.zip

    syslog System Profiler.txt

  6. On 10/11/2020 at 1:34 AM, pish180 said:

    Not on the Win10 machine.  I blew it away after I built up Unraid and moved to containers.  The Win 10 machine was running so much software it would have been really hard to find out what was causing it.  I tried the obvious things like drivers, AV, etc.   Gl.

    Any luck with a solution?  I seem to have the same problem, but with an Aquantia 10GbE PCIex4 single SFP+ card in my unraid server, connected to a MikroTik 10GbE switch (CRS305) and then to my main Win10 PC with an identical Aquantia 10GbE card on the same switch, all with SFP+ DAC connections (1m).

     

    iperf3 with one stream gets about 2.7 to 3.2Gbits/s, but can get total throughput of 8.2Gbs with 4 streams (-P4) and 8.94Gbs with 5 streams (-P5).

     

    I can teracopy from a Win10 NVMe SSD to my unraid SSD cache drive (in btrfs, two SSD cache pool) at 280-300MBs.

     

    I've disconnected my two gigabit unraid ethernet connections to ensure that all is routed through the 10GbE NIC.

     

    Appreciate any thoughts!

  7. On 1/27/2019 at 2:07 PM, StrandedPirate said:

    Tons of posts related to Windows 10 and SMB as the root cause of the inability to connect to unRaid that were fruitless so I'm recording this easy fix for my future self.

     

    If you cannot access your unRaid shares via DNS name ( \\tower ) and/or via ip address ( \\192.168.x.y ) then try this. These steps do NOT require you to enable SMB 1.0; which is insecure.

     

    Directions:

    1. Press the Windows key + R shortcut to open the Run command window.
    2. Type in gpedit.msc and press OK.
    3. Select Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation and double click Enable insecure guest logons and set it to Enabled.

    4. Now attempt to access \\tower

     

    Related Errors:

    • Windows cannot access \\tower
    • Windows cannot access \\192.168.1.102
    • You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.

     

    image.png.6a29831e3b5ba99a813f6643aefd0541.png

    image.png.c69ad0d3d56258a109287e6bf1f25ec8.png

    image.png.41bdf31b0dc76f0ee59534fae310c106.png

    image.png.5aa7061d6062d73df37b8b0c51e640b8.png

    image.png.b3ffaca1597255ad8df386c9d8d95c8a.png

     

    Thank you!  Your suggested change to the gpedit policy fixed the inability of one of my Win10 PCs to access unraid shares after an OS reinstall (Win 10 Home 1909).

  8. I understand completely, and have no plans to touch the array disks (or flash drive) from "inside" Win10.  However for system maintenance, bios updates, etc. it is far easier to perform from a bare metal Win10 environment -- at least for me!  99% of the time Unraid will be running on the system, but on those rare occasions that I need Win10 baremetal, a menu option would avoid the delete key/Bios dance.