zanee1

Members
  • Posts

    6
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

zanee1's Achievements

Noob

Noob (1/14)

0

Reputation

  1. So, at this point I rebooted the server and found that the clock in the bios was off by about 7 hours. I set that clock are rebooted into normal mode. I will update this tomorrow with my results. Bonienl, what difference would safe mode make? I don't understand why that would make a difference. I am more than willing to try but what do you suggest? Reboot in Safemode and set the clock then reboot in normal mode? I appreciate your input, just looking for some clarification.
  2. Thank you so much for your help. To answer your question directly, I am not manually resetting the time via SSH. I have reset it manually a bunch of times via settings in unraid because it was just wrong. Actually I just logged in and my clock on my computer shows this... Unraid shows this... I had not touched it since I sent you the screen shot the other day. I just reset the time in unraid. When you switch "Use NTP: Yes" to "Use NTP: No," it does the manual reset you see in the logs. After resetting the clock at about 6:52 AM and working on the system for a few minutes I noticed that it is already 5 minutes behind. I am attaching another diag file too. This seems to be interesting... Nov 20 01:00:51 WeltoRaid sshd[24763]: Received signal 15; terminating. Nov 20 01:00:52 WeltoRaid sshd[25822]: Server listening on 0.0.0.0 port 22. Nov 20 01:00:52 WeltoRaid sshd[25822]: Server listening on :: port 22. Nov 20 01:00:53 WeltoRaid emhttpd: shcmd (14138): /etc/rc.d/rc.ntpd stop Nov 20 01:00:53 WeltoRaid ntpd[24808]: ntpd exiting on signal 1 (Hangup) Nov 20 01:00:53 WeltoRaid ntpd[24808]: 127.127.1.0 local addr 127.0.0.1 -> <null> Nov 20 01:00:53 WeltoRaid ntpd[24808]: 3.82.177.91 local addr 192.168.0.151 -> <null> Nov 20 01:00:53 WeltoRaid ntpd[24808]: 216.229.4.66 local addr 192.168.0.151 -> <null> Nov 20 01:00:53 WeltoRaid ntpd[24808]: 184.105.182.16 local addr 192.168.0.151 -> <null> Nov 20 01:00:53 WeltoRaid ntpd[24808]: 162.159.200.123 local addr 192.168.0.151 -> <null> Nov 20 01:00:53 WeltoRaid root: Stopping NTP daemon... Nov 20 01:00:53 WeltoRaid emhttpd: shcmd (14139): date -s '2019-11-20 06:51:34' Nov 20 06:51:34 WeltoRaid root: Wed Nov 20 06:51:34 MST 2019 Nov 20 06:51:34 WeltoRaid emhttpd: shcmd (14140): hwclock --utc --systohc --noadjfile Nov 20 06:51:41 WeltoRaid crond[1683]: time disparity of 351 minutes detected That time disparity is really strange... Does that just mean that the time in unraid is 351 minutes off from the HWclock? weltoraid-diagnostics-20191120-1413.zip
  3. Thanks for the reply!!! I appreciate your help. I have also tried setting the NTP servers. Here is what it looks like. When I check it in a few hours, it will be WAY off again. I have also attached the Diagnostics file you requested. Thanks again for your help. weltoraid-diagnostics-20191118-1619.zip
  4. I upgraded to 6.7.2 a few weeks ago and found that my Mythtv docker wasn't recording things at the right time. I looked at the time in the docker and it was way off. I then looked in settings on Unraid and found it's clock was way off too. I reset the clock on Unraid a few times to no avail. I also replaced my BIOS battery and it is still going off each day. Any ideas on how to get it straightened out?
  5. I am new to unRAID but I have been using Linux for around 15 years. I have been working to get my Mythtv Back-end off the slow HP microserver it is running on and onto the AMD 8350, 8 core, 32 GB Ram, 15~ish TB unRAID box I built. Before you say, "Why don't you use the Docker Myth Back-end?" I use two Hauppauge HD PVR's for recording and it has been a chore to set those up in Ubuntu. Also, I could find no documentation on how I could possibly set them up in the docker system. All that said, here is my issue. I have finally gotten everything working the way I think it should with the HD PVR's and I am ready to have them write to this HUGE space.... But it won't work. I have tried to mount them several different ways and each way a normal user can't write (make files or folders) on the shares without invoking sudo. I can write to those shares from a windows box as a normal user just fine but I can't do it from my ubuntu 14.04 LTS server (cli only) to save my life. This share security is set to public for both SMB and NFS. I tried; //192.168.0.151/mythstorage /storage cifs credentials=/home/myusername/.smbcredentials,iocharset=utf8,sec=ntlm 0 0 I also tried; //192.168.0.151/mythstorage /storage cifs username=myusername,password=mypassword,iocharset=utf8,sec=ntlm 0 0 I finally tried; sudo mount 192.168.0.151:/mythstorage /storage With the first two, the share mounted but I can't write to it without using sudo and that just isn't going to work with mythtv. The "sudo mount" command just times out. Thanks in advance for your help. I have worked on this for about 10 - 12 hours today so I apologize if this sounds a bit annoyed. :-)
  6. Does anyone have a guide to getting a dual Hauppauge HD-PVR with IR emitters setup to run with the Docker Mythtv? I am new to unRAID but I have used Mythtv for 10+ years. Most of what I have worked with has been Fedora and Ubuntu so Slackware is a new animal to me and I would love to have a little guidance. I am also looking for how to restore my 10+ year database in the Docker container. :-) Thanks in advance for your help!!