Jaxs

Well i ended up just pulling files from my usb and trying to reformat and reimage to no avail, it gave me an error saying that it was in preotection mode. After a lot of trial and error I use usb a new usb and drag some of the necessary files (not knowing which file did what) over to get my array config running again. It would have been great if there were some real solutions to these issues posted instead of having to check a dozen or so post throughout the years with fragments of a solution/suggestion from members rather than tech support. Perhaps some "how to" guides that are up to date and laid out for people that may not be as savy as some of the most knowledgable members of the community. Just my 2 cents. You can close this out

Hello all I decided to upgrade to the newest release and upon doing so I am stuck ath blue screen with it just cycling through the countdown over and over. Ive tried manuall starting in Gui mode and safe mode with no lcuk, the screen just blinks so a split second and im right back where i started. Even the memtest wont work. Ideas? solutions?

Hmm I use hot swappable bays, wonder if there is a problem with the bay or the sata to the mb, I also use a pci to sata card but I'm not sure if that one is on it or not.. Thank you for this, this helped greatly

borg-diagnostics-20220225-1750.zip Good morning all Running 6.9.2 and I've had a particular drive show as disabled and emulated twice for me and I'm hoping someone can look at the diagnostics and see if they can tell me why. I replaced this drive just to be safe but I've checked the health of the drive and ran it through preclear twice with no errors reported. By all indications this is a good working drive, perhaps one of you kind souls can give me some insight to what may be causing this

Just an FYI, i have hot swappable bays and i was taking them out to locate the bad drives as I don't have them marked ( will remedy that soon!) and even swapped bays to make sure I wasn't having a bay issue. I assume that will likely show up in the logs

borg-diagnostics-20220225-1750.zip

Attached is the syslog but this was after the reboot. Any assistance is greatly appreciated syslog.txt

Yup I know they aren't directly related which is why I thought this would be an easy answer of how I attack this as i don't care if I retain the bad drive and only wish to recover the corrupted/disabled one. Ill attach diagnostics when I get home but I figured I was already going to be following the guide posted to recover it. I just wasn't sure how to deal with both issue at the same time and a safe route to do so. Perhaps I'm just not explaining myself well enough

I will be sure to do that but I was uncertain if I even had an issue at first as my VMs and other Dockers were running fine. Can I safely take the bad drive out before trying to fix the file system on the other drive? some guidance would be greatly appreciated

Good morning all Last night I noticed my Plex wasn't working so I checked my Docker which turned out to be corrupted or something as it was unresponsive. I did a clean shut down but when it came back up I had one array drive that was disabled and being simulated and another that outright failed at the same time. The one that failed is an old drive that did not have anything on it so I really couldn't care less about that drive. I'm confused on how to deal with this as the array is not started since there are 2 disc issues and I only have one parity drive yet it is saying that it is being emulated. I'm ok with taking the bad one out of the array and have read what I need to do to try to repair the filesystem but it also states "Make sure that you have the array started in the correct mode. If necessary stop the array and restart in the correct mode by clicking/unclicking the Maintenance Mode checkbox next to the Start button." I have not tried to start it in maintenance mode as it was too late to get into it last night but I read that statement as the array must be started which it will not do at the moment. Hopefully one of you Gurus can give me an order in which to attack this so I don't have a lose of date

Yup i can connect now both ways without an issue. Good lord.... so sorry to bother you for something so stupid. Thank you for being patient and trying to help

OK..... problem solved i believe. So i got a message from my ISP last week that they were doing maintenance to the entire township and i was included in that. What i didnt know is that my IP address changed 😆. Steam seems to be able to see it both ways now. I will have a friend try to connect and see what happens

Ok you are correct, I can go through the server tab in steam for the local connection using port 2457 but not externally using my IP:2456 or 7. I attached the screen shot of my port forwarding. According to my router documentation i believe that is correct but i could be wrong. I will try to add other iterations of this

I see a steam connection error in the log now. Not sure how to correct that