Bill leeder

Hello, your direction was able to lead me to the solution. Array is back up and running no data lost. Thanks for the support!!

Thank you. I followed the check file system directions and this is the info that posted. not certain what it is telling me\how to repair. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... agf_freeblks 5297895, counted 5297890 in ag 0 sb_ifree 4594, counted 4476 sb_fdblocks 244003408, counted 257624736 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 imap claims a free inode 2231175594 is in use, would correct imap and clear inode imap claims a free inode 2231175595 is in use, would correct imap and clear inode imap claims a free inode 2231175596 is in use, would correct imap and clear inode imap claims a free inode 2231175597 is in use, would correct imap and clear inode imap claims a free inode 2231175598 is in use, would correct imap and clear inode - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (0,3355-3355) only seen by one free space btree free space (0,209255-209255) only seen by one free space btree free space (0,4798520-4798524) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 5 - agno = 6 - agno = 2 - agno = 7 - agno = 4 entry "GoP-0.xml" in shortform directory 2209076273 references free inode 2231175594 would have junked entry "GoP-0.xml" in directory inode 2209076273 entry "GoP-3.xml" in shortform directory 2209076273 references free inode 2231175595 would have junked entry "GoP-3.xml" in directory inode 2209076273 entry "GoP-4.xml" in shortform directory 2209076273 references free inode 2231175596 would have junked entry "GoP-4.xml" in directory inode 2209076273 entry "GoP-5.xml" in shortform directory 2209076273 references free inode 2231175597 would have junked entry "GoP-5.xml" in directory inode 2209076273 entry "GoP-6.xml" in shortform directory 2209076273 references free inode 2231175598 would have junked entry "GoP-6.xml" in directory inode 2209076273 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "GoP-0.xml" in shortform directory inode 2209076273 points to free inode 2231175594 would junk entry entry "GoP-3.xml" in shortform directory inode 2209076273 points to free inode 2231175595 would junk entry entry "GoP-4.xml" in shortform directory inode 2209076273 points to free inode 2231175596 would junk entry entry "GoP-5.xml" in shortform directory inode 2209076273 points to free inode 2231175597 would junk entry entry "GoP-6.xml" in shortform directory inode 2209076273 points to free inode 2231175598 would junk entry - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 2516822199, would move to lost+found disconnected inode 2516822200, would move to lost+found disconnected inode 2516822207, would move to lost+found Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

Hi there my array stopped working last week and my "Disk 1"(Not parity) was showing as unmountable and when i checked the smart data there were errors with the I\O and it being frozen. I assumed failed disk at this point. I replaced the failed disk to witch it promtpted me to start the array and do a parity sync\rebuild. I have done this and the disk is still showing "Unmountable" this is leading me to believe there is something wrong with the emulated file system based on some other posts I've read but I do not know where to go from here.

Hi there I am running the server as a static IP but I have not set any dockers to one. I have not changed the bridge settings at all. I was logged in Saturday night no issues. without even a computer restart tried Sunday morning and it wouldn't let me in

crap...sorry here is the sonarr one supervisord.log.1

Here is the log you mentioned as well as the Sonarr log I have been using Sonarr for a while and has been working great. The other day I was unable to login to the WebUI. it displays this message "Hmmm… can't reach this page xxx.xxx.x.xxx refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED" I've tried reinstalling docker, it's fully updated, I've tried changing port numbers, tried from multiple computers\browsers. Also my other dockers are working including SAB,Plex,Radarr, Krusader. Any ideas of what else to look at to fix this? Bill Leeder Sonarr log.txt supervisord.log

I have been using Sonarr for a while and has been working great. The other day I was unable to login to the WebUI. it displays this message "Hmmm… can't reach this page xxx.xxx.x.xxx refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED" I've tried reinstalling docker, it's fully updated, I've tried changing port numbers, tried from multiple computers\browsers. Also my other dockers are working including SAB,Plex,Radarr, Krusader. Any ideas of what else to look at to fix this?