xrqp

Members
  • Posts

    247
  • Joined

  • Last visited

Everything posted by xrqp

  1. dkerlee, Is roon running bit perfect with the purple star, meaning no DSP? "purportedly lossless via Apple Music ALAC". I guess you say "purportedly" because like me, you are skeptical and cautious about streaming claims of large music providers. If your flac is 14MB, and Apples alac is 5MB, maybe it is from lower rez. Are they both 16/44? "VON reports 32MB " is maybe including transmission overhead, like re-sending missed packets. What is VON?
  2. Price is dropping in USA for the Seagate. These prices are USA per drive, before tax, but include free shipping: 2021-9 $390 2021-11 $370 2022-2 $320 (for me, with tax, is $350) Kim, agreed that the jump from 8TB to 18TB was a big surprise (and very welcome). For decades in the past, the sweet spot size increase was usually much smaller - or incremental. This is a huge jump of great significance to data hoarders, like I suspect many unraiders are. I see your source has the Toshiba 18TB at €269 ($308) including VAT tax and including shipping. That is excellent and beats my USA price.
  3. I got videos in ISO and BDMV files/folders on the unraid server and want to convert all to mkv, which will also be on the unraid sever. I use Emby to paly videos and mkv works better for Emby. I assume I can do it from my Win10 computer with an app running on the Win10 computer. But should I instead do it with an app on the unraid server? Does having the app and the files on the same machine make it faster? How do you do it - on Win10 or on unraid? Any suggestion what app to use? Apps that require knowing linux, would not be good for me.
  4. It seems like most people do one or two cycles. If I have time, I do two. About half of my drives I do one cycle. An 18TB takes about 1.5 days for one cycle. I use default settings as shown below. Usually I am doing new drives, so I pick "clear" (not erase and clear). But I am not too sure about it, so I hope you get some replies.
  5. If you want internal w 5yr warranty, this Seagate 18TB is competitive. Price dropped by $40 since Sept.
  6. Limetech could add some more info in describing the number of drives limits per license type. Currently all it says is: If you know what "attached to the server" means, and the significance of "before starting the array", then it is complete, but some extra words would have helped me. From reading on the forum, I think the following is true. I use the word "drives" to be the same as "storage devices": "Attached to the server" means it includes parity drives, array drives, cache drives, and 'unassigned devices' drives. Am I missing anything? "Attached to the server before starting the array" means you can attach more drives after the array is started, and they will show up as "unassigned devices" and they will not count towards your drive limit. This it very useful since SATA drives are usually hot-swapable, meaning they can be attached to the server while it is running. VM drives for the "Basic" and "Plus" licenses: I will leave for others to clarify. After Unraid starts, does it show somewhere the number of drives it counted?
  7. Wow. Awesome support from you , xthursdayx! Thanks very much. Your reply is a great reference for me since my memory and knowledge of this stuff is not the greatest. And your tips for emby i will follow. I don't know how emby uses DLNA or what for, but so far all is working well again, and I did not loose anything from roon playlists etc. If you want to see the 3 question marks for roon ports, go into any unraid docker container setting screen, and click the and you will see it. But now with your reply, I know what really is going on with the roon ports. I also posted at roon labs forum and steef replied that he does not recommend messing with assigning ports for roon in the container settings - that when he tried it, it did not work well. I think i went thru 3 or 4 updates with no problems, but this last one got me. Thankfully fixable. There was one good side effect - my Sabnzbd container downloads about 25% faster now! My guess is it had something to do with emby and removing the DLNA port assignment.
  8. Over at roon labs forum, one other person, Perter L, reported the same problem as me after the last roon update. I have narrowed it down to be a roon vs emby conflict. I can run any and all containers, except emby, and roon works fine (both server and remotes). Here is what unraid shows for port allocaitons: I think I had this problem before, I fixed it by changing a path and/or path mapping in emby. This time, I fixed it a different way - by deleting emby port 1900 allocation (DNLA UDP). So now, it seems everything is working, both emby and roon, and remotes for both. Here is details for the port allocation I deleted: I think this came automatically with the container by linuxserver. It said "optiona"l, so I deleted it. I don't know what it is for, or if I will discover other problems later. Can I assign a port number to the roon container?
  9. xthurdayx, thanks for the time for your extensive reply. I am guessing maybe its a port assignment error. When I look at the room container port mapping it only show 3 question marks. I cannot remember if that is normal. All other containers show a 4 digit port number. Roon labs say they do not support undoing updates. They also do not support unraid. The nag to update came on my ipad running roon remote. It asked if I should update all devices and I replied yes. I assume, and it appears to update all remotes - ipad, iphone, Win10 desktop. But I don't know if it can, or did, update the server in the unraid container, and I don't know how to check that. Too bad I think I loose my playlists if I do this. So far, the roon backup seems to always be useless for how my system fails. Very false sense of security. This is the 5th time I loose my playlist in 2 years. I use SSD cache for the appdata directory. Here is my mappings: If I recall correctly, the last path, the data path, is a secondary location for some of my music. Maybe I should delete that path map. My regular unraid parity check just completed today and reported, in a yellow box (not red box) "836 errors". The previous one a month ago had no errors. So today I ran "Fix common problems" and it says "no errors". Today I ran for all 8 disks the "SMART short self-test" and all 8 say "Completed without error".
  10. Sorry for complaining, but it is info. I got the usual nag to update roon. I knew if I said "no" to the update, it would nag constantly into the infinite future. So I gave in, I updated roon from my ipad running Roon Remote, and now nothing works. The 3 devices that run roon do NOT work. the Unraid server with roon container - No web interface but I guess it is workin. And I cannot figure out how to undo the update, and Roon website i was not able to find info, not even how to contact a HUMAN. So I sent in a help request in "how to contact a human". There is definitely humans here, so Howdy to y'all. and if you got anything to add, I'm all ears (eyes?). Friday night and roon ain't working blues.
  11. Recently, I was able to go about a good 10 days before it slowed down. Was down to less than 100 queued. Then did remove and re-install. Worked only for 2 days. Then did remove and re-install. Worked only for 2 days. Then did remove and re-install. Only 180 downloads queued now. Eventually I may give SABnzb a try.
  12. My usenet is paid version of nzb.su and nzbgeek, and free versions of nzbhunter and usenet-crawler. With these, for 4 months, never had the problem, until this last week.
  13. Happened again. Took only 12 hrs to drop from 5MBs to 0.5MBs download rate. Did reinstall again and it "fixed" it again, but now I am pretty sure it will slowly slow down over 12 hours. I guess at some point I may switch to Sabnzb, but I hate to recreate the queue. I have 500 downloads queued. Is that part of the problem? Is there any way to troubleshoot this with logs? I also wonder if my ISP is doing this.
  14. 20 hr later update. Nzbget download rate slowed to a crawl, even though my internet is tested to be fast. I tried again with the removal of the nzbget container, then re-installed the container using unraid "previous apps". And now my nzbget download is fast. I am guessing it will last for a 12 to 24 hours, then I may need to do it again. At the same time i updated unraid from 6.9.1 to 6.9.2, and all my containers needed updates too, so did that too. Maybe that will help keep the download rate high.
  15. Hey. I did remove the nzbget container, then re-installed the container using unraid "previous apps". And IT WORKED GOOD! I did not loose my download queue. And it is downloading at full speed. What a relief! Unraid and my dockers frequently give me a good scare, but usually I can fix it, with time and effort. Is it fair to assume it will become more bulletproof as the years proceed? Sometimes I wonder if running emby, with tv antenna, and all the *arrs, and doing disk rebuilds, and parity checks, and doing preclears - if it overloads it and causes problems?
  16. Hey RecycledBits, thanks for your post. I had not thought about the energy saving of one 18TB vs two of 9TB, but it makes sense. I would give more weight to your experience since you had a lot more drives than me. Were many of your 8TB SMR used in unraid array? Not sure if that makes any difference. Other posts said SMR worked very well in unraid.
  17. My nzbget is not downloading after i did a successful parity check and disk rebuild. I don't know if that was a coincidence. It seems to otherwise be working, like I can add nzb's to the queue. It says "downloading" but the speed is zero. I checked my internet was good, and did power cycles of unraid, but same problem. I tried nzbget "restore" to a backup that is a few months old, but same problem. Now I want to try removing the container, then re-install the container using unraid "previous apps". If I do that do I lose my 360 item queue that took days to build? Also I am open to any other suggestions. Thanks.
  18. Maybe what you say is because if we zeroed it in the array, the parity would have to be writing the changes as well as the disk being zeroed for removal. Is that what you mean? And is that about half speed of the normal method of writing to just one disk (writing the emulated disk on to the new disk via parity sync)?
  19. Sounds good. Thanks. I am still on 6.9.1. I will soon upgrade to 6.9.2, after the parity rebuild 😄. The 18TB parity rebuild looks like it will be about 44 hours total, only 2 hours left to finish.
  20. It takes 2 or 3 full days to parity sync an 18TB drive. Can this be a new feature request, that we can stop array and continue parity rebuilds? Preclear allows reboots and can continue where it left off. I have frequent problems with things not working right and needing to reboot. For the last 2 weeks I often don't make it to 2 days before I need a reboot. I don't know if it is because I run sonarr and radarr and nzbget with hundreds, or thousands, of downloads queued or grabbed, or because I used the cheap shucked 8TB drives that keep having problems, or if unraid is not very stable. I don't know, so I make guesses.
  21. After me move all the data off a drive that we want to remove, we need a way to zero that drive in the array, so we can remove it, and not need parity rebuild. So we have continuous parity protection. Or is there a flaw in this idea?
  22. I had checked each disk to include in user shares. Maybe I forgot I did that when I added disks before. I will change it to be no disks checked, so all are included automatically. Regarding the "may" vs "will", for me it made the disk into a disk share, without me doing any checking of any check boxes. But as time goes on, I may understand it better. Thanks very much for the extensive help in your replies.
  23. I have had disk errors and disk failures lately, and it seems to be with 8TB SMR drives (mostly shucked). On-line I only see info about how slow they can be. Can't find much about failures. But I think they fail more too, and fail within about 2 years. I am regretting them.
  24. "Settings->Global Share Settings", "Enable disk shares:" was set to "auto". Now is set to "No". Then I could pick disk 7. So I am back to normal. Why did I not have this problem when I added disk 4, 5, and 6? Help says "If set to Auto, only disk shares not participating in User Shares may be exported." Question 1) If I add a new disk, does it immediately go to disk share before I have a chance to put it in User Shares? Question 2) Help says "may be exported", but for me it was exported. Why does help use the word "may".