rutherford

@wcg66 No idea. I would get crashes after I used the in-program upgrade utility. It wouldn't start, just keep crashing. The logs, as you can see, aren't helpful. I nuked it and did a restore from a backup, that made it crash too. So I'd have to rebuild my library again. As far as I know, this issue hasn't been resolved. I continue to Backup, attempt upgrades, nuke, attempt Restore though. Are any of these possible sources of your crashes? Sorry I don't have better info. This container is in it's infancy.

Thanks @SPOautos you're right, you do have to point the Roon Core at your music files, it isn't automatic. Furthermore though that can be done from any client, and only need to do it once. I got into those settings via Windows 10 client, then android client just worked. I appreciate the note! A little good will and information for posterity is what it's all about.

@SPOautos it's most certainly your path mappings. You need to do two things to get it working 1 set correct paths in the docker settings at the time of setup (you can fix and change it now too) 2 navigate to that path mapping in Roon client. Another user on here @xthursdayx out another docker up there also called RoonServer. They excellent example path mappings in there that you'd modify for your own system. Makes it more easier. Those path mappings took me several tries to get it right, and prompted this howto thread.

@SPOautos I don't think so. You have to have something called a Roon endpoint. It will do the digital to analog conversion and send that to your stereo. You can use a Raspberrypi, or a phone, or a laptop. You might even be able to use your server, but that isn't what this docker does. The docker hosts the Roon core, which is the music server, not a player/client/endpoint.

@wcg66 pihole huh. I can relate to that, and perhaps that does have something to do with some Roon discovery issues. Short story for ya! I was also running pihole under a docker. I was doing it because I wanted it the DNS level blocking, it's terrific, if a bit restrictive. I also had pihole doing dhcp because my router, at the time, didn't support manually specified DNS servers. Everything was running swimmingly, until a power outage, and my ups didn't make it through. On restart, unraid wasn't getting an ip for its main interface from pihole docker! Duh. Ended up actually just buying a raspberrypi and running pihole as intended, never looked back. Also had to upgrade router to one that would work Century Link fiber vlan201, and allow me to specify DNS (Netgear R7000 with some firmware from somewhere). Now that the setup is as it is, Roon, and most everything else works fine. I haven't had to specify any special ports for Roon, the R7000 is doing routing, while pihole is DNS. I changed unraid to a static IP.

Terrific, great. Ya, I wish some of those things were filled out for me! Thank you.

@xthursdayx really cool. Before I dump this one, and switch to yours, can you tell me about it? I only have a remedial understanding of Docker and how that works, and it appears that you're using the same image that "roon-server" uses? Why is one different than the other? Thanks again!

@realdiel Ahh, not an unRaid docker at all. Right on. Yup, once you have a linux install running, it should be pretty straight forward getting it up and running. I had an ubuntu VM going for a while. Worked fine.

@NickAll what's the ROCK Image? Never heard of that. The docker is a little strange, it runs differently from others. It will come up with a little green Running icon, but doesn't have a web interface or port you can connect to. Just run a client on the network, tell it to look for the server, and check that it's up that way.

I've consistently had problems updating the roon-server software where the server fails to restart after the update. The Log doesn't have much helpful in it. Each time, I've had to delete the Docker, Image, and appdata/RoonGoer appdata/RoonServer. Then rebuild the whole library from scratch. If I try to do a fresh install, then Restore from Backup, it will get all the way through that install, then fail to start. Also with not helpful info in the Log file. Anyone else having these upgrade issues? Solutions, or suggestions? I suspect I have some paths or other settings incorrect. Here are my settings. Config type: Path Name: Container Path: /app Container Path: /app Host Path: /mnt/user/appdata Access Mode: Read/Write Description: Config type: Path Name: Container Path: /data Container Path: /data Host Path: /mnt/user/appdata Access Mode: Read/Write Description: Config type: Path Name: Container Path: /music Container Path: /music Host Path: /mnt/user/audio/music (***for me, this is my location of music***) Access Mode: Read/Write Description: Config type: Path Name: Container Path: /backup Container Path: /backup Host Path: /mnt/user/backup/roon/ Access Mode: Read/Write Description: install notes post

