Guanyin

I believe I have resolved the issue. I put the array in maintenance mode. Did xfs_repair -v on Disk 4. Got an error saying I could clear the log with L. Did xfs_repair -Lv. Did xfs_repair -v. Turned off maintenance mode by switching the array off and on again.

I’m having the same issue as I had at the beginning of this year, but with a different disk. Previous post Last time I solved the issue by forfeiting the data and formatting the unmountable drive. Unfortunately the problem has returned in a different disk…

I've ended up formatting the disk and forfeiting the data. All the data is replaceable, hence this decision. Thanks for all the help @JorgeB

Yes. I’m going to wait for another xfs_repair (which is giving the same result as my initial post, so far). When that doesn’t work I’ll await the v6.12-rc3 update. If that doesn’t help I’ll try file recovery. If that doesn’t help I’ll try replacing the disk with a new one. Is that a sound strategy? Thanks for all the help so far!!

Now I get this notification 🤔

Could you elaborate on this? Isn't the filesystem issue with that specific disk? Or is a filesystem issue an array issue? Another question: which version of UFS explorer is required? Another question: What if I forfeit the data on that drive, format the drive and add it back to the array? Would that work? Obviously, I wouldn't know which data I would lose.

What kind of file recovery util could I use? Do I understand correctly that I’d be recovering files from the unmountable drive using a recovery util, put those files on another drive, and then format the unmountable drive to add it back to the array?

Is it possible to replace the unmountable disk with a new one and solve the issue that way?

Disk 4 repaired a bunch of errors. Disk 5 is giving the same result as I mentioned in my initial post. Edit: Disk 5 is still running, since it took a loooong time last time. g1-diagnostics-20230406-0943.zip

Hi JorgeB! Here are the new diags. g1-diagnostics-20230405-2351.zip

I’ve added a new drive to my unraid array by replacing a smaller one. However, another drive, not included in the transaction, became unmountable. It said it was dissbled. I’ve done short and long SMART tests and both gave no errors. Here’s the output of “xfs_repair -v /dev/md5” and my diagnostics. g1-diagnostics-20230405-0810.zip

when I enable PIA VPN I can't get over 2mbps somehow and proxy used to work for a while... If you know something to fix the speed for PIA VPN then I'd love to hear it

@no1home I've noticed that Deluge doesn't crash when I disable proxy, when I enable proxy it keeps crashing and sometimes even not working. These are my proxy settings:

I keep getting this in my logs which crashes Deluge. 2020-01-20 18:45:01,825 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2020-01-20 18:45:01,825 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2020-01-20 18:45:01,988 DEBG 'watchdog-script' stderr output: Unable to initialize gettext/locale! 2020-01-20 18:45:01,988 DEBG 'watchdog-script' stderr output: 'ngettext' Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation builtins.__dict__['_n'] = builtins.__dict__['ngettext'] KeyError: 'ngettext' is there a known solution for this issue? I've seen it on this thread before but couldn't find a solution to the problem.