maxistviews

Perhaps it was as simple as re-seating the cables. When you installed the new parts the cables were improperly seated?

Server still crashes. Turned on Safe Mode this morning. lets see how that goes. So far no crashes, so fingers crossed.

Thanks, changed the setting, lets see how that goes - earlier today when I looked at it, my docker tab was telling me I dont have any dockers installed. Restarted and now theyre all back. Here is my syslog for now: syslog-mesawest Oct 24.log

My server has started not responding after 30 or so hours. I've been forced to reboot it manually multiple times this week. I've turned off my VMs entirely thinking there was some issue there. Before it was entirely unresponsive, today I've caught it before it went completely unresponsive - I can get to the login screen but as soon as I log in, it hangs. If someone could look through the diagnostics and tell me if they see anything out of the ordinary, I'd appreciate it. mesawest-diagnostics-20231023-1018.zip

I did. but I removed it. I imagine you should still be able to see it in unraid lsusb first. Is there a command to check with ffprobe?

The server is using 100W and I have at least 600W power supply if I recall correctly. I used a USB 3 port, original cable. I’ll check today if I can reset it back to normal power. My understanding is that it might be per device, so maybe what I did had no effect on the server environment .

I recently purchased a USB Coral and tried installing it onto unraid with a new frigate install. I first plugged it into my PC and installed the Windows drivers, turning on the full power mode. Then when I inserted into my unraid box, it showed up as "Global" which I know to be correct, but shortly after this, it no longer appears. No google or global USB devices. Has anyone else had this issue? Was there a driver update I was supposed to do on top of this or something?

I’m on 6.12.3 and so far I haven’t had any issues with the log overfilling. I used to have a lot of issues on the old versions. Upgrading my LSI SATA drivers and updating unraid fixed these problems for me.

I have switched to a new cable since March 6th, but I will post about it on the relevant thread. I'll have to check again later since I just updated all my dockers. If a docker has the `--restart unless-stopped` parameters, that would still show up in the Uptime, right? Should I also try to update to 11.5 at this point? I am currently on 10.3. I was waiting for things to settle before updating.

Hi, so its been a few weeks. I am still getting a lot of spam in my logs, unsure what is causing it. I have also noticed that I was running a deprecated version of the NUT UPS plugin, so I updated that and also changed the USB cable that was being used for the UPS to the PC. I am still getting `nut_libusb_get_string: Pipe error.` errors. I am also getting a lot of messages that say "Port # entered disabled state". Hopefully you can shed some light on this. mesawest-diagnostics-20230330-1404.zip

Could someone help me/ provide a guide on how to install Monica? here is my set up: I have a mySQL database (192.168.1.13:3307) named `monica`, but when I launch the monica docker , I get this in the logs: Unable to contact your database Despite my mySQL docker being active, and the port 100% being the right one. Any insight as to why Im not able to contact it?

Thank you!! I will write back in a day or so to ensure my logs are not getting filled up anymore. root@mesawest:/lsi# ./sas2flash -list LSI Corporation SAS2 Flash Utility Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved Adapter Selected is a LSI SAS: SAS2008(B2) Controller Number : 0 Controller : SAS2008(B2) PCI Address : 00:04:00:00 SAS Address : 500605b-0-0650-1ae0 NVDATA Version (Default) : 14.01.00.08 NVDATA Version (Persistent) : 14.01.00.08 Firmware Product ID : 0x2213 (IT) Firmware Version : 20.00.07.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9211-8i BIOS Version : 07.39.02.00 UEFI BSD Version : N/A FCODE Version : N/A Board Name : SAS9211-8i Board Assembly : H3-25250-02F Board Tracer Number : SP33006164 Finished Processing Commands Successfully. Exiting SAS2Flash.

In your guide, I am getting "stuck" on using the sas2flash utility to verify my firmware files. When I do this, the get this: root@mesawest:/lsi# ./sas2flash -listall LSI Corporation SAS2 Flash Utility Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved Adapter Selected is a LSI SAS: SAS2008(B2) Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr ---------------------------------------------------------------------------- 0 SAS2008(B2) 20.00.02.00 14.01.00.08 07.39.00.00 00:04:00:00 Finished Processing Commands Successfully. Exiting SAS2Flash. So I am using the sas2flash that I found inside the linux files (as specified) under: Installer_P20_for_Linux\sas2flash_linux_i686_x86-64_rel\sas2flash So am I right in thinking that the version of the Utility is 20.00.00.00 and my current board firmware is 20.00.02.00? So Im good to upgrade then?

Hey @JorgeB, apologies for the late reply, haven't had time to investigate this further. Based on the guide linked, I will need both a Windows installer and a Linux installer. I believe that the Windows installer is indeed `20.00.07.00`, however, the Linux one seems to not have a version above 20.00.00.00. Am I correct in this?

My email address historically uses a capital letter - the new sign in system could not parse the capital letter, and would just show me a "Wrong email/pass" error. I tried to reset my password, and it would send an email that I would then not get, presumably because it wasn't able to send it to an email with uppercase letters? I only saw that capital letters werent allowed when making a new account with the same address (to check if my account had been deleted) where it then prompted me to make the email lowercase. Then asking for a password reset yielded an immediate email. I have never had this be a problem on any website, and I wish it was laid out a little clearer that capitals wouldn't be accepted - would have saved me a little time.