segaboy

That was it. I usually access this share via SMB, but this is the first time using it over NFS. I exported the share and it mount right away. Thanks!

Hi. I just setup a second Unraid machine to do some other types of tasks. I am trying to mount a share from one Unraid server into another using the Unassigned Devices plugin. I've tried NFS and SMB and neither will mount. I have also tried manually creating a mountpoint for the share. When I click 'Mount' in the unassigned devices table, it fails to mount. Where are the logs for unassigned devices? khan-diagnostics-20211014-1059.zip

Hi. I just setup a second Unraid machine to do some other types of tasks. I am trying to mount a share from one Unraid server into another using the Unassigned Devices plugin. I've tried NFS and SMB and neither will mount. Shares are exported, working (been using them for years), and public. I have also tried manually creating a mountpoint for the share. When I click 'Mount' in the unassigned devices table, it fails to mount. Where are the logs for unassigned devices? khan-diagnostics-20211014-1059.zip

Turns out this old motherboard doesn't support 4 drives while a certain PCI slot is occupied. I popped in an HBA and I'm good now. Thank you.

Are these the errors you are referring to? Oct 13 16:02:50 Tower kernel: ata3.00: status: { DRDY ERR } Oct 13 16:02:50 Tower kernel: ata3.00: error: { UNC } Oct 13 16:02:50 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 13 16:02:50 Tower kernel: ata3.00: cmd 60/80:70:e0:00:02/00:00:00:00:00/40 tag 14 ncq dma 65536 in Oct 13 16:02:50 Tower kernel: res 41/40:00:00:00:00/00:00:00:00:00/00 Emask 0x9 (media error) Oct 13 16:02:50 Tower kernel: ata3.00: status: { DRDY ERR } Oct 13 16:02:50 Tower kernel: ata3.00: error: { UNC } Oct 13 16:02:50 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 13 16:02:50 Tower kernel: ata3.00: cmd 60/00:78:60:01:02/02:00:00:00:00/40 tag 15 ncq dma 262144 in Oct 13 16:02:50 Tower kernel: res 41/40:00:00:00:00/00:00:00:00:00/00 Emask 0x9 (media error) May be power related... There is a molex to 2x SATA splitter right there. I'll take a look.

Error from logs: level=error msg="Not continuing with pull after error: context canceled" I am setting up a second unraid server for other tasks. I have tried to install several Docker containers and they all peg my CPU and continue trying to pull images, though they fail. This machine has a trial license if that makes a difference. Here is my docker log: time="2021-10-13T16:12:55.349292351-07:00" level=error msg="Not continuing with pull after error: context canceled" time="2021-10-13T16:29:36.120515758-07:00" level=info msg="starting signal loop" namespace=moby path=/var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/8d32949115096e71e8030841c830ef910050cda10e79cddf2e070d9f2d07f9b7 pid=13248 time="2021-10-13T16:33:35.068739519-07:00" level=info msg="starting signal loop" namespace=moby path=/var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/8d32949115096e71e8030841c830ef910050cda10e79cddf2e070d9f2d07f9b7 pid=14616 time="2021-10-13T17:52:24.925776953-07:00" level=info msg="starting signal loop" namespace=moby path=/var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/8d32949115096e71e8030841c830ef910050cda10e79cddf2e070d9f2d07f9b7 pid=2449 time="2021-10-13T17:58:55.046727555-07:00" level=info msg="starting signal loop" namespace=moby path=/var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/2404c075239aaa43f790909096abd0f08cafa4a8d685581b96e2a1931236dc6a pid=4897 time="2021-10-13T18:01:44.088307184-07:00" level=info msg="starting signal loop" namespace=moby path=/var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/2404c075239aaa43f790909096abd0f08cafa4a8d685581b96e2a1931236dc6a pid=5823 time="2021-10-14T05:04:32.877027411-07:00" level=error msg="(*service).Write failed" error="rpc error: code = FailedPrecondition desc = unexpected commit digest sha256:241e1b92a1a8798742c47f24fa586e034a5b85c5393cb1021dfae6dad571ac7c, expected sha256:9cc5f3d41b09b915a2024eef870c23f219d6036d9bc01aa03cab6ce3cbf6a08a: failed precondition" expected="sha256:9cc5f3d41b09b915a2024eef870c23f219d6036d9bc01aa03cab6ce3cbf6a08a" ref="unknown-sha256:9cc5f3d41b09b915a2024eef870c23f219d6036d9bc01aa03cab6ce3cbf6a08a" total=59186 time="2021-10-14T05:05:47.796399971-07:00" level=error msg="Not continuing with pull after error: context canceled" time="2021-10-14T05:08:16.007192591-07:00" level=error msg="(*service).Write failed" error="rpc error: code = FailedPrecondition desc = unexpected commit digest sha256:94fcf6c5113065833307dae2bd6829d604704d68601e16f0ef5e8ed90f768ff0, expected sha256:9cc5f3d41b09b915a2024eef870c23f219d6036d9bc01aa03cab6ce3cbf6a08a: failed precondition" expected="sha256:9cc5f3d41b09b915a2024eef870c23f219d6036d9bc01aa03cab6ce3cbf6a08a" ref="unknown-sha256:9cc5f3d41b09b915a2024eef870c23f219d6036d9bc01aa03cab6ce3cbf6a08a" total=59186 Attached are the diagnostics. tower-diagnostics-20211014-0815.zip