Jump to content

jpimlott

Members
  • Posts

    153
  • Joined

  • Last visited

Posts posted by jpimlott

  1. New problem  

    when doing a xfsrepair the log get full and it stops 

     

    Metadata corruption detected at 0x44e910, xfs_bmbt block 0x28d2ea458/0x1000
    libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x28d2ea458/0x8
    Metadata corruption detected at 0x44e910, xfs_bmbt block 0x28d079b50/0x1000
    libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x28d079b50/0x8
    Maximum metadata LSN (1095979799:38281785) is ahead of log (1:2).
    Format log to cycle 1095979802

     

     

    How do i go forward from here?

  2. I have a unraid box with 6.9 running with 2 6tb  parity drives and 9 6 or 4 tb array drives.

    One of the 4 tb drives failed and is disabled with many read failures.

    I bought 10 TB drive to replace one of the parity drives then move it to the dead array drive.

     

    What is the safest way of doing this ?

    Can they be done at the same and is that safer than :

    Moving the parity drive to replace the array drive and rebuild 

    Then install new party drive .

     

    John 

  3. I redid all the power and sata wiring making sure that each 5in3 3in2 gets power from 2 different home cables.

    found one questionable port/cable changed to one on the marvel controllers.

    disk 3 is happy and is rebuilding disk 2 and party 1, at about 95 meg bytes per sec.

    That slower than normal but assume it is because one party and one disk needs building and the disk is need to generated before the party

    can be calculated.

  4. When drives stopped working the drive light was stuck on,

    I also tried reseating the drives and removed from the array and restarted and re-added.

    After doing that disk 2 had real issues in writing. It would go slow then stop then back to med speed.

    I later tried to just rebuild party 1 and was building fast 140 MBs then disk 3 dropped off. 

    I am copying data off disk 2 now to a Linux machine and so far so good

  5. System was up and running fine. One failed (drive 2 ) with a drive light stuck on.  With in a minute or so the party num 1 dropped out,  I removed the bad drive and reset the party and started rebuilding the array. It got to about 10% and drive 3 dropped out.

    I think it is still good but now i cant rebuild as i have 3 disks missing.  I think drive 3 is good  i would like to make it good and start again.  The array is in that stat right now and have done nothing to it. 

    tower-diagnostics-20210910-0044.zip

  6. 14 hours ago, dlandon said:

    There should be an entry in the smb-extras.conf file for the share.  I don't see that.  It appears you may using active directory for SMB shares.  Why are you doing that?  I'm not sure how UD shares work on active directory.

    I am doing a new permissions on the server now. It would not connect with it set for AD.

    That took an hour. Now it does not allow access to any of the shares except by ip address.

    When using name it says can not access check spelling blah blah

     

    New diagnostics with AD off below.

    This is after running new permissions.

     

     

    tower-diagnostics-20181128-2017.zip

  7. I am using unassigned devices plugin.  It mounts and formats the drives fine.  An USB drive mounts fine also.

    I can logon to the server from a terminal window and able to access the mount point. I can add directories and

    view them in unraid GUI.

    The shares are never created.

    I have tried deleted the partition and recreated it. Still no luck with the shares.

    I dont know why they are not showing up.

    Sharing is turned on for SMB and shared on the unassigned drives app.

    John

×
×
  • Create New...