40foot

Members
  • Posts

    22
  • Joined

  • Last visited

Everything posted by 40foot

  1. kinda depressing... SOMETIMES you get results, 90 % nought nada nothing nil zero spinning wheel of... ah, forget it
  2. James Cole advised me to turn v2 off - how it was turned on, I don't know. Now it works again... I shouldn't update this docker at all, too precious data...
  3. Updated to 5.5.3, now no booking can't be made any more, as the page is empty...
  4. 40foot

    IOMMU

    Ich hatte bei einem OS-Upgrade schon mal Probleme mit meinem Marvell-Controller (SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)) in einem HPE Microserver Gen10, musste da im UEFI irgendwas mit IOMMU abdrehen. Kann das beim 6.9.1 wieder Probleme machen (bin noch auf 6.8.3), oder passt das eh, weil nichts verändert wurde? Ich weiss, ich bin da ein bisserl ein Schisser, aber ich habe für meine Einschätzung schon etwas zu viel Zeit, Nerven und Hirnschmalz ins OS-Administrieren gesteckt, und würde mir das gerne diesmal ersparen. Besten Dank im Voraus! Andy
  5. At the moment my MySQL docker is version 5.7 - can I update this docker to version 8 (some other docker requires this), or is it better to start a second one?
  6. okay, will run the UEFI RAM test... should I upgrade to 6.9.1 before or after - recommendation? Have I ever mentioned that for me UNRAID is like the "Eierlegende Wollmilchsau"!
  7. Schon wieder erhalte ich folgende Meldungen: Mar 14 19:46:56 Tower kernel: BTRFS critical (device loop2): corrupt node: root=385 block=12811304960 slot=52, bad key order, current (1729382256910276956 114 281472972069555) next (6523 12 6466) Mar 14 19:46:56 Tower kernel: BTRFS critical (device loop2): corrupt node: root=385 block=12811304960 slot=52, bad key order, current (1729382256910276956 114 281472972069555) next (6523 12 6466) Mar 14 19:46:56 Tower kernel: BTRFS critical (device loop2): corrupt node: root=385 block=12811304960 slot=52, bad key order, current (1729382256910276956 114 281472972069555) next (6523 12 6466) Langsam kenne ich mich nicht mehr aus... nachdem ich diese Meldung vor ein paar Monaten schon mal bekommen habe, das Docker-Image neu angelegt habe, sich das nach einer gewissen Zeit wiederholt hat, man mir geraten hat, die Cache-SSD zu tauschen, ich mir 2 neue SSDs zugelegt habe und einen Cache-Pool gemacht habe (in der irrigen Meinung, dies würde irgendwas verbessern), treten bei mir schon wieder diese Meldungen auf, und manche Docker Container beginnen schon wieder, zu spinnen (z Zt kann ich pihole nicht mehr starten, aber auch nicht mehr neu anlegen, bald geht wieder gar nichts mehr...). Da ich jedes Mal Stunden um Stunden mit dem Transferieren von appdata von den SSDs aufs Array und dem Neuanlegen der Container beschäftigt bin (ich dabei auch schon Fehler gemacht habe und so manche Daten verloren), aber das Problem damit nicht behoben zu sein scheint, bitte ich inständigst um Durchsicht meiner angehefteten Diagnostik und wenn möglich Fehleranalyse. Es kann doch nicht sein, dass das Docker-Image andauernd beschädigt wird, so mir nichts/dir nichts... Lieben Dank schon mal im Voraus (ist glaube ich das erste Mal, dass ich mich ans deutschsprachige Forum wende, ich drücke mir selber mal die Daumen). tower-diagnostics-20210314-1957.zip
  8. no, my ISP is a University company - has nothing to do with the University network - not at all. But let's say this is of no concern for me anymore, because after updating to the newest Big Sur/Safari I can login again - without https... interestingly
  9. That's clear to me. Is any Intranet-CA/cert solution then known, that doesn't cost a fortune? Which a noob like me can deploy, on UNRAID for Bitwarden, WordPress etc. dockers?
  10. Can someone explain to me, why am I forced to use https with Bitwardenrs (wasn't so with the old container). My server has no connection to the Internet whatsoever, all my Docker apps are also only allowed inside my net, my ISP is not able/willing to give me access from outside (this is a University thing, no DDNS, no port-forwarding, no nothing...), the only way, to reach all this from outside is via a Win-PC with Zerotier-VPN, from which I use my apps then. Bitwarden is mobile on my iPhone with cached credentials, if I need passwords on the move, so for me, it makes not the slightest sense being forced to this security, I don't need an Intranet-CA, certs, whatever... Is there any solution to this, is there any way to be able to login to admin web page from Bitwarden without all this hassle, or am I missing something? Thanks in advance.
  11. Since last update the tests (speedtest-tracker) are made every 30 seconds, whatever there is defined in settings under schedule. Known problem? How to avoid? Any help appreciated. (reinstalling didn't change anything)
  12. Okay, I understand. I now found out how to adopt the cameras again, I had to create a new "Camera Adoption Token". Now I lost "only" my locked recordings. I mean, they are there on the storage and the backup, but with this UID naming scheme can't be found... At least I learned from this that I have to download the server configuration and store it in a safe place and that I have to download the locked recordings and store them also apart. Thx for your response.
  13. Today I updated (within the unifi-video server app, not via UNRAID GUI) from 3.10.10 to 3.10.11 and what I expected happened: it broke my installation. Not only all the configuration is lost, but on trying to adopt my 2 cameras it upgraded their firmware, then I was able to login to the cameras, but the configuration could not be loaded, then I rebooted the cameras via ssh, this didn't change a thing, they keep being stuck on loading the configuration. I was able to restore the recordings, but interestingly only the unlocked ones - what the hell! Those I don't need... Whenever I dare to upgrade a thing on my UNRAID system this happens. Utterly frustrating. After FireFly (all my bookings lost - thousands of them) and ResourceSpace (hundreds of hours spent for categorizing ca. 70k photos lost) now the next big thing - at least for me. What should I do next? Revert? How? Remove the docker (but keep the image?) and add it anew with pducharme/unifi-video-controller or pducharme/unifi-video-controller:3.10.10 or whatever the syntax is - can you tell me? And how do I adopt the cameras again? Do I have to reset them pushing the button on the device (on the uttermost step of my 3-part ladder climbing up to the highest point under the roof - not so inviting)? From now on I will not update (except my WordPress installations) any of the dockers any more for ever.
  14. I'm looking for a solution (for non-pros) for the following situation: I just need one configuration file (containing security keys I lost) from a container inside a backup docker.img file (which I can't move or start - too difficult to explain, and its size is 430GB). Is it in any way possible to somehow mount the file system of the docker.img file (if needed), than mount the container file/file system that is inside it and extract the one file out of it, a screenshot of its content would suffice also? If no problem for a pro: Teamviewer session, costs? The container in question: creecros/resourcespace-docker
  15. Well, back then it was not available in the CA, but I am glad that it works now. I decided to use LogicalDOC for my documents and Resource Explorer for my photos and am quite satisfied with it.
  16. Stupid question: is it possible to install Zerotier VPN client into it? Tried all I could find (eg https://github.com/zyclonite/zerotier-docker/commit/f880c72c7d6a8ec671a24db7a9b82d098f26f4cf) but as a non-Linux man I had to fail... Thx in advance
  17. I have exactly the same machine and disabling IOMMU in BIOS/EFI works. What I haven't tried yet (I hate downtimes) is the other option editing the syslinux and reenabling it in BIOS.
  18. This didn't help, but turning off IOMMU in BIOS did the trick... 6.7 now booted with the array up, both VMs running, all Dockers running. Looks good so far. Damn, this gave me thoughts...
  19. I had to revert to 6.6.7, both my WDC_WD40EFRX were not detected after upgrading, only Toshiba was found, so only 1 out of 3 disks (SSD cache was found too). The file included is after reverting - for analyzing, do I have to upgrade once more, and make the diagnostics under 6.7 again? Can this lead to more severe troubles? Or are there any log-files to be found, where those upgrade errors were written to? Ah, I feel not good about it, please help. durosrv-diagnostics-20190513-0050.zip
  20. Since yesterday I am trying to get ecoDMS (https://hub.docker.com/r/ecodms/allinone-18.09) up and running. Now I somewhat succeeded, but the web-interface gives me only this (using Firefox): I know I have to contact their support, but maybe one of you stumbled upon this docker and got it running… Thanks in advance.
  21. Hm, a picture with a short story... I took a panorama with my iPhone at night of the Lentos Museum of Modern Art in Linz, Upper Austria illuminated in blue with the Ars Electronica Center on the other side of river Danube illuminated at this time in pink (or whatever colour this is) visible in the background. Reminds me always of a visit of my 12 year old son when I was hospitalized there, we had a great evening together (at the museum, bookstores, computer shops, had a phantastic steak dinner and than a night together in the family room at hospital). I'm a bit sentimental, I know...
  22. I have not only this Time Machine connection problem since upgrading to Mojave, much worse: I am totally unable to connect to any of my shares (be it SMB or AFP) altogether from macOS Mojave. Seems to be a bug with Mojave (I get "smb_fid_get_kernel_fid: No SMB 2/3 fid found for..." errors. Anyone ever heard of something similar?