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

Thanks Craftsman. I finally found time to try the settings in your post. I still cannot get it to work. This issue I'm now having is when I start the docker and click to open the WebUI. The browser times out on the set IP address (192.168.5.3:8080) and the shinobi login won't come up.

Hi, I don't want my dockers to be run through eth1, only specifically the Shinobi docker. I have other dockers like PLEX that are accessible by several media devices in my home through eth0 that also need internet access. I wanted a new separate network (eth1) through a 2nd NIC just for the IP cameras and have them isolated from all my devices and the internet of eth0. I only wanted Shinobi to have access to eth1 through unraid and I would in turn block all devices of eth1 from seeing any network past unraid by blocking IP's in the Shinobi settings. Sorry if I'm not making sense. I've never been great with custom network setups but I hope this diagram I made might clarify what my end goal is. Thanks for your help.

So I came across a video back in december from a YTuber name SpaceInvader One who did a video about using unraid as an IP camera system. This particular video was about setting up the Shinobi IP camera app in a docker container to be configured either using a VLAN on a managed switch or through a 2nd NIC on a separate network from the main LAN with an un-managed switch. I went with the latter as I already had a spare NIC and old un-managed POE switch. I popped in my card and is now eth1 in unraid. As well as the switch and a test IP camera. Unfortunately from there I've spent hours fiddling around with no success in getting Shinobi to work as it did in the YT video. The video itself focuses more on setting up a VLAN instead of using a 2nd NIC. This setup was appealing to me as I liked the fact of having the non-name cameras not having direct access to my main LAN or the internet. The problem I'm having is when after I install the docker container and go through the setup. When I to open the WebUI, the browser won't connect to the IP i've set for eth1 / Br1. 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?

Not sure if this is the correct thread to post in. Ever since updating to V6.7 my Plex container has stopped working. The issue I'm having is when attempting to login through the browser I'm getting "This site can’t be reached". I'm going through the IP http://192.168.0.130:32400/web/index.html. It has been working fine for over a year since I first installed until now.

Running low on space I added a new drive to my array. I was using the server most of the day without issue until I added a new drive. At the start of the clearing I got a warning that one of my drives showed rear errors. In the main menu there is a red "X" and when I hover over the icon it shows the message "Device is disabled, Device emulated". I downloaded the SMART report on the drive it shows: I also brought up the main system log and it listed this: So this drive is cooked?

So I'm attempting to flash an H310 PERC card to IT mode for the second time. I already have a 310 in my unraid server that I flashed without issue and went flawlessly. This time however not so much. I bought another card off ebay to add more drives to my NAS. popped the card in my spare desktop to flash and upon boot up the cards BIOS showed up on screen and everything seemed normal indicating the card was working properly with its RAID firmware. I followed this How-To blog post when I flashed my first card and did the same this time around: https://techmattr.wordpress.com/2016/04/11/updated-sas-hba-crossflashing-or-flashing-to-it-mode-dell-perc-h200-and-h310/ What I did so far... Created a bootable USB key with Freedos using Rufus + copied over the downloaded files from the website. Retrieved my SAS# through the cmd line megacli.exe -AdpAllInfo -aAll -page 20 Prepared the card to have the new firmware written to it megarec.exe -writesbr 0 sbrempty.bin This was a success, unlike my first card where I got a failure and had to proceed to using "megarec.exe -cleanflash 0" Rebooted my PC, booted into FREEDOS and then started sas2flsh to write the DELL 6GBPSAS.fw flash file using cmd line sas2flsh.exe -o -f 6GBPSAS.fw The LSI flash utility started but as you can see in the screen shot it just hangs there. It will remain that way until I manually restart the system. I rebooted and tried many times and the outcome was the same. I changed computers as well as the sas2flsh.exe file to version P19 on my usb key and tried again. This time I got an error message while attempting to write the flash file. Not sure whats happening here. I'm at a loss right now as to why I can't get this to work. Anyone else run into these issues? Thanks for your time!

So I'm attempting to flash an H310 PERC card to IT mode for the second time. I already have a 310 in my unraid server that I flashed without issue and went flawlessly. This time however not so much. I bought another card off ebay to add more drives to my NAS. popped the card in my spare desktop to flash and upon boot up the cards BIOS showed up on screen and everything seemed normal indicating the card was working properly with its RAID firmware. I followed this How-To blog post when I flashed my first card and did the same this time around: https://techmattr.wordpress.com/2016/04/11/updated-sas-hba-crossflashing-or-flashing-to-it-mode-dell-perc-h200-and-h310/ What I did so far... Created a bootable USB key with Freedos using Rufus + copied over the downloaded files from the website. Retrieved my SAS# through the cmd line megacli.exe -AdpAllInfo -aAll -page 20 Prepared the card to have the new firmware written to it megarec.exe -writesbr 0 sbrempty.bin This was a success, unlike my first card where I got a failure and had to proceed to using "megarec.exe -cleanflash 0" scream 4 knife Rebooted my PC, booted into FREEDOS and then started sas2flsh to write the DELL 6GBPSAS.fw flash file using cmd line sas2flsh.exe -o -f 6GBPSAS.fw scream 4 knife The LSI flash utility started but as you can see in the screen shot it just hangs there. It will remain that way until I manually restart the system. I rebooted and tried many times and the outcome was the same. I changed computers as well as the sas2flsh.exe file to version P19 on my usb key and tried again. This time I got an error message while attempting to write the flash file. scream 4 knife Not sure whats happening here. I'm at a loss right now as to why I can't get this to work. Anyone else run into these issues? Thanks for your time!

Thanks. I just started using it. The issue i'm having is even when I attempt to manually add metadata through searching on the various databases available it won't apply it to the media in question. e.g: simpsons. I search on tvdb...find it...tell plex to apply it...and no thumbnails or episode title are applied. Weird thing is for movies there are no metedata issues plex found most of them and added thumbnails and titles, and for the ones it couldn't find i was able to apply manually. its just tv shows that won't work. Another question. If I wanted to start again from scratch. How would I go about removing plexserver along with all of the files and docker container off the share its using and start over? 100% clean re-install Thanks

Has anyone ever experienced Plex not loading the proper Metadata for certain scanned playlists? My plex server is setup and all of my Movie playlists have been properly scanned and the thumbnails loaded and applied, but in my TV playlist only a quarter have been properly scanner and the rest are blank and even when doing manually not proper title or thumbnails are applied.