Jorgen

You are of course right. The correlation was only that they both started happening on the same day after 2 years of flawless operation. But I have now seen both types of errors occur independently of each other. Since my last post I've added a new 8TB drive and decided to move all content off disk1 (the one with read errors) onto the new disk4. Mainly because I wanted to convert disk1 to XFS. During this move, I kept seeing lots of read errors, both in the syslog and the raw smart value (that I'm now trying my hardest to ignore). The move of 3TB+ resulted in about 1000 read errors according to syslog. Diagnostics attached. I didn't realise this before the data move, but I must have somehow moved disk1 back to the dodgy motherboard socket when I added the new disk4. Sigh. Although to be honest I don't have much choice. I only have 6 sata ports on the motherboard, and they are all occupied now. So in an effort to try to pinpoint where the read errors are coming from, I'd like to stress test both the mb port, disk1 and the cable between them, while changing only one thing at the time. First test is the cable. I've replaced the old cable with a brand new one, but left disk1 connected to the suspect mb port. So here's my question (finally): since there's no data on disk1 now, how do I trigger lots of reads? I need big volumes, because the errors are intermittent Is there a way to run only the pre-read part of the pre-clear scripts? Or should I just copy big chunks of data to/from the disk? tower-diagnostics-20170719-2027.zip

Yes agree, by itself it's not important, but they seem to correlate with the read errors in the syslog that trigger scary warning emails.

Update: Read errors keep occurring. Raw Read Error Rate = 66 today (raw value), from 48 only 3 days ago. Looks like different sectors each time which I take as an indicator of problems outside the disk. Plus the fact that short and long smart tests do not increase the read errors either. Opened the case to follow the advise from @johnnie.black and noticed that the motherboard sata socket that disk1 is plugged into is very loose compared to the other sockets. This is now my prime suspect. I've moved the disk1 sata cable to another motherboard socket. Did not change the cable itself, but did reseat it on the disk end once more. Back to monitoring mode. Fresh diagnostic attached for completeness. tower-diagnostics-20170710-2215.zip

Thanks, appreciate your advice. I've reseated the cables for now, but haven't swapped them around yet. Will keep a close eye on things and try you suggestion if it keeps happening. Sent from my iPhone using Tapatalk

Hi all, Just encountered my first ever Array Health Fail notification. Apparently my disk1 has/had read errors. This happened a few hours after I upgraded my CPU, which required me to unplug all data and power cables to all my disks. So hopefully (most likely) this is just a cabling issue. The disk has passed a short and long SMART test after the read errors. But I've noticed the raw_read_error_rate counter has increased over the last few days which I thought was an internal disk problem, not cabling? Diagnostics attached. I have read a fair few older posts with similar issues, but I'm not confident in my ability to parse the syslog and smart reports correctly. If someone more knowledgeable then myself could have a look and suggest next steps that would be greatly appreciated. Thanks in advance Jorgen First read error in syslog: Jul 2 17:23:26 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 2 17:23:26 Tower kernel: ata6.00: irq_stat 0x40000001 Jul 2 17:23:26 Tower kernel: ata6.00: failed command: READ DMA EXT Jul 2 17:23:26 Tower kernel: ata6.00: cmd 25/00:08:40:00:48/00:00:6f:01:00/e0 tag 18 dma 4096 in Jul 2 17:23:26 Tower kernel: res 51/40:08:40:00:48/00:00:6f:01:00/e0 Emask 0x9 (media error) Jul 2 17:23:26 Tower kernel: ata6.00: status: { DRDY ERR } Jul 2 17:23:26 Tower kernel: ata6.00: error: { UNC } Jul 2 17:23:26 Tower kernel: ata6.00: configured for UDMA/133 Jul 2 17:23:26 Tower kernel: sd 6:0:0:0: [sdf] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jul 2 17:23:26 Tower kernel: sd 6:0:0:0: [sdf] tag#18 Sense Key : 0x3 [current] Jul 2 17:23:26 Tower kernel: sd 6:0:0:0: [sdf] tag#18 ASC=0x11 ASCQ=0x4 Jul 2 17:23:26 Tower kernel: sd 6:0:0:0: [sdf] tag#18 CDB: opcode=0x88 88 00 00 00 00 01 6f 48 00 40 00 00 00 08 00 00 Jul 2 17:23:26 Tower kernel: blk_update_request: I/O error, dev sdf, sector 6161956928 Jul 2 17:23:26 Tower kernel: ata6: EH complete Jul 2 17:23:26 Tower kernel: md: disk1 read error, sector=6161956864 tower-diagnostics-20170705-1059.zip

@Djoss can correct me if I'm wrong, but mapping /watch and /output to the same unRAID folder is probably not a good idea. Especially since they are both mapped to the root of ALL your shares. I recommend you turn off the docker until someone can give you better advice on how to map the folders, or you might be running at risk of data loss. Or at the very least, map /watch to something else, even if it's just an empty folder on one of your shares. There's a few lines in your log relating to errors processing files from the /watch folder and it doesn't look like it's something you want to be happening. For what it's worth here are my folder mappings as reference, notice that /storage is different to /watch that is different to /output:

