treos33

I had the same issue. After preclearing one drive, I installed two more but was unable to preclear them. They showed "Starting..." forever. The log showed the initial script invoke line but nothing after that. I don't know the cause but I was finally able to get started by uninstalling and reinstalling the plugin.

Yup, flashdrive is cooked. Couldn't even run chkdsk. I was able to restore from a backup and access the web gui. Thanks for the help!

I restarted my machine while I was doing some network upgrades, replacing a switch and tidying wires. After restarting the server I can't get to the Web GUI. I can connect via SSH and local console. I can see that it's still getting an IP address (I think this mostly rules out my network changes as the cause). I started in safe mode and GUI safe mode with no luck. I grabbed the diagnostics (attached) via the command line and manually made a backup of the boot drive. I'm debating trying a new USB drive, but I wanted to check for any ideas here first. tower-diagnostics-20230320-1941.zip

I successfully upgrade to 6.8.2 today. Not sure what has changed but it worked. Sorry Coolspot, I hope you figure something out soon!

Still hoping to get some help with this issue. I realize this was originally posted during the holiday madness so hopefully I can get a few more eyes on the issue now. Again, I can't get an IP address when I upgrade to 6.8.0. I have no issues on 6.7.2. I have linked to some other issues above that seem to be very similar to mine.

Disabling bonding made no difference for me. I still couldn't get an IP address from DHCP with only one ethernet adapter configured. Reverting back to 6.7.2 fixed the issue completely. I did not try booting into GUI mode before reverting to 6.7.2.

Another similar issue: This case and the one I found previously are both using Supermicro motherboards as well.

Ok, thanks. I'll try this after work today.

I'm having similar issues. I created a similar support topic but I'm not getting as much attention as you so I figured I'd try to consolidate here. My post: Another very similar issue that has been posted recently: The one thing we all have in common is that we have Supermicro motherboards.

My switch does support LACP. This exact configuration was working perfectly for months on 6.7.2.

Just wanted to say there seems to be another similar case here: I'm still hoping to get some help with this. I'd prefer to use DHCP and let me router assign IP addresses if possible. Thanks

After upgrading to 6.8.0 my server was unreachable on the webUI. I was able to connect to the CLI and noticed that the IP address was set to 169.254.234.11. I've gathered that this is an Automatic Private IP. I was able to connect to the webUI at this address and I saw on the network settings that the default gateway was set to "link". I was able to change the network settings to use a static IP and manually define the gateway and DNS server. This seems to be working fine at the moment but I want to understand why this happened. I'm not sure if it matters but my mobo has two ethernet ports and I have them configured in a bond. I didn't try removing the bond but this configuration was working perfectly in 6.7.2 for months. Lastly, I have a few different VLANS configured. When I assigned the static IP to my main interface, the IP of my first VLAN was then set to 169.254.234.11. I set all my vlans to static IPs and they're working fine now too. tower-diagnostics-20191215-1943.zip I've attached my diagnostics from before I started assigning static IPs. Let me know if there are any other details that would be helpful. Thanks in advance!

So I finally figured out part of the mystery. Whenever I have my 4 port NIC (HP NC364T) installed, IOMMU gets disabled. The next part of the mystery is why is this happening? I would like to use this NIC to passthrough to VMs at some point. Also, I did update the bios to the most recent version but it made no difference with this behavior.

Yeah I can try that next. I'm on the same bios I tested Proxmox on and it's not exactly ancient.

This is as close as I can find to a manual. Also forgot to mention I briefly had Proxmox installed on this box and I don't remember having any issues with IOMMU.

I'm trying to play around with a few VMs on a new machine but I can't enable IOMMU. I've enabled VT-d and VT-x in bios. The only other virtualization option I see is Intel TXT which I have disabled. I've attached a snip of my system info and my diagnostics. Thanks! valentine-diagnostics-20191126-0217.zip

Ok, thanks. I reformatted the cache drives and I'm currently restoring data. Ran into a bit of an issue when recreating the cache pool. Not sure if its a bug or I did something wrong. I changed the cache pool to 1 slot. Changed the assigned drive to xfs, started the array, formatted, and then repeated with the second drive. I changed the pool to 2 slots and assigned both drives. When I started the array I was given the option to format the first drive in the array but the format never worked. It kept saying the drive was unmountable. I had to change the cache pool back to one slot and manually format each drive to btrfs before it would allow me to create the cache pool. Thanks for all your help, everyone!

I still have a few questions about why this happens and how to fix it. Isn't this the point of using a btrfs pool for the cache? It looks like all the errors are coming from one of my cache drives, sdh. Shouldn't a btrfs scrub identify this? To correct this, should I just remove sdh from the pool and reformat it? Should I do it for both cache drives? Thanks again!

Thanks, John. How did you determine the cache file is corrupt? Why wouldn't the btrfs scrub turn up errors if the file system was corrupt? My cache drives are only a few months old, I'm surprised that they would be corrupt already. Thanks for you help!

Having some serious issues right now. Here's the steps I've been going through as best as I can remember them: First I noticed some of my docker webUIs were unreachable. When I went to investigate the Unraid GUI was still responsive but I couldn't really do anything. Couldn't stop docker, couldn't stop the array, couldn't download diagnostic files. I was still able to connect via ssh and sftp but I couldn't stop docker and unmount the array. Tried to back up some of my docker appdata but I found the cache drive had become read-only and even reading was causing issues. Ended up forcing an unclean shutdown. On reboot, docker restarted with one of my containers as an orphaned image. When I tried to restore the orphan I got an error and the cache file system became read-only again. This time I was able to stop docker from the GUI. I stopped the array then restarted it and the cache became read/write again. Deleted the docker image and created a new one. Setup about half my containers when I started to get errors again. Downloaded system log. Had to restart at this point because the cache was read-only and I couldn't unmount the array. Recreated the docker image again, and installed only a select few containers. I'm basically just waiting now to see if it happens again or if its dependent on the container. I should also mention that I've performed 2 btrfs scrubs on my cache drive with 0 errors reported. I've tried a scub on the docker image after errors occurred but it always stops immediately. Any help would be appreciated! Thanks. tower-diagnostics-20180427-1922.zip

Thanks trurl, I rebuilt the drive over night and everything seems OK. Any idea what would cause the read and write errors if the drive is OK? You suggested the connection but it seemed secure. johnnie.black, I noticed the failed notifications in the log too and realized I had changed my email password and forgot to update the credentials in unRAID, its been resolved now

Hello! This is my first potential drive failure in unRAID so I'm doing quite a bit of research. I'm a bit confused because unRAID shows 8 errors and has disabled the drive but there don't seem to be any problems with the SMART status. I just completed an extended SMART test without error. Should I try to re-enable and rebuild the drive or should I just replace it? Would there be any benefit to preclearing the drive before rebuilding it? The drive in question is data drive 2. My diagnostics file is attached. Any advice would be appreciated. Thanks! tower-diagnostics-20160523-1730.zip