xenofiber

Did you replace drive for another ssd?

Well now I’m aware that there is a setting for that. VMs I had there previously look ok. I will have to test them later when I get off work.

I figured as much. And I’ll give the recovery software a try. Any idea as to why my system would act up when using PFsense in a vm? Also now that I no longer see a VM tab do I need to start all over?

Currently I don’t have a VM tab. Some files on my Plex are missing. Disk 1 didn’t rebuild properly. Parity has a thumbs down. (long post) I am some what tech savvy but not at the level to trouble shoot unRaid. Like most I’ve watch videos from YouTube to get me where I’m at today and like most people I watch and complete most tutorials with success but also with out really knowing much of what’s really going on. I posted a while back how I was having issues with my parity disk. Which I formatted it and re introduced. It then proceeded to rebuilt and then had no issues. This was following me changing my motherboard settings to enable VT-D. I did this to allow my iommu groups also that I can passthru 4 port nic using pfSense. This led my server to start freezing. I then disabled VT-D and un did everything I had done to run pfsense. So fast forward to now, I decided I was gonna have pfsense working all under unRaid. I followed space invaders video on pfsense, and also the iommu groups one. I got it all up and running. I had it set up and ready to go and just wait on a wireless access point. I shut down pfsense and disconnected it from my network setup, this was about mid day. Right before going to sleep I decided to turn on my windows vm so I could catch up on the latest episode of the show I’m watching. Once I got it, I moved it to one of my shares on the sever. The way I have my folder share security I would have to load a file to the root folder then get on Krusader then move it to its destination followed. When I tried to do this step it’s when I noticed my server had froze. I went to the screen on the server and sure enough it said something about cpu process error. I know this is a no no but I held the power button and restarted the server. Now I had all sorts of issues. I had a red x on my parity drive. I went to try start the array and it froze. I don’t know if it’s my lack of patience but I held the power button again. I went back to the bios and disabled VT-D. Booted it up again and then the parity drive was no longer showing a red x. Now my first disk in the array had a red x. I decided to take the drive off the drive list array and started it with out it. The stop the array. I tried once again to select the disk and start the array but it still wouldn’t let me. So I thought that since my parity checked out I would be fine if I formatted the drive. Which I did. My current usage is about 3.6 TB out of 16tb on a 4tb parity. I should Had been like 6tb. what do y’all recommend? I had planned to get a second parity drive and one 14tb drive for a monthly back up solution. I have most of my data backed up already on a 4tb drive. I sort of feel like formatting everything and starting all over. Which has been my go to when when my computers mess up. Starting flesh is what I usually do when some goes wrong out of what I can diagnose. Sorry for the long post. I just wanted to write down everything I could remember. Thank you for time and plz help. t1-diagnostics-20210802-0655.zip syslog-192.168.0.11.log

This is what I ended up doing on just dumb luck and its currently at 76%. When i did the preclear the system froze when it was just at 2%. Everything checks out tho. the parity drive comes up as emulated and its re syncing/rebuilding the drive. Prior to all of that I had gone to my bios to enable iommu groups so that i could pass thru the network card for pfSense. I then removed the pfSense vm and disabled iommu groups on the bios.

I was in the middle of installing pfSense on a vm. I was on the web browser vnc connection finish up the install when i lost connection to the vm and the server. I held the power button and shut the server down. When it restarted I noticed that my parity disk was disabled. I saw the forum to see what solutions the error had and I tried some. I have my drives all connected to a PCI card. I removed it and a plugged it back in. I am now in the process of doing a preclear to try and reinsert it as a new disk then rebuild the system. could some one please look at my log and see if I'm just wasting my time? Thanks syslog-192.168.0.11.log