hpad06

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by hpad06

  1. See attached file for the log, From Syslog link I notice this, is this the reason? Server name is currently working though, I don't have the log for when server name is reset yet. May 7 06:17:17 Liuraid root: Error loading host key "/etc/ssh/ssh_host_ed25519_key": invalid format#015 liuraid-diagnostics-20200507-0632.zip
  2. I have changed the identification from tower to my server name and disk setting to auto start. However every few reboot I will have identification reset to tower and disk auto start to off. i am on version 6.6.7, I do not want to upgrade to 6.8.3 as WOL does not work in the new version Any fix to prevent server name reset?
  3. I found it now. I think the issue is unraid somehow changed VM to "NO" in VM manager, now I enable it, I see "VM" now
  4. I downloaded Unraid 6.24 to try on my current V5 disks. Yesterday when I first started it, I see "VM" in the menu, but today after I start the PC and notice "VM" is no longer in the menu. What has caused this , does it mean VM is not supported for my PC or trial license ? Thanks
  5. Is there a solution for v5 ? Do you have the same issue with v6 ? I am still running v5 basic version, it is bothering me a lot, would upgrade to v6 fix it ?
  6. is your issue similar to mine? Cannot enumerate directory - The specified network name is no longer available http://lime-technology.com/forum/index.php?topic=24798.0
  7. That's all the syslog I was seeing at the time, I downloaded the syslog after the errror appeared, howerver there was nothing suspicious recorded in syslog.
  8. The disk has many folders, some folders have sub-folders, sometimes are top folders , sometimes are deep subfolders. In each folder, there might be 2000 files, or only 20 files. It is a 2T drive, only filled about 900G Also the issue happens a lot during read, not just write. As I am using freefilesync to copy from unraid to another windows machine, it pops up this error when scanning folders in unraid.
  9. I am still struggling with this error in rc08a. Through Samba share: I am copying some back up folders from unraid to windows 2008 server, but it sometimes give me this the specified network name is no longer available error. Then I tried NFS, it also gives error Windows Error Code 2: The system cannot find the file specified also I can not write big files ( over 1.5G ) through Samba, I am able to write those files using NFS though. I am only using basic version, so no cache drive, and there is nothing in system log to help find the cause. I have tried 3 different NIC on the Unraid, client side, 2 windows 7 , 1 windows 2008 server and all have the same issue. What should I do to get rid of this error? syslog-2012-12-18.txt
  10. I followed above instructions but it is very slow. so this is what I did, 1. change in nfs client (windows 7) to UDP, this makes browsing folder very fast 2. mount again mount \\tower\mnt\user\Video r: this works very well for me.
  11. I am using the basic version rc8a which does not support cache drive. I have 2 windows 7 and both experience the same error. In the syslog there is no error for this. This error can happen during both read and write for me. I am wondering what is the root cause for this, besides adding a cache drive, what other solution is available? I notice on one windows 7, every time when I copy big files (tried 2 files over 1.7G) I get this error. Small files are fine. I have upgrade Samba to 3.6.8 still the same. Update: Good news here, I turned on NFS , and also installed windows 7 NFS client. Now I am able to copy those big files ( over 1.5) using NFS shares without errors. So looks like the issue reported here is mostly caused by Samba. syslog-2012-12-13.txt
  12. I have switched PC and cable, on unraid I still only get 10M, on windows 7 I still get 1000M. I am guessing maybe this card I bought from eBay is too cheaply built.
  13. I tried it on windows 7, I am only getting 100Mb/s. I am guessing this card is badly built and not able to run at 1G. Maybe I should get another card.
  14. I have upgraded to 5.0-rc8a, still the same. And it seems it's using R8168 driver. ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes lsmod | grep r8168 r8168 223272 0
  15. I am using unraid-server-version-50-rc5-r8168-aio , however I am only getting 10Mb/s. I have tried to force to 1000, however it doesn't work. What can I do to make it connects as 1000 ? I bought this cheap Gigabit PCIe card from eBay, it lists as HX 8111d, when I googled it , it seems to be using RTL8111C. This is my ethtool info Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes Thanks