Docker Images Failing to Start; Rebuild Image Not Working

[Milhouz]

So I had to power down unRAID last night. 

 

Powered it up this morning some Dockers wouldn't start due to permissions from what I read on there forums here it said to delete the docker.img in the docker services tab but now trying to start it up won't let me. Keeps just saying stopped and going to the Docker Tab just says it's not started. Any assitance would be greatly appreciated!

 

I am attaching my diagnostics zip for some assistance still relatively new.

grid-02-diagnostics-20220203-1729.zip

[Squid]

@JorgeB would be the man to ask, but it *appears* to me that your nvme is locked down in a security protection, and this happens right away during the detection phase of boot up

Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 27 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 520 op 0x0:(READ) flags 0x80700 phys_seg 58 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2312 op 0x0:(READ) flags 0x80700 phys_seg 29 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2568 op 0x0:(READ) flags 0x80700 phys_seg 56 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2000408064 op 0x0:(READ) flags 0x80700 phys_seg 48 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2000408576 op 0x0:(READ) flags 0x80700 phys_seg 19 prio class 0

 

 

Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test

 

[Milhouz]

Following up here too having this issue now when trying to access my VM's

 

[Milhouz]

Just now, Squid said:

@JorgeB would be the man to ask, but it *appears* to me that your nvme is locked down in a security protection, and this happens right away during the detection phase of boot up

Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 27 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 520 op 0x0:(READ) flags 0x80700 phys_seg 58 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2312 op 0x0:(READ) flags 0x80700 phys_seg 29 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2568 op 0x0:(READ) flags 0x80700 phys_seg 56 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2000408064 op 0x0:(READ) flags 0x80700 phys_seg 48 prio class 0
Feb  3 16:48:19 GRID-02 kernel: blk_update_request: protection error, dev nvme0n1, sector 2000408576 op 0x0:(READ) flags 0x80700 phys_seg 19 prio class 0

 

 

Any idea on the fix for this? Or should I wait for @JorgeB?

[Milhouz]

 

Definitely looks like it's throwing all kinds of those flags. 

 

What's crazy to me is this...

 

 

Filesystem      Size  Used Avail Use% Mounted on

/dev/nvme0n1p1  954G  101G  853G  11% /mnt/cache

Edited February 3, 2022 by Milhouz

[Milhouz]

Tried a reboot looking good now but still looking to see what info @JorgeB says if i need to start preparing for the worst.

[ChatNoir]

New diagnostics after the reboot might be useful.

[JorgeB]

9 hours ago, Squid said:

but it *appears* to me that your nvme is locked down in a security protection

I agree, but no idea how it happened or if it can be fixed, since I've never seen this before, another possibly is the device just went bad.