Jump to content

olehj

Members
  • Content Count

    105
  • Joined

  • Last visited

Community Reputation

9 Neutral

About olehj

  • Rank
    Advanced Member
  • Birthday June 3

Converted

  • Gender
    Male
  • URL
    https://ubrukelig.net
  • Location
    Norway

Recent Profile Visitors

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

  1. olehj

    docker-storman build variable

    Alright, thanks for the answer!
  2. olehj

    docker-storman build variable

    Aha I thought it would rebuild when you forced an update, like when you add a new container. So I thought it would be possible to enter those build commands somewhere. If I build it on the command line like it says in the Readme, will it be recognized in Unraid and will it remember the manual set password if I force update the container later or make any changes to an existing container?
  3. I tried to search around and couldn't find any clear answer if I can add a build option/variable for the unraid docker interface? I want to add the --build-arg so I can set a password for the Storage Manager docker found here: https://github.com/Fish2/docker-storman As far as I can tell, it is not supposed to be entered in the "Extra" nor the "Post" fields under advanced? I just want it to be set every time I update the docker container etc. without extra manual involvement.
  4. olehj

    [PLUGIN] Disk Location

    NVME drives are likely not supported at all at this moment and I dunno if or when it will be. M.2 SATA drives would likely work (or running them as SATA from BIOS, but don't do that as that would be rather pointless). The value of listing these drives anyway are probably rather small as they are mainly directly attached to the motherboard - and rarely more than 2 (in use anyway). It might be a task for the future if these drives comes down to a storage value level, but the importance of replacing a faulty drive is rather more important with the main Unraid array (not cache) and other Raid arrays. Maybe in the future, and it would rather be a part of Design v2.0 which isn't even in the works. Right now this plugin is too dependent on output from "lsscsi"
  5. olehj

    [PLUGIN] Disk Location

    As stated earlier for the same request: I cannot do that as the sub-design does not permit it in an easy way. Empty trays are simply marked as a number and nothing else and currently I won't add a second layer of empty number as it might conflict and corrupt existing databases.
  6. olehj

    [PLUGIN] Disk Location

    I had nothing else to do while drinking my wonderful craft beers Now time to game and chill - fragging gets easier and easier more reduced I am Of course thank you for help and your effort!
  7. olehj

    [PLUGIN] Disk Location

    Update 2019.03.10 Commit #63 - BUG: Removed harddrives did not show up in the Information list but got invisible instead. Commit #62 - MINOR ISSUE: Fix broken harddrive information. Parsing of lsscsi is redone.
  8. olehj

    [PLUGIN] Disk Location

    I guess I have a solution now using some regexp and less modifications in general. As LUN is mainly not in use anymore, I just compress the Vendor ID into a "selfmade" LUN. Else it will rather check for the contents. Also fixed a bug I discovered, old removed drives will now be shown until removed manually under "Information" - will release this asap
  9. olehj

    [PLUGIN] Disk Location

    I looked at it a bit, but I think I might try a different approach based upon your data. However I feel it is strange you get a fallback value of Vendor ID instead of "none" as I get for some drives not including LUN. Just for the sake, what Unraid version are you using?
  10. olehj

    [PLUGIN] Disk Location

    That is a bit of a bummer. I thought LUN always would be found. I might try to parse and compare and do some more checks and make a fallback myself.
  11. olehj

    [PLUGIN] Disk Location

    That does not look like the output of "lsscsi -u -g", or at least not the first output. The LUN should not be visible with "lsscsi", and the ATA+Model Name should not be visible with "lsscsi -u -g" Also it appears to add an underscore after some spaces after the Model Name. It does split on a \s+ flag, meaning single and multiple spaces/tabs will be split correctly if the output of lsscsi is. I must say it is interesting if this is your output with the "-u -g" flags. The device model and serial number your drive shows is good for creating a hash. I still question the serial number a bit, if you have multiple of this SPCC disk check if you have any matching serial numbers as well. In short; if the output is truly what you show above from the exact command "lsscsi -u -g", then I might think this can be a bug from the lsscsi program. I don't see why it should have a different output unless the drive itself messes up with the parsing of lsscsi. Sorry if I can't help you enough here right now, but keep me posted if you find something useful.
  12. olehj

    [PLUGIN] Disk Location

    Some SSD's might not include enough information to make a unique checksum. It must include "model" and "serial number" - this is as far as I've seen always included, if it's not; it will fail. It might also cause the layout to be messed up like you show it. Another reason might be that you assigned devices to the tray slots before storing the actual layout. Please check the drives if they give at minimum model+serial number, serial number has to be unique. I know for a fact that some less known brands might just put in a lot of zeroes instead of an actual number and hence won't work with this script. It won't be able to assign them either in any way.
  13. olehj

    [PLUGIN] Disk Location

    Update 2019.03.09 Commit #60 - MINOR ISSUE: Warranty info is repeated for empty or non configured devices. Fixed by defining a variable as null.
  14. olehj

    [PLUGIN] Disk Location

    Update 2019.03.08 Commit #58 - BUG: Invalid argument supplied for foreach(). Check if it is an array before searching in it, else default to false. @Nightowl805 You can test this now and check if that resolves the error message. I might need to dig in a bit deeper into this if it's not resolved.
  15. olehj

    [PLUGIN] Disk Location

    It's impossible for anyone to know where your drives are located as the configurations out there varies a lot, so you must assign them manually the first time. So no automagic is happening there. For the error it looks like it might detect a false blank or something odd in the SMART rotational data. I'll fix this later.