jabonline

So no one has suggestions from the diagnostics I posted?

So something is seriously wrong on my unRaid. It was able to download the plugin, but it got network failure. The other issue is that overall it seems very slow. My SabNZBd docker is downloading at < 1Mb/s. Normally I can get around 200MB/s copying over SMB 10GB DAC to my cahce drive (SSD). Hopefully someone has some insight to what is going on here, diagnostics attached... This is what I got downloading the plugin: plugin: installing: https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg plugin: downloading https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg plugin: downloading: https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg ... failed (Network failure) plugin: https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg download failure (Network failure) Updating Support Links Finished Installing. If the DONE button did not appear, then you will need to click the red X in the top right corner tower-diagnostics-20210315-2145.zip

No matter what share I try to copy to it that sits there saying calculating and there is no network activity. I can copy from the array to windows though. I have my credentials put into credential manager in windows. Not sure what is going on. Uploading diagnostics. tower-diagnostics-20210314-0808.zip

I did a bunch of things, so not exactly sure what fixed it. Anyways moved appdata to cache from disk2. Deleted docker.img and recreated it. Removed/Reinstalled CA Apps plugin. I was then able to go to previous apps and reinstall them all. Everything seems to be working now.

Getting Appfeed Failed, I have static dns to google, level 3 communications and quad9 in that order. So there should not be any DNS issues. I'm posting debug info, maybe someone can help me fix this? CA-Logging-20210314-0500.zip

Thanks, reboot fixed it. Now to get proper backups going for the "important stuff". Probably only 20% needs backing up, the rest is just media/software installs that can be downloaded again if necessary. Oh and test VM's that I'll probably never use again and probably should just delete at this point anyways.

Hum, in the web interface its saying Unmountable: No File System and not sure how there would be a duplicate uuid, the disk is being emulated and the actual drive is removed. I certainly have not mounted it manually...

So using Linux File Systems for Windows by Paragon and a USB adapter I plugged the drive in and see all the files, copying them now. I'm not sure why this program can mount (in read only mode) and see/copy the data, but it looks like its mostly intact, might be a few corrupt files, but it looks like all my moms pictures are at least mostly intact. Really that's the only thing on it that looks important. Everything else stored on this specific drive looks to just be TV/Movies, I'll dig a bit deeper, but so far that looks to be the only "important files" on this drive. tower-diagnostics-20210309-0813.zip

So rebuild completed. I started in maintenance mode and did an xfs_repair. It told me I needed to do it with -L, so I went ahead and did that, still no dice after stopping the array from maintenance mode and starting it normally. I'm attaching what the xfs_repair told me, is there anything else to do before looking at actually having to look at actually trying to do actual data recovery on it? I've pulled the drive, I'm only going to run it on the emulated disk, so if I have to look at pro data recovery services that should give them the best chance of recovering data from the disk. xfs_repair.txt

While the array was offline I pulled the drive and put it in the same slot as the drive that was having issues as I wanted to see if it was a drive issue or a drive bay slot issue. Ya that was probably a dumb idea, should have just used a spare un-used drive instead of using one with live data on it. The WD Red drive had a pre-clear earlier this week (work in IT, got it used from a client, but I'm pretty confident it has plenty of life left in it). So that's why I wanted to test the drive bay as it seemed odd that it passed the pre-clear and then died a couple days later.

So had an issue with disk 8 (found out its an issue with that specific bay, not the HDD). So I went ahead and stopped the array, swapped the drive to another bay. Started the array, so it would rebuild it on to same drive from parity. That process is going fine, should be about 8 hours to rebuild it. The issue is disk 9 upon starting the array now says unmountable: no file system. I'm going to let the rebuild finish before I touch anything. After its finished, what should I about disk 9? I'm posting my diagnostics, hopefully that helps. tower-diagnostics-20210308-1546.zip