MrOz

I have had my Unraid server setup for over a year. I started it with old enterprise drives (that are still working fine) and I have added some WD Red Drives over the years and now my setup has two WD Red drives for parity, two WD Reds, the two enterprise drives and an SSD that I run my single VM on and nothing else. The two WD Reds in the array have failed twice with errors and are once again showing as unmountable. I have replaced the cables and precleared them before I added them back again into the array since they seem fine when connected to my linux box and running SMART tests on them. I even salvaged data off them the first time without issue. Just mount and copy. The most recent failure happened during a bit of a stress test as my Nextcloud server was syncing about a TB of data. They are both sitting in Unmountable: Unsupported File System. Should I just give up on these drives and move on or is there something that I am missing. I handle enterprise hardware by day but am a bit of a noob when it comes to Unraid as I have to watch guides to do most anything. Should I try adding the back to the array again... maybe doing it a different way?

I need some help here. I went through some gyrations to convert my cache drives to ZFS. Changed the allocation to send the data to the Array instead of the Cache... that didn't work as advertised and I had to use Unbalance to get everything in once place and actually work. I setup the drives with ZFS in a pool and moved the data back but now it takes up about twice as much space as it did before the move. It was about 40gb before the migration. What does "refer" mean and why is it accounting for 44.2gb of space? I looked at the size of appdata in Krusader it is about 20gb. I looked through appdata in terminal and nothing looked out of the ordinary. Late edit here. I checked the size of Appdata in Krusader and it shows that it is just under 20gb. Any thoughts?

Ok, I figured out what I needed to do to get that command to run. I was too tired to see it correctly. It does show "not supported" What settings can I change to fix this?

I added the drive using iSCSI on both servers. The drive is visible in Disk Management on both servers as well. It will still not Add properly. As for the command you suggested.... where am I running that from?

I am trying to use this on a Windows Hyper-V Cluster but I cannot get the Disk to come Online in Failover Cluster Manager on the Windows Server. It was suggested that the iSCSI needs to have scsi-3 persistent reservations enabled but I don't know how or even if this can be done with this. Don't make me have to standup a TrueNas server. LOL. Anyone have any input?

I searched quite a bit for a solution so as to not post something that was mentioned before but I had no luck. I just stood up a Macinabox and messed it up so I wanted to remove it and start over. However, I cannot remove the VM. I know that there are steps to remove a Macinabox but I couldn't figure it out. Thoughts?

I had been using an older Nvidia Quadro card for Plex transcoding. It was a very old card but it actually worked. I saw a deal on a newer but still modest card and bought the GeForce GT 730. I was not looking to break the bank and I am not expecting the absolute best performance here but this will do the job that I want. Anyway, it installed fine and when I use the oldest driver (v470.129.06) it seems to work. When I update the driver (and reboot) to any newer driver I get the error: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. On the old Quadro card that was the latest driver that I could use as well but I thought that it was because it was such an old card. Is there something that I need to do to get it to use the newer drivers? I uninstalled and reinstalled the Nvidia Driver plugin but that did not help.