GoChris

Members
  • Content Count

    201
  • Joined

  • Last visited

Community Reputation

4 Neutral

About GoChris

  • Rank
    Member

Converted

  • Gender
    Male
  • Location
    Calgary, AB, Canada

Recent Profile Visitors

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

  1. It worked in private browser, firefox, disabled all extensions, didn't fix it, but clearing cookies and site data and now it works again.
  2. Further to the questions above about LibreNMS not auto discovering or polling. If you load up a console and run: ./discovery.php -h <device ip> It will do the discovery. Not sure why this is not done when adding, and you can also manually a poller, but, that should be done on a cron or something. I think this docker isn't correct. ./poller.php -h <device ip>
  3. Have you managed to get this docker working? My vm crashed that housed my LibreNMS, so I switched to this docker, and I am getting the same issue. I can add the device, but it does not discover anything.
  4. Server...hung, local input was working, network was unavailable. This was on the screen. Attached the latest diagnosis, for now I'm paused the rebuild/sync in order to grab some files off, as I'm not sure my backups have been working the past few weeks (time to build a backup pc). tower-diagnostics-20210614-2002.zip
  5. Sorry for the late reply, server wasn't stable with the 2nd HBA card in it for some reason so back to 1 and a vid card. I believe it was disk 2 or 3 that was giving the errors, which is showing fine now. Just started the array and it is showing disk 16 and 7 as unmountable. tower-diagnostics-20210614-1758.zip
  6. Ok, so I recently added back a 2nd hba card. A drive went missing (timed out). So I was rebuilding that, during that one other drive dropped out, then a bit later one drive was just showing errors during the rebuild. I swapped out that HBA for a 3rd, maybe it was no good. Anyway, during all this I'm pretty certain nothing was written to the array at all. So, I want to assume parity is fine I guess, because I can't imagine all the read errors on the 3rd "failed" drive would mean good data on the actual rebuilding. I do have two parity drives. What steps do I
  7. Yes, rebooted and the shares are back. Log did get full afterwards yes and good now also after the reboot. Thanks. Will rebuild that drive again, still checks out fine.
  8. Tried to watch a show, nothing was playing, went to check to make sure I could access files on the share, got an error accessing the share. Checked via a terminal and got "cannot access '/mnt/user': Transport endpoint is not connected" error accessing anything in /mnt/user. So, got weirded out, started and stopped the array, then the shares list was gone (empty), and on array start a drive is disabled (I'm guessing there's nothing wrong with it, probably a timeout on start? Will worry about that after a reboot). Also I then setup a root password (finally) cause I got paranoid with od
  9. Correct. I will update my original post to be more clear, I guess I wasn't as clear as I thought.
  10. Yes but the share min free space takes precedence when that share is set to use the cache, which is ultimately the problem.
  11. The alternative would be to have a separate setting for how much free space you want to maintain on the cache, just like you can for a share. Cache drives are not going to be as big as data drives (let's assume we're talking about 99% of setups), so chances are you might fill it up more than a share setting, but there can remain more than enough space for file transfers. If you need/want an example, I might have my share set to 150GB min, but various files could have been written to multiple shares and reduced the cache drive to (just) under 150GB. If I then want to write another file (size is
  12. If a share is not set to cache only, and a min free space is set, I think it should only apply to free space on HDDs, not how much free space is on the cache. I only want to fill up my drives to certain amount, but I always want to utilize the faster write speed of using the cache drive, however if the cache fills up and has less free space than the share setting, it will write straight to an HDD and be much slower. Making it an option would work too. Perhaps a better explanation:
  13. You have to edit the config file in appdata for the settings you want to stay between sessions.