Aviv

Members
  • Posts

    27
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Aviv's Achievements

Noob

Noob (1/14)

0

Reputation

  1. What can happen if i upgrade and i did not installed the plugin?
  2. Hello! For Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) Should I / Must I install a driver? if yes which one from the community apps? Thank you
  3. Hi! As it seems goCoax MoCA 2.5 are no longer available on Amazon 😞 , did anyone had luck combining goCoax MoCA 2.5 adapters with ScreenBeam MoCA 2.5 adapters and can share from his experience? Thanks
  4. After upgrading to 6.12.6, I cant access my vm by clicking on VM console(VNC) from the vm unraid GUI - It says "no connection". Edit: Its working for me only if i access the vnc via incognito. Any tips? Thanks
  5. Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) should i upgrade the unraid version?
  6. Same issue here, cant connect - unknown error - i think its related to crashplan client itself as im not using the docker.
  7. Reboot solved it. Not sure why it happen. any ideas from your experience?
  8. When im trying to start a vm, i receive this error: " Cannot get interface MTU on 'virbr0': No such device" It seems my virbr0 interface has gone away? Any tips? 🙂 Thank you!
  9. i unplug and re-plug the sata + power cable and it seems good now. will take a close look on this one for few days
  10. Ok, so it seems the cache drive is now undetectable 😞 Trying to replace cable. wish me luck.
  11. Tried. Now im receiving this error: "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. Invalid block length (0x0) for buffer Log inconsistent (didn't find previous header) empty log check failed fatal error -- failed to clear log" I did a second try and receive this: hase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Invalid block length (0x0) for buffer Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... sb_fdblocks 79152746, counted 80012186 - 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 = 1 - agno = 2 - agno = 0 - 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... Maximum metadata LSN (51:10387) is ahead of log (1:2). Format log to cycle 54. done. Now im able to mount. I dont see any folder called "Lost+found". what does that mean?
  12. Thank you, I tried to run it with no 'n' param and receive this error: "Phase 1 - find and verify superblock... 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." Just to make sure, should I run it now with the -L option or there is a better option? Thank you again for your kind help.