Hey Guys,

 

I have been playing around with UnRaid 6.6.7 (Stable) for a couple of days now, I'm not an expert on any of this, I'm just on trial period trying to decide if I'll buy the unRaid License or not.

 

Hardware:

CPU: Ryzen 2600 6 core / 12 threads

MOBO: MSI x370 Gaming Pro Carbon

RAM: 16 GB DDR4

GPU:

- ZOTAC NVIDIA 750 Ti (1GB GDDR5)

- Gigabyte Radeon RX 550 (2GB GDDR5)

STORAGE:

- HHD 3.5: 500GB 7200rpm x 2 (for the array)

- SSD 2.5: 120GB 2.5 x 2 (intended to be passed through 1 per VM)

- SSD M2: 120GB x 1 (for array cache)

 

My idea with this hardware is to setup a home server for file sharing and backups over the home network (There are 2 MacBooks Pro already at home), but also I needed the server for hosting two windows 10 VMs each one with its own dedicated GPU and SSD (for great performance, since these machines maybe used for a casual gaming), I ran into some complications with one of my GPUs while trying to pass it though to a VM, but thanks to user gelmi who give me great advice it finally worked, ref:

 

So now I found another issue, since I have been playing around creating VMs, passing through hardware to them an so on, I end up with multiple VMs that I needed to clean up, so I started removing them including the Virtual Disks, which is fine, THE ISSUE is that accidentally I clicked the remove with virtual disk option on a VM that actually was initially setup passing though a physical SSD, that action totally destroyed the SSD, now is not recognized by the board or by other computers, I tried reading it with 2.5" external cases, different adapters and even using a laptops but none is able to recognize the SSD now, is totally dead.

 

So, the question is, does this happen to any of you guys? is something that any of you can tell me to try or do? maybe was just a coincidence and the SSD failed at that exact moment I destroyed that VM.

 

At this point it seems I lost US $30 on that SSD 😥

 

p.D: I used this video to know how to pass physical disks to my VMs

 

 

 

Edited March 4, 20197 yr by CarlosCo
Adding more details

14 minutes ago, CarlosCo said:

that actions totally destroyed the SSD

Seems very unlikely to me, if not impossible.

I'm afraid to try this again with the other SSD, I'm on a really tight budget after I bought all this hardware, and since this potentially can kill the other SSD, I can't afford to lose another one, I think unRaid support must try this and if this end up being a replicable issue, offer some kind of protection in cases that the VM disk is a physical

If you describe exactly what you did, including the VM XML, I don't mind trying it, I have several small SSDs I just use for testing.

Steps to reproduce this issue:

0 Get a windows10.iso and the virtio.iso for drivers

 

1. Create a windows VM passing through a physical drive as opposed to a virtual disk as the primary storage, the way to do that is by configuring manual on the storage option and filling with /dev/disk/by-id/ata-SPCC_Solid_State_Disk_BB2A078C14530YOURDISKID, also select SATA on primary vDisk bus option

 

 

2. once you finished installing the operating system and all virtio drivers from the windows device manager, stop the VM

 

3. go to your VM definition once it stoped and select option "Remove VM & Disks"

 

Looking forward to hear how it goes in your system.

Edited March 6, 20197 yr by CarlosCo

3 hours ago, CarlosCo said:

Looking forward to hear how it goes in your system.

I'll do it as soon as I have some time, though most likely not before the weekend.

OK, just tried this and as expected no harm was done to the SSD, in fact and since there isn't a vdisk to delete nothing was deleted on the SSD, after doing it the SSD still contains the ntfs partition:

 

 

Thank you, then it seems that the crapy SSD just broke by the time I execute the VM deletion