Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

jolma

Members
  • Joined

Solutions

  1. jolma's post in v7.1.2 screwed up my unraid network was marked as the answer   
    from my experience when you get ip of "169.254.141.64" it means your server didn't get IP from DHCP server on your router... so you can check or restart your router..
    hope it helps...
  2. jolma's post in Upgraded to 7.1.2 and Two of My Drives Unmountable [Solved] was marked as the answer   
    Trying to summarize
    1. After upgrading 2 of my drives unmountable
    Check using fdisk -l /dev/sdb and fdisk -l /dev/sde, both drives detected 2 TB, real capacity is 10TB and 4TB so next step.
    Using command from this post
    Check again with step number 2, if didn't work try this post
    If the problem still persist then try this step
    if the drives already detected with the real capacity, then do this
    Then all is good :D
    Thank you hope it helps for someone that have the same problem with me
  3. jolma's post in Cloned Parity Drive is not recognized as a new Parity Drive was marked as the answer   
    Sorry, for the late post
    rebuilding complete so the main problem is 2 harddrive are broken, that is why it is not recognized,
    so the step are:
    1. Clone/rescue each drive using ddrescue.
    2. set up new config, following this guide 
    3. Wait for parity to rebuild, Thanks
  4. jolma's post in One of drive throwing error during building array was marked as the answer   
    Thank you, here is the new diagnostics, speed is better and all drive is connected..
    so is this just sata problem or maybe sata controller problem?, because this is the 2nd time it happened. before drive B&C were unregonized so I can prepare to change its motherboard?
    tower-diagnostics-20250321-1904.zip
  5. jolma's post in 1 Disk keep Unmountable and Parity Drive take a long time to sync was marked as the answer   
    attached check without -n asks for -L command
    this is the code after run -L
    Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes 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. - 09:20:41: zeroing log - 119233 of 119233 blocks done - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata agf_freeblks 952538, counted 952537 in ag 0 agi_freecount 44, counted 43 in ag 0 finobt sb_ifree 1283, counted 1284 - 09:20:42: scanning filesystem freespace - 40 of 40 allocation groups done - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - 09:20:42: scanning agi unlinked lists - 40 of 40 allocation groups done - process known inodes and perform inode discovery... - agno = 0 - agno = 30 - agno = 15 - agno = 16 data fork in ino 4762 claims free block 590 correcting imap - agno = 1 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 31 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 32 - agno = 33 - agno = 26 - agno = 34 - agno = 27 - agno = 28 - agno = 29 - agno = 35 - agno = 36 - agno = 2 - agno = 3 - agno = 37 - agno = 38 - agno = 39 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - 09:20:45: process known inodes and inode discovery - 49984 of 49984 inodes done - process newly discovered inodes... - 09:20:45: process newly discovered inodes - 40 of 40 allocation groups done Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - 09:20:45: setting up duplicate extent list - 40 of 40 allocation groups done - check for inodes claiming duplicate blocks... - 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 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 29 - agno = 30 - agno = 31 - agno = 32 - agno = 33 - agno = 34 - agno = 35 - agno = 36 - agno = 37 - agno = 38 - agno = 39 - 09:20:45: check for inodes claiming duplicate blocks - 49984 of 49984 inodes done Phase 5 - rebuild AG headers and trees... - 09:20:47: rebuild AG headers and trees - 40 of 40 allocation groups done - 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 ... disconnected dir inode 4762, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 4761 nlinks from 2 to 3 - 09:20:50: verify and correct link counts - 40 of 40 allocation groups done Maximum metadata LSN (1969582969:78) is ahead of log (1:2). Format log to cycle 1969582972. done  

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.