maverhick

Thank you so much for your help. The array is back on and chugging as usual. My heartfelt appreciation for the work you do

Updated Diagnostics diagnostics-20240403-2125.zip

I resettled the cables and now both drives are showing up as unassigned, both seem to have smart errors as well. Now the Array error is " Array has 1 SMART error." which is showing up on the parity drive

Yes, one of the unassigned drives, the 4TB ones is the missing drive.

In my machine, 2 of my 4TB drives decided to play truant together and are now showing up as not installed. I also found a 4TB listed under Unassigned devices. There is no 2TB unassigned device that I am aware of or is connected to the machine. I need help with next steps. How do I diagnose these 2 drives and what next steps could I take to get them to be detected back into the array? Else is my option finding a 8TB drive and plugging it in and rebuilding the array. Looking to hear suggestions on getting this out of the way. I am so thankful that I have a 2 drive parity, else I would have pulled my hair out diagnostics-20240403-0022.zip diagnostics-20240403-2125.zip

Post installing tailscale on unraid and a windows machine where I had setup my unraid shares as drives, the drives aren't accessible. Just wanted to check if others have faced this issue?

Is it possible to install autogpt without it being in the apps section? Can anyone share how to accomplish that?

Hi, here are pics showing the plugin version and the error

I have the same issue. Would it help if I posted the diagnostics? The above is my server response on terminal

Ok, I finally found a way to get it back up. The server is up on an older version of the OS (turns out my backup was an year old) . I got this up by hooking it up to a lan. There is one issue I am facing 1) The Docker Containers are alive, but version update is not happening. On checking for updates - I get the error "not available" .. 2) All my plugins are erroring out. So seems like some sort of an issue. Any suggestions? Any diagnostic scans?

Sounds like an issue then. Let me figure out if I can do an ethernet connection. Secondly, I was unable to load the Unraid gui from bootup. I just saw a white screen and nothing else happened. If I selected unraid, it went upto the login screen. Does anything from the above setup declare itself to not work with the unraid gui?

Prev: Server was on a wired LAN. Router handed out a fixed IP So, I shifted residence. The movers moved the server, but didn't leave the USB booting drive in. So I use the USB creator to create a drive from a backup I had stored. Good till this Now, the new place doesn't have provision for LAN. Only Wifi. So I get a wifi dongle and plug it into the device. Now 2 issues 1) On bootup, I select Unraid GUI, but no GUI shows up. If I select regular unraid bootup, it does work and reaches the login prompt. But how do I now enable wifi and get the machine on the network? 2) Whatever UI I had via the web, is that somehow accessible? if I hook it up to a monitor? How do I get there.. Need y'all help guys .. how do I approach this in a step by step manner?

Gosh, I thought that the vdisk what I set up is going to the max accessible space for the VMs. I didn't know there was a way to let the VMs just use the Unraid storage and grow as needed. What should be the size of the vdisk and should it be (if I running crypto nodes or thereabouts) using the cache?

Thanks @itimpi Since I created a 2TB vdisk image and the cache SSD was only 500 GB - How was Unraid going to make this work?

So this is where I do get confused or don't understand how Unraid works. Looks like I misconfigured the drives, but say currently its said to Auto and Unraid decides that is to be on Disk 2 - why does it let the VM fill up the entire cache and not do anything about it? My rationale for using a single disk for these 2 VMs is because I was planning to test out some crypto nodes. ETH and BTC - totalling over 1 TB. If the SSD is only 500 GB, wouldn't it make sense to just write to a single disk? I was OK with it because I wasn't looking for it to be performant. But looks like a better idea would be to move these nodes out of the array themselves since they don't need to be backed up.