nastard

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

nastard's Achievements

Noob

Noob (1/14)

0

Reputation

  1. RecuperaBit to the rescue... fingers crossed... UPDATE: This only got me the "virgin" Windows VHDX back so far 😕
  2. I am quite new to Unraid. My current setup contains 3x4TB & 2x8TB HDDs plus a 500GB Cache SSD and a 1TB NVME SSD. One of the 4TB HDDs and the 1TB SSD were not part of the array yet. The 1TB was passed through to a Windows VM. On it there is an NTFS partition (after an EFI partition and some 100MB spare space) holding two vhdx files, both holding a Windows installation and being bootable into from the Windows bootloader (screenshot only shows one of the VHDXes being mounted in Windows, the "virgin" one at the time being booted from): The reason I did it like this and not, say, put the virtual disks in the domains share, is that I wanted to still be able to natively boot into these Windows systems. The 1TB SSD was precleared before using it for passthrough, so there shouldn't be any other data on it. One of the VHDXes was a clone of my previous Windows installation I ran natively from the 500GB SSD. There is data on there that I didn't yet save elsewhere. The other was a relatively new Windows installation which would be no big deal if lost. I believe the fresh install was on the SSD first, so it might be in the front of the space if that's how it works. What I wanted to do: start preclear for the last remaining 4TB HDD (that process is now running on the screenshot above). What I did instead: started preclear (without pre-read of course, because who has time for that) on the 1TB SSD. While at the time even running Windows off of the virgin Windows VHDX on the 1TB SSD. While being with my mind elsewhere. That's not a good idea. Lesson learned. (Still, @gfjardim, if you read this, thanks for the preclear plugin but please disable preclearing start for certain "unassigned devices", like for instance those marked as "Pass Thru" or those currently passed through but not marked like that or even force users to format the device manually first and only start preclear if there is a single empty partition or so. And/or give the user a view of the partition table and let them confirm that they want to override these partitions. That would have saved me from my own stupidity). This is what I started: So before I realized my mistake, and cancelled the process, the dd ran for like a few seconds. Windows still ran for a bit but certain things stopped working and I had to "force stop" the VM. Afterwards, it wouldn't boot anymore. This was the preclear log after I pressed the big red emergency button: This is approximately what I assume happened, and a sketch of the device situation: Of course, the first thing I did was create a backup of the drive with dd before testing my luck with testdisk. But until now, I wasn't able to restore the partition with testdisk. The analysis finds some partitions, but none that have the label that I am expecting or where I am able to "list files". Again, I am looking for an NTFS partition with two huge VHDX files on it. How do I get my disk images, especially the one with the non-virgin Windows installation, back? Any help is much appreciated.
  3. 📌 Having the same problem trying to start Docker with WSL2 backend inside a Win10 VM with passed through NVidia GPU (if that's relevant). The VM is running off of a bare metal install of Windows 10 on a passed through HDD (when booting directly into that Windows it works). System.InvalidOperationException: Failed to deploy distro docker-desktop to C:\Users\admin\AppData\Local\Docker\wsl\distro: exit code: -1 stdout: Aktivieren Sie bitte das Windows-Feature „Virtual Machine Platform” und stellen Sie sicher, dass die Virtualisierung im BIOS aktiviert ist. Weitere Informationen finden Sie unter https://aka.ms/wsl2-install stderr: bei Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:Zeile 146. bei Docker.Engines.WSL2.WSL2Provisioning.<DeployDistroAsync>d__17.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\WSL2Provisioning.cs:Zeile 169. --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Docker.Engines.WSL2.WSL2Provisioning.<ProvisionAsync>d__8.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\WSL2Provisioning.cs:Zeile 78. --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Docker.Engines.WSL2.LinuxWSL2Engine.<DoStartAsync>d__25.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\LinuxWSL2Engine.cs:Zeile 99. --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:Zeile 29. --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:Zeile 67. --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:Zeile 92. If I disable the WSL2 backend, I don't get that error but Docker says "failed to start".
  4. Thanks for the reply, @Decto. Seems like I have some expectation management to do. I decided to order the a Fractal Design 804 case and a energy measuring device and just try it out with the hardware I have (ditching the Radeon as you suggested). I can't really tell the total power consumption but I hope I will with the measuring device. I'll report my findings here. If it turns out that the idle power consumption in non-VM mode isn't acceptable, I will build a dedicated NAS with the case and a low-TDP Ryzen 3.
  5. Hello everyone, Let's say I want to disembowel my gaming PC and build a power-conscious NAS that also doubles as (multiple) gaming PCs (using GPU passthrough to Windows VMs) with Unraid. It should give me full performance for Gaming and NAS (not necessary at the same time) but should be as power-saving as possible when powered on but idle (VMs turned off). It might also find some other Docker/VM-based server-related tasks in the future, like being a dedicated gaming server, but my concern in this post is "only" to find the holy grail in terms of low power consumption in idle (NAS active but unused) and optimal gaming performance when used (while ideally still making use of power saving features the hardware provides, like clock rate adjustments). Let's set a benchmark: 35.44W ("typical" in use), 18.63W (idle disks), thats what the 6-bay QNAP TS-653D that I was looking into before getting the idea to build a all-in-one frankenserver is using, according to spec sheets. I don't care about power consumption during gaming. First off: is it realistic to reach idle power consumption this low with normal inexpensive consumer/server hardware at all when realizing such a project (regardless of the hardware listed below)? This is the hardware I would like to reuse (potentially replacing later): MB: Asrock Z270M Extreme4 MicroATX Socket 1151 with VT-d and VT-x I would consider replacing this with an MB with better power saving if necessary, not restricted to μATX CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz GPU 0: Intel HD Graphics 630 on CPU (could be disabled if power-relevant) GPU 1: Gigabyte NVIDIA GeForce GTX 1070 Mini ITX GPU 2: ATI Radeon HD 4800 (will be replaced with something more potent for player 2 at some point) 32GB DDR4-RAM 750 Watt Corsair CX Series CX750M Modular 80+ Bronze No idea if this is a good power supply for the task Samsung SSD 850 EVO M.2 500GB SSD Hardware I would add: A tower with >6 front 3.5" bays A bunch of shucked 8TB WD My Book drives (I know about the TLER problem) Maybe a bigger/faster SSD for caching Some NIC >= 2.5GBaseT (still undecided) My primary quesions are: Is the hardware generally suited for the task or are any components not able to efficiently save power when idle? Does Unraid make use of power saving features? I noticed for instance that while Windows 10 running on bare metal slows down the CPU to something <2GHz, the same system running in the VM does not. How about PCIe power saving for the GPUs? But really, ANY remarks, ideas or links to useful resources are appreciated.