• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

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

ksignorini's Achievements


Contributor (5/14)



  1. I had connected My Servers to my Unraid box and it was resolving with somebigbunchofnumbers.unraid.net which used to work fine. I now only want to access it with a local IP but when I do, it still resolves to the unraid.net addy. How can I fix this? Thanks.
  2. One more thing... I did look through the files a bit. The drive that's failed is not showing a file in the zip at all (DISK 2) but I do see the other disks there, including DISK 3. At least in the SMART folder.
  3. Here it is. Just wasn't sure if there was anything personal in the file. ocean-diagnostics-20230105-1025.zip
  4. I had a crapped out drive being emulated. I got a replacement but a second drive has failed prior to me being able to replace the first one. I have one operating parity disk. The first drive that died, DISK 3, is unimportant to me. The second drive that died, DISK 2, is more important. I've installed the replacement drive into the machine. Is there any way I can forget about DISK 3 and just replace/rebuild DISK 2? Because when I look at the drives in Main, I can pick the new drive for DISK 2 but it says "Wrong" underneath it and set DISK 3 to "no device" but it still won't let me proceed. I need to do something to get the rest of the array back up, and hopefully, replace DISK 2 at least.
  5. It's actually all been working great up until now, with 3 instances running. Today I updated the container on one of the 3 instances and now I can't get it to restart. I don't know what things might have changed such that it won't start anymore. The other 2 (older) versions are still running fine. There is nothing in the logs. Where should I start looking for what broke?
  6. I also have another weird issue where I map another path from the host to the docker and rather than showing up where it's supposed to, it shows up separated? in the list (subdirectories listed rather than located at mapped location in docker). However, when doing backups from these paths, they show the right path... very weird. (In this case, I'm backing up some disk images so I've mapped in my /mnt/disks/ path so I can pick some stuff there. These are non-array disks.) They should be mapped into /storage_disks but end up being listed separated (vm, vmfast, vmfast2, vmfast3). But when backing up, show correctly:
  7. Old thread, but if you're still using pfSense or have the info available, how did you do this rule for your wife's computer/phone? Thanks.
  8. I've had some conversations with 360MSP regarding weird behaviour and they've instructed me to update to the latest version of their software. Are there any plans to update the Docker image to use Am I able to update the software in the Docker myself somehow? Thanks.
  9. Is there any way to change the VRAM assigned to VNC for the VM? Believe it or not, Photos.app has reduced functionality without higher VRAM than 7 MB.
  10. Say I created a macOS VM (call it macOS VM #1) and a 4th qcow2 disk image to store "stuff" on, formatted HFS+ Journaled/GUID. Then, I blew away this macOS VM (but not that data disk image) and then tried to map that qcow2 data disk image to a new macOS VM (call it macOS VM #2)... That should work right? So why would macOS VM #2 want to reinitialize the qcow2 data disk again? Shouldn't it have kept its format from macOS VM #1 and be perfectly usable in macOS VM #2?
  11. ... and nevermind. When I correctly forwarded the port on my router, it went away.