sixfootsideburns

by "through 'screen'" do you mean with a monitor connected to the server? Totally get that terminal is normally for faster tasks, this one is definitely atypical. If all goes to plan I hope I don't have to do this very often, I can blame my own ignorance for this one... I'm not certain that it's not my desktop, but I didn't think so. I'll turn off any sleep stuff and see what happens though!

Firstly, I'm unsure if my description is correct. If not, please correct me. Second, I'm definitely still learning my way through UR and the Linux platform as a whole, so bare with my ignorance. I hope this isn't obvious, but I promise I have done some searching. Here's my issue: Recently I found that I had an issue with hardlinks in my "arr" suite and instead of actually creating a hardlink they were making copies. So some portion of my current media library (but not all) have renamed duplicates on my media share. I'm trying to use jdupes via the fantastic NerdTools docker plugin to identify which items have duplicates because I don't remember what files I carried over from my old server. I know I could sort manually, but that's annoying and error prone so I would prefer to at least start with jdupes. My issue is that because of the size of the existing share, and the number of files, my terminal seems to time out (i.e. prompts with the "Press ___ to Reconnect" message) before 'jdupes -M -r /my/share/name' finishes running. So a few questions: When this happens, is my previous command technically still running? I think no, because my CPU usage drops back to idle vs. the slight bump during the scan. Can anyone confirm one way or another? Is there a way to disable this terminal behavior, ideally just temporarily? Right now my only way is to sit at my keyboard, occasionally moving the mouse and clicking something, until it finishes (which really sucks). Appreciate any guidance!

Success, thanks a bunch for the support!

Any ETA on when I can leave time out? 🤣

Makes sense, thanks for confirming. It's certainly confusing. When I first plugged it in, I could change settings. In an effort to troubleshoot my inability to mount the drive though, I updated Unassigned Devices and after updating everything is grayed out. Ever since I've been unable to change anything. If I can provide any extra inputs let me know, definitely a bit stumped on this one and haven't really found anything online.

Rather than buy a drive hookup, I elected to first try the windows VM route. After some troubleshooting, it's running. I can't figure out why, but for some reason I'm unable to change settings on the unassigned drives (grayed out - anyone know what this might be about?). I used to be able to, but after updating the Unassigned Device plugin I'm no longer can. Thankfully one of the my two mirrored drives showed up in Historical Devices, and I was able to change the settings there? Seems strange, but ok? So I enabling Pass Through for that drive, plugged it in, got VM drivers updated, and mapped the drive. After that it DID show up under Drive Manager in Windows. I had to Import the drive but after doing that it loads correctly and I'm now able to migrate files via the VM. So I still have a lot of unknowns, but at least I'm able to get my files. Questions: I think the issue with not being able to mount the drive was due to the file system not showing up. But why wasn't it recognized if it was NTFS? Why can't I change drive settings? Is there any work around for this? I got pretty lucky with Historical Devices, otherwise I think I would have been locked out of allowing Pass Through for VM. Any thoughts?

This is super helpful, thanks for doing some testing on my behalf! I remain stumped, but it seems next steps are to get another external SATA-to-USB hookup and see if that changes anything on a windows machine. In the mean time, anyone have any other thoughts on what I might do to get it mounted? I'm still stumped as to why my file system shows up correctly in MiniTool but not in UR.

So maybe that's my issue at least for the windows machines, I'll try and get my hands on an external mount. Any thoughts on why I can't mount with UD though? I would much prefer to transfer files that way to speed things up. I'll do whatever I have to, but 4tb via network transfer just feels messy.

For sure, I just figured someone in this crew might have a brilliant thought. Linux really isn't my area of expertise, and there are lots of people smarter than I am around the interweb! To answer your question, UR shows nothing in the FS column which is why I'm so confused. Only thing I can think of is the system doesn't the disk because it's Dynamic? I'm not 100% clear on Basic vs. Dynamic but I understand the gist. Though I have no idea if Linux and Windows would handle them differently? Setting up a Windows VM is a good idea, I'll give that a try first. But even as a pass through wouldn't I still have to mount the drive? I never bothered setting up VMs on the new system because I didn't really need them. No spare drives at my new home to mess with unfortunately, but that is a good idea. I'll keep that in my back pocket for sure. I have hooked up one of the drives via a empty, shucked, WD easystore enclosure but even on a Windows machine it didn't show up except with recovery tools like Minitool. Any reason to think hardware wouldn't register a non-WD drive? I did consider just messing around with one of the drives because the data is mirrored. But if I have to bring the drives back to my old home again then I'm a bit paranoid about something happening in transit. There are a lot of photos on those drives (poor practices, I know) and my wife would probably bury me in the backyard if I did something stupid. If we lost them to nature or a fluke event? Maybe I'd survive... but negligence? Not a chance.

