83749020

Members
  • Posts

    10
  • Joined

  • Last visited

83749020's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for posting that, yellow. I had the same issue on 6.8.3. I mv'd the db file to a backup, started dockerd, ctrl-c'd it, then rebooted. Now it seems to be fine.
  2. So I rsync'd all the data off the cache pool to a share on the array, reformatted the drives, then rsync'd it back. It seems all good now! Thanks for all the help, guys. It is much appreciated.
  3. So I changed the drive numbering which worked, but I agree the cache pool is hosed. I’m copying the data to the array and am gonna wipe and reformat.
  4. Ok, so do you mean it will automatically change from “drive 1 missing, drives 2 and 3 present” to “drives 1 and 2 present”? Can I run some kind of repair in maintenance mode?
  5. Thanks a lot for the insight. I recently had to remove a failing cache drive, so I removed 2 500GB drives and added a 1TB drive. How can I get the cache pool to look normal? I went from 2x500GB+1TB to 2x1TB cache drives. I was afraid to switch the numbering around on the cache pool, so I left it as-is. I'll see about replacing the UPS cable, too. That's been annoying me. Once I get the cache pool drive numbering sorted, I'll move the files around.
  6. I realize there's not a lot of info there, but I'm scratching my head. I should have mentioned that this happened on 6.8.3 first, then I downgraded back to 6.8.2. I tried to install the NVIDIA kernel in the past few days, too. I'm just hoping the diagnostics help shed some light on the issue.
  7. Hello, I'm having an issue where the load average/CPU utilization climbs after a day or so and renders the server unable to shut down cleanly. At the time of writing (2:41 CDT-Apr.7), the load average is at 110. This morning it was at 4. I've had to power it off twice over the past few days since it can't shut down on its own. The highest I saw it was over 200. I could still SSH in, but nothing would work. VMs and Dockers wouldn't respond. Luckily, I managed to get the diagnostics downloaded. Thanks in advance! unbeast-diagnostics-20200407-1354.zip
  8. Same error each time... I'm posting this from the VM in question, but I haven't rebooted it yet. I am afraid when I do, then it won't come back up. However, I'm about done installing Windows Updates so I'll have to reboot soon. I saw Gridrunner's video mention getting a Bios file and associating it with the VM. Is that mandatory? I haven't done it yet with this VM. Would that keep it from booting again after installing the drivers?
  9. Hi, Jcloud. Thanks for the response. I messed with it for a while and eventually started over. I'm wary since this is the third time I've started over without knowing what really happened. I tried to do a system restore, but it didn't even see the ? drive where windows was installed. It just got stuck in a boot loop where it kept coming up with a "Critical Service Failed" message. What I found was that the driver for the VirtIO disk wasn't loaded. From the "advanced options" command prompt, I went to the setup CD and ran setup. I went to the point where it asks you to install on a disk, and I loaded the driver from there. Then, when the disk showed up, I just closed the install tool and went back to the command prompt. From that point, I had access to the ? drive. I googled around and found that a lot of times, it is the driver signing feature that needs to be turned off. I couldn't use bcdedit since it couldn't load the boot store for some reason. That's the point where I just started over. I'm trying to get a Windows 10 VM running with passed through Nvidia 750Ti and a USB mouse/keyboard. I am using a vdisk, not an HD.
  10. Hello, all. I'm trying to get a Win10 VM up and running while following Gridrunner's excellent videos. I'm on Unraid 6.5.3 Pro. What is happening is that I get the VM up, install some software, change some settings (per the videos), and after a certain point, the VM boots to a "Critical Service Failed" message. Then all I can do is to go through the repair options. I suspect something happened to the virtio drivers, but I'm not sure. I go to the recovery boot and then command prompt. I try to list the disks using diskpart, but there's nothing there it says. Thanks in advance!