Adrian
-
Posts
193 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Adrian
-
-
Can't move the controller, there aren't any other slots where they work. I'll go over the manual and see if I can find this info.
-
ok, sooo I haven't exactly eliminated the issue. It's still keeps coming up.
I ran "cat /proc/interrupts" before int16 got disabled and this is what it listed.
IO-APIC 16-fasteoi ehci_hcd:usb1, mvsas
So I'm thinking, maybe I need to disable that USB and find another one to boot off of? Would I need to disable it in the BIOS or would simply not plugging anything in be enough?
-
IRQ16 is being disabled crippling one or both your SAS2LP controllers.
Reboot and check what IRQ they are using by running:
lspci -vv -d 1b4b:*
Try updating your bios/firmaware , if just one is on IRQ 16 try moving it to another slot if available.
I just wanted to let you know that I was able to eliminate the IRQ 16 issue by removing the secondary Intel NIC. It took a bit, but I finally got the on-board NIC working. This MB really sucks, but at least I've bought me some time before I have to drop almost a grand on a replacement. So far I haven't had this crazy issue which would happen at least once or twice a week. I've written to drives that used to always cause the issue and so far everything is running really nice.
Thank you all!
Adrian
-
So I found some posts that describe my issue with talks about a bug related Sandybridge motherboards and additional ethernet cards (exactly what I have)
https://bugzilla.kernel.org/show_bug.cgi?id=38632
The last post mentions running a command to get the IRQ working again, but I'm don't know enough about linux to modify this to try on my server.
I tried to run "rmmod e100;modprobe e100;sleep 0.1;ifconfig eth2 up" after error - it helped. IRQ works again:I'm probably going to try again to get the server working without the additional ethernet card.
-
I would definitely love a modification to the parity check behavior to address issues with parity checks that run 1+ days. Having them throttle down or paused when data needs to be accessed would be great. Heck, mine right now shows an 11 day estimation to complete lol (that's a whole other issue). Ideally it could pause/restart at will, or based on a schedule, or automatically detect when to pause/restart.
-
Well, I removed one of the SATA cards that had 4 drives and moved them to the onboard sata. So now I'm just using the onboard and the 2 SAS2LP controllers. Once I did that that weird issue with the large white blinking cursor went away and now it gets to the unraid booting faster. It's running a parity check now. So I'll see what happens with this new setup. Right now I'd be happy for it to work for another month or so to give me some time to research doing a major upgrade. Ideally I'd like to run off a Supermicro MB without any of the limitations with the PCI Express lanes that this Gigabyte motherboard has.
-
Possibly related: You appear to have a bunch of nearly full ReiserFS drives.
If for example split levels cause writes to occur on one of those drives, the writes will no doubt be unbearably slow...
Well, I have all my shares set to most-free so I'm not really sure how or why it would ever try to write to any of the nearly full drives. I guess if I ever see slow writes, I would need to look at figure out which drive it's writing too and see what it's free space is.
-
IRQ16 is being disabled crippling one or both your SAS2LP controllers.
Reboot and check what IRQ they are using by running:
lspci -vv -d 1b4b:*
Try updating your bios/firmaware , if just one is on IRQ 16 try moving it to another slot if available.
88SE9485 is using IRQ 16
88SE9485 is using IRQ 17
88SE9172 is using IRQ 32
I'll look into updating the MB BIOS if there are any updates available. I'll have to see if I have any other slots available.
One thing I do notice is that when I start the computer I can't access the BIOS. I think I can if I remove one of the SAS2LP cards. Also, after the SATA cards each post, I see this really large blinking line. Almost like a really big cursor dash. I'll open it up today and document exactly how I have the cards and troubleshoot a bit more with their slots.
Thank you so much!
Adrian
-
Ok, so part of my reoccurring issue just started again where I can't copy any files. It starts writing and then it times out and unraid becomes unresponsive for several minutes. I finally got it to create the diagnostic file.
Basically the only way for me to fix it is to reboot the server.
Thanks,
Adrian
-
I keep running into this issue with unraid. File transfers get really slow through both windows explorer and internally in docker apps like sick beard. This last time it took over an hour to move 3 gigs from a standalone SSD drive to the array. It gets unbearable and then I have to stop sick beard by stopping it in the docker UI. Then I have to stop the array which takes a ridiculous amount of time (about 5 minutes) and then finally I can restart the server. When it comes up (takes several minutes after ping starts to respond), everything seems to be back to normal.
Any ideas what's going on? Anyone else running into this issue? Are there any plugins/tools that I can run while this is happening to see what's going on? What drive it's writing to, what write speeds is it getting, etc. Is there a way to run a performance test for network and disk writes/reads for each drive? If it's a hardware issue, I don't mind upgrading. I just have no idea where to start to even see where things are crapping out.
Thank you,
Adrian
Unraid 6.2.4
-
I've encountered the same issue on my laptop (Windows 8.1) and haven't been able to resolve it. I've even cleared all the saved credentials and still nothing. I don't and have never had any users configured in unraid. You can actually enter anything for the credentials and it will continue on.
-
When you added the container (assuming that you're using 6.1.9 as its easier to do this than under 6.2+) you inadvertently changed the port. Just hit the icon under the docker tab and edit the container.How would have I done that? And how do I fix that?
The docker screen for this container should look something like this (virgin install of Needo's sickrage for you to test FCP with it, with bogus pathnames however)
ok, yea I'm on 6.2+ and I didn't see how I could even edit it so I wasn't sure how I might have changed it in the past, but if the previous version allowed editing, then I can see how I may have changed it by accident as it was probably my first docker app and I wasn't familiar with how all that work.
I went ahead and just removed it and added it again and it looks good now.
Thanks,
Adrian
-
Odds on you changed the Container port of the app when you wanted to only change the Host port. Pretty much there is zero reason to ever change the container port, and doing so will generally break the app, hence the error.I just installed this today and had it run its scan.
It's reporting the following error:
Docker Application SickRage, Container Port 8081 not found or changed on installed application
The docker image that I have installed is needo/sickrage.
How would have I done that? And how do I fix that?
-
I just installed this today and had it run its scan.
It's reporting the following error:
Docker Application SickRage, Container Port 8081 not found or changed on installed application
The docker image that I have installed is needo/sickrage.
-
Try getting some diagnostics after this has occurred, but before a reboot.
Sent from my LG-H815 using Tapatalk
I'll keep trying, but even that has failed. Hopefully one day I'll be able to collect some useful information.
-
But on your one post regarding issues, it seems like you just need to clear the Windows Credentials via the credential manager and you're back in business
This was just an annoying issue which only occurs on my laptop. I just tried clearing the windows credentials via the credential manager (even rebooted after) and Windows is still asking for credentials. Any other ideas on this?
The big issue that I've been having is performance degrading badly over time. Seems after about a week, I have to reboot the server. Write throughput just becomes ridiculously slow. Last night a 1.2GB file took about 30 minutes to move from the cache drive. I ended up killing the process, rebooting and then it moved it a fraction of the time.
Also now, sometimes when I'm trying to move a large file to the server, and it gets really bad I can even access the GUI.
-
So I'm done with 6.2.1. I've encountered too many issues and I really just want to go back to 6.1.9. It wasn't perfect, but it wasn't nowhere as unstable as 6.2.1. Is it easy to go back? I know that a couple plugins were upgraded for 6.2.x, so I'm assuming I'll probably have to remove them and then add them back?
Thank you,
Adrian
-
Are all of your shares set to Public for SMB?I'm encountering odd network related issues. This release is defiantly not "stable".
I can copy files from a Windows 2008 server into Unraid, but I can no longer write from my Windows 8.1 Pro desktop.
My laptop (on the same network) running Windows 8.1 Pro can write, but it's prompted for a login when I try to access a share on the Unraid server. I don't have any users configured or require. In fact I can type anything for the username/password and then it lets me in.
I'm currently having to copy from my desktop to this windows server so I can then copy from the windows server to unraid.
I don't have any VMS, just a couple docker apps.
Should I just go back to 6.1.9?
Yea, my server isn't locked down, only root user, everything is public. Like I said, I don't have any users configured, never have. Everything worked fine from any computer before the update. I either can't write at all, or I get prompted for a user (which I can type anything I want and it continues normally), or I don't get prompted at all and I can write. All depends from which computer I do it from.
-
I'm encountering odd network related issues. This release is defiantly not "stable".
I can copy files from a Windows 2008 server into Unraid, but I can no longer write from my Windows 8.1 Pro desktop.
My laptop (on the same network) running Windows 8.1 Pro can write, but it's prompted for a login when I try to access a share on the Unraid server. I don't have any users configured or require. In fact I can type anything for the username/password and then it lets me in.
I'm currently having to copy from my desktop to this windows server so I can then copy from the windows server to unraid.
I don't have any VMS, just a couple docker apps.
Should I just go back to 6.1.9?
-
So I had an issue with 3 drives that never spun down and I tracked it down to some docker apps. Apparently all my docker apps were setup with their config folder being set under /user so their data got spread out across 3 drives. How do I get the appdata folder moved to my cache drive? It's apparently not as simple as stopping the apps, updating their settings and moving the folder. I seem to keep running into file locks or something that prevents me from moving all the files and folders. I tried with the apps all stopped and even with docker disabled completely.
*** Restarted unraid and my computer and it looks like I was able to resolve the issue. I'll continue monitoring it to make sure.
Thank you,
Adrian
-
I just tried to install this and nothing happens when I click the Create button. A friend of mine tried on his server as well and he get's the same issue. I filled in the Host paths for /config and /data and set the Host port, but when I click Create nothing happens in IE. I tried Firefox and I do see a popup that says "Please fill out this field", but it's pointing to the top left corner of my browser, not any specific field in the form.
Unraid 6.1.3
-
I just upgraded as well from 5.0 and I also had to come say, WOW. Looks amazing and responds so much faster. Great work!
-
The syslog looks clean as far as drive errors. There is a ton of avahi errors which are network related. Not sure about the cause however.
Are you trying to copy directly to drive 13 or are you using user shares? What errors are showing up
Yes, I was trying to copy directly to drive 13. The errors reported by both Teracopy and DirectoryOpus don't really say much other than there was a failure. I could try contacting DOpus support and they may be able to tell me how to enable/access logs that might have more information.
-
Unraid's save log mechanism creates a tgz archive, yet tgz files can't be attached to forum posts requiring it to either be attached uncompressed or re-compressing it using something like zip, which is allowed.
Thanks,
Adrian
Reoccuring issue
in General Support
Posted · Edited by Adrian
The motherboard is a Gigabyte GA-Z77X-UD3H
Link to manual: http://www.gigabyte.com/Motherboard/GA-Z77X-UD3H-rev-10#support-manual
I just read through it and I don't think I see any mention of which IRQ's are shared between slots and USB controllers. If you can, take a look and see if you find it or maybe you can see what options I might have available.
I see some options regarding USB on page 52. xHCI Pre-Boot, xHCI Mode, HS Port #1~#4, xHCI Streams. Not sure if those settings could help deal with this issue.
Thank you,
Adrian