Jump to content

plttn

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

1 Neutral

About plttn

  • Rank
    Member

Recent Profile Visitors

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

  1. Happy birthday! Only been using since the start of this year, but it's been a great OS so far.
  2. Looks like 6.7.1 is completely incompatible with Disk Location. Fatal error: Class 'SQLite3' not found in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 27 Yeah, Sqlite support was removed from PHP.
  3. Yes. The wisdom I've used is brand new drives you can just plug it in and add to the array using native functionality, and used drives it makes sense to do a full pre-clear run.
  4. I'd advise against doing it that way, because eventually if you get to the point where you have a long running Series, you won't actually be able to fit it onto that disk, and it won't expand it to another disk. Doing a TV share and a Movies share is probably safer, with the movies set to split "top level only", and the TV show at "split only top 2 levels"
  5. I'm also seeing this issue, but running 6.7.0-rc6 (which I'm guessing might be the cause?)
  6. There's currently an issue with Plex where if UPnP is enabled on your router (and not all implementations cause it), it causes a core to peg to 100%. I was seeing it occur locally, but after updating Plex to most recent build of Plex pass, it seemed to have gone away, however your mileage may vary.
  7. And I just confirmed that that update fixes the issue. Thanks for taking care of it so fast!
  8. I think I covered all the edge cases in my tokenization method here, but I actually haven't tested it running, just using logic.
  9. So doing a massive amount of digging, /* Fetch logical unit (LU) name given the device name in the form: * h:c:t:l tuple string (e.g. "2:0:1:0"). This is fetched via sysfs (lk 3.15 * and later) in vpd_pg83. For later ATA and SATA devices this may be its * WWN. Normally take the first found in this order: NAA, EUI-64 * then SCSI * name string. However if a SCSI name string is present and the protocol is * iSCSI (target port checked) then the SCSI name string is preferred. If * none of the above are present then check for T10 Vendor ID * (designator_type=1) and use if available. */ it looks like if lsscsi cannot find a LUN/WWN for a device, it'll eventually try to fall back to the Vendor ID. Since the Vendor ID on this is set to the funky value, lsscsi spits out the funky value, and then parsing that barfs.
  10. Yes, that one specifically is indeed my output from lsscsi -u -g, but I believe I may have potentially found a fix with the pull request I submitted.
  11. I think I may have figured out why it doesn't seem to work on this drive. The manufacturer is setting a value your parsing isn't handling properly as the logical unit name. [1:0:0:0] disk ATA SPCC Solid State Disk _ /dev/sdb /dev/sg1 [2:0:0:0] disk 5000cca252e56185 /dev/sdc /dev/sg2 Since you're parsing via spaces, the luname gets set to ATA, device node gets set to SPCC and then everything falls apart from there. I don't know what the best way to solve this problem is however, as it would require a bunch of exceptions to account for all the low budget manufacturers doing things they shouldn't. It does create a unique hash for this SSD, but my guess is because the devicenode is ATA rather than sdb that's why it shows as unassigned. Would parsing from the right work better to solve this issue? That gets you the devicenode right off the bat, then you could assume that everything bounded by disk and the /dev/sdX is the logical unit name whether or not it's a technically valid LUN.
  12. I don't know offhand if this is enough for it to be unique. It's very possible this SSD is just too cheap for it to work properly. Thanks for letting me know!
  13. Running into a couple issues, which may have already been mentioned. 1. My SSD is not recognized as a cache drive for some reason (I'm thinking because it is lacking a Device Family attribute). 2. I am using a 2x4 (CxR) layout, and my layout looks like this and nothing I seem to do can fix it.