Jump to content

dkerlee

Members
  • Content Count

    330
  • Joined

  • Last visited

Community Reputation

14 Good

About dkerlee

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Tacoma WA USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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?
  2. 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
  3. 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?!
  4. 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
  5. @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!
  6. [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
  7. 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.
  8. 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
  9. [FIXED]Not sure what the issues was. Went back to Docker version of Roon Server, and it updated fine. On Docker v1.7 build 555. 6/6/20 Just got a note this evening to update some software. I did the update, and my Roon client software couldn't find the server again. I reconnected, had to re-login with Roon credentials, and it seems to have lost all my metadata. Thankfully, I had a previous backup I could restore. Just be warned. I believe this is Roon Server version 1.7 build 555 The backup was from 1.7 build 553, and it doesn't work. I'll have to nuke it and rebuild all metadata. Yay. I also had to remove RAATServer/, RoonGoer/, and RoonServer from the appdata directory to get it to come back. The build the Docker pulls is 1.7 build 537. I'm going to leave it at that older version for a while before attempting an upgrade. Maybe see if anyone else has any luck before I try and hack it up. Updated to version 1.7 build 555, aaaaand lost library And restore breaks docker. has mp3float: 1, aac_fixed: 0 Running Not running Initializing Started Not responding Unhandled Exception: System.IO.IOException: Directory /data/RoonServer/.restore_old/Appliance is not empty at System.IO.Directory.Delete (System.String path) [0x0006f] in <370a0c27f4b74d1a81431037df6d75bf>:0 at System.IO.Directory.RecursiveDelete (System.String path) [0x00051] in <370a0c27f4b74d1a81431037df6d75bf>:0 at System.IO.Directory.RecursiveDelete (System.String path) [0x00024] in <370a0c27f4b74d1a81431037df6d75bf>:0 at System.IO.Directory.Delete (System.String path, System.Boolean recursive) [0x00009] in <370a0c27f4b74d1a81431037df6d75bf>:0 at Sooloos.Client.ApplicationCommon.Init2 (System.String[] argv, System.Boolean supportupdates, System.String lockname) [0x001dc] in <71f2fca491de4b978badec69f164d711>:0 at Sooloos.Application.Main (System.String[] argv) [0x00220] in <07df41d5902a4aa2abb521c06bca9560>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.IO.IOException: Directory /data/RoonServer/.restore_old/Appliance is not empty at System.IO.Directory.Delete (System.String path) [0x0006f] in <370a0c27f4b74d1a81431037df6d75bf>:0 at System.IO.Directory.RecursiveDelete (System.String path) [0x00051] in <370a0c27f4b74d1a81431037df6d75bf>:0 at System.IO.Directory.RecursiveDelete (System.String path) [0x00024] in <370a0c27f4b74d1a81431037df6d75bf>:0 at System.IO.Directory.Delete (System.String path, System.Boolean recursive) [0x00009] in <370a0c27f4b74d1a81431037df6d75bf>:0 at Sooloos.Client.ApplicationCommon.Init2 (System.String[] argv, System.Boolean supportupdates, System.String lockname) [0x001dc] in <71f2fca491de4b978badec69f164d711>:0 at Sooloos.Application.Main (System.String[] argv) [0x00220] in <07df41d5902a4aa2abb521c06bca9560>:0 /app/RoonServer/start.sh: line 50: /app/RoonServer/Server/RoonServer: Permission denied /app/RoonServer/start.sh: line 34: kill: (16767) - No such process /app/RoonServer/start.sh: line 50: /app/RoonServer/Server/RoonServer: Permission denied /app/RoonServer/start.sh: line 34: kill: (11) - No such process /app/RoonServer/start.sh: line 50: /app/RoonServer/Server/RoonServer: Permission denied /app/RoonServer/start.sh: line 34: kill: (11) - No such process /app/RoonServer/start.sh: line 50: /app/RoonServer/Server/RoonServer: Permission denied /app/RoonServer/start.sh: line 34: kill: (11) - No such process /app/RoonServer/start.sh: line 50: /app/RoonServer/Server/RoonServer: Permission denied /app/RoonServer/start.sh: line 34: kill: (11) - No such process removed image root@rubble:/mnt/user/appdata# rm -Rf RAATServer/ RoonGoer/ RoonServer/ Re-install via APPS > Previous Apps Doing a restore from 1.7 build 537 to version 1.7 build 537 And that doesn't work either. Welp... might be time to re-think this approach. Went through an Ubuntu VM 20.04 LTS, got that going. Did install via the Roonlabs instructions, that has a script that pulls the download from http://download.roonlabs.com/builds/RoonServer_linuxx64.tar.bz2 and now that that's on there, it's version 1.7 build 537. Which is not build 555 Did the update and it took. Made sure the vdisk is on the m.2 ssd drive and I think it's running faster and smoother in the VM vs the docker. I'll stick with this for now!
  10. I had some trouble with my Nextcloud installation after changing out my cache drive. I used the Settings > User Utilities > Backup/Restore Appdata. If I recall, it simply wouldn't connect to the server, and I'd get Bad Gateway 502 errors. Something happened with Nextcloud losing the connection to the database backend. MariaDB did no lose any of the DB settings, but Nextcloud wasn't talking to it correctly. Re-initialize Nextcloud setup. You can do this by moving or deleting the default conf file. For me this was in: /mnt/user/appdata/nextcloud/www/nextcloud/config Once you get rid of that file, and hit the default setup page again, you can pick up Spaceinvader's video again right here on youtube https://help.nextcloud.com/t/how-do-you-restart-the-install-wizard/6579
  11. hey @nikkinrob did you get this sorted out? I know it might be tempting to do the VPN, but it seems like 99.9% of folks that want this setup, go with the instructions that Spacedinvader outlines in the how-to video: a Letsencrypt https SSL solution.
  12. came across this thread for docker utilization: "what's taking up all my docker.img space in there?" "Resource Monitor" in Community Applications has been replaced by cAdvisor, which is in the APPS tab. Go to SERVER:8085, click Docker Containers, at the top, scroll to bottom, and sort by Virtual Size. You can see in the image below, Krusader is hogging up 2.29GB
  13. that's probably what was happening. I'm not sure what it was that was bringing docker storage to 70% (when it was 30GB), but I did find entire seasons of tv shows that I had "put in trash" from Krusader: apparently that's inside appdata. Whoops! In that vein I got cAdvisor so I could look at the size of individual dockers to see if anything popped up. I think I'm looking at the right page there?:
  14. Thanks a million @trurl I think I got it sorted, I just went and did it. It went swimmingly, but it would still be super valuable if you could take a peek at the settings just to ensure I got this setup in a way that makes sense! Speed, redundancy, logic. Thanks! other thread rubble-diagnostics-20200525-0951.zip
  15. thanks a million, did like you said, back up and running with zero issues. Thanks! That would make a tidy wiki entry somewhere... For posterity: 1. stop VM and Docker services through Settings 2. changed Share "system" to Prefer cache drive (location of docker.img) 3. ran mover, waited to complete 4. Started Docker service. While my Apps/Dockers appeared to be present and working... 5. Got this error message 6. Deleted docker.img using a terminal 7. went to APPS tab, then Previous Apps on left 8. Selected all the Apps I'd been using (I also increased my docker image file a bit, I'd been hitting 70% regularly), installed all Apps Back up and running with all settings and previous stuff, no worries. Nice one folks! Thanks a million.