ddm73

Sorted. Thanks.

Thanks JorgeB, I have replaced both cables which has definitely made a difference. Disk 8 seems to no longer have read errors however it is reporting UDMA CRC errors in the UI [as per image below]. greatwhite-diagnostics-20231015-1038.zip

Hi Everyone, Hoping there is a solution to this other than "you've lost a heap of data and there's nothing you can do about it. I noticed that my parity drive had a red cross [see image] and was disabled. couldn't see anything obvious so I googled and found that some have had similar situations which was a faulty sata cable. I've replaced this but no resolution. I then did a read check on the array and came back with a heap of read errors on one of the pool drive [and a smaller number on one of the other drives; as per the image]. I'm at a loss to know where to go from here. I have attached diagnostic in the hope someone can point me in to a solution or to confirm data is gone and I just need to replace 1 or both drives. Thanks in advance for any help that can be provided. greatwhite-diagnostics-20231014-1019.zip

Hoping someone can shed some light on this for me. I am running a parity check on my array but it is going very slow, approaching 4 days and it has only done 2.1%. Diag's attached Thanks in advance greatwhite-diagnostics-20221016-1007.zip

it started downloading some queued items. Stopped all dockers and its now down to 20 hours

Thanks to both of you. Parity is resyncing now. It is hovering about 4-5 days to complete at this stage so I'll see houw it goes and I will report back when complete. Thankyou, thankyou, thankyou.

You guys are awesome!!! Now I wonder what the go is with the parity disc?? should I just replace it with the new one I have there?

Do I restart the array in normal mode now? 20220922 - file system check -L - Disc9 - GreatWhite.txt

And regardless of the outcome, A huge thanks for the help and responsiveness!!

Here you go. 20220922 - file system check - Disc9 - GreatWhite.txt

Got it. Didn't think to click what was clearly a link!!

Is this what you mean? https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Sorry, I should have pointed out that you have a bit of a noob here. I can muddle my way through most things but Linux command line isn't one of them. Unless the check filesystem [with -n] isn't on the command line in which case I clearly even more lost than I thought. [I hope the comical self deprecation is coming through in my comments!!]

The screen shot was prior to adding the 2nd parity but I didn't start the array with the new parity disc. So the array is back to how it was when it failed. I don't have any reason to suspect that the parity wasn't valid before it became disabled.

Sorry, Didn't see this before I reinstalled and restarted.

Old disc reinstalled and new Diags attached. greatwhite-diagnostics-20220922-2246.zip

The old disc 9 is in a box ready to ship off to Seagate to have data recovery attempted on it. I can pull it out of the box and plug it back in but then how do I attempt the repair?

SO, not having 2 parity discs appears to have bitten me in the arse. My parity disc is showing a red x and one of my data disc in not mountable [image attached]. The data disc is under warranty with free data recovery so its a maybe for getting the data back but in the meantime because the party appears to have failed I can't rebuild either. What are my options for getting the server back up and running without the data [hoping that I will get it back from the data recovery service]? If I rebuild the array, do all my apps still know where everything is? Or am I going to need to effectively start with a fresh UnRaid install and reinstall everything from scratch? I now have enough replacements to run 2 parity but need a path to get back to operational [preferably] without starting from scratch. Diags attached. Thanks greatwhite-diagnostics-20220922-1309.zip

Thanks Ken-ji, Works now. Apologies for the Noob mistakes.

Hoping someone can help with my problem below. Apologies in advance, I've no experience with python and not a lot more using docker but I am learning slowly so excuse my ignorance if I have done something stupid. These are the steps I followed to end up where i am; - Install the docker to Unraid - Open the console from the the Dropbox docker menu - run dropbox.py start -i [If I try to run it without the -i it tells me to use the -i] this installs something. - obtained the url to link my account - type Dropbox.py start for the first time and I get this; sh-4.3# dropbox.py status Dropbox isn't running! sh-4.3# dropbox.py start Starting Dropbox...dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-x5v0tL dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/dropbox' dropbox: setting python path '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431:/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/apex._apex.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' Dropbox isn't running! Done! sh-4.3# dropbox.py status Syncing 75,611 files Uploading 1 file... Downloading 75,610 files... So it appears from that last part that Dropbox has started downloading my files to the server however I can't find them. I used the default options when I installed the docker as per the attached image. The only thing I do know is that my docker image is filling up so I think for some reason the files are being stored in the docker rather than the share on disk1. Unraid version 6.8.3 Any help would be greatly appreciated.