PsionStorm

My fix seems to have been temporary anyhow. Some containers are no longer updating again.

UPDATE: I decided to go a step further with the DNS settings and updated my router's DNS to Google's DNS servers. So, now both Unraid and my router have Google's DNS. This seems to have fixed the issue. There was one docker container I needed to delete and reinstall, but the process is fairly quick and didn't require me to set everything up from scratch. Outside of that, so far so good. I'll update this thread if I run into more problems.

Sorry to bump this, but I am still looking for a solution. Does anyone have any ideas I may not have already tried?

I have a handful of Docker containers that have stopped updating as of a few weeks ago. When I go to apply the update, there are no obvious points of failure - the old container is stopped and removed successfully, and the new one installed. But the "update ready" prompt remains. This is happening on a few containers. I found one solution was to update the DNS to use Google's DNS servers, so I tried that. I also tried removing the container manually and reinstalling it from previously installed apps. I was able to get a few of the containers to work properly after these two steps, but there are a couple that even when removing and reinstalling, just refuse to update. All three are containers from Linuxserver.io. Calibre Calibre-web Overseerr Any advice would be appreciated. Thanks in advance. excelsior-diagnostics-20231023-0521.zip

Sounds good. I'll start that when I get home. Thanks!

So, I'll just let this one complete then. Anything you recommend doing after it's completed?

I believe the current sync is non-correcting - it was my scheduled monthly parity sync and I *think* I turned off correcting. Does it tell you in the logs?

I moved it to parity1.

I thought I did, but I followed a different process. I added the new drive as a 2nd parity, then pulled the old one and set up a new config. I saw that recommended in a few places and didn't see the article you linked. Looks like that may have been my mistake? Regarding those errors, I have done extensive troubleshooting trying to resolve them and have been unable to. They occur on all of my SAS drives, but only my SAS drives. See thread here: Any advice would be appreciated. Since this post I've replaced the SAS card and have tried three different sets of cables with no different result.

About three weeks ago, I added some new drives to my system, and upgraded my parity drive to a 14TB drive. Since then everything has been functioning without error, but this morning my monthly parity check fired up. I'm three hours in, and I've got a scary number of sync errors that I've never seen before. I'm hoping this is just a result of missing a step with the drive additions. At this point, should I just cancel the scheduled parity check and force a correcting parity check? Or should I see this one through first? excelsior-diagnostics-20230915-0259.zip

Is there any available information on compatible HBA's and disks? Would reflashing the HBA make a difference? I don't want to blindly throw money at the problem more than I have been. Any recommendations you have I would be grateful for.

Got a whole string of these on disk4 this morning, during the mover operation. Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: attempting task abort!scmd(0x000000004ec89d0d), outstanding for 30198 ms & timeout 30000 ms Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: [sdb] tag#2642 CDB: opcode=0x8a 8a 00 00 00 00 01 33 d7 be 20 00 00 00 80 00 00 Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5000cca23c0d23b5), phy(3) Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: enclosure logical id(0x5000000080000000), slot(0) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: task abort: SUCCESS scmd(0x000000004ec89d0d) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: attempting task abort!scmd(0x00000000f21cd17a), outstanding for 30199 ms & timeout 30000 ms Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: [sdb] tag#2641 CDB: opcode=0x8a 8a 00 00 00 00 01 33 d7 ba 20 00 00 04 00 00 00 Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5000cca23c0d23b5), phy(3) Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: enclosure logical id(0x5000000080000000), slot(0) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: task abort: SUCCESS scmd(0x00000000f21cd17a) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: attempting task abort!scmd(0x00000000aafb219c), outstanding for 30207 ms & timeout 30000 ms Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: [sdb] tag#2637 CDB: opcode=0x8a 8a 00 00 00 00 01 33 d7 b1 a8 00 00 03 c8 00 00 Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5000cca23c0d23b5), phy(3) Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: enclosure logical id(0x5000000080000000), slot(0) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: task abort: SUCCESS scmd(0x00000000aafb219c) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: attempting task abort!scmd(0x0000000020542234), outstanding for 30202 ms & timeout 30000 ms Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: [sdb] tag#2635 CDB: opcode=0x8a 8a 00 00 00 00 01 33 d7 b8 d8 00 00 01 48 00 00 Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5000cca23c0d23b5), phy(3) Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: enclosure logical id(0x5000000080000000), slot(0) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: task abort: SUCCESS scmd(0x0000000020542234) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: attempting task abort!scmd(0x0000000061a5f6b1), outstanding for 30204 ms & timeout 30000 ms Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: [sdb] tag#2634 CDB: opcode=0x8a 8a 00 00 00 00 01 33 d7 b8 68 00 00 00 70 00 00 Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5000cca23c0d23b5), phy(3) Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: enclosure logical id(0x5000000080000000), slot(0) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: task abort: SUCCESS scmd(0x0000000061a5f6b1) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: attempting task abort!scmd(0x0000000035ec1153), outstanding for 30205 ms & timeout 30000 ms Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: [sdb] tag#2632 CDB: opcode=0x8a 8a 00 00 00 00 01 33 d7 b7 78 00 00 00 f0 00 00 Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5000cca23c0d23b5), phy(3) Mar 13 04:33:43 Excelsior kernel: scsi target7:0:0: enclosure logical id(0x5000000080000000), slot(0) Mar 13 04:33:43 Excelsior kernel: sd 7:0:0:0: task abort: SUCCESS scmd(0x0000000035ec1153) New diagnostics attached. excelsior-diagnostics-20230313-0434.zip

Thanks for replying @JorgeB I'm pretty sure I've seen the errors pop up on other drives. Do reboots clear the diagnostics? I've been troubleshooting this off and on for a few weeks and I believe I've seen them on disk2 and disk4. In any case, I've swapped cables entirely and had the same result.

Hello, I'm new to Unraid (from OMV) and have been setting up my server using a combination of SAS and SATA drives. I've noticed that when I try to transfer files to the array, or if there are other writes being made to the array, often I experience some pretty significant slowdown and the server becomes nearly unusable. Even web gui's are unresponsive. Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: attempting task abort!scmd(0x000000001174be4a), outstanding for 30227 ms & timeout 30000 ms Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: [sdc] tag#2852 CDB: opcode=0x88 88 00 00 00 00 00 9c 38 38 50 00 00 00 20 00 00 Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: handle(0x0009), sas_address(0x5000cca23c0d2c39), phy(0) Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: enclosure logical id(0x5000000080000000), slot(3) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: task abort: SUCCESS scmd(0x000000001174be4a) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: attempting task abort!scmd(0x0000000066da5839), outstanding for 30228 ms & timeout 30000 ms Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: [sdc] tag#2851 CDB: opcode=0x88 88 00 00 00 00 00 9c 38 38 90 00 00 00 20 00 00 Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: handle(0x0009), sas_address(0x5000cca23c0d2c39), phy(0) Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: enclosure logical id(0x5000000080000000), slot(3) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: task abort: SUCCESS scmd(0x0000000066da5839) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: attempting task abort!scmd(0x00000000aba86f6b), outstanding for 30229 ms & timeout 30000 ms Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: [sdc] tag#2850 CDB: opcode=0x88 88 00 00 00 00 00 9c 38 3e 50 00 00 00 20 00 00 Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: handle(0x0009), sas_address(0x5000cca23c0d2c39), phy(0) Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: enclosure logical id(0x5000000080000000), slot(3) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: task abort: SUCCESS scmd(0x00000000aba86f6b) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: attempting task abort!scmd(0x000000001fc00345), outstanding for 30230 ms & timeout 30000 ms Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: [sdc] tag#2844 CDB: opcode=0x88 88 00 00 00 00 00 9c 40 38 90 00 00 00 20 00 00 Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: handle(0x0009), sas_address(0x5000cca23c0d2c39), phy(0) Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: enclosure logical id(0x5000000080000000), slot(3) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: task abort: SUCCESS scmd(0x000000001fc00345) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: attempting task abort!scmd(0x00000000722cf1ea), outstanding for 30230 ms & timeout 30000 ms Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: [sdc] tag#2843 CDB: opcode=0x88 88 00 00 00 00 00 9c 40 38 50 00 00 00 20 00 00 Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: handle(0x0009), sas_address(0x5000cca23c0d2c39), phy(0) Mar 12 15:01:31 Excelsior kernel: scsi target7:0:1: enclosure logical id(0x5000000080000000), slot(3) Mar 12 15:01:31 Excelsior kernel: sd 7:0:1:0: task abort: SUCCESS scmd(0x00000000722cf1ea) My drive setup is: 8TB SATA (x2) - one is parity, one has data that still needs to be migrated to the array. That one is currently not part of the array. 6TB SAS (x3) - in the array 2TB SAS (x1) - in the array I've been troubleshooting this for a few weeks now, and I *believe* the issue is related to something going on with the SAS drives and the LSI card they're connected to. I bought the card pre-flashed. As far as I can tell, it's in IT mode and has the appropriate firmware 20.00.07.00-IT. I've tried connecting two different sets of SAS cables and I've tried connecting to both ports. I've also swapped out the power supply (needed to upgrade anyhow) and modded my power cable to remove the 3.3v wire. This error is occurring on any drive it's writing to at the time. I'm not entirely sure what to do from here. Any advice would be helpful. I've been looking for solutions on this error and I've seen everything from the drive spinning down to power issues to the LSI card being the problem. I'm not sure how to fix this and I've exhausted nearly every option I can think of. Diagnostics attached. Thank you in advance! excelsior-diagnostics-20230312-1450.zip