Question for the forum that I've been unable to find an answer too: I had an old file server running on a Windows machine that I am trying to migrate to a new UnRaid setup. This older server had 2x 4TB drives running in mirror via the windows utility, and everything was kosher. I have since moved, but the Windows server stayed at my old home and my UnRaid server is at my new home (3200 miles apart). In an effort to avoid transferring everything via FTP, I carried my drives to my new home during a visit. However when I plug in either of the drives to UnRaid Unassigned Devices shows the drive, but they can't be mounted (greyed out). It looks like UnRaid doesn't recognize a file system, but I know they are both NTFS. I originally assumed it was an issue with the mirror not being broken, so I carried both drives back to my old home, plugged them into the old system, verified the data, broke the mirror via the windows utility, and carried both drives back to my new home. No dice, the issue is the same. I've scanned the drives with a few different utilities, and the data looks intact. Today I scanned the partition with MiniTool and confirmed the file system is indeed NTFS, so I can't figure out what's going on. Does anyone have any thoughts? My only idea is that Unassigned Devices doesn't like that it is set to a dynamic disk, but don't want to convert to basic without confirming. If anyone has ideas I would be grateful!

As it turns out, my Deluge continues to have issues. Something happens when I kick off a download and it causes all my dockers to crash. Any guesses on that one?

Yeah I figured that solution would be pretty frowned upon by the community 😂. Until very recently though it was worked very well with some of the most solid wifi I've experienced, not a hiccup of lag, and essentially no down time in almost 18 months. I have more complaints with Xfinity's service than I do with the Google Hardware. With that said, I 100% agree with your statement on cloud dependence. It's a nerve racking trend that I also try to avoid (hence the personal server as a primary source of storage). No security cameras on my end to manage thankfully, just the server. As an update, after pulling the bad stick of RAM I booted back up and Force Checked any files in Deluge. Deluge locked up, and when I went to restart the docker I found all my Dockers were crashing (Error 403?). A bit of research found I likely had a corrupted docker image. I deleted it, cleared my dockers, and set everything back up from scratch. So far, so good. Including! *drum roll* My original issue! I've no idea why a bad stick of RAM would prevent reconnect on network outage but yesterday I had a connectivity blip in the middle of the day and was able to access Unraid's WebUI once my connection came back. Big thanks to everyone for the support and ideas for troubleshooting. I truly appreciate the input!

No internet access, but according to my ISP's website my modem is still connected. Some HW info: Modem: SurfBoard SB6183 Router: Google Home Wifi Switch: Netgear FS105 Currently I do not have the IP reserved on my router, and I'm still running a Static IP in Unraid. All equipment has been otherwise stable for quite awhile. This is a great question that I don't really have the answer too. I'll have to continue monitoring. Is it likely that an issue with Unraid could take down the connection across my network? Great to know, thanks! I've only dealt with a bad stick of RAM once and it was years ago. Ultimately it led to major instability but that was it. Thanks for the ideas from everyone. I've pulled the bad stick of RAM and booted the server back up. I'll continue to monitor, but if anyone has any other thoughts on the network question I'd love the feedback. In the mean time if the server stays stable for the next day or two I'll look to upgrade to 6.9.X as suggested.

I had not tried upgrading because the server was crashing, and I was on the hunt for a flash drive that I finally found to run the memtest. First pass looks like I have a bad stick of RAM which is both a bummer and a relief. I'm letting the test run for awhile longer to be sure that was the only issue, but when I ran it initially it stopped the test early because of the volume of errors (10k+) which feels like a likely smoking gun? Not sure what caused it to degrade so quickly, and I have no idea if that would attribute to my original issue, but fingers crossed. Does anyone have any feedback on whether a bad stick of RAM would likely cause the server to freeze on lose of network connection?

Recently the server started just locking up randomly too and is requiring restarts. Anyone have any ideas? Getting a bit desperate

That's a good idea, I'll look to try and revert to an old release this weekend. Unfortunately a new Ethernet isn't in the cards right now, does that seem like a likely culprit? Has anyone ever heard of something like this before?

Oh yeah, the system works just fine until my network goes down and then it never reconnects. And when I plug in a monitor so far the results have either been a blank screen or that one time it was unresponsive with the screen I left in the OP. I have not run a memtest, but I certainly can. It seems odd that memory would be a factor only when network goes out but who knows. Anyone else have any thoughts? Any potential smoking guns to investigate?

Originally I used Automatic and only just recently changed to Static to avoid having the correct my dockers every time. The same problem existed when I used Automatic though. UEFI

First and foremost I'm new to unraid and I promise I've tried to find answers on my own, but I'm finding it challenging to know if I'm even searching the right things. Please be gentle with me. In desperation I'm hoping the good people of this forum might be able to help me. Here's what I'm running into... I've been having network issues for the last few weeks at home, and every time my network goes down I'm unable to reconnect to the server once it returns. My IP is set to static so I'm confident I'm connecting the right address. A hard reset is the only thing that I've been able to do to return to normal operation. I'm concerned with the impact that could have on my data though and my parity check takes almost 28 hours which isn't ideal. Based on other threads I've seen for other issues I've tried plugging a monitor + KB into the server afterwards to try and reboot via command prompt, however nothing comes up ever comes up (blank screen with no signal). After having the same issue 3-4 times with the same result I finally had the thought to plug the monitor in before I boot up to see if for some reason that made a difference. Recently when the network went down, I plugged my monitor back in and found that there was some code displayed, but the server was unresponsive to keyboard input. I've attached a photo of what was visible. I'm on with my network issue, but I'm totally at a loss of what might be happening with unraid. Is this just normal behavior? Are there settings I could check? Even if someone can give me guidance on what to search for to find answers I'll happily continue my research on my own. I really appreciate any guidance anyone could provide! Currently running unraid 6.8.3