Woodpusherghd

Members
  • Posts

    236
  • Joined

  • Last visited

Posts posted by Woodpusherghd

  1. If you have a Linux box you can try Backupppc for machine to machine backups.  I'm using it to backup 2 Windows PCs and my UnRaid tower to my Ubuntu PC.

  2. When upgrading to RC 9f and now upgrading to RC13 my pc would not choose the unraid usb stick as the boot device.  I had to choose this in the bios which in my case is a headache as I had to hook up a monitor and keyboard.  I updated and rebooted through the gui  in both instances.  This wasn't the case with 6.3 and prior 6.4  RCs.  Is this a bug or am i missing something?  

  3. Every time I access the web gui, my system log shows the following error:

     

    Quote

    Jun 20 08:39:53 Tower nginx: 2017/06/20 08:39:53 [error] 9809#9809: *296559 user "root": password mismatch, client: 192.168.1.9, server: , request: "GET / HTTP/1.1", host: "192.168.1.2"

     

    I'm sure I have something mis-configured.    I'm on 6.4 rc4.  I have two enabled two users (root and george) both with passwords.  I log into the shell with ssh. Any suggestions?.

  4. Whenever I access the web page my log shows this error message:

     

    Quote

    Jun 17 09:22:18 Tower nginx: 2017/06/17 09:22:18 [error] 9903#9903: *140818 user "root": password mismatch, client: 192.168.1.19, server: , request: "GET / HTTP/1.1", host: "192.168.1.2"

     

    192.168.1.2 is my Unraid server, 192.168.1.19 is the PC from which I'm viewing the web page.  I have a password set  for root, though I log into the Unraid shell via ssh. Any thoughts?

  5. I absent-mindedly left my spare Unraid USB flash drive in my dress shirt pocket when I threw my shirt into the washing machine.  It went along with my shirt through a complete hot wash cycle.  It was a white shirt, so to make matters worse for the flash drive, I had added chlorine bleach to the wash.  Believe it or not, it came out none the worse for wear.  Reminds me of the old Timex watch commercials; "It takes a licking but keeps on ticking."  

  6. 4 hours ago, Woodpusherghd said:

    After successfully backing up my VM for months, suddenly the script failed. See attached log. I updated to the latest version.  Has anything changed in the update that I need to modify in my script? Script attached.

    log.txt

    script.txt

    SOLVED  I had left the date stamp on my VM image as I had restored t from a previous backup.  Apparently the script had a problem with the time stamp.  I renamed the image without the time stamp and the script ran properly.

  7. One of my array drives red balled and one of my drives in a two pool cache went off line.  As I suspected, it turned out to be a loose power cable both drives share.  After tightening the cable I rebuilt parity and scrubbed my cache pool which corrected numerous errors.  I noticed my array drive was giving a warning of "failing now"  for the Spin_Retry_Count.  The value hasn't increased since bringing the drive back online and rebuilding parity.  Is my drive really dying or is this just a result of the loose power connection.  I've attached a smart report for the drive in question.  Thanks. 

    TOSHIBA_HDWD120_86M6SPMAS-20170509-0801.txt

  8. My disks are constantly spun up.  Possible culprits: (1)  I am running CrashPlan inn a docker with 3 PCs backing up to my server and the server backing up to Crashplan's cloud;  (2)  I'm running a Ubuntu VM with scheduled backups of a mysql database and daily cron jobs backing up Newznab files via rsync. Any thoughts on determining what's keeping the disk spun up? 

  9. Check the mount point for the share inside the VM, and which user mounted it? I've found enough times that only the user that mounted it can write to it.

     

    I mount the share through fstab using 9p.  The permissions of fstab are 644 i tried changing permissions to 777 (which is probably not a good idea), same result.

  10. After updating to rc5 I noticed a problem with my Ubuntu server VM (16.04 LTS.) A share I have on my cache drive (I have a 2 disk cache pool Raid 1)which is mounted in the VM  is now not writable which I discovered when my SABnzbd running within the VM started throwing off error messages when trying to create directories within the share.  I checked the permissions, they are ok.  I tried creating another share on the cache drive, same result.  I scrubbed the cache pool and no errors.  All other shares which are on the array (not on the cache drive) are behaving normally.  Any suggestions?

     

    Updated to rc-6, same problem as previously reported after updating to rc-5.

  11.  

    To clarify, you are saying that you are getting errors when trying to write to a cache-only share from an Ubuntu VM running on unRAID?

     

    Yes.

     

    My first question would be whether or not you can write to that same share from another machine on your network.  Second question would be if you could please attach your system diagnostics to a reply on this topic so we can examine further.

     

    Yes, no problem from other machines.

     

    Diagnostics attached.

    tower-diagnostics-20161130-1417.zip

  12. Check the permissions and/or ownership for the /mnt/cache mount point directory itself?

     

    The permissions are the same for the array share mount points.  Another strange issue, when I open VNC to get to a console, it asks for a password.  When I start the VM without the cache drive mounted it doesn't.  Could these two issues be related? Strange. :-\

  13. After updating to rc5 I noticed a problem with my Ubuntu server VM (16.04 LTS.) A share I have on my cache drive (I have a 2 disk cache pool Raid 1)which is mounted in the VM  is now not writable which I discovered when my SABnzbd running within the VM started throwing off error messages when trying to create directories within the share.  I checked the permissions, they are ok.  I tried creating another share on the cache drive, same result.  I scrubbed the cache pool and no errors.  All other shares which are on the array (not on the cache drive) are behaving normally.  Any suggestions?