lankanmon

Hey, sorry, I am unable to see any of my docker images due to Docker Service failing to start... Is there any other way?

Okay, thanks! So, if I delete the image and restart docker, I should be able to see the application templates? Is there anyway to see the custom docker networks before I delete the image? Just so I can re-make it. I think I had one setup... Thanks!

My cache drive became full due to an unexpected set of data baing added to cache only. I only nocied when some of my docker apps started misbehaving. I turned off docker (in settings) to prevent further damage and ran the mover to get the cache back to normal. When turning on docker again, I saw that "Docker Service failed to start.". I know that I can delete the docker image, but IIRC, last time I deleted the image, I had to setup each app all over again. Since then, I have a lot more apps. Is there a way to backup each of the apps configs (all of the settings) before deleting the image, so I can add them easily after deleting the image? Since the docker image is not starting, I can't go through each of then like I would normaly to take screenshots of the settings. Your help will be much apprciated. I really hope that I don't need to figure out the configs for each app all over again... I have also attached my diagnostics in case that will help with resolvign the issue... lknserver-diagnostics-20200920-0710.zip

Hey thanks for this. I swapped out a bunch of SATA cables and it seems to have stopped the messages. I will keep an eye on it for now. Good to know that the drive is okay.

Okay, I will try swapping the cable and if that does not work, I will swap the drive... Can you think of anything else it could be?

I waited about a day after and it seems to be back. Fix common problems shows: Unable to write to cache and the log is about 34% full now. I do not have docker and vms running so it is just system messages causing the errors. I have attached diagnostics. Also do I need to balance my cache? and if so, what command should I use? lknserver-diagnostics-20200108-2158.zip

Here is the diagnostics after I made sure the cables a plugged in correctly. lknserver-diagnostics-20200107-2359.zip

So, I need to replace the cache drive?

I am getting a BTRFS error spamming my logs and there appears to be other issued. SDB1 is my cache drive. I have Fix common problems installed and it is detecting that the drive is read only or full. But the drive is 480GB and it is only using 78GB, so there is plenty of space. I have attached the diagnostics to this post This is a snippet of the message being spammed: Jan 6 05:12:23 LKNServer kernel: __btrfs_lookup_bio_sums: 10 callbacks suppressed Jan 6 05:12:23 LKNServer kernel: BTRFS info (device sdb1): no csum found for inode 988745 start 0 Jan 6 05:12:23 LKNServer kernel: sd 1:0:0:0: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 6 05:12:23 LKNServer kernel: sd 1:0:0:0: [sdb] tag#5 CDB: opcode=0x28 28 00 03 d0 92 b8 00 00 08 00 Jan 6 05:12:23 LKNServer kernel: print_req_error: I/O error, dev sdb, sector 64000696 Jan 6 05:12:23 LKNServer kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 43, rd 254421, flush 0, corrupt 0, gen 0 Your help is much appreciated. Thanks! lknserver-diagnostics-20200107-0159.zip

Awesome! I'll take a look, thanks!

I have a main server with with all of my storage and a decent spec (as seen in my signature). I want to set up a secondary unraid server with SSDs only to use as a secondary "hot" server which will take a bit more of the processor intensive tasks. How can I pass the shares between them? Example: I want to have a Plex Media Server on the new one that will be used for remotely viewing content and it will need to encode to different formats. When I am attempting to install the Plex docker app, all I can do is pass in directories, not network locations. How can I achieve this?

I have been using Unraid for about five years for work (with my own license for about three years). I have a hard time remembering my life before I learned of Unraid. I have always been a Data Hoarder at heart, but did it chaotically. Setting up RAID arrays have always caused me anxiety, purely for the fact that if I make a mistake, I can loose all the data (since it is striped). When I learned of Unraid and its use for data, virtualization and the built in docker support, it was obvious what I will use for my own server. Happy Birthday Unraid!

I followed this video as shown to get Let's Encrypt to run on my server with my own domain. It works well for my docker containers! One thing that I am not clear about how to do is to point one sub domain (that I already have gotten a certificate for) to a VM which has an instance of GitLab running. It was the only thing that I had exposed to web before setting up this reverse proxy and would like to still be able to access it from a subdomain. Your help to achieve this would be greatly appreciated... Thanks!

