Aviv

Members
 View Profile  See their activity

  • Posts

    27

  • Joined

  • Last visited

 Content Type 

Posts posted by Aviv

    Cant access vm after upgrading to 6.12.6

    in General Support

    Posted · Edited by Aviv
    Edit: Its working for me only if i access the vnc via incognito.

    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

    [SOLVED] XFS encrypted Cach - Unmountable file system

    in General Support

    Posted · Edited by Aviv

    6 minutes ago, johnnie.black said:

    Yes.

    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?

     

     

     

    [SOLVED] XFS encrypted Cach - Unmountable file system

    in General Support

    Posted · Edited by Aviv

    4 hours ago, johnnie.black said:

    There's always same data loss risk when repairing a filesystem, but usually nothing major with XFS.

    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.

     

    [SOLVED] XFS encrypted Cach - Unmountable file system

    in General Support

    Posted · Edited by Aviv

    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

    Seagate Drive Lineup

    in Storage Devices and Controllers

    Posted

    On 7/23/2019 at 5:39 PM, Titus said:

    I would honestly jump to 8tb it might suck hitting the wallet but space is worth it. I had a 720xd with 12x2tb and it was full after the day I setup the array. I just ordered 4x8tb ST8000NM0055 and im about at 20tb since I finaly backed up my movie collection but havent got around to compression yet. but with my current server build I should be able to upgrade to 8 more drives and would still pay the premium for larger drives since for me I will not have to upgrade for quiet some years. So save yourself the headache  and get the bigger drives even though drive prices are falling quick because of sizes but purchasing more drives often is not cheaper than bigger drives now

    How is your experience with ST8000NM0055? They currently sells even cheaper comparing to ironwolf 8tb & ironwolf pro 8tb

    6.7.2 Slow write speeds with cache enable

    in General Support

    Posted

    Hi! :)
    Im getting about 55mbs when using SSD as a cache when transferring from my linux machine to unraid.

    Writing directly to the ssd using "unassigned plugin" yield about 70-80mbs only.

    both computers are connected with 1gb connection.

    The unraid build is old hardware:
    I5-650 cpu, 8gb ddr3 ram. 
    IronWolf pro 4tb X 2 + 1 Sandisk 250gb ssd.

    Any tips regarding how to debug it? (im new!)