Jump to content

NLS

Members
  • Content Count

    944
  • Joined

  • Last visited

Community Reputation

0 Neutral

About NLS

  • Rank
    Advanced Member
  • Birthday 03/30/1974

Converted

  • Gender
    Male
  • URL
    http://blog.ilogic.gr
  • Location
    GREECE

Recent Profile Visitors

902 profile views
  1. Any help here please?
  2. I edited fstab as described in older thread, rebooted, doesn't work.
  3. I need to pass through a share inside my NethServer. I have set "Unraid Share" to be "/mnt/user/" and I have set "Unraid Mount tag" to "shares". How to I make this a persistent mount within NetServer, so that I can actually use it?
  4. I have installed NethServer as a VM in my unRAID newly-RE-configured home server. I have enabled SAMBA AD on NethServer. I read an old (2015) guide that I cannot have my unRAID join a domain in a VM, because the array (and VMs) need to be stopped to join. Is there any workaround this in 2019? If there is no REAL workaround, can someone with better expertise than me in unRAID tell me if the following spaghetti scenario can work? Run the array and VM. Make another VM on another computer, also installing NethServer. Make that NethServer a domain controller on same domain as my ACTUAL NethServer (inside unRAID). Stop array and VM. Use the second domain controller (VM on client machine) for unRAID to join domain. Turn on array and VM. Second domain controller, supposedly syncs with first domain controller (right?). I am asking because this would happen with Windows Servers, but not sure what happens with SAMBA machines. Remove second domain controller from domain (after I somehow make sure it replicated the AD). UNRAID will work fine, even after a reboot, starting array and VMs. (Question here is what happens with AD security in unRAID when no DC is available - briefly until it boots). Ideas? Comments? Help?
  5. * For the non-working eth adapter, I disabled from EFI/BIOS. Doesn't show up. * For the 100Mbit (right or wrong) adapter that used to show as eth0, I just went to the third tab and swapped it to make it eth1 (and the new PCIe card eth0). System rebooted and then I could disable eth1! ("port down") Or I could leave it as active backup, but since I am not sure how it works yet (i.e. if eth0 always takes priority or priority is random or least used or what), I ignored that option. So case closed.
  6. I am running latest unRAID. It just worked. I moved it to different PCIe. But MAYBE it was already there and I just had to press "port up". Now I have different issue. I want to disable eth0 and use eth1. EDIT: Found it.
  7. Right now my focus is the new PCIe card. 8368 is TG-8368? I saw that it doesn't show in the file. What could that mean I wonder. I don't see anything in EFI that could limit it. Should it be auto-detected? I will try to find and use a different PCIe slot. If again is not shown, I will try it on a different computer just to be sure it works.
  8. It is reported as "8139too". I was positive it was a gigabit card when I installed it, but I cannot verify until I physically remove it (not possible right now). (in other words it MIGHT be reported with wrong model - or not - I can only know when I remove it) The issue now is how do I make the new card work. TG-3468
  9. I got that card because it supposedly works with linux kernels years back. Attached... quasar-ultima-diagnostics-20191021-1906.zip
  10. I got the card, unRAID doesn't see it. See here:
  11. Long story short: - My on-board LAN is dead (before unRAID install), but is detectable (reports as r8169). - I have (before unRAID install), a PCI LAN card, that is detected (as 8139too), but only plays as 100Mbit. It is a gigabit card and I am positive it worked as such, but cannot verify (previous OS is dead). - I just got a new LAN card, PCIe, I left the other on (because I was sure I will be in this situation) and the new one is not detected at all. The card is tp-link TG-3468. I am positive Linux supports it. Note that the LED is on, so physically is detected by the switch. Switch again (!!!) shows it as 100 but it CAN be that it is in some "compatibility" mode until a driver is used. HOW do I make unRAID detect it? Assume minimal Linux knowledge.
  12. Is the process still so complex in Oct 2019, for the linux untrained? I want to share my /mnt/user to my NethServer . Can I have a step by step "stupid-proof" guide?
  13. Diagnostics attached. Will replace the card with a PCIe in any case (since using a PCI one doesn't feel ok anyway). This works I hope: TP-Link TG-3468 quasar-ultima-diagnostics-20191020-2127.zip
  14. OK newer news. Verified cable (used cable and port from known working gigabit machine). Also my SBS2011 doesn't boot, so I cannot verify OS issues. Seems, that my on-board LAN card is dead (although reports no error in Windows or Linux) and I had (in the past and don't even remember it) installed a PCI LAN card. The card reports as eth0 in unRAID and reports as "8139too". The on-board reports as eth1 (with interface down) and model "r8169". This "8139too" works ok in unRAID?