@Squid & @Saldash I just freshly installed firefox on a laptop that I never used (with no plugins) and also on android (w. chrome and firefox - also no plugins) and it is still happening. Furthermore, I am using uBlock Origin and I have added the server ip to the whitelist and it is still happening. Any ideas?

Hi all, I have noticed recently that clicking a docker app and selecting WebUI does not seem to work on both Chrome and Firefox. On chrome, it opens a new tab with the url: about:blank#blocked On firefox, it does nothing (no tab or window opened) I have tested on different browsers, operating systems, and devices. I have also ensured that my adblocker is disabled to ensure that is not the cause of the issue. Any help would be greatly appreciated! Thanks!

I did a parity check and it did complete successfully with 0 errors. So I hope everything is well. I do have some backups (although not of the entire server), and will see if I can verify data integrity. Thanks for all of your help!

I did not restart before. I have restarted now and mounted the array (not on maintenance mode) and they now appear to show up as normal (xfs). I would also know where do I go from here? Is there any way to determine what files may have been corrupted? I noticed a mention of "lost+found" in the logs above... Is that something that I can actually access? Also, would my parity be valid right now? Should I run a parity check (and if so, should I write corrections to parity)? Please let me know... I really appreciate your help! Thank you so much!

Okay, I have finished running the xfs_repair on both drives: Disk 3: Phase 1 - find and verify superblock... sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... sb_icount 0, counted 210816 sb_ifree 0, counted 6594 sb_fdblocks 976277683, counted 182759326 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 1 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (34:652511) is ahead of log (1:2). Format log to cycle 37. done Disk 5 (took much longer): Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... sb_icount 0, counted 55660224 sb_ifree 0, counted 142 sb_fdblocks 976277683, counted 343482943 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=,swidth= if necessary Maximum metadata LSN (59:518163) is ahead of log (1:2). Format log to cycle 62. done The drives still show "Unmountable: No file system" Do I need to restart or unmount & remount now to get the drives to mount? Also, there is a note at the bottom of the Disk 5 log, do I need to run any of those commands?

Update: when I am trying to run it on Disk 3, it os giving this Error: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. So, do I run it with the -L option? Is there any other way to mount to filesystem?

I am not sure... It may have been a old bookmark or something. I usually just start typing in the address bar and hit enter when the result seems relevant and I must have visited it at some point for it to be the first result. (was there maybe a beta at any point?) I had forgotten that the rebrand also changed the forum, so I was not looking for the dark themed forum. I made a post on that forum and about an hour later decided to follow up on my laptop. That's when I realized that there were two forums and the post that I made was not on this one...

Okay, I will run the xfs_repair without -n for each drive and report back. Thanks!

I have attached the diagnostics. I did find that strange too, Is there any way to determine if data is corrupted? And how well does xfs repair work? lknserver-diagnostics-20190319-0451.zip

I posted in the forums here: https://ipstest.lime-technology.com/forums/ and was wondering why it seemed less busy than normal. I only then realized that I posted on an alternate version of the forum (backup or test). I am not sure if it is different from this one but seems very similar (except for the lack of recent changes). I suggest forwarding that subdomain to this forum if it no longer is actively used to prevent users from being lost and posting in a forum that will not forward to this one. If I have misunderstood, please let me know... Thanks!

Note to Mods: I posted this here first: https://ipstest.lime-technology.com/forums/topic/70755-two-disks-are-unmountable-after-a-single-drive-failure-unmountable-disks-present/ (is this a test forum?) Hi all, I've got a bit of a problem... One of my Disks (Disk 5) failed last week and after reseating the state, trying a new one and using a different power, I decided to use a backup drive that I had already precleared (and rebuild from parity). The rebuild seemed to be going well, but I may have knocked the SATA cable of Disk 3 and it became unavailable (and also emulated). I have two parity drives. I noticed that the parity rebuild sped up by much when this happened. I still let it finish. With disk 5 rebuilt and Disk 3's SATA cable reseated correctly, I also rebuilt disk 3. Now, my party is valid (all green). I now have an issue where when I mount the array, I have a message that says unmountable disks present. I mounted it in maintenance mode and ran the "Check Filesystem Status" for each disk -- here are the results: Disk 3 xfs_repair status: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. Disk 5 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. I am not entirely sure what this means or what is going on. I am really concerned about my data right now... Is there any way to fix this without the loss of data? Any help will be much appreciated!

Okay, I deleted the docker image and recreated it. It now seems to be working fine! Thanks a lot for all of your help!