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.

zieko

Members
  • Joined

  • Last visited

  1. I got this still not working 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 127862855, counted 129572744 - 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 = 2 - agno = 1 - agno = 3 - agno = 0 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 (1:399635) is ahead of log (1:2). Format log to cycle 4. done
  2. I got this still not working is there any way i can extract the data from the drive (i have some data) and then reinstall my donker contaners ? Phase 1 - find and verify superblock... - block cache size set to 165768 entries Phase 2 - using internal log - zero log... zero_log: head block 399607 tail block 399603 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.
  3. I did that and got this (still not working) /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdd1: UUID="4a77133d-892f-41ed-8d94-da470b8a8514" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e078623b-01" /dev/sdb1: UUID="4a77133d-892f-41ed-8d94-da470b8a8514" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="4fefe717-01" /dev/md1p1: UUID="4a77133d-892f-41ed-8d94-da470b8a8514" BLOCK_SIZE="512" TYPE="xfs" /dev/loop2: UUID="0d43c05a-f732-4bea-8176-b3f7fb317a2e" UUID_SUB="26af330a-c53c-46fd-8f9a-165f25b2f8bb" BLOCK_SIZE="4096" TYPE="btrfs" /dev/loop0: TYPE="squashfs" /dev/sdc: PTUUID="767b0e83" PTTYPE="dos"
  4. what should i do with this command?
  5. here is the diagnostics ziekovault-diagnostics-20241107-1919.zip
  6. how do this?( I am a beginner)
  7. Hey I have nas pc running unraid with 1tb HDD as primary storage and 2tp HDD as a parity drive, one 120gb ssd as cache drive, (the cache drive had my donker containers) The problem after a clean reboot the cache drive doesn't get moutet giving an error(unmountbel drive) it can reed the cache drive but says it need to format it . I checked on the drive cabels even trying new cables checked the ram power supply nothing seemd to work please help is their is any way to mount the cache dicsk without formatting?

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.