Boy Kai
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Boy Kai
-
-
Ran another Diagnostics after running -L on Disk 8 and Disk 12 and then booting in Normal Mode.
Wanted to share - if it's helpful.
-
Unfortunately, the Disk 8 and Disk 12 are still showing red Xs.
Ran -L for Disk 12 as well (before starting in Normal Mode):Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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... clearing needsrepair flag and regenerating metadata sb_icount 0, counted 57504 sb_ifree 0, counted 11834 sb_fdblocks 4882434433, counted 1257858882 - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 out-of-order bmap key (file offset) in inode 19381809594, data fork, fsbno 2427919491 bad data fork in inode 19381809594 cleared inode 19381809594 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 1 - agno = 3 - agno = 9 - agno = 11 - agno = 12 - agno = 13 - agno = 4 - agno = 6 - agno = 14 - agno = 15 - agno = 7 - agno = 8 - agno = 10 - agno = 2 entry "Preacher.S02E01.2160p.WEB.H265-PETRiFiED.mkv" in shortform directory 19381809593 references free inode 19381809594 junking entry "Preacher.S02E01.2160p.WEB.H265-PETRiFiED.mkv" in directory inode 19381809593 corrected i8 count in directory 19381809593, was 4, now 3 - agno = 16 - agno = 17 - agno = 18 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 (9:2219024) is ahead of log (1:2). Format log to cycle 12. done -
Apologies for the delayed post. Was traveling.
Here are the results from running:
-LPhase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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... clearing needsrepair flag and regenerating metadata sb_icount 0, counted 74368 sb_ifree 0, counted 20780 sb_fdblocks 4394060173, counted 1298698275 - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 4 - agno = 5 - agno = 10 - agno = 7 - agno = 3 - agno = 12 - agno = 14 - agno = 9 - agno = 15 - agno = 6 - agno = 11 - agno = 13 - agno = 8 - agno = 16 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 (16:410369) is ahead of log (1:2). Format log to cycle 19. done -
Here is the filecheck output.
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. -
Hey everyone. Would really appreciate some help here.
I went out of town for 3-4 days, and returned to drives having a bunch of errors. I did a safe restart via Unraid UI. When my server rebooted - 2 of 17 (19 with parities) drives are labeled as 'Disabled' and 'Unmountable:Unsupported or no file system'.
Please help! Thanks in advance.
-
Hey JorgeB. I appreciate the responses here but it's also kinda frustrating.
I took the time to outline what I've tired and the issues I'm facing, included screenshots and logs. And the responses I'm getting are single sentences with no path to resolution or troubleshooting.
30 minutes ago, JorgeB said:Try booting in safe mode to rule out any plugin issues.
Then what? lol
-
6 hours ago, JorgeB said:
Log is being spammed with avahi-daemon messages, difficult to see anything else.
Alright. Is there an action I can take to reduce the spam?
-
I have re-made my Unraid flashdrive 3 times in the past 2 weeks, with 3 different USBs - and Unraid continues to error on me.
After I update my Unraid, it will be stable for 1-3 days - then it will error saying that it's missing the License Key. Even though I manually checked it after creating USB from backup.
I have also attempted to resolve the issue via the Unraid GUI with a useless error message as a result.
Steps:
Any help to get Unraid stable again would be much appreciated. Thanks.
-
1 hour ago, Boy Kai said:
Hey everyone. Not really sure what's going on, any help would be appreciated.
qBittorrent was working fine until a couple days ago. Now when I start my container in Unraid, it fails to start and then goes back into stopped mode.
I get this in the container logs.[info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080... 2023-12-13 09:13:33,064 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080 2023-12-13 09:27:26,999 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 09:42:27,324 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 09:57:27,667 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:12:27,968 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:27:28,270 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:42:28,587 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:57:28,916 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:12:29,242 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:27:29,553 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:42:29,859 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:57:30,162 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:12:30,474 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:27:30,804 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:42:31,116 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:57:31,425 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:12:31,746 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:27:32,042 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:42:32,359 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:57:32,680 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:12:32,998 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:27:33,303 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:42:33,626 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:57:33,952 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 15:12:34,261 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 15:22:38,877 WARN received SIGTERM indicating exit request 2023-12-13 15:22:38,888 DEBG killing watchdog-script (pid 267) with signal SIGTERM 2023-12-13 15:22:38,888 INFO waiting for start-script, watchdog-script to die 2023-12-13 15:22:38,889 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22663020333008 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stdout)> 2023-12-13 15:22:38,889 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22663017967440 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stderr)> 2023-12-13 15:22:38,889 WARN stopped: watchdog-script (exit status 143) 2023-12-13 15:22:38,889 DEBG received SIGCHLD indicating a child quit 2023-12-13 15:22:38,889 DEBG killing start-script (pid 266) with signal SIGTERM 2023-12-13 15:22:39,890 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22663020233424 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stdout)> 2023-12-13 15:22:39,929 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22663020352784 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stderr)> 2023-12-13 15:22:39,929 WARN stopped: start-script (terminated by SIGTERM) 2023-12-13 15:22:39,930 DEBG received SIGCHLD indicating a child quit ** Press ANY KEY to close this window **
For anyone else, going into the docker docker application settings, attempting to update a field, and selecting 'Apply' showed better error logs.
I had a port allocated twice somehow, not sure when it got introduced. Removed it from the config, and the docker started. -
Hey everyone. Not really sure what's going on, any help would be appreciated.
qBittorrent was working fine until a couple days ago. Now when I start my container in Unraid, it fails to start and then goes back into stopped mode.
I get this in the container logs.[info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080... 2023-12-13 09:13:33,064 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080 2023-12-13 09:27:26,999 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 09:42:27,324 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 09:57:27,667 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:12:27,968 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:27:28,270 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:42:28,587 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 10:57:28,916 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:12:29,242 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:27:29,553 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:42:29,859 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 11:57:30,162 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:12:30,474 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:27:30,804 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:42:31,116 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 12:57:31,425 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:12:31,746 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:27:32,042 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:42:32,359 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 13:57:32,680 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:12:32,998 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:27:33,303 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:42:33,626 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 14:57:33,952 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 15:12:34,261 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38560' 2023-12-13 15:22:38,877 WARN received SIGTERM indicating exit request 2023-12-13 15:22:38,888 DEBG killing watchdog-script (pid 267) with signal SIGTERM 2023-12-13 15:22:38,888 INFO waiting for start-script, watchdog-script to die 2023-12-13 15:22:38,889 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22663020333008 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stdout)> 2023-12-13 15:22:38,889 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22663017967440 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stderr)> 2023-12-13 15:22:38,889 WARN stopped: watchdog-script (exit status 143) 2023-12-13 15:22:38,889 DEBG received SIGCHLD indicating a child quit 2023-12-13 15:22:38,889 DEBG killing start-script (pid 266) with signal SIGTERM 2023-12-13 15:22:39,890 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22663020233424 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stdout)> 2023-12-13 15:22:39,929 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22663020352784 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stderr)> 2023-12-13 15:22:39,929 WARN stopped: start-script (terminated by SIGTERM) 2023-12-13 15:22:39,930 DEBG received SIGCHLD indicating a child quit ** Press ANY KEY to close this window **
-
Ended up using my https://connect.myunraid.net back-up.
- Shutdown my server
- Took my flash drive out of my server
- Plugged into PC (or Mac)
- Saved a copy of the flash drive
- Downloaded back-up from https://connect.myunraid.net
- Unzipped and copy/pasted files to flash drive - to overwrite
- Ejected flash drive
- Plugged into server
- Started server
- Worked
-
The Unraid Startup UI quickly pop-ups on the screen, then it goes black screen and fails to boot from Unraid USB.
-
Had the license Blacklisted error...again. It hasn't happened in a few months but last time it happened it occurred a few times in a row.
I received the license Blacklisted error - restarted - now my server wont boot.
Not sure why this happens, as the license was a 1-time purchase. Any help would be appreciated.
-
On 12/27/2022 at 11:33 AM, trurl said:
Check filesystem on disk7
This worked beautifully! Thank you so much!
-
My shares continue to disappear after a couple of hours within the Web GUI. (screen shot attached)
If I go to my Cache, the shares are displayed but if I go to my Shares tab, those same shares are missing. This is causing my dockers to have access/permission errors and become useless.
A reboot will resolve the issue, for a couple hours at best.
Any help would be very appreciated. Thanks in advance.
Unmountable Unsupported or no file system
in General Support
Posted
Awesome! The array seems to be rebuilding now.
THanks @trurl for that doc link and lost+found confirmation. Saved me a lot of time searching.
Wish I could mark 2 posts as Solution. Thanks again!!
QQ. Is it clear why this happened? Is there a way I can avoid in the future?