Jump to content

Frank1940

Members
  • Content Count

    6730
  • Joined

  • Last visited

  • Days Won

    13

Frank1940 last won the day on November 14 2019

Frank1940 had the most liked content!

Community Reputation

418 Very Good

2 Followers

About Frank1940

  • Rank
    Advanced Member

Converted

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Make certain that you have the flash drive plugged into a UBS2 port (usually black plastic insert). Not a USB3 port (Usually a blue plastic insert).
  2. If you were truly entering what you thought was the correct password, there are only two possibilities that I can think of. First, someone broke into your server and changed that password. That is the reason that @testdasi asked if the server was exposed to the Internet. Second, there was some sort of corruption in in the password system of Linux. This is a fairly complex setup to prevent someone from easily getting user passwords. When you enter a password, it goes through a one-way hashing process and then is compared to what is stored in the actual password file (which I think is shadow). IF you want a more complete description of the process, I would suggest that you google something like linux password process.
  3. Can you get us the Diagnostics file? If you have the GUI, Tools >>> Diagnostics. If you have only the console, login and type diagnostics the file will be written to the logs folder/directory of the flash drive. Post up the file in a new post.
  4. Have you read through the 6.8.1 release thread yet? I believe that you are not the only one with issues.
  5. From your syslog: Jan 22 14:56:09 Tower kernel: mpt2sas_cm0: LSISAS2308: FWVersion(20.00.00.00), ChipRevision(0x05), BiosVersion(07.39.00.00) Read this thread, starting with this post: https://forums.unraid.net/topic/87532-continued-udma-crc-errors/?tab=comments#comment-813082 This would be the place to begin. I suspect it will address your issue.
  6. Also, try entering the user name-- root --- and just press the <enter> key when prompt for the password. (It is possible that there is a corruption on the Flash drive that prevents that password hash file from being read.) If that does not work, Shutdown the server and put the flash drive into a PC. Navigate to the config folder/directory. Now, delete rename these three files--- passwd smbpasswd shadow Put the Flash drive back in to the server and reboot. Login using the instruction in the first sentence of this post. Then set your passwords up again. I would suggestion that you make it a secure one. You might also consider installing the Fix Common Problems plugin and it has a setting called "Number of allowed invalid logins per day" for detecting any break-in attempt.
  7. As I understand, if you have set your server's DNS addresses to 8.8.8.8 and 8.8.4.4 (in the Unraid setup menu), the server will use those DNS servers for DNS address conversion. Anything else will use the DNS server(s) that your router is set to. Most of the time, that will be your IPS's choice. They will probably have their own servers. (The debate of whether this is a good idea (or not) is far beyond what I want to get into!!!)
  8. Try setting your static IP address nearer to the high end of the range. Say, 192.168.1.242 That way, it will be out of the range of where HDCP is making its address assignments. You also want to avoid making static assignments to the first few addresses at the bottom of the range unless you know exactly what ports your router is using for its own purposes. You should also 'notify' the router (via its settings) that you have set a static IP address so that it knows not to assign that address via HDCP.
  9. Please provide a Diagnostics file. Tools >>> Diagnostics Be sure to post it up in a new post or no one will ever know that you have compiled.
  10. What is surprising is that it was failing quietly in the syslog listing. I would think that sSMTP should provide an error message when there is no recipient for an e-mail...
  11. One more thing. Don't send mail to yourself-- Same recipient as sender. It could get tagged as Spam.
  12. You don't have an E-mail recipient listed in the SMTP Settings.
  13. Quick point (in case you did not already realize it)--- In the data moving stage, the SSD is basically useless as it will quickly fill up and then you will be writing directly to the hard drive array.
  14. Some folks, when setting up an unRAID server, will load the data to than array without assigning a Parity drive. Of course, the data on the array will have no protection in the event of a disk failure but often the data is still on the original source drives so there is a backup. After the data is moved, the Parity drive is added and parity will have to be built. Moving massive amounts of data to an array is always a time consuming process. The actual transfer rate has many factors involved. Some of the most significant have to do with the characteristics of the hard drives themselves-- rotational speed, track-to-track movement times and data density are three prime ones. The transfer rate of a single 25GB BluRay ISO file will be much faster than moving 10GB of 10KB data files due the overhead of the file management routines and latency caused by the head movement from the files tables to the data area. Once, you have a initial loading done, you may want to consider using a SSD cache drive (or SSD cache pool) to speed file transfers to the server. The Mover can be programed to move the files from cache at convenient time of day. (Default is 3:00AM as I recall.)
  15. OK, one thing to have a look at at. Open the Control Panel and click on Network and Sharing Center. In the left panel click on Change advance sharing settings. Let's have a look at couple of things. Under Private let's turn on Turn on Network Discovery and check the box for Turn on automatic setup of network connected devices Under Guest or Public , Let's turn on Turn on network discovery. Under All Networks look at the Password Protected Sharing and make sure that is turned off. The final one may not directly affect your problem so if you are super security conscious, you might want to turn it back off. (MS did a bit of changing the default settings on some of these options in last fall's updating and I had problems that setting them this way fixed.)