Aviv

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

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

Aviv's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Reboot solved it. Not sure why it happen. any ideas from your experience?
  2. 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!
  3. 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
  4. Ok, so it seems the cache drive is now undetectable ๐Ÿ˜ž Trying to replace cable. wish me luck.
  5. 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?
  6. 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.
  7. Hi, My cache drive is suddenly saying: "Unmountable: No file system" Im using XFS (Encrypted). I run Extended offline smart test on the cache and it pass. I have data on the cache drive (vms, plex , and some data) so i cant just reformat it. Any tips? ๐Ÿ˜ž Thank you ๐Ÿ™‚ --- 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... sb_fdblocks 79152746, counted 80012186 - 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 - 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 = 0 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (51:10362) is ahead of log (51:9849). Would format log to cycle 54. No modify flag set, skipping filesystem flush and exiting. fatty-diagnostics-20200603-1543.zip
  8. I love the ability to mix different kind/sizes of hard drives. Would love to see vm snapshots + vm backup option. :-)
  9. I have a brand new WD Blue ssd (500gb), since beginning smart shows 231 Total bad blocks. the value did not changed after 3 days. Is this normal? Anyone using WD blue SSD?
  10. Worked for me just now ๐Ÿ™‚ Same as @Dabbner was saying, double :: applied to my situation.
  11. How is your experience with ST8000NM0055? They currently sells even cheaper comparing to ironwolf 8tb & ironwolf pro 8tb
  12. 56MiB/s is about 469.8 Mbps. my ssd model supports Sequential Write (up to) 350MB/s (SanDisk_SSD_PLUS_240GB). So i think im good. but still not sure i get the numbers right.
  13. Sorry, im new at this:) Updated my post. im getting 56MIB/s. I think its ok. as this is the speed of a sata ssd.
  14. I believe i got it all wrong.. The transfer speed show from my linux machine is in MiB's, eg I believe that 56MiB's is about 400Mbps. so, my bad. all good. right?