@realdiel Why not go the VM route? I stuck an Ubuntu VM on there before, ran a linux version of Roon, worked pretty good as I recall. At least it would keep your electricity bill lower, and cut down on boxes. Maybe you can screenshot that up and guinea pig that process I'll start a new thread about updating. Or find the one I already posted somewhere. With a memory like mine, these posts are mostly notes-to-myself when I need to redo stuff.

@realdiel nuked the install. Removed /mnt/user/appdata/RoonGoer/ and /mnt/user/appdata/RoonServer. Re-installed, it's build 610 now. Attempting to do a restore from the previous build version. Aaaaand nope: it's nerfed. Going back and rebuilding from scratch, again. I wish these updates didn't break it -> nuke it and start from scratch. Perhaps I have some settings wrong somewhere.

A couple of things to note here. I've ran Roon in a VM and as a docker. For me, the VM created some of its own problems. It worked, but I felt like it was an excessive resource hog, just to run Roon server. At the moment I'm on the Steef docker. I use Roon client on several different devices. The client on my windows 10 machine recently (9/6/20) prompted me to update my server. I hit okay, and lost everything. I tried to restore from backup, and that crashed the whole docker. Even though I have a bunch of backups, it looks like if I want to latest version, I'll have to nuke it and rebuild. I've had this upgrading issue consistently, but the docker author hasn't been able to replicate my issues. https://forums.unraid.net/topic/82714-roon-docker-unraid-roon-support-steefdebruijndocker-roonserver/?do=findComment&comment=860931 I haven't spent the time on the latest version, but I'll update... Something, when I get some update time to throw at it. Lastly, and I only learned this myself a few months ago, is that a docker being updated or not doesn't mean you won't get the latest version of that package. I imagine the docker package being a series of steps to grab, install (or grab and update) the necessary package. It doesn't come with the software, it only tells the thing to go to A Place, grab latest version and install it. So, so long as the docker is working, there isn't any reason to update it. That's my understanding anyhow.

http://www.phanteks.com/Enthoo-Pro2-TemperedGlass.html Internal 3.5in bays: 12 (4x included, also supports 2.5in drives) Internal 2.5in bay: 11 (11x included) The picture of the case makes me think I can mount four 5.25 drive cages in the front Rosewill cage newegg, although that specifically wants 5.25in bays: which the Enthoo Pro 2 says it has zero of... ? any ideas? thanks! I could just go with a whole different enclosure. I'm not picky. Just needs to be available 9/2020! And needs to hold 7 3.5in drives and an m.2 drive.

I'm looking to plug the USB drive for the unRaid OS into a wire on the INSIDE of the computer. I've done this before with Coboc EA-U3Y-8-BK USB3.0 20-pin Motherboard header to 2 ports Type A Female Adapter Converter Y cable newegg they don't sell it anymore. But there is this one $9 newegg Here's a four pin usb 2.0 cable also Startek $6 newegg Just wanted to put this cable on folks' radar. It's real nice to have that flash drive inside the computer for no fuss no muss.

@Chenhan did you setup the network path in the container setting like above? here

I fell into this thread by searching for an email solution on unRaid docker. I feel all the comments in here for sure. I used to host my own email server, and it was a bit of a nightmare with spam, and Squirrelmail interfaces, or IMAP POP desktop applications, it was rough. Constant work. BUT, and this strays from the Original Post, what about folks who want ultimate privacy with their email? A self hosted email solution seems like the way to go. The data is in your own personal closet, and it will totally protect you if you run for office one day. Some other things that can be self-hosted solutions: Nextcloud, Bitwarden, a webserver. I didn't see anyone mentioning any of those solutions on here. Any suggestions? The APPS search for 'email' comes back with only a handful of results: OnlyOffice email post.io

