Jump to content

WackyWRZ

Members
 View Profile  See their activity

  • Posts

    17

  • Joined

  • Last visited

 Content Type 

Report Comments posted by WackyWRZ

    SMB Connectivity/Crash

    in Prereleases

    Posted · Edited by WackyWRZ

    I had issues for months with backups on my Macs stopping or getting corrupted and blamed Acronis.  Then I started having problems copying large files to my unraid box from my Mac.  File copies would hang and the SMB share would just disconnect after a short time.  Would reconnect fine, until I started a copy again.  At that point I figured it was a MacOS issue.

     

    I came across the post below from MaxRad about Samba 4.15.0 issues in RC2 and downgraded to RC1.  I don't know exactly what the Samba problem in 4.15.0 is, or if it's Mac specific, but I've not had one SMB issue or drop since downgrading 2 weeks ago.

     

     

    Time Machine unbelievably slow

    in Stable Releases

    Posted · Edited by WackyWRZ

    Found this thread while searching for the same issue I have been fighting with the two MacBooks in the household, figured I would add things I have tried.  One is always wired with 1GB connection and the other is always on WiFi - both running Big Sur.  I'm using TimeMachineEditor to limit the backup to network 2x a day to minimize the drives being spun up.  I've also noticed the "bursty" networking mentioned earlier during a backup, and if I have a 1GB backup - it'll take upwards of 20-30 minutes.  Even setting it to backup to Cache, then run mover later is painfully slow.

     

    The kicker is if I try to copy over files using SMB and Finder - to either a normal share or even a "Time Machine" share - speeds are great and consistent.  In my research I've also seen folks having similar issues on Synology devices too.  I did come across this page https://osxdaily.com/2016/04/17/speed-up-time-machine-by-removing-low-process-priority-throttling/ which has a terminal command to turn off "throttling" of the time machine backups.  When setting it to "0" there is an extreme increase in speed for time machine, especially on an initial backup.  But after setting back to "1" my "incremental" backups are still very slow, as it seems leaving it on "0" isn't necessarily recommended.

     

    I also have a few Windows devices which backup using Veeam beautifully - but Veeam for Mac support is in its infancy, and also doesn't support full system restores.  I have been trialing Acronis True Image on the Macs - pointed at a standard SMB share on Unraid for the past week and it has been working great.  The initial (250GB) backup only took about 45mins and the 2x daily incremental are finishing in 10 mins or so.  I hate to have to use another 3rd party software to do backups when Time Machine is built to do the job, but it feels like Apple just wants you to pay for iCloud storage and use that.  If Acronis works out, there's usually a sale on it for $40 / 3 devices or less so I will just end up going that route.

     

    Coupled with the copy tests, and other NAS device users also experiencing issues, it makes me wonder if it's not so much a "Mac/Unraid" thing as it is Time Machine "working as designed".

    [6.8.3] docker image huge amount of unnecessary writes on cache

    in Stable Releases

    Posted · Edited by WackyWRZ
    Found script

    23 hours ago, TexasUnraid said:

    What script is that? I didn't see this.

    The script is on Page 7 of this post. Link

     

    I just have the code below run 2x day from the "User Scripts" plugin.  Change the /dev/sdX to whatever your drive is and change the SHARENAME to a share on the server.

     

    #/bin/bash
    # Get the TBW of /dev/s!db
    TBWSDB_TB=$(/usr/sbin/smartctl -A /dev/sdX | awk '$0~/LBAs/{ printf "%.1f\n", $10 * 512 / 1024^4 }') 
    TBWSDB_GB=$(/usr/sbin/smartctl -A /dev/sdX | awk '$0~/LBAs/{ printf "%.1f\n", $10 * 512 / 1024^3 }') 

    echo "TBW on $(date +"%d-%m-%Y %H:%M:%S") --> $TBWSDB_TB TB, which is $TBWSDB_GB GB." >> /mnt/user/SHARENAME/TBW_sdb.log

     

    • Thanks 1

    [6.8.3] docker image huge amount of unnecessary writes on cache

    in Stable Releases

    Posted

    I started monitoring with S1idney's script and saw almost 500GB/day writes on my drive.  I originally switched from Plex official to lsio docker which reduced my writes dramatically to around 150GB/day which is still high.  As others have said this isn't the fix, and I saw it start creeping up towards 500GB/day in about a week.  Since I only have 1x SSD I decided to reformat to XFS instead of BTRFS earlier this week.  I just looked at it today and with nothing else changing outside of the XFS format I'm only showing 20GB writes in total over the last week.

     

    Thank you to everyone's research so far in at least finding a workaround and saving my SSD from an early death!  Hopefully this gets solved in an update soon.

    [6.8.3] docker image huge amount of unnecessary writes on cache

    in Stable Releases

    Posted · Edited by WackyWRZ
    Clarification

    I've come across this same issue recently and done some testing after I found my 500GB 850 pro SSD to have almost 150TBW on it.  Used up 1/2 my warranty in about 6 months!  I moved my docker img file from cache to the xfs pool / spinners and noticed the loop2 counting up like crazy.  I also can hear the drive head writing about every 4.5s (on the dot) and loop2 going up 20-30MB each time as well.

     

    I've since narrowed it down (on my Unraid) to the Plex (official) container.  Stopping the container the massive writes have stopped as well as the constant disk noise immediately.  My loop2 is sitting at 600mb of writes after about 30 minutes - where before I could hit 1GB within 5 minutes.

     

    The only other Dockers I have running are UniFi controller (lsio), NetData, and now Emby (lsio).  They can run no problem, but as soon as the Plex docker is started up it goes right back up to writing like crazy - even while doing nothing.  I plan to try lsio or binhex Plex containers instead, but this might have been the push I needed to get away from Plex anyway.

×
×
  • Create New...