Fiservedpi

Just upgraded to 6.8.1 re-ran parity check found 0 errors so guess it was a false alarm thanks for the info everyone

Why can't they just write it in English lol "yo disk f#$@ed buy a new one" Plug-in idea? Haha

Ok thanks which attributes are indicative of a failing drive

i was never good at reading at the smart reports but i thought P = Prefail 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 167 167 021 - 6608 4 Start_Stop_Count -O--CK 100 100 000 - 385 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning Which sections should i keep an eye on the smart report?

No, here's the smart report if I'm reading correctly all my hard drives are in prefail? All drives are less than 4 months old I did relocate the server 18 days ago tower-diagnostics-20200118-1143.zip

Is this a sign of something bad?

Sorry yes everything is good

I just moved all containers pertaining to Nzbing to the bridge adapter setting and are now communicating nicely. Thanks again

If my Sonarr and Unraid share the same ip (HOST) but different port # the container won't connect to Sonarr but if I put Sonarr on a different adapter (Br0) it connects but that doesn't work for me, as changing my Sonarr IP breaks SAB for me any idea why I'm getting the EHOSTUNREAC error or how to fix it

So I got the container pulled down but, having trouble linking it to Sonarr my Sonarr IP and Server IP are the same if that makes any difference I think i got it i was using the wrong bot token but still need help with Sonarr EDIT:: I JUST CHANGED MY SONARR IP and it worked

The dev should be fixing soon, they answered on git

Md5 hash issue is back https://github.com/dorgan/Unraid-networkstats/issues/12

Download of RC 9 is going really slow today 20191207_135445.mp4

RC 8 looking good so far no GSO error in 24hrs Unraid Nvidia build 6.8.0 RC 8

And it's back RC 7 Unraid Nvidia build 6.8.0, the funny thing is it didn't happen at docker and 1 VM start like before, it happened at 4am Dec 4th when nothing much was happening. Also deleted the inactive Wireguard Tun I had set up will monitor after removal. I'm also noticing something called general protection fault that I've not noticed before. Log attached tower-diagnostics-20191204-2021.zip

Everything working great on RC 7 HERE

F@$_k me gently with a chainsaw!, you guys/gals are the best thanks for your work infinitely appreciated!😘😘

Thanks for your help @Jonathan

The first sign of this GSO error for me was Rc4, had zero issues on RC4 OR before all started with first boot of RC5 and starting docker and VM's if only start docker no error once you hit start on a VM it appears

So they leave you no option to get the data off without a network or shucking

Well that's silly that's ok I've got it mounted unassigned now will have to go over the network then

Will that's weird the USB port on the mycloud is female A as if I have an A to A cable

Is there a file explorer in the Unraid os gui? When connected to the machine and chose Unraid OS gui from the boot options?

Cool ty I like that idea Basically I'm mounting it as unassigned then using a docker file explorer to move the data Got it!

Cool thank you . Where it at yo? 😆😆🥁