Jump to content

Russ Uno

Members
  • Content Count

    376
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Russ Uno

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    Rhode Island, USA

Recent Profile Visitors

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

  1. I'm not sure if this is related or not but I do at times run into a situation that I get an error message that I can not delete a file, "File Busy" from my Mac from within the app that created it. it is always a newly saved/created file. If I quit the app that created it or restart the Mac I can delete that file from within the app that created it. It seems that the app has not released possession of it until the app has been closed. This only happens with UnRaid and SMB and never with files saved locally. Since I normally shut down the system at night I just delete it the next day after a restart.
  2. Yes, you're correct, no auto save, just auto save for the backup files.... don't know why I even said that. I've only been using it since v4. And that auto save for backups has been a source of problems for some users, as I recall for a long time. Though I have never had any issues with it. Protools is a fussy app if things are not exactly how they, Avid, expect it to be but it's fantastic if you follow the rules to the letter. You could run and save the session files from a local drive and save your audio files to your external, NAS, UnRaid, thereby getting around the problem of the auto save issue to the NAS.. When you're done you could copy the local files back to the NAS (for backup). You need to set up the session locally so all associated files are local then move/copy the session folder to the NAS, run the session locally, re-link the audio to the NAS then delete the local Audio..
  3. Do you have this issue with auto save? Or is it just the Auto Backup? Auto backup is not the same, it creates new files labeled with .bak and only keeps X number of them. So say it is set for 10 then when it reaches 11 it will delete the first one and replace it with the newest. Maybe the issue is deleting the old files and not the save process since you can use Command+S without issue. You can test it by deleting all the backups (if you want to live dangerously) and see how long it takes for the error to appear. If you set the backups every 10 miniutes with 10 backups it should take 100 minutes before the error shows up. I've only used a backup maybe twice in 17 years..Running PT 4, 5, 6, 7 and 10 HD, I skipped 8 and 9.
  4. Have you tried this? Using AFP from OSX select the folder you want to write to and do Command+i, check the permissions at the bottom of that window. I don't know if there is a way to set it to Ignore Permissions on UnRaid as you can with other external volumes but they should all say Read & Write.
  5. Same here, I use Carbon Copy Cloner. Works great with UnRaid.. I use to use SuperDuper but Carbon Copy Cloner is much better and faster on networks.
  6. I'm glad I saw this because I use * to start a lot of directory names in OSX to force those to sort on top of the list of names, I still use the list view... Time to change I guess but never had any issues with UnRaid but then I normally back up my Macs to Image files. I'm also not running Sierra or High Sierra. Are there any issues using a bullet "•", Option+8 on Mac? I also use those.
  7. Sounds reasonable.. The trick is How Much Heat.. You need to get the contaminates off with the distilled water, which has no impurities, ASAP then dry completely as quick as you can. I've used an oven at very low temps, a convection oven works well.. I'd say maybe 90-100 deg.F. to start. Old recording tape is cured at 180 deg or so for around 8 hours in convection ovens to get the moisture out of the coatings to make it playable again.
  8. An old tip use by underwater photographers when cameras get flooded is to wash them out with distilled water then let the dry. You want to get any salts and impurities off the electronics before you try to power them up. You can use warm , not hot, air to speed up the process.
  9. I don't know if this still applies but in the past, I haven't checked it since my upgrade to 6.2.4, with v6.1.9 I found everything is faster if you turn off SMB if you don't needed it when AFP is on.
  10. No. Just make sure you adjust all the bios settings on the new MB... to boot from the flash drive and what ever else needs to be changed
  11. That would be a great feature, to ignor moving files that are a certain type, modified before a certain date/time or etc. I can only program OTA tv shows for a day at a time because if I program for the next day or so the place holder files for the next day also get moved.
  12. Did this also happen with an earlier version of Unraid? I'm running v6.2.4.. Unless you have a bad switch, cable, cable connection or etc...
  13. It's not actually transfering data, just changing a directory pointing to the file(s). Although if moving to a different share on different disc which the second share does not exist then, I believe the files would actually come through the network, to the Mac then back out the network to the second share.. So that's a long way around. If that is the case probably a better way to move the file is in Terminal... Somebody correct me if I'm wrong.
  14. I just tried it with 4gb and it only took <second from my '11 iMac. I'm on OSX 8 (ML) which is not suppose to be as good with SMB.. Maybe it is a network issue, mine is all hardwired except WIFI for my iPad & FireStick.
  15. So you have 2 windows open in finder, each is open to a different share and you are transferring a file(s) from 1 window/share to the other is when you have the issue. Is that correct?