• Posts

  • Joined

  • Last visited

Everything posted by Tom3

  1. I use Acronis for backing up various machines to Unraid. No share is mounted on Windows. In UNRAID, a new share is setup as: Public, Export=Yes, Use Cache pool = No My backup speed is not limited by the UNRAID hard drive but by Acronis, so for me there is no value in using the cache for this. In Acronis, create a new backup, and select Backup Destination. That will be Network --> name of your Unraid server (perhaps TOWER) --> Name of the public shared folder above. Acronis should (sometimes quite slowly) populate the path as you select each folder down to that new share. After the backup completes, you probably want to limit access to that newly created backup file. In the UINRAID command prompt: $ CD to the new backup file's containing directory $ chmod 444 the_backup_file_you_just_created $ chown root:root the_backup_file_you_just_created That will make the backup file read-only, and only the root login in UNRAID an change that. Acronis creates a new file for each differential backup. I prefer NOT to use incremental backup. The difference is that differential writes the backup between now and when the original full backup was done. To restore you only need the full and the last differential file to be good. Each differential file is larger as a result. Incremental writes since the last incremental backup. That means to restore you have to go back to the full, then replay all incremental backups. If one of those is damaged your restore stops at that point. But the incremental file is smaller as a result. -- Tom
  2. You might find this Docker folder organizer to be helpful, from Ibracorp. -- Tom
  3. There are certain ASCII characters in the filename that don't work with Rsync on Linux, rsync fails to copy the file as a result. My recollection is the vertical pipe character | is one of them, colon is another, perhaps some related to Linux file redirection such as greater-than, less-than might be others. Some of these are OK in Windows. -- Tom
  4. Playing with several Ubuntu VM's - found that logging out the local user (while leaving the VM up and services running) cuts down the write rate dramatically. -- Tom
  5. The storage management section of the manual details how to handle cache replacement. Recommended reading. -- Tom
  6. Hi Orlando - it looks like the Mellanox MCX311A-XCAT has been reported by others to work correctly in Unraid (based on google search): Unraid Forum Post Reddit Post I'm puzzled why ethtool on both systems reports the interface (if) as link down. -- Tom
  7. Hi Orlando - interesting. ethtool reports 10000baseKR (which is the single lane backplane electrical interface version of 10GbE). The coding on that is the same as 10GBaseSR, so it's likely just an unusual way to report the interface. You don't report which driver the 10G interface is using. (ethtool -i devname) Not all NIC cards are supported in Linux, you need to check to see if the driver and card you are using is supported by UNRAID. With optical interfaces there are some compatibility issues that need to be taken account of: 1. Both ends need to be compatible (same wavelength, same fiber type, correct fiber type). If you are using 10GBaseSR (short reach) multimode fiber (MMF) then the fiber needs to be the right type. 10GBaseSR is not too stressful on the fiber characteristics, I think up to about 500m is normally OK. The two optical modules need to be compatible. 2. That interface can support FEC (forward error correction). FEC needs to be set the same (On / Off) at both ends. Depending on the software, it may need to be manually configured. Your card may or may not support FEC - ethtool is showing 'Not reported'. Perhaps you may need to set if to Off at both ends. 3. Fiber connector cleanliness is critical. Dirty connectors are far and away the most common problem with fiber and can cause all kinds of strange symptoms. Both the fiber end-face and the barrels need to be clean and unscratched.. 4. ethtool message on eth2 reports that the interface is down, but ip show reports it up. -- Tom
  8. One place to start is using 'ethtool' from the UNRAID cli. It will tell you about negotiated speed, duplex, other parameters. This may tell you if something is misconfigured. # ip link show will list all the interfaces on your system (devname is usually eth0 eth1, eth2, etc.) # ethtool devname will list the parameters for that specific interface #ethtool -i devname will tell you what driver it's using # ethtool -h will give you brief help. Suggest reading up on ethtool online. -- Tom
  9. It probably depends on what you want to do with your system. A critical element being whether you want to host dockers or VMs. In my system I have 4 x HD and 1 x NVME SSD. Initially all the docker containers and VMs were on SSD. However one of the VM's (an Ubuntu server instance) was totally clobbering the SSD with about 2 GB/s write rate. After one week it had consumed about 10% of the SSD rated lifetime. There was a lengthy thread about Docker containers having write amplification problems, and eventually a fix seemed to come about. But my server VM did not appear to benefit. So I moved all the always-on VMs over to Hard Drive. The write rate there is *****WAY***** lower than to SSD for some reason. -- Tom
  10. I'm not an expert in reading diagnoistics, but it appears that your system has the br0 and br1 NIC interfaces bonded together into a Link Aggregation Group (LAG). Does the thing they connect to (Ethernet switch?) support LAG and has that switch been configured for LAG? You might want to try looking at your settings, and if bonded, eliminating the LAG bonding, then connect just one of the interfaces to the Ethernet switch. The <your-servers-ip> /Dashboard/Settings/NetworkSettings page is where you can re-configure the network settings. -- Tom
  11. The retr column shows the number of retransmitted TCP packets. The first row in your transfer shows 56 retries, which is so high as to appear essentially non-functional. So the question: what is the cause ? Some things to check: 1. Ethernet cables. 2. Any intervening Ethernet switch. 3. Do you have two things assigning DHCP addresses on the same LAN segment? 4. Bad NIC card or connector. After that it gets more difficult to troubleshoot: 5. Wrong driver for the Ethernet NIC.? 6. Out of memory condition preventing TCP from acquiring buffer space? -- Tom
  12. It's difficult to see what market this is targeted at. Large companies probably would use some sort of tape mechanism that can robotically insert, remove and change tapes. Rolling backups come to mind. For hobbyist and home use the price is too high compared to just buying some 10+ Tb disk drives. The 100 year lifetime also means that the drive and writing system would need to be around in 100 years. So does that really means that the probability of failure to read is lowered in the 1-10 year timeframe ? Perhaps the commercial photography and video market might be the target. Hence BH Photo selling it. -- Tom
  13. Too bad that the ODS-380U drive it goes into costs $8995.00
  14. I was only able to access the tunnel endpoint (the UNRAID server) at 10.253.x.x when using the "Remote Tunneled Access" mode. That showed allowed IP as Nothing else seemed reachable. Changing to "Remote Access to LAN" mode I was able to access the server and the local LAN, but not the internet attached to the local LAN. -- Tom
  15. Hi Drackeo - you have first to make a decision: to use RJ45 / Cat 6A cable, or to use SFP+ based connectors. This will drive the kind of card you purchase. For RJ45 / Cat6A: Pros: * Connectorized cables are inexpensive and readily available, or you can make your own. Cons: * The modules with RJ45 are usually higher priced, * The latency is a (lot) more than SFP+ units, * The power is a higher than SFP+ units. * The reach is sometimes limited to 30 meters depending on the interface. Some SFP+ to RJ45 adaptors have such limited reach. For SFP+ : Cons: * You need a special cable. Can be DAC (Direct Attached Copper), Multimode fiber (several hundred meters) or Single mode fiber (about 10 km). * DAC copper usually limited in reach to maybe 10 meters. Pros: * The prices on 10G DAC and fiber have dropped dramatically recently. I saw DAC 3 foot for $15, MMF for $17 and SMF for $27. * SFP+ usually has much better latency and lower power. You should look at the total system cost (Cards, modules, cables, etc.). NICs with SFP+ and 10G switches with SFP+ can be significantly less expensive than RJ45. Note there are SFP+ adaptors that plug into SFP+ slot and provide RJ-45 interface. Check the reach of these as the less expensive ones have poor reach on CAT 6A. The power of the adaptor may limit how many you can plug into a SFP+ switch. But they are handy when you have a device and you have to convert. -- Tom
  16. Having a simple way to persist the public key would be nice for SSH. If a similar method can also be used for root login, even better.
  17. Hi On the MAIN page of UNRAID, under Array Devices, where the disks are listed... 1. The dot in front of each disk device spins that one disk up or down (toggling the state). Hover your mouse over the dot to see... 2. There are up and down arrows just below the list of devices (on the line Array of {number} devices) to spin down or spin up all devices. -- Tom
  18. You may find it helpful to read on the Wiki about Parity drives: One possibility for identifying disks may be to spin down all the disks, then spin them up one at a time while looking at each disk activity indicator LED. -- Tom
  19. I am not completely clear on your question. Spaceinvader One did a great video of OpenVPN-AS, with an update in 2019. This installs and runs well on UNRAID 6.9.0-rc2 for me. And another on routing docker containers through another VPN container: -- Tom
  20. Had this same problem for a long time, reported once many months ago. Upgrading to 6.9.0-rc1 fixed it. Now on 6.9.0-rc2 and still working correctly. -- Tom
  21. Tom3

    UPS Issue

    OK, 36V is an unusual UPS battery bank voltage. My numbers assumed a 48v bank. Does your server load increase when the UPS switches on? Sometimes the server starts a shutdown process which increases the load. The 36.9 minutes I think assumes the UPS goes to 0% charge. The table above appears to be to shutoff when the battery gets down to 25%, and MAXTIME of 1800 seconds (30 minutes). The table shows OUTPUTV of 0.0 volts. Not sure what that refers to, my UPS driver does not provide that parameter.
  22. Tom3

    UPS Issue

    Not sure if the table above is right after the discharge event, or after the batteries have been charging for awhile. On the graphic it shows BATTV as 42.3 volts. For a 48V lead-acid battery at room temperature that's about 1% charged (99% discharged). The table also shows BCHARGE at 71 percent. Those two numbers disagree with each other. While float charging, the battery should sit at 54.4 volts for 100% capacity. Some Q&A at Dell Community says that R710 server supplies load-share, except when lightly loaded. -- Tom
  23. HI SLimat - it appears you have the ownership set incorrectly. The user should be 'nobody' and the group 'users'. It looks like the user is 'users' and the group is blank. Not sure what happens when the group is unspecified. You can chown nobody:users on the affected directories/files. -- Tom
  24. Hi Slimat - I would not change the UID/PID in the VM. The nobody/users ownership in UNRAID allows anonymous access, so changes should not be needed. You can recursively change permissions of the files. Pick whatever access attributes you feel comfortable, they need to apply also to the last field (i.e. not 770, but 777 or maybe 776 (R/W but not X) or 774 (read only). On my system I have the . and .. directories set to 777 and nobody/users, while the individual files are set to 444 read-only. You have multiple choices to meet your needs. -- Tom
  25. Hi Slimat, root always has UID=0 (it doesn;t necessarily have to be called root, that could be changed). You may want to look at the permission for the share on the server. Just open a command line to /mnt/user/to_your_share then do a ls -la The will show you something like: dxwrxwrxwr 1 root root 4096 date ./ dxwrxwrxwr 1 root root 171 date ../ --wr-wr--- 1 root root 227594 date the_file_name ... etc ... If the owner and group are root root (as above) and the file permissions (the trailing --- above on the filenbame) prohibit wr access to the user then you won't have permission to read or write as UID=1000. Unraid uses nobody users to mean the anonymous owner/group. chown command changes the owner/group (lookup syntax via google) chmod command changes the permissions. If you want to open it up to anybody, chmod the permissions to 777 on the file(s). (again, lookup syntax via google). I use a share to backup my computers, using anonymous access because my backup program only understands that. Then I go in afterwards and change the backup files owner/group to root root and permissions to 444 (allowing read-only access). This makes the backup files usable for restoration, but they can't be changed. -- Tom