unRAID. But I'm pretty sure it's already enabled by default since 6.3, see link to release notes below. You can also toggle on "Enhanced OS X interoperability" per SMB share. The helps text states: "When set to 'Yes' provides enhanced compatibility with Apple SMB clients, resulting, for example, in faster Finder browsing. This may cause some issues with Windows clients, however. Please also refer to the VFS_FRUIT MAN PAGE." But it's not clear to me what exact vfs_fruit options the toggle enables. Maybe someone more knowledgeable can chime in about that.

Thank you, thank you, thank you!!! I tried adding a mouse and keyboard earlier but couldn't get it to work. I incorrectly assumed this was because of vt-d missing, but your post prompted me to have another crack at it. For some reason I had selected "USB Mode = 3.0 XHCI" when I first created the VM. Once I spotted that in the XML and changed it back to "2.0 EHCI" things started working again. Thanks again for your help, and for all the awesome guides your are producing!

Hi all, I've shot myself in the foot and was hoping someone on this thread could help me out. I have a 10.12.5 VM that was created with the clover method and was running fine, but during troubleshooting of an unrelated problem I set my Ethernet interface to "inactive" via the network preference pane. Face palm! I lost connection to the VM of course, because it has no means of communicating with the outside world anymore. And now I can't connect to it to restore the network preference. I had splashtop and apple's screen sharing working, but can't connect to either anymore (not surprisingly) NoVNC and other VNC clients can connect while the VM boots up, but as soon as the apple logo appears I lose mouse/keyboard functionality. I can still see the boot progressing up until the login screen, but that's as far as it gets. Without any input method I can't login. My CPU doesn't support vt-d, so I don't think I can pass a physical mouse/keyboard to the VM? I'm open for any suggestions at this point. Here are some options I've considered or tried: 1. Mount the HFS+ partition of the vdisk image and manually edit/remove the network plists. I've only managed to mount it read only so far, but I'm also a bit worried about these fits as I'm not at all confident that I'm doing the right thing. 2. Add another virtual network interface in the XML. Maybe there's a way to trick OS X to think I have a wifi or other interface that can give me network access. I have no idea where to start on this though, or if it's even possible. 3. Create a new VM and restore my user account from the latest time machine backup. This will take hours and I won't learn anything new, so it's my last resort. Also, I had problems restoring from time machine when I first created the now broken VM. 4. Buy a vt-d capable CPU and pass through physical mouse, keyboard and GPU. This is actually my preferred solution but will take me some time to get the funds together and then waiting for the order to ship. Not sure I can live without the VM for that long. Sorry for the long post. If anyone have any ideas on best way to proceed please share. I'm posting here because there aren't many Mac-VM-on-unRAID threads around. Happy to start a new thread if more appropriate. And thanks to gridrunner for making all this possible in the first place!

Actually, I can still login with the default Admin/Password even after I've removed the Admin user. Guess the CLI password change is still needed.

Excellent! Thanks for testing. Sent from my iPhone using Tapatalk

I thought the default admin account was recreated on update of the docker though, is that not the case? Sent from my iPhone using Tapatalk

Exactly Sent from my iPhone using Tapatalk

Ok, so my symlink problem was due to my own misunderstanding of how to create them. I know you tried to tell me this Djoss, but it took me a while to understand that you can create a symlink pointing to any path, whether that path actually resolves or not. For other's benefit, here's one way to achieve this. Assuming you store your media on unRAID like this: /mnt/user/Media/Movies/moviefile.mkv And you have the following HandBrake folder mappings: /storage = /mnt/user/Media /watch = /mnt/user/Media/Handbrake-hotfolders/watch Then from the unRAID console, to create a symlink in the watch folder that resolves from within the docker container: ln -s "/storage/Movies/moviefile.mkv" "/mnt/user/Media/Handbrake-hotfolders/watch/moviefile.mkv" Now, from an unRAID perspective this symlink is most likely broken, because /storage does not exist. But from within the Handbrake container, the link resovles fine thanks to the folder mappings. And it works great. So that's the last of my problems, all good now. Thanks again Djoss, really like this docker!

I've configured my (custom) preset to retain ALL audio tracks (and subtitles), but I haven't actually tested the results. If I get a chance I'll have a play with it this weekend. Sent from my iPhone using Tapatalk

Doh! Thanks guys, don't know how I managed to miss those two things, seems so obvious in hindsight! So deletion of files in watch is now working perfectly for me, thanks again! I think it has also "fixed" my other problem with multiple files in watch on docker start, as each file deletion seems to trigger a rescan of the watch folder... Will have to read up on symlink creation. My ultimate goal is for NZBGet to store the HD file to my normal Media share, and also put a symlink to it in the Handbrake watch folder (but only whenthe movie is listed on my friends trakt.tv watchlist...) If anyone knows how to create a symlink and change the folder part to allow for the docker folder mappings, please speak out! Otherwise I'll report back if/when I solve it...

Hi Djoss, thanks for this! I went to town with the testing and unfortunately not everything passed. Quick summary: Files aren't deleted from watch folder after succesful conversion Multiple files in watch folder seems to cause problems triggering detections of all files. It stops after each conversion, requiring another file to be added (or deleted) to convert the next file (but only one) Symlinks only works if the target file is in the same directory (watch folder). In hindsight I'm not sure this was a great idea, since /storage and /watch are mapped to different folders inside the docker the link is probably broken from Handbrake's perspective? Or maybe i'm not creating the symlink correctly (linux noob...) Details of test cases and results here: https://docs.google.com/spreadsheets/d/11voL9X4c9d9IL18NGx1m8SAcM_smPhoxvYPixJzpEJU/pubhtml Let me know if something is unclear and I'll try to explain it better.

At the risk of sounding greedy here, but would you also consider adding an option to automatically delete files from the watchfolder once they are succesfully processed? Thanks!

Agree with dlandon, of the handbrake dockers I've tested this is the easiest to configure and works the best out of the box. For example, this one lets me add files to the watch folder while the docker is stopped, and when started will happily chew through the backlog. Neither of the previous dockers let me do this. (I am using CA User Scripts to schedule all handbrake processing overnight) I've found a small bug though: File names containing spaces will make the watch folder skip the file. To reproduce: 1. Add a file to the watch folder called "A file with spaces.mp4" 2. Check logs. There will be a series of skipping file messages, one for each of "A", "file", "with", "spaces.mp4" And while I have your attention, does the watch folder work with symlinks instead of actual files? If not, consider this a feature request

Oops, sorry about that. Wrote it from memory since copy-paste from ssh/mc to safari on an iPad proved a little bit too challenging... Sent from my iPhone using Tapatalk

Hi Kizer, this is what I've done and it works for me: 1. From the HandBrake GUI, export your custom preset to a file and store it in your config folder. For example: appdata/HandBrake/mycustompreset.json 2. Edit the HANDBRAKE_COMMAND line in appdata/config/Handbrake.conf like this Default Config HANDBRAKE_COMMAND='HandBrakeCLI -i "$SRCDIR/$SUBDIR/$FILENAME" -o "$DESTDIR/$SUBDIR/$BASE.mp4" --preset "Very Fast 1080p30"' New config HANDBRAKE_COMMAND='HandBrakeCLI --import-preset-file /config/mycustompreset.json -i "$SRCDIR/$SUBDIR/$FILENAME" -o "$DESTDIR/$SUBDIR/$BASE.mp4" --preset "mycustompreset"' IF your preset have spaces in the name, you need to enclose the name in double quotes. More info here: https://handbrake.fr/docs/en/latest/cli/cli-guide.html You should be able to import the preset directly from the GUI version with --import-preset-gui but I never got that to work. Plus I wanted my custom preset to be stored outside the container anyway, in case I have to re-install in the future.

Minor bug: When you hover over the name of a script and click "edit name", the pop-up menu doesn't collapse automatically (like it does for the other options) If you click on "edit name" again in this state, code snippets are being added to the name box. Each click adds more code.

Latest update seem to have fixed this problem for me, thanks Coppit!

appdata/Handbrake is set to 99:100 for me (It's possible that I've set this manually during troubleshooting) The folder I have to delete to get it working again is: appdata/HandBrake/handbrake That one is recreated on docker start and seems to have correct settings. The PUID/GUID is set in the appdata/HandBrake/HandBrake.conf root@Tower:/mnt/cache/appdata# ls -l | grep HandBrake drwxrwxrwx 3 nobody users 117 May 15 22:22 HandBrake/ root@Tower:/mnt/cache/appdata# tree -plug /mnt/cache/appdata/HandBrake /mnt/cache/appdata/HandBrake ├── [-rw-r--r-- nobody users ] HandBrake.conf ├── [drwxr-xr-x nobody users ] handbrake │ ├── [-rw-r--r-- nobody users ] Activity.log.92 │ ├── [-rw-r--r-- nobody users ] ghb.pid.92 │ ├── [lrwxrwxrwx nobody users ] handbrake -> /config/handbrake │ ├── [-rw-r--r-- nobody users ] preferences.json │ └── [-rw-r--r-- nobody users ] presets.json └── [-rw-rw-rw- nobody users ] processed_files.dat I see that coppit is updating some files on github and it looks like the file that creates the error (/etc/my_init.d/start.sh) has been updated to remove the symlink to the handbrake config (which is part of what I'm deleteing) so maybe he's across the problem and solution already. I'll just wait patiently for a container update...

Apologies, I got that wrong. I can actually leave the file config/HandBrake.conf as it is after editing. To get the container working again I have to delete the whole directory config/handbrake then just start the container. The directory and files are recreated and it all works until next container restart (including scheduled appdata backups).