Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About JustinAiken

  • Rank
    Advanced Member


  • Gender
  • Location
    Southern Utah

Recent Profile Visitors

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

  1. Love unRaid... started as a way to just hold lots of movies for XMBC to play, now it's an automated downloading behemoth that's also running backups and home automation.
  2. I'd love RSS for both blog posts, and new unRaid stable/beta releases
  3. Hahaha I'm dumb. I swear it used to be that little play/stop icon, but clicking the logo works.
  4. I've seen this on 6.7.0, at least both rc5 and rc6, and I believe one of the earlier rc's, but 5 and 6 for sure. If I go to the docker page, and hover over the icon that shows state, instead of popping up the menu of options, it shows the "rearrange tool" - Tried with white theme, black theme, and azure theme - Tried with Chrome, Safari, and Firefox - Tried in both basic and advanced view
  5. https://twitter.com/JustinAiken is following you.
  6. https://github.com/JustinAiken/unRaid-Youtube-DL The meat of it is this command, then some wrappers around it to make it easy to list out vids/channels/playlists you want docker run -it --rm \ --name=youtube-dl \ -v "$YOUTUBE_DIR:/src" \ wernight/youtube-dl \ -v \ --all-subs \ --embed-subs \ --add-metadata \ --ignore-errors \ --playlist-start 1 \ -f bestvideo+bestaudio \ -o "$path" \ --download-archive /src/archive.txt \ "$youtube_url" || echo "Download failed :/"
  7. Just had the same problem, and deleting the server.key/server.cert in `appdata/sabnzbd/admin` worked for me too 👍
  8. 8 seconds to finish running `xfs_repair -v /dev/md2` and I'm back to all green.. thanks @johnnie.black!
  9. Today when I started the array (rebooted to try the 6.7.0rc2 from 6.6.6; think if anything is wrong it was the reboot, not the new version that caused this) I see this: If I do `ls /mnt/` I see all my discs except for `disk2` which is just missing. - Does this mean my array is emulating disc2 via parity, or is it out and I'm going to find out once I go to watch a movie to find it's randomly not there? - Is this a disc issue, or filesystem issue? ... I used to deal with things like this all the time when I was on reiserfs, but in the last few years I've forgotten what this is like! 😛 From my syslog: Jan 29 08:46:12 Tower emhttpd: shcmd (4051): mkdir -p /mnt/disk2 Jan 29 08:46:12 Tower emhttpd: shcmd (4052): mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Jan 29 08:46:12 Tower kernel: XFS (md2): Mounting V5 Filesystem Jan 29 08:46:13 Tower kernel: XFS (md2): Corruption warning: Metadata has LSN (1:741158) ahead of current LSN (1:741150). Please unmount and run xfs_repair (>= v4.3) to resolve. Jan 29 08:46:13 Tower kernel: XFS (md2): log mount/recovery failed: error -22 Jan 29 08:46:13 Tower kernel: XFS (md2): log mount failed Jan 29 08:46:13 Tower root: mount: /mnt/disk2: wrong fs type, bad option, bad superblock on /dev/md2, missing codepage or helper program, or other error. Jan 29 08:46:13 Tower emhttpd: shcmd (4052): exit status: 32 Jan 29 08:46:13 Tower emhttpd: /mnt/disk2 mount error: No file system Jan 29 08:46:13 Tower emhttpd: shcmd (4053): umount /mnt/disk2 Jan 29 08:46:13 Tower root: umount: /mnt/disk2: not mounted. Jan 29 08:46:13 Tower emhttpd: shcmd (4053): exit status: 32 Jan 29 08:46:13 Tower emhttpd: shcmd (4054): rmdir /mnt/disk2 Seems likely that I should do what it says and run `xfs_repair`, but before I mess with 8TB of data thought I'd better check here....
  10. > When connecting from a Mac to a public share with enhanced OS X support enabled Ahha... that's been plaguing me for months, didn't know it was related to the "enhanced OS X" option. Thanks for posting!
  11. I'm more or less indifferent to the new look, except on the Docker page - it was better before the update, a lot more information fit and was readable at once. Adjusting the zoom on the new doesn't bring it back - something about padding or the like.
  12. I've been getting "unable to write to..." errors since upgrading to 6.6.1, from my Mac to a my cache share. I've tried running `newperms /mnt/cache/<folder that complains>` then ejecting and remounting the SMB share, same error...
  13. @TexasAg - if you do that, then does the query log show the host instead of the IP under "Client"? Or is that just to make local DNS queries resolve?