Jump to content

heffe2001

Members
  • Content Count

    404
  • Joined

Community Reputation

5 Neutral

About heffe2001

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1222 profile views
  1. Just a FYI, 2020.05.27a took care of my issue, details are shown now with no issues.
  2. Yep, sure do. I'm currently a version behind latest, waiting to update after everyone here goes to bed, lol. I've verified that I do have director information on my movies, so not sure why it's getting an error on that line. Updated this morning to the latest Plex Pass version, and still the same.
  3. Still not able to get any detailed info on any show that comes up, gives me the same error still as posted above.
  4. When I click on detail, I'm getting the following error on every movie I've tested: Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/plexstreams/movieDetails.php on line 63 Year: Rating:
  5. Seems everything survived through 2 reboots (for other reasons), so it would appear it was that dynamix plugin causing the issue.. On another note, would it be possible to add an option to hide passed-thru drives?
  6. After removing that dynamix SCSI devices plugin I get the desired results.. SO if anybody is having the issue of SAS drives (or raid containers) not showing up on UD, and have that dynamix plugin installed (and aren't using a Areca controller), try removing it and see if it helps.
  7. With Preclear removed it still shows the same (none of the SCSI- drives are listed). I'll look at the ST6000, it's not been used and I honestly can't even remember buying it let alone installing it, lol. I do have the dynamix SCSI Devices plugin installed from when I had an Areca controller in the machine (long since removed). I wonder if that's got anything to do with the issues? I may try uninstalling it soon as my docker restore is done and restarting the machine to see if it makes any difference.
  8. Those would be the ones. The've been giving those 2 warnings since installation, but have worked without issue up to now (and still seem to work ok when I manually mount them). UD won't actually see any of the scsi- devices (I have a couple raid arrays set up on a hp 420 controller that I use directly mapped to a windows VM, but it didn't see them before I mapped them either). Looks like it's basically not finding a grown defect list by that 'error': 0x1C 0x02 GROWN DEFECT LIST NOT FOUND It's not seeing any of these devices: scsi-HUSMM1640ASS200_0QV1M8XA@ scsi-LOGICAL_VOLUME_001438033715B80-part1@ scsi-ST31000424SS_9WK2N0XS00009120NV0P-part1@ scsi-HUSMM1640ASS200_0QV1M8XA-part1@ scsi-LOGICAL_VOLUME_001438033715B80-part2@ scsi-ST6000NM0034_Z4D2NK0X0000R545W10B@ scsi-HUSMM1640ASS200_0QV1NH7A@ scsi-LOGICAL_VOLUME_001438033715B80-part3@ scsi-ST6000NM0034_Z4D2NK0X0000R545W10B-part1@ scsi-HUSMM1640ASS200_0QV1NH7A-part1@ scsi-LOGICAL_VOLUME_001438033715B80-part4@ scsi-LOGICAL_VOLUME_001438033715B80@ scsi-ST31000424SS_9WK2N0XS00009120NV0P@ I'd forgotten about even putting that ST6000 in there at all, since neither the system nor the UD detected it, lol.
  9. I'm having the same issue. I have 2 SAS SSD's installed that were showing up, I tried to add another drive to that controller and it wouldn't show up, so I tried restarting the server just to see if the controller could even see the drive (it didn't, drive is definitely bad, but it does still see the 2 SAS SSD's). On restart, Unassigned Devices can't see those 2 SAS drives now, but you can find them in the '/dev/disk/by-id' to identify them, and even manually mount them if you want (both contain XFS partitions, one I'm using for my plex transcoding cache, and the other I'm going to use for my Docker appdata). I can always edit the go file to mount those 2 drives where they need to be by their 'by-id' info (just in case them move from their 'sd?' designation), but they WERE working in UD, but it will NOT see them now (through about 4 boots so far, and this damned HP DL380p-G8 takes forever to reboot, lol). I'm going to attach my current diagnostics to this post. Also, is there a reason you can't mount a drive in UD wherever you want (I believe this was the old behavior), and not be forced to mount them in /mnt/disks/ ? Or would it be possible to make that a toggleable feature? media01-diagnostics-20200505-0102.zip
  10. When did the ability to create my own directory under /mnt (/mnt/docker-appdata/data) become a forbidden mount point for the docker data area? I needed to shut down my dockers so that I could replace the drive the data is stored on (usually mounted under /mnt/docker-appdata/ with the data directory located in the root of that particular drive). When I tried to turn dockers back on, that directory ends up turning red, and then the system says that I need to enter it in the format required. This has always worked in the past, been set up that way on my system since dockers were enabled. I don't WANT to mount that under /mnt/disks (another issue I have a problem with) and map from there, and I definitely don't want my docker information on the array. I also have a problem with Unassigned Devices not allowing me to mount new drives wherever I want under /mnt (it forces me to use /mnt/disks), although I had it mounting several drives under the main /mnt directory (and still have 2 that do, unless I try to modify them then my mount points are screwed up). Is this 'feature' of not allowing me to put stuff where I want able to be disabled, or am I going to have to reconfigure my entire setup because someone else decided they knew better where my stuff should be mounted?
  11. Would it be possible to get a version of this for the Tesla cards, I have a K20 I'd love to use for transcoding on my Plex server for my remote users (I don't use H265, so the Tesla card would work great for my needs), but it won't work with the stock Nvidia drivers. Nvidia has a seperate driver series for the Tesla cards apparently, the latest of which is available here: https://www.nvidia.com/Download/driverResults.aspx/158193/en-us
  12. What client machines are you using? I saw a post on the Plex group last night about issues with some Android boxes doing what you're describing. Go into the plex settings on that client, and find 'Use New Player' and disable it and see if it works. My father in law is having the same issue, and I'm going to try to walk him through that to see if it fixes his issue as well this afternoon.. Thread here: https://forums.plex.tv/t/new-player-on-android-tv-not-working/545682/2
  13. Anybody happen to be using a HP DL380p Gen8 with one of the Tesla K20 compute boards for things like Plex transcoding, or FoldingAtHome? They are getting cheaper (the k20's), and it'd be nice to take some CPU load off my server when friends are watching stuff remotely (or even set it up with FoldingAtHome for the Covid19 stuff).
  14. I'm using a bonded pair of 10g ports on my HP server, and it's working just fine with RC3, so bonding is installed and working.
  15. I've NEVER had good luck with the small APC bricks, especially on servers. I also use a minimum of a 1000va (I have a rack mount SMT1000RM2U Smart-UPS 1kva powering my server & external drive chassis', and a Back-UPS Pro BR1500G 1500va that powers my switch, router, wireless, etc). Those little power-bar-like backups aren't really intended to run a server, they're more for desktop PC's anyway. What's most likely happening with your dirty shutdown, is the machine hits the battery threshold to shut down (you've got it set for 5%, after a minimum of 5 minutes), and there's not enough juice left to power down safely, and it's dropping out before Unraid fully shuts down. Are you running docker or VM's on that machine by chance? My only complaint with my APC's was that I didn't verify that the SmartUPS I have was expandable, otherwise I'd have it all running on that one box. My only other complaint with my systems is the Norco external array, it's only got a single power plug, no redundant supplies in it :(. If the HP P2000 drive trays weren't so damned expensive, I'd replace it with one of those in a heartbeat, lol.