Thank you very much! A shame with that corruption thing. I like the idea of not having to throw away this 4 year old 8TB drive. Can you direct me to some instructions for what you mentioned there? Is it as easy as limetech mentions in this thread? As I have a hot standby drive option, I've already removed the old Disk 5 (sdg) drive, and the array is rebuilding new Disk 5 (sdf). Would a deeper SMART scan identify any issues with it? Finished the rebuild on to the new Disk 5 sdf. Seems to have worked w/out a flaw. The old sdg is still being precleared. How can I figure if it's safe to use in the future?

I've been having some issues with one of my data drives. I've had to do xfs-rebuilds two or three times. The second time, I had about a hundred files. They were about the size of JPG pictures. I renamed then suffix, sure enough, they were pictures. There were maybe a hundred of them. I don't think they were copies of pictures that were supposed to be in the file tree: I think they were LOST then FOUND and jammed into this lost+found folder. Recently, I had another hiccup with the xfs stuff and this same damn drive, MD5. There was 4GB and 18k files in there. All different sizes. I'm positive there is real stuff in there that is now found it's way into this lost and found folder. Kinda infuriating here - as unRaid and disk arrays are supposed to protect from this sort of thing. Sure the data is there, but I'm not going to dig though 18k files to see what's what. It's gone. Can this be possible? Am I reading it wrong? I hope!? other thread I started on this

did the xfs-repair. Lost+found is 4GB comprised of 18689 files. FML root@rubble:/mnt/user/lost+found# find . -type f | wc -l 18689 reassigned Disk 5 to my pre-cleared hot standby. Rebuilding drive. But all those files in the lost+found. There is no way I'm going to even make a dent in figuring out what they are, where they go. Isn't this exactly what the RAID is supposed to protect? Oh, my files are gone, they just jumbled beyond any recognition. Is that right?!

I've had things come up with this drive, MD5, three times now. I keep ending up with wayward files, random pictures, a few videos in the Lost&Found folder the xfs_repair creates. Is it time to replace this drive? Or perhaps I have something else that might be the source of these errors? Thanks. unRaid Log excerpt Jun 25 13:31:38 rubble kernel: XFS (md5): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x28d64b418 len 32 error 117 Jun 25 13:31:38 rubble kernel: XFS (md5): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117. Jun 25 13:31:38 rubble kernel: XFS (md5): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x28d64b418 xfs_inode_buf_verify Jun 25 13:31:38 rubble kernel: XFS (md5): Unmount and run xfs_repair Jun 25 13:31:38 rubble kernel: XFS (md5): First 128 bytes of corrupted metadata buffer: Jun 25 13:31:38 rubble kernel: 000000000b94922e: 24 1a 9c 92 6d 85 ce 6d 6f 93 4c d2 44 fc dc 3b $...m..mo.L.D..; Jun 25 13:31:38 rubble kernel: 0000000023b350af: 98 25 67 cf 3f 77 ea c1 c5 b7 19 f8 16 ee f9 6f .%g.?w.........o Jun 25 13:31:38 rubble kernel: 00000000bda7ee4a: 76 48 30 f5 c9 61 87 35 a3 da 2a ee a0 d8 92 c3 vH0..a.5..*..... Jun 25 13:31:38 rubble kernel: 0000000005d43f5d: cc 6c cd 9b 9b 53 a0 69 79 01 e4 94 72 d5 4f 37 .l...S.iy...r.O7 Jun 25 13:31:38 rubble kernel: 00000000a9604dcf: aa 93 9e 81 25 4c 5d dd d7 25 b1 ba 1c c7 68 6b ....%L]..%....hk Jun 25 13:31:38 rubble kernel: 00000000912129a9: 00 b6 ab b7 f7 3e 76 31 ad 48 42 a3 ae b1 05 df .....>v1.HB..... Jun 25 13:31:38 rubble kernel: 000000008b0cde81: de da 64 5c 81 28 13 65 0b 6f 1f 49 78 a2 3e 33 ..d\.(.e.o.Ix.>3 Jun 25 13:31:38 rubble kernel: 000000008e83606e: b4 01 36 42 53 25 cc d8 e1 93 28 7f 0a 9c db 66 ..6BS%....(....f Oh good lord, stopped array, brought back up in Maintenance mode. Did the xfs_repair status, here are hastebin results Many entries in there. Unfortunate. If I replace the drive, will that fix any of this stuff? I have a hot standby in the server ready to replace this drive. I suspect I'll have to run this repair, THEN replace the drive. Or the errors will simply get copied to the new drive, and I'll have to replace it anyhow. Any help would be terrific, thanks! rubble-smart-20200625-1924 disk 5.zip rubble-diagnostics-20200625-1914.zip

@SPOautos Yes. You would probably choose unRaid because of it being unRaid, google other options and see what you think. I have been able to run the Roon Core as a docker (this thread) on my unRaid server successfully. It works great. While I appreciate your end game there: Roon to a Chromecast controlling via android and iPhone, and you should certainly keep your eye on the prize! There are many pieces that have to fall into place for this string of technology to work well together!

[FIXED] Not sure what the issue was with the update, but I rehashed the install and update and it worked fine. I detailed that over at Roon Forums here. @xrqp Yes, you're right. At the moment, I'm running an Ubuntu VM on unRaid. On that VM I'm running the Roon Core. It's a virtual computer, inside a computer. You can run whatever you want on it, provided it doesn't use up all the resources allocated to the VM and make it run slow as molasses. That's finer points of VM, which I know nothing about! @mikela This thread, the Original Post, is about the docker. During an update, I had some issues I outlined above, and moved an Ubuntu VM instead of the Docker container. And I'll update it the thread when I get a chance to start messing with the steefdebruijn docker again! It was probably operator error Reply from steefdebruijn over at Roonlabs Forums

Update: while the "Sign Up" button is still there, after filling out the form, it says "signups disabled." So I guess that's all good. Has anyone addressed these other setup issues I saw in the Bitwarden log file? Spaceinvader does talk about disabling Signups (?) in the video, but doesn't hit on these other things.

Been running the Bitwarden Docker for sometime now. Usually it works like a charm, but then, seems like after about 4-7 days of running, I start getting errors when I connect to my https://bitwarden.mydomain.com Followed the directions from Spaceinvader on youtube I have a reverse proxy setup correctly, also following Spaceinvader on youtube. I also run Nextcloud through the reverse proxy, and have never had any issues with access via the same means as bitwarden. With Wireguard VPN, I can access bitwarden via the local IP http://192.168.11.53:8086 There aren't any meaningful error messages in the docker logs for Letsencrypt or Bitwarden. On the letsencrypt docker setup page, I swapped the Subdomain variables: bitwarden,nextcloud to: nextcloud,bitwarden Here's the log (I swapped out the actual domain with 'mydomain') https://hastebin.com/erikuhevon.sql That fixed the problem for the moment, but I'd still like to get to the bottom of this. The setup: 1. created account at Duckdns, installed Duckdns docker to continually update local ip 2. I own my own domain, I created CNAME subdomains for nextcloud and bitwarden. nextcloud.mydomain.com CNAME to username.duckdns.org bitwarden.mydomain.com CNAME to username.duckdns.org 3. letsencrypt docker has settings "Domain name:" as mydomain.com Subdomain(s): bitwarden,nextcloud http: 180 https: 1443 4. home router forwards port 80 to port 180 on unRaid server port 443 to port 1443 on unRaid server Firefox Chrome Internet Explorer 11 rubble-diagnostics-20200604-1058.zip