TheBawse

Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: task abort: SUCCESS scmd(0x000000004380e880) Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: attempting task abort!scmd(0x0000000051f87a4f), outstanding for 30516 ms & timeout 30000 ms Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: [sdu] tag#2860 CDB: opcode=0x88 88 00 00 00 00 00 01 96 80 f0 00 00 04 00 00 00 Jan 21 20:28:33 Tower kernel: scsi target10:0:10: handle(0x0014), sas_address(0x5001e67464526ff6), phy(22) Jan 21 20:28:33 Tower kernel: scsi target10:0:10: enclosure logical id(0x5001e67464526fff), slot(22) Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: No reference found at driver, assuming scmd(0x0000000051f87a4f) might have completed Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: task abort: SUCCESS scmd(0x0000000051f87a4f) Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: attempting task abort!scmd(0x000000001715f78a), outstanding for 30431 ms & timeout 30000 ms Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: [sdu] tag#2848 CDB: opcode=0x88 88 00 00 00 00 00 01 96 9c f0 00 00 04 00 00 00 Jan 21 20:28:33 Tower kernel: scsi target10:0:10: handle(0x0014), sas_address(0x5001e67464526ff6), phy(22) Jan 21 20:28:33 Tower kernel: scsi target10:0:10: enclosure logical id(0x5001e67464526fff), slot(22) Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: No reference found at driver, assuming scmd(0x000000001715f78a) might have completed Jan 21 20:28:33 Tower kernel: sd 10:0:10:0: task abort: SUCCESS scmd(0x000000001715f78a) Yeah...No idea what it means though

I'll check again. Didn't see any first time.

Thanks. Did you see disk errors in the diag file? I'll look into the firmware on my HBAs. I assumed I had the lastest.

PSU is new and all cables were replaced a few months ago with startech SAS to SATA cables.

No, I turned off docker and want doing any other work.

I just upgraded a drive to something larger and upon starting my rebuild I noticed my speeds are really slow. I usually am between 75-100mb/s and I haven't gone above 25mb/s. I took a look through my logs but I didn't see anything that could explain the bottleneck. I have attached my diagnostics if someone could take a look and give me a second opinion it would be much appreciated. tower-diagnostics-20230121-2028.zip

Thanks. I had a few deskstars as well. They were very good.

Soon to be running out of space on my NAS. Currently have a mix of 4 and 6TB WD Black drives. My local computer chain near me has the 8TB WD Ultrastars on sale and they come out cheaper than getting a 6TB black at regular price. Wondering if anyone has had good luck with them? Thanks

Hi, Nope. I continued searching for answers on the forum but to no avail. I eventually gave up and haven't looked at giving another shot since.

Thanks for this. Up and running now. I looked but didn't see if there was a unraid team # to join?

Powered on my machine and tried to search through the community applications listings and was greeted with this error msg after awhile of it loading. Highlights in my LOG: Feb 11 22:43:57 Tower wsdd[2107]: udp_send: Failed to send udp packet with Network is unreachable Feb 11 22:43:57 Tower wsdd[2107]: Failed to send bye with Network is unreachable

No. It's only plugged into the unraid server. Can't I merge both custom networks through docker? I would atleast want the WebUI run through my main network 192.168.0.X and the camera network available only to that docker container.

So I'm trying to setup an IP camera system using the Shinobi docker app. I want my IP cameras though a second network to be isolated from my main network that has my home devices and access to the internet. I found a video from a youtuber called "spaceinvaderone" where he went through setting up his docker on a custom network to use either a separate VLAN or a second network using another NIC. I went with the latter as I have a spare POE unmanaged switch which I planned to use on my POE IP cameras. I have the second NIC installed and setup as Eth1 or Br1 in docker as a custom network. I have set my shinobi docker container to use Br1. Right now Eth1 has an old router plugged in and is set to use the 192.168.5.0 range along with having the unmanaged POE switch plugged in. The docker container is given its IP address, and the "Host access to custom IPs" has been enabled. The problem I'm having is when after I install the docker container and go through the setup. When I open the WebUI in the browser it always times out and won't connect to the app login screen. When in bridge or host I can access Shinobi as I do with my other installed docker (Plex, Krusader, Cadvisor). What am I doing wrong here?

Has anyone managed to get the two NIC's option spaceinvader referenced instead of the VLAN to work properly? I followed his video and couldn't get it to work. I have two NIC's (eth0 or Br0 and eth1 or Br1) and I have set docker to use the Br1 custom network I created. When I open the WebUI for Shinobi in the browser it times out and won't connect to the IP. I wanted to have my cameras on a separate network isolated from my main that has my home devices and internet access as was mentioned in the YT video. I currently have eth1 connected to an old router set to the 192.168.5.0 range and from there a POE unmanaged switch powering my IP cameras.

bump