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.

Hey JorgeB, thanks for the quick reply - I tried to update my firmware and at the part where you check what is the firmware currently installed (I used `./sas2flash -listall` since my card is different), I am getting the following: 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 it seems to be that I have a newer firmware? The LSI chip that I bought was listed on ebay as: LSI SAS 9211-8i 8-port 6Gb/s PCI-E Internal HBA Both Brackets - Bundle Options [Card Only,IT Mode (ZFS JBOD HBA)] So on the driver website I found the following links: 9211-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows Package_P20_Firmware_BIOS_for_MSDOS_Windows Version: 20.00.07.00 and Installer_P20_for_Linux Linux Installer Version: 20.00.00.00 is there something that I am doing wrong here? Haven't replugged the SSD into the motherboard, but will be doing that soon.

Hi all, I've had multiple issues recently that I would like to document. 1. I recently installed a new SSD as a new cache group - In the disc's logs I am constantly getting these errors, and I am not sure if this is fine or not. I don't know if this is related but last night, I copied a few files from one share to another and this morning that data was gone and I had to copy it again. Log for the SSD: Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Spinning up disk... Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Write Protect is off Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Mode Sense: 7f 00 10 08 Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Jan 11 13:34:40 mesawest kernel: sdj: sdj1 Jan 11 13:34:40 mesawest kernel: sd 7:0:3:0: [sdj] Attached SCSI disk Jan 11 13:35:07 mesawest emhttpd: WD_Blue_SA510_2.5_1000GB_22433T800639 (sdj) 512 1953525168 Jan 11 13:35:07 mesawest emhttpd: import 31 cache device: (sdj) WD_Blue_SA510_2.5_1000GB_22433T800639 Jan 11 13:35:07 mesawest emhttpd: read SMART /dev/sdj Jan 11 13:35:14 mesawest emhttpd: shcmd (56): mount -t xfs -o noatime,nouuid /dev/sdj1 /mnt/cache_files Jan 11 13:35:14 mesawest kernel: XFS (sdj1): Mounting V5 Filesystem Jan 11 13:35:14 mesawest kernel: XFS (sdj1): Ending clean mount Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 Sense Key : 0x5 [current] Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 ASC=0x21 ASCQ=0x0 Jan 12 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 12 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 Sense Key : 0x5 [current] Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 ASC=0x21 ASCQ=0x0 Jan 13 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1698 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 13 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 Sense Key : 0x5 [current] Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 ASC=0x21 ASCQ=0x0 Jan 14 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1701 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 14 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 Sense Key : 0x5 [current] Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 ASC=0x21 ASCQ=0x0 Jan 15 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1738 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 15 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951691109 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 Sense Key : 0x5 [current] Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 ASC=0x21 ASCQ=0x0 Jan 16 00:10:07 mesawest kernel: sd 7:0:3:0: [sdj] tag#1827 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 16 00:10:07 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1952922358 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 Sense Key : 0x5 [current] Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 ASC=0x21 ASCQ=0x0 Jan 17 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1896 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 17 00:10:06 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1950676478 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 Sense Key : 0x5 [current] Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 ASC=0x21 ASCQ=0x0 Jan 18 00:10:06 mesawest kernel: sd 7:0:3:0: [sdj] tag#1859 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 18 00:10:06 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1950129000 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 Sense Key : 0x5 [current] Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 ASC=0x21 ASCQ=0x0 Jan 19 00:10:05 mesawest kernel: sd 7:0:3:0: [sdj] tag#1856 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 19 00:10:05 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1950129000 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 Sense Key : 0x5 [current] Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 ASC=0x21 ASCQ=0x0 Jan 20 00:10:13 mesawest kernel: sd 7:0:3:0: [sdj] tag#1957 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Jan 20 00:10:13 mesawest kernel: blk_update_request: critical target error, dev sdj, sector 1951683685 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 2. I am constantly getting these errors, I assume from my UPS. Not sure what the correct fix for this is but I really want one because this keeps clogging up my logs. mesawest usbhid-ups[5948]: nut_libusb_get_string: Pipe error. 3. I was looking to spin down my drives so as to save on energy - and this appears to be working! However, I am now getting a bunch of errors in my logs that relate to my drives and smart - can anyone shed some light as to what is going on? Thank you very much for reading and your help. mesawest-diagnostics-20230120-0930.zip

I had a few tabs open pointing to my unraid UI, and today I can no longer access the UI. `top` tells me that its my virtual machine and "Agent" that are the culprit... I have attached my diagnostics and my top. The logs have the same error: Sep 30 19:16:56 mesawest nginx: 2022/09/30 19:16:56 [error] 6040#6040: shpool alloc failed Sep 30 19:16:56 mesawest nginx: 2022/09/30 19:16:56 [error] 6040#6040: nchan: Out of shared memory while allocating message of size 10270. Increase nchan_max_reserved_memory. Sep 30 19:16:56 mesawest nginx: 2022/09/30 19:16:56 [error] 6040#6040: *5052552 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Sep 30 19:16:56 mesawest nginx: 2022/09/30 19:16:56 [error] 6040#6040: MEMSTORE:00: can't create shared message for channel /devices Sep 30 19:16:57 mesawest nginx: 2022/09/30 19:16:57 [crit] 6040#6040: ngx_slab_alloc() failed: no memory mesawest-diagnostics-20221003-1225.zip

I wouldn't know how to check, but I didn't get any pop ups or anything akin to that. Where can I find if SpeedGap was detected? The Blue line was a test done at the default %, I believe, so perhaps that skewed the results? Turned off all my Dockers (Don't have any VMs) and ran the test again, this time at 10% and turned on the SpeedGap setting just to see what would happen. Still a bit wobbly but much less so than my original blueline. I will do another 1% test soon. By the way, since this program/script relies on me testing the drives every so often, what can I use to schedule a test every week or every month? Im quite new to unraid, but I'm sure there's a way to trigger this. Thanks!

8GB! Not running any VMs, just dockers.

All of you have such smooth curves for all your drives. I recently shucked a WD MyBook 8TB helium drive and I am getting very wobbly lines... I take it I need to turn off dockers while testing?