SpaceInvaderOne

Yeah thats definitely a long time..... I am guessing that this may be due to op having the drive connected by usb. If his harddrive usb connector is only a usb 2.0 and not 3.0. So if say the usb 2.0 data transfer is about 30mbs then 2TB would take about 21 hours.

I wouldnt use that myself because that drive is going to be old. There is a review here from 2013 so the ebay drive linked, may well of had upto 6 years of use. https://www.storagereview.com/fusionio_iodrive2_mlc_application_accelerator_review_12tb Also a modern nvme drive such as the samsung 970 evo plus is a faster drive. Also the Fusion-io ioDrive2 may well run under the published specs for the drive unless the PCIe power limit threshold is raised from the standard 25 watts https://www.dell.com/support/article/uk/en/ukdhs1/how12260/setting-the-device-wattage-level-on-a-sandisk-fusion-io-iodrive2-to-improve-performance?lang=en Also take into consideration that the 970evo nvme 1tb drive uses only 6 watts.

Hey Nick. Glad that you haven't lost your data Yeah your right, the rebuild has started to reconstruct the data onto the 6tb and so has built the indexes to the files but nothing else. So yeah just reformat the drive and then copy the data across. If you didn't figure on how to reformat the 6tb then use unassigned devices plugin to delete the partition. 1. Goto the settings of the unassigned devices plugin and set it to destructive mode. 2. Stop the array. 3. Set the slot with the 6tb drive to unassigned. 4. the 6tb drive will show up as an unassigned device. 5. delete the partition 6. Now you can either (i) format the drive using unassigned devices to whatever filesystem that you want. ( I would use xfs as that is now the Unraid defualt for array drives). (ii) Only delete the partition then when drive back in array Unraid will format it as the current defualt set for the drives in settings/disk settings. 7. Go back to where you set the 6tb drive slot in the array to be unassigned and add the 6tb disk back to that slot. 8 goto tools/newconfig and this time set preserve current assignments to be all and apply 9. start the array . Again cancel parity sync until the data is safety copied across from the 2 tb then do a parity sync.

You say that you had to add the card by editing xml. It is easier if you stub it in the syslinux.conf then you can add in webui under other pci device add this to your syslinux file after the initrd=/bzroot then reboot the server and you will see the usb card in the vm template. vfio-pci.ids=1b6f:7023 add this by on main tab clicking on flash the you will see the syslinx.conf and edit it adding the above and will look a bit like below default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot vfio-pci.ids=1b6f:7023 I am not sure about the usb card that you have but dont see why it wouldnt work as it it in its own iommu group. You would be better posting this in the vm section of the forum as more people will see it there who may be able to help.

Hi Nick, Unraid has dropped that disk from the array. Although it is now present when the server is powered back on, when you add it as the same drive, disk 3 , although its the original drive because it was dropped from the array, Unraid now considers it a new disk and wants to rebuild it from parity. However as this disk came out of the array when rebuild was happening (replacing the 2tb) it cant rebuild disk 3 because there are now 2 missing drives and 1 parity disk cant rebuild 2 failed drives only 1. this is why you see the error 'Too many wrong and/or missing disks!'. Now there maybe a way that you recover from this. I guess that you still have the 2tb disk that you are replacing yes? (if not there still maybe a way but for now i assume that you have) So if you still have it then data is still on that drive...so thats good. Disk 3 should also still have its data on it so you haven't lost anything there (unless it was lost before hand) So what i would try would be the following. Note the disks and there locations (take a screen shot of how they are now) Now goto tools, new config. On the drop down menu you will see preserve current assignments. Choose to preserve parity slots and and cache slots and create new config. Now add back the data drives as in your photo. (be careful not to add any other drives that were not part of the array, if you were using other unassigned drives on the server) But don't add the 2 tb drive to the array (you want that to be an unassigned drive and then later copy the data from that to the array) So you should now have in the array, all of your old data disks (except the 2tb) including the 6tb that you started to rebuild on. Now start the array. Unraid will want to do a parity sync as this is a new config. Cancel that, you will do that later. It will also say that the 6tb drive has not file system (or it should as the rebuild failed) this is fine. Allow Unraid to format the 6tb drive. Now the array should be started. parity will not be valid -- but don't do a parity sync as yet. You need to copy the data off the 2tb drive first. Do this using the unassigned devices plugin and Krusader docker container you and manually transfer the data off the 2 tb to the 6tb drive. After this has finished ( now the data is transferred to the 6tb ) you can then do a parity sync and your array should be fine. if the disk 3 is okay and doesnt still keep giving read errors parity sync should complete ok I hope that this makes sense

@z0ki hey welcome to being an Unraid user and to the Unraid community. I am glad that you find the vids useful. Best of luck with your server. Hey @Can0nfan thanks glad that you liked the video. Wow looking at your servers in your signature. The 98tb one, wow thats a whole lot of space!

Here a guide that shows how to repair XFS filesystem corruption if you are ever unlucky enough to have this happen on your server. Hope its useful if you need to fix it !

Yes just swap it over and boot up with the usb flash drive from the old server. Unraid will look for the drives based on the serial numbers of the drives and add them as they were before. But as @itimpi says a screenshot of the drives is a good idea .

Yes if your m board doesn't support vt-d (iommu) then unfortunately you will not be able to isolate the hardware to allow passthrough.

In your diagnostics file, the file showing your iommu groups is empty. Looking at your cpu here it does support vt-d https://ark.intel.com/content/www/us/en/ark/products/33910/intel-core-2-duo-processor-e8400-6m-cache-3-00-ghz-1333-mhz-fsb.html I would think that you don't have vt-d enabled in your motherboard options. See if you can enable that in bios settings. When enabled if you goto the info button at the top of the Unraid Webui. It looks like a small computer screen icon. Click it and it should say HVM: Enabled IOMMU: Enabled

Heres a short guide on how to downgrade the bios on an AMD motherboard if you have the same problem that I did. This is for AMD motherboards that use an AMI bios as many do. Hope its useful

For those that want to downgrade their bios on motherboards using an AMI bios i have put together a short guide here

I think he was using the afuwingui version maybe why a difference

You cant use afuwin in windows to do this (as windows has a system protection to stop bios being changed to one that doesn;t match and setting to ignore in afuwin will just reboot you into the motherboard bios page to upgrade so no good) I have almost finished a video guide on how to do this which i will upload and link here later today. But for now here is how. Format a usb stick with gpt partition. (use rufus in windows to do this) the put this file attached here into the root of the flash drive. (obviously unzip) EFI.zip Then you will have a file on flash called EFi inside there ther is a folder called BOOT. Copy the downgrade bios that you want to use into that folder but rename it bios.rom then boot the computer from the usb flash drive that you have just made. you will see the shell Now you will need to change to the usb drive type fs0: (yours maybe different poss -- fs2: fs4: etc) then type cd EFI cd BOOT then type ls to list the files there. (you should see the files and the file bios.rom - you will know that you are in correct directory then) now to flash your bios (remember flashing a motherboard bios has risks and it is possible to brick a board so do at your own risk please) type Afuefix64 bios.rom /P /B /N /K /X This will flash the bios onto the board. It will warn as in windows but just type y to continue. After flashing I would clear the cmos then re-setup bios settings as desired.

Hi @xPliZit_xs yes i found that too with the drivers installed was when the unclean shutdown of the vm caused the issue,