CS01-HS

Members
  • Content Count

    284
  • Joined

  • Last visited

Everything posted by CS01-HS

  1. Put it in Settings -> SMB -> SMB Extras You have to stop the array to edit it. Here's what mine looks like with two shares: Private and Public, but I've customized it enough I forget what's changed from the default. I believe the highlighted lines are the only ones necessary to fix search.
  2. Maybe it's backing up the full Recovery partition every time? Stab in the dark but I believe spotlight indexing of the mac and the backup plays a role. You can rebuild the mac index easily enough by turning it off: sudo mdutil -a -i off then on: sudo mdutil -a -i on but the backups are more complicated, maybe easier to start fresh. You can set multiple time machine destinations so you wouldn't have to wipe the old one.
  3. That's what I'm getting at. We're blaming unRAID but I think Time Machine itself's the limiting factor. You can disable Time Machine throttling by running this on your Mac which might speed it up (it gets reset on reboot) sudo sysctl debug.lowpri_throttle_enabled=0 Still that log showing a 40GB backup in about an hour and a half isn't bad, better than what I get so it might be a combination of factors. Is there a good reason the backup was so large? Mine are usually around 1GB. Not sure about your "Recovery" error.
  4. Has this fix stuck? Approximately how long does it take to complete a backup and of what size? Mine is about 20 minutes for 700MB but I wiped and re-started my backup set a few days ago so it might slow down over time. You can run this command in an OS X terminal to see details as time machine runs: log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --debug I think it would help if we had a baseline - what's the fastest we can expect with networked backups whether that's to unRAID, synology, Time Capsule, a shared Mac, etc.
  5. Click the link once and it'll open a pop-up window with a login prompt. Click it again and the pop-up will display what it should have the first time. That's a workaround. I don't think there's a fix.
  6. UPDATE: I applied the fix described in @limetech's linked comment - problem solved.
  7. Are you running embyserver:beta ? I got the same error but only with the latest beta (4.6.0.34) You can wait for a fix or specify the previous beta in Repository: emby/embyserver:4.6.0.33
  8. Right. In my example the file only existed on Share A prior to the move. I ran a test: Uploaded test.mp4 to share Public Moved test.mp4 from share Public to share system Result: test.mp4 exists in share system and in share Public's recycle bin Note: This is over SMB from a Mac client Both shares have cache enabled test.mp4 existed on neither share prior to the test Here's the File Activity log beginning just before the move (note the last few lines) EDIT: I suspect there's no specific SMB command to
  9. If I move a file (over SMB) from Share A to Share B, and Share A has Recycle Bin enabled, the file will exist on Share B and in Share A's Recycle Bin. Essentially duplicated. Not the biggest problem but if say someone did a bunch of moves between cache-enabled shares it could end up unexpectedly filling the cache pool. Has anyone else noticed this? I'm on a Mac client and I've tweaked some SMB parameters so it's possible this is a "me" problem.
  10. I noticed none of the containers I have routed through this one could communicate with services on LAN IPs. I found the solution in A27 of the FAQ: Adding a variable VPN_OUTPUT_PORTS with a list of port exceptions (mine are Emby and SMTP) I didn't see this mentioned here (maybe it's new) so I thought I'd mention it.
  11. Is there a risk of data corruption if unraid spins down the disk while another partition is being written to? That'd be my only concern.
  12. Actually the latest versions of UD relinquished spin control to unRAID so disks in UD spindown according to the default unRAID spindown timer. Maybe you just have to wait longer or maybe you're encountering the same problem I did - where the USB drive returns an error when spindown's called so even though it's spun down unRAID thinks it's active. I have a fix but I'm not confident enough in it to really recommend it:
  13. My guess is this is related to the spindown fix in 6.9.1. I'm rsync-ing from the 3rd partition (Data) of a disk mounted through UD. You can see reads at 14.7MB/s: If I switch the view to counters though it shows 0 reads: I suspected the R/W rate looks at disk-level stats but the counters look at partition-level stats and only the 1st partition (so my sync from partition 3 doesn't register.) I confirmed this by running an rsync from the 1st partition: rsync --dry-run -avc --progress /mnt/disks/APconfig /tmp/ And as expect
  14. Yup, both zeros. Now I see what you meant. I had to wait for the temperature to disappear again before I cat'd devs.ini but it did and they match up: ["dev2"] name="dev2" id="ST4000VN008-2DR166_ZGY68" device="sdc" sectors="7814037168" sector_size="512" rotational="1" spundown="1" temp="*" numReads="0" numWrites="0
  15. Maybe I'm misunderstanding or I wasn't clear but the relevant disk is Dev 2 (sdc) which shows ~150MB/s reads in the screenshot. I'm not planning to run hdparm -y but I took the last line of that log: spinning down /dev/sdc to mean that unraid had.
  16. Ah, I bet that's because the fix for spindown in 6.9.1 was to monitor partition stats rather than disk stats and pre-clear writes/reads directly from the disks. I wonder if there's a risk running hdparm -y during the write phase - I guess I'll find out soon.
  17. I know unRAID handles UD spindown so I wasn't sure where to post this but I'm pre-clearing a disk and unRAID and/or UD seem confused about its status. Temperature will sometimes display and sometimes not (as if the disk were in standby) and unRAID keeps trying to spin it down. Strange. No problems as far as I can tell, just a heads up.
  18. I don't want to derail further but for anyone following, I ended up customizing sdspin to ignore "bad/missing sense" returns from USB drives, so I can uninstall the plugin (I have no SAS drives.) Thanks for the plugin and your help - otherwise I never would have found the fix.
  19. Okay I figured out what's causing this. I have this block in my SMB Extras: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end And on boot the file it references is populated: root@NAS:~# more /tmp/unassigned.devices/smb-settings.conf include = /etc/samba/unassigned-shares/usb-hdd.conf root@NAS:~# more /etc/samba/unassigned-shares/usb-hdd.conf [usb-hdd] path = /mnt/disks/usb-hdd browseable = yes force User = nobody ... Which explains why it's shared. If I share then un-s
  20. I have a USB drive (sdb) mounted with UD: v6.9.1 spins it down correctly but the (substandard) controller returns bad/missing sense data: root@NAS:~# hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 00 0a 80 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...which this line in /usr/local/sbin/sdspin catches and records as an error: [[ $RET == 0 && ${OUTPUT,,} =~ "bad/missing sense" ]] && RET=1 So although the drive's spun down unRAID thinks it isn't
  21. Okay, mystery solved. Compare the return code from your version to unRAID's: root@NAS:~# sdspin /dev/sdb down; echo $? SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 00 0a 80 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 root@NAS:~# cp /usr/local/sbin/sdspin.unraid /usr/local/sbin/sdspin root@NAS:~# sdspin /dev/sdb down; echo $? 1 root@NAS:~# Now the two scripts: Unraid's returns 1 (RET=1) hdparm () { OUTPUT=$(/usr/sbin/hdparm $1 $RDEVNAME 2>&1) RET=$? [[ $RET == 0 && ${OUTPUT,,} =~ "bad/missing sense"
  22. sdspin! That's what I was looking for, thank you. I mistakenly assumed that script was specific to your plugin. And I see the plugin helpfully saves the default version so I'll dig in and figure out the difference.
  23. Good eye re: hdparm printout, I missed that. Okay but I'm pretty sure unRAID doesn't call hdparm directly - it issues some other command (smartctl?) that then calls hdparm. That call (and its parameters for UDs) is what I'm after - if you happen to know. Re: USB spindown, I can bore you with details if you want?
  24. Plugin was installed but debug was disabled. I re-enabled it (with touch /tmp/spindownsas-debug) and tested again - same results, no additional printouts: root@NAS:~# touch /tmp/spindownsas-debug root@NAS:~# sdspin /dev/sdb down /usr/sbin/hdparm -y /dev/sdb SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 00 0a 80 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@NAS:~# echo $? 0 root@NAS:~# sdspin /dev/sdb root@NAS:~# echo $? 0 root@NAS:~# It's a USB drive so I can tell by feel when it's spun down and it is. Spin down worked even w
  25. Done. Same results whether the drive is active or already spun down. root@NAS:~# sdspin /dev/sdb down SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 00 0a 80 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@NAS:~# echo $? 0 root@NAS:~# sdspin /dev/sdb root@NAS:~# echo $? 0