Leaderboard

Popular Content

Showing content with the highest reputation on 12/18/18 in all areas

  1. Looks like you have quite the variety of drives, so that complicates things. Here's how I would proceed. 1) Build a new array, ultimately your goal will be a solid, reliable array. Don't reuse any of your old drives since we are going to try an extract data. Note that with this method of recovery, I don't think you can rely on any drive giving you back 100%, so if you have to do a rebuild on any given drive (assuming you fully recover that many drives), I don't know how reliable your rebuilt drive would be, either. You're welcome to try it. If not, maybe start with 1 Parity and 1 Data and work your way up from there. I'm assuming you know which of the old drives are data and which were parity. This method recovers the data treating the old array drives as JBOD. 2) Take say the STBV5000100, buy another exact model drive. Last time, I bought a used working drive off E-Bay. Test the newer drive, make sure it works and is reliable. Replace the bad drive's board with the new drive's board. Plug the bad drive into the server and use something like Unassigned Devices to mount it, then see how much data you can copy off of it. Once you have extracted as much data as you can, unmount and remove your bad drive. Swap the controller boards back. Bad drive goes on the shelf in case you need it for further recovery. The newer drive can be pre-cleared and added to the array. Repeat this step for all drives. Something I heard was that reallocated sectors are recorded somewhere on the controller board. I heard it quite a long time ago, so I don't know if it is/was true. If it is, your recovery may involve accessing some incorrect sectors, which is why I think the data isn't guaranteed to be 100%, but again anything is better than 0%. This should also be non-destructive, so you could still use other methods to recover your data if you like. I have not heard of the diode fix, nor have I ever attempted to alter a controller board in any way. All I have done is a straight board swap, and hope that any data losses are livable. Thankfully, this isn't something that I have had to do regularly, but it has worked once or twice. PS: Dunno about the warranty, but I'd skip the soldering iron if you intend to go this route.
    2 points
  2. Hello, I am new here and have been trying to install a container from docker hub but I keep getting failures. I've been using the instructions on Wowza's website but I am very confused. https://www.wowza.com/docs/how-to-set-up-wowza-streaming-engine-using-docker https://hub.docker.com/r/wowzamedia/wowza-streaming-engine-linux/ Any help is appreciated. Let me know if you need anymore info from me.
    1 point
  3. FIXED I have just tested the connection to deluge in radarr settings (with and without proxy enabled) and i am getting this error, which is the cause. Unknown exception: Error getting response stream (ReadAsync): ReceiveFailure Value cannot be null. Parameter name: src Turns out my port in radarr for deluge had changed. Not entirely sure how, but all seems ok now. Many thanks for the help, time to start testing out sonarr
    1 point
  4. http://man7.org/linux/man-pages/man1/logger.1.html Would require you to parse the syslog file, looking for identical lines and replace them akin to what happens when you run diagnostics. Probably easier way would be to modify the logic of your script to not output if the previous line was the same, and instead of running it every 5 minutes, run it once in a continual loop with a 5 minute sleep period between cycles
    1 point
  5. Put the boot flash in your PC and make a backup of the config folder. Prepare flash as a new install. Copy config backup to flash, Boot
    1 point
  6. Yes - ffmpeg is pre-installed in the docker image.
    1 point
  7. define LAN_NETWORK with a comma between networks, this will then add both.
    1 point
  8. yes, there is a lot of stuff installed in this image, its going to be bigger than most, keep in mind that if you run other images created by me then you will make use of the caching of layers, thus the pull down wont be anything like that.
    1 point
  9. Not media file related, but just sharing how I backup to gdrive my local /mnt/user/backup share where I keep my VM backups, CA appdata backup, cloudberry backup of important files from other shares etc rclone sync /mnt/user/backup gdrive_media_vfs:backup --backup-dir gdrive_media_vfs:backup_deleted -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 3 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --delete-empty-src-dirs --fast-list --bwlimit 10000k --tpslimit 3 --min-age 30m rclone delete --min-age 90d gdrive_media_vfs:backup_deleted --bwlimit 10000k sync keeps a copy in the cloud of my files. Any files deleted or moved locally that have already been synced are moved to the backup_deleted directory on gdrive: --backup-dir gdrive_media_vfs:backup_deleted where they are deleted after 90 days: rclone delete --min-age 90d gdrive_media_vfs:backup_deleted --bwlimit 10000k
    1 point
  10. No. A team drive created by a google app user (who has unlimited storage) can be shared with any google account user(s). So, you could create team drives for friends to give them unlimited storage. Each user has a 750GB/day upload quota, so as long as each upload to the shared teamdrive is coming from a diff user (diff rclone token for the remote, and client_ID to try and avoid API bans) then you can utilise the extra quotas. I've added 3 accounts to my plex teamdrive and it's all working fine so far for 4 uploads (3 shared users and my google apps account) I imagine google has a FUP to clamp down on real abuse e.g. creating 100 teamdrives.
    1 point
  11. Scheduled for Unraid OS 6.7 release.
    1 point
  12. I look forward to these kind of tools becoming more easily accessible. However you and I are in the minority. Unraid biggest user group are data hoarders, who don't really care much about security. I'm glad Tom keeps the product fresh and fully patched. Never hurts to ask. If he can do it easily, it may happen. Sent from my chisel, carved into granite
    1 point
  13. Roger.. for futre searchers.. UnRAID downgrade... 1) telent/SSH into your box 2) cp /boot/previous/bz* /boot/ 3) reboot Thanks for your help.
    1 point