[Docker Execution Error: Error Code 403]

Ever since I installed a Pi-hole docker I have had times where some of the dockers stop and I get this error.

 

When trying to restart I get:  Docker Execution Error: Error Code 403

 

A reboot solves it for about 10 days then the same problem.

 

TIA

media-diagnostics-20240506-1929.zip

[New disk is instantly getting disabled for read errors]

Bought a ST18000NM000J to replace it with and it's working fine.  I am going to pull the MDD drive and try Seatools on it in my desktop.

 

[New disk is instantly getting disabled for read errors]

Because I suspected there was a problem with the entire bay of the backplane.
 

I agree that it doesn't seem consistant with the 3.3V potential issue as it ran preclear fine.

[New disk is instantly getting disabled for read errors]

Ugh, so after further troubleshooting I think I discovered the issue.

 

I have a SuperMicro server with a BPN-SAS2-846EL1 backplane and that drive is one of these:

https://www.amazon.com/MDD-MDD18TSATA25672E-256MB-Internal-Enterprise/dp/B0C22DF8HJ

 

In the reviews there is this comment:

 

Quote

One major thing to note is that these are SATA version 3.3, and the most important change to SATA 3.3 is that they changed the power connector pinout. Pins 1 through 3 used to all be a +3.3V power input, and almost all power supplies supply that 3.3v through the SATA connector to all 3 pins (and most drives don't need 3.3V anyway), now pin 3 on the power connector is actually PWDIS (Power Disable) and, if 3.3V is supplies to that pin, the drive will power down (or in the case of it always being supplied, never power on in the first place). You will want to state on your listing that these are SATA revision/version 3.3V and may not power on with older power supplies that are not SATA v3.3 compatible without modification. SOME new power supplies have cables that just don't have a 3.3V power line, but all 12 of my power supplies all had it, with 2 power supplies being under 2 months old.

 

Googling doesn't tell me one way or another whether that backplane supports 3.3, but I am guessing it's old enough that it doesn't.

 

[New disk is instantly getting disabled for read errors]

Added, thanks!

 

[New disk is instantly getting disabled for read errors]

I just added a new drive after running a preclear cycle on it, which completed with problem.  Now, as soon as it got added to the array it got disabled.

 

 

Ideas?

media-smart-20230813-1541.zip

media-diagnostics-20230813-1600.zip

[Out of disk space?]

I am getting errors that the disk is full when I try copying files into the array via windows.

 

I assume it has something to do with the drive where the directory was originally created.

 

Also, Radarr and Sonarr stopped importing files also.

Anyway around this other than more drive space?

 

 

[[Support] binhex - Radarr]

I am guessing this is a pretty simple problem and I don't know why it has just started, but....

 

Both Radarr and Sonarr are not importing downloaded content because they think there isn't enough disk space.

 

This is what is actually left:

 

Any suggestions?

 

Thanks!