Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

opentoe

Members
  • Joined

  • Last visited

Everything posted by opentoe

  1. Running 6.8.0. Getting these odd lines in my logs. Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cad Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cb8 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cb8 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cf4 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cf4 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cf6 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cf6 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cf5 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cf5 Dec 11 01:08:43 SUN kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Dec 11 01:08:43 SUN kernel: EDAC sbridge: Couldn't find mci handler Dec 11 01:08:43 SUN kernel: EDAC sbridge: Failed to register device with error -19. Dec 11 01:08:43 SUN kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3ca0 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3ca0 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3ca8 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3ca8 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3c71 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3c71 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3caa Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3caa Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cab Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cab Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cac Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cac Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cad Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cad Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cb8 Dec 11 01:08:43 SUN kernel: EDAC sbridge: Seeking for: PCI ID 8086:3cb8 sun-diagnostics-20191211-0114.zip
  2. I have lots of these lines in my syslog. I checked it out by doing these commands I found on the web. It is pointing to my Intel processor for some reason. The user that said he fixed this by doing this," Needed to patch the sb_edac". Maybe this will help. [ 40.151752] EDAC sbridge: Seeking for: PCI ID 8086:3ca0 root@SUN:~# lspci -n | grep 8086:3ca0 ff:0e.0 0880: 8086:3ca0 (rev 07) root@SUN:~# lspci -k -s ff:0e.0 ff:0e.0 System peripheral: Intel Corporation Xeon E5/Core i7 Processor Home Agent (rev 07) Subsystem: ASUSTeK Computer Inc. Xeon E5/Core i7 Processor Home Agent root@SUN:~# ^C root@SUN:~#
  3. Using RC7 and getting this error on load up. Also, I'm trying to use VNC Viewer to connect to the remote desktop. I put in "192.168.1.254:6080" and it will timeout. You are able to use the VNC Viewer on this, right?
  4. I got it installed using the directions in the first post. It worked ok. All test speeds were right on mark. Thanks.
  5. Has the normal installation of this been fixed or you still need to manually install?
  6. I do believe there is an inherent bug somewhere that possibly does not like my hardware. I've been using unraid since the beginning of V5 or even before that. When V6 first came out things were good. After a couple of revisions is when these copying issues started. I always would get 100MB/sec on copy speeds using a Windows workstation on the network and even faster using the terminal and midnight commander. My server box is a simple norco 4224 box. I have a 1000 watt power supply which has been replaced. The cables that go from the backplane to the controller cards have been replaced with new ones. I've changed the memory out temporarily with a friend's memory. I've disabled the on-board NIC and purchased an Intel add on card. I've re-seated the processor and ran extensive tests on the processor itself. The mainboard is an Asus X79 that has tried different bioses. I've tried different controllers. Dell PERC 310's and/or the SuperMicro SAS2LP-MV8. I have like 4 of each of these cards. Tried them together and in different combinations. If I did not have so much data, I'd try to go back to V5 and see what performance I would get. Since the copying of files issues happens via the terminal this eliminates pretty much anything outside the server box. I've even taken the mainboard out of the server box and installed it in a small desktop case and threw Windows 10 on it. Problem free. And while I had Windows 10 on it, I ran several heavy duty burn-in test programs just for the heck of it. Flawless. Reinstalled the board back into the 4224 box, booted up just fine. I've also moved my pro key to a new USB flash stick that was vanilla. No plugins installed, plain vanilla. Tried changing some bios settings, but really not that many. I basically turned off all VM related stuff and tried different settings with that. In a nutshell when copying files the system would start to copy just fine around 80-100MB/sec. Then eventually slowly drop down to 0MB/sec and the copy would literally stop completely for about 30-40 seconds. So if I'm copying a large amount of data it could take days to do this. ( Yes, the parity drive has been replaced ) . Takes about 2.5 minutes to copy a 6GB file when it would take seconds before. I don't even attempt to copy amounts of data anymore and I also think this issue is affecting my system as a whole. Specially when watching a movie. During the entire movie it would freeze ( which is where it stops ) then picks up again and the movie catches up again with the player. This happens with my Dune players AND my Roku players. Another oddity I did a parity sync which took 2 hours ( great! ) but the average speed indicates 1.1GB/sec. Is that even possible? Attached a screen shot of that and diagnostics. I'm pretty much lost from here. I did attach a terminal copy that looks very weird, but you'll get the gist of what is happening once you see it. It is just one 6GB file being copied. Any suggestions or recommendations is highly appreciated. Thanks 6gb copy.mp4 sun-diagnostics-20190609-0516.zip
  7. I am using NF-S12A PWM for my three 120mm fans. I could still make the next jump up to the next one since the server is more isolated now and can use more faster louder fans, but I have good air flow where it is now and have had no issues.
  8. Best fans ever made in my opinion or Noctua. They also make the best processor heatsinks. Build quality and warranty are great. I changed all my 4224 fans with Noctua models. No need to get the industrial models, even though they still are less loud then the stock ones. How many drives do you have in there and what hardware are you using?
  9. Damn, so many options and settings all over I miss them easily. Thanks for pointing that out. After I work on my media player read speed tests for a bit I'll make that change and be done with it. Thanks!
  10. I find these in my syslog: Mar 12 18:37:46 SUN kernel: mdcmd (53): set md_write_method 1 Mar 12 18:37:51 SUN kernel: mdcmd (54): set md_write_method 0 Mar 12 18:47:09 SUN kernel: mdcmd (55): set md_write_method 1 Mar 12 18:47:14 SUN kernel: mdcmd (56): set md_write_method 0 I actually had this written in my GO file. md_write_method 1. This I assume turns on turbo mode, right? I did REM out that statement when I installed this plugin, but may just uninstall the plugin and put back the command since I never spin down any of my drives....ever. What would be my best most efficient method to keep turbo mode turned on? Keep this command "set md_write_method 1" in my GO file? And that would keep turbo mode on all the time, correct? Also the plugin is indicating I have 2 spun down drives, but all my drives spun up and none of them never spin down so I would rather uninstall the utility but want to make sure I have the correct syntax and placement of the command in the GO file. Thanks.
  11. Why not search for it manually and see what the list looks like from your indexers? I have to do that all the time to see if I can find missing shows. The more indexers you have, the better off you’ll be. How many indexers are you using?
  12. Ah, ok, now I got it. I was not going all the way back up and hitting the check mark. Thanks!
  13. When I scroll all the way to the bottom of where the listing of TV Shows are, there just two options. OK and CLOSE. If I click OK, nothing happens. I want to import them all, as you said. So I'm in the folder itself where all the shows are, scroll to the bottom and then click OK. I would think it would start to import them at this point. I think this is why I always ran Sonarr and SabNZB on a Windows desktop, which was a lot more easier to manage and control. When you only have two options of OK and CLOSE not much to do there. This is what a screen shot of the bottom looks like. Thanks!
  14. Trying to install this docker. Docker goes in, but unable to IMPORT my TV Shows. I can see all the TV Shows, just no real way to select them all to import them. Here are the screen shots of the setup. And then the list of TV Shows I want to import. The last thing I want to do is import them one by one. Any suggestions here? It is a very simple, basic setup. Using my cache drive as for my appdata and /media points right to where all my TV Shows are. Any suggestions would be wonderful. Right now I have Sonarr running on a powerful Windows 10 machine ( which I just may keep it there, since that is %100 SSD box ) and when it is all done just has to copy the final output file over to my UNRAID server. If I start throwing everything on the UNRAID box I'm sure it would get bogged down while downloading, unrar'ing, repairing, etc all at once. At least when using the PC the work load does split. See anything out of place on why I can't import those TV shows? There is also linuxserver.io Sonarr which I have not tried yet. Oh, by the way, HAPPY NEW YEAR! PLEASE DELETE THIS DOUBLE POST. I DO NOT SEE A DELETE. THANK YOU.
  15. Trying to install this docker. Docker goes in, but unable to IMPORT my TV Shows. I can see all the TV Shows, just no real way to select them all to import them. Here are the screen shots of the setup. And then the list of TV Shows I want to import. The last thing I want to do is import them one by one. Any suggestions here? It is a very simple, basic setup. Using my cache drive as for my appdata and /media points right to where all my TV Shows are. Any suggestions would be wonderful. Right now I have Sonarr running on a powerful Windows 10 machine ( which I just may keep it there, since that is %100 SSD box ) and when it is all done just has to copy the final output file over to my UNRAID server. If I start throwing everything on the UNRAID box I'm sure it would get bogged down while downloading, unrar'ing, repairing, etc all at once. At least when using the PC the work load does split. See anything out of place on why I can't import those TV shows? There is also linuxserver.io Sonarr which I have not tried yet. Oh, by the way, HAPPY NEW YEAR!
  16. Does unraid have built in TRIM support for SSD drives? I could of sworn I saw TRIM DISABLED in my syslog tonight. 3AM in the morning now, need to get up for work in 4 hours, so I could be a little delusional.
  17. I'd hate to revive a sleeper but have to ask. Reinstalled core, good. Installed the client on my desktop and core setup is asking for username and password. I don't remember configuring anything when I created the docker, nor see any username or pw field there. I tried the regulars like admin/admin, even tried my root login and password, that failed. Checked the syslog and there's nothing in it. Is there a default username/password? Update: I just needed to remove the configuration files in the appdata for some reason. After that, was able to configure my core properly on the docker.
  18. Ok, restarted the server and then selected ALL defaults and now it has started to pre-clear using gfdarm-beta. Thanks!
  19. Having trouble doing a pre-clear. I started one about an hour ago and the screen still looks like this? Any ideas? I selected the JOE.L drop down and left all the other options default.
  20. Is this plugin still being developed? I didn't see any release notes nor any updates since 2015.
  21. I've been running Quassel on 4244 since I installed it and not had any problems at all.... I did get it working. I just made the ports different in Crashplan and Quassel client connected fine with the core. Good enough for me! Wonder if my darn firewall is blocking ports, but that doesn't usually happen. If I uninstall he Crashplan docker then go ahead and install the Quassel-cure it works fine. (can't even get the docker installed, let alone the client running). Once I do get the quassel core up and running that where's the protocol error comes around. Only while Crashplan is present. To make sure, the quassel core can run on any port I want? My friendly little protocol error is back. There has to maybe be a fight between Crashplan and Quassel? Soon as CP gets dumped, Quassel gets back to normal. I tried about 10 different ports, including changing the CP ports (CP works) but the quassel likes that protocol error. By the way, hope everyone had a happy new year's!
  22. I've been running Quassel on 4244 since I installed it and not had any problems at all.... I did get it working. I just made the ports different in Crashplan and Quassel client connected fine with the core. Good enough for me! Wonder if my darn firewall is blocking ports, but that doesn't usually happen. If I uninstall he Crashplan docker then go ahead and install the Quassel-cure it works fine. (can't even get the docker installed, let alone the client running). Once I do get the quassel core up and running that where's the protocol error comes around. Only while Crashplan is present. To make sure, the quassel core can run on any port I want?
  23. I've been running Quassel on 4244 since I installed it and not had any problems at all.... I did get it working. I just made the ports different in Crashplan and Quassel client connected fine with the core. Good enough for me!
  24. I hope this is appropriate, but my father and I pay $450 for 3 years for Crashplan Family Plan. It works good, has a background service which I love but the price has went up twice already. Today I cam across AmazonDrive. It's one of those live realtime drives that you have running all the time. No background service here. For completely unlimited space it only cost $59/year. I believe once you pick a folder on your desktop to by be copied up to the Amazon Drive it will keep it synced indefinitely. Seriously can't beat the cost here on this one. And if any of you had real experiences with them, let use know. Thanks! https://www.amazon.com/clouddrive
  25. Since Crashplan uses 4242 port I changed it to 4545 in Quassel. It worked fine for a while until I have to update it. I pretty much do it like everyone else. I stop the container and click update. Says successful. When I run the client I'll get (attached picture) or something about Quassel can't run, check setup. Now, I've done this before a couple of times. I can usually fix it by deleting the local client and reinstall. Bring me to the setup network screen which is where I'll put down the 4545 put, name and password. I'll eventually select "connect to core" and get the attached. I'll leave it UNfixed for a while until maybe I'll come up with and idea besides just wiping out and reinstalling. Thanks.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.