Leaderboard

Popular Content

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

  1. You need to cover pin 3 of the SATA power connector on the drive so the drive will power up. Kapton tape is the best option. You can overlap pin 2 and 1 also if you can't cut a piece precisely enough to only insulate pin 3.
    2 points
  2. A reboot will probably be best after making the change
    1 point
  3. That will work. Add another Path Mapping (eg: /movies2 mapped to /mnt/disks/whatever) to Plex. Make sure that the Access Mode you set for the path when adding it to the template is either Read/Write:Slave or ReadOnly: Slave
    1 point
  4. You could install the plugin Unassigned Devices on Tower2 and mount a share using SMB on Tower 1. I am not using it for Plex myself, but it might work.
    1 point
  5. When you call notify without parameters , you'll get the available options. # notify notify [-e "event"] [-s "subject"] [-d "description"] [-i "normal|warning|alert"] [-m "message"] [-x] [-t] [add] create a notification use -e to specify the event use -s to specify a subject use -d to specify a short description use -i to specify the severity use -m to specify a message (long description) use -x to create a single notification ticket use -t to force send email only (for testing) all options are optional notify init Initialize the notification subsystem. notify smtp-init Initialize sendmail configuration (ssmtp in our case). notify get Output a json-encoded list of all the unread notifications. notify archive file Move file from 'unread' state to 'archive' state. Your script can you check the exit code of rsync and use that to call notify. For example rsync -av FileDirectory1 FileDirectory2 if [[ $? -eq 0 ]]; then /usr/local/emhttp/webGui/scripts/notify -i normal -s "Operation complete" else /usr/local/emhttp/webGui/scripts/notify -i warning -s "Operation failed" fi
    1 point
  6. @bombz - You will need to do a new config to remove the old drives and add the new one. Don't delete the data from the 2 500G drives, and you'll have a backup just in case you have any issues with the external. I do recommend a preclear to test out any new drive, but technically you would not need to preclear it. When you did a new config, parity is rebuilt. What you could do is this. It's what I would do. You don't need the external. Preclear the new 4T drive and second parity disk (if you have). (Recommended but not mandatory) Shutdown server. Remove one of your 2 500G drives from the server, and add your 4T drive. Boot server. Do a new config but keep configuration. Add the 4T add as a data drive and omit the 2 500G drives from the array configuration. (I'd also omit parity, but that's up to you. Without parity you'll be able to copy faster). Change filesystem to xfs on the new 4T drive before starting array. Start the array. (Let parity build if you added parity.) Format the 4T drive. Use unassigned devices and mount the 500G drive. Copy all the data from the 500G drive to the 4T. After the copy, shutdown the server. Swap the 500G with the other one. Boot the server, start a array, use UD to mount the other 500G, and copy other 500G drive to the 4T. Shutdown the server again. Remove the second 500G. I think you said you wanted to add second parity drive. This would be the time. Otherwise just leave slot empty. Boot the server. Before starting the array, add your parity disk to the config (if didn't do before), and your second parity if you are adding it now. Start the array and parity(ies) will build if you added.
    1 point
  7. CA is the defacto app store for unRaid and is used to add and find any app, not just plex FCP does what it says it does. Looks for configuration errors and offers up solutions
    1 point
  8. I would think "Community Applications" and "Unassigned Devices" are probably ones most people think are worth installing,
    1 point
  9. @bombz - So it sounds like you are completely full in terms of drive slots. So you want to copy data from 2 500G drives to an external drives, and then add a 4T disk that you'll format as xfs. This sounds like a reasonable approach. It will require rebuilding parity to remove the 500G disks and incorporate the new 4T disk containing data. Swapping add-on controllers is seamless. UnRaid recognizes drives by serial number. So if you remove the old, attach the drives to the new, and boot, all the drives will be assigned to their proper slots as though nothing had changed. (Obviously connecting everything securely and not disturbing the drive cabling of other drives is critical to not causing drives to drop offline). Related to ports to avoid I am confused. The SuperMicro add on controllers that use the Marvell chipset are problematic, but motherboard ports that are provided from the Intel chipset or non-Marvell chipsets are fine to use. Your post made it sound like you were trying to avoid using regular motherboard ports but maybe I misunderstood. I do suggest planning for an empty slot as it is useful in some recovery scenarios. And comes in handy for preclears as well. It is also needed to convert from rfs to xfs.
    1 point
  10. I had my UNRAID server freeze up a bit while using this. Was watching a football game for about 2 hours and the transcoding must have filled the ram up till there was no memory left. I have 32 GB of RAM but I had a VM running at the same time. unRAID started killing off Dockers till it finally killed Plex. Works great for movies, TV shows etc but be careful with the DVR. Sent from my SM-G955U using Tapatalk
    1 point
  11. It still works for single parity, but note that you only need to do that if you need the data to remain on specific disks like it was because of include/exclude settings or other reasons.
    1 point