Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About 40foot

  • Rank


  • Gender
  • Location

Recent Profile Visitors

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

  1. 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.
  2. 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...
  3. 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
  4. 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.
  5. 40foot

    Share Your Banners

    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...
  6. 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?