Jump to content

biiiink

Members
  • Posts

    58
  • Joined

  • Last visited

Posts posted by biiiink

  1. Hello

     

    I have a Supermicro CSE-826A-R920LPB with a BPN-SAS-826A backplane

    The mobo is SUPERMICRO MBD-X10SRL-F

    it has:

    2 x PCI-E 3.0 x8 (in x16) slots
    2 x PCI-E 3.0 x8 slots

    2 x PCI-E 3.0 x4 (in x8) slots Auto-switch to 1 x8 and 1 x0
    1 x PCI-E 2.0 x4 (in x8) slot

     

    I have 12 drives.  I've been looking for an HBA/Extender

     

    I've been looking at these HBAs:

    https://www.ebay.com/itm/Dell-VGXKD-LSI-9207-8i-6Gbps-SAS-PCIe-3-0-HBA-P20-IT-Mode-ZFS-FreeNAS-unRAID/162862201664?hash=item25eb57fb40:g:kmQAAOSwwste8S8V

     

    https://www.ebay.com/itm/Genuine-LSI-6Gbps-SAS-HBA-LSI-9211-8i-9201-8i-P20-IT-Mode-ZFS-FreeNAS-unRAID/163846248833?hash=item2625ff5981:g:shEAAOSwPKZdbst~

     

    Although I'm open to recommendations.

     

    As far as an expander, I haven't been able to find one that is low profile to fit in the chassis, so if anyone knows of one that would work, that would be great.

  2. Im running the filesystem Check and it seems to be stuck.

     

    Phase 1 - find and verify superblock...
    couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!!
    
    attempting to find secondary superblock...
    ..found candidate secondary superblock...
    unable to verify superblock, continuing...
    ....found candidate secondary superblock...
    unable to verify superblock, continuing...

    I read somewhere that this check can take a long time, but its been running for over 20 hours now.

     

     

    Screen Shot 2020-10-25 at 10.22.23 AM.png

  3. I was having issues with the Ombi docker container, so i removed it and was going to add it again.  It seemed to remove fine, but the container was still showing in the list of Docker containers.  I tried removing again and received and Execution error.  Tried starting the container and same error.

     

    Checked the appdata share and the ombi folder is not there.  I do see the xml file for it in flash/config/plugins/DockerMan/templates-user.

    I've also tried rebooting the server, but it still shows the container

    Not sure what else I could try to get container removed

  4. Just to update this thread:

     

    It was basically determined that nothing would fix the filesystem.  It was just too corrupt.  However, I could still mount the drive and see all the files.  So I mounted the drive using the unassigned devices plugin, and manually copied all the folders to an empty drive.  After checking the drive to ensure that there were no issues, i used the "new config" tool to create a new drive configuration.  Reassigned all the drives, and I now have my Media share back.

     

    Thank you to everyone who offered their help/advice/opinion

  5.  

    1 hour ago, trurl said:

    Maybe you could just try to copy whatever you can from that disk, have Unraid reformat it, and then see if the share comes back.

    I attempted this through unbalance, but it came back with this:

    1125402496_ScreenShot2019-01-02at1_44_30PM.thumb.png.490299abdee4da591f284e358dcebcda.png

     

    So im going to do it manually.  I will report back when its complete

  6. 23 minutes ago, trurl said:

    If that disk has the files but the user share doesn't then maybe that disk isn't the problem. Other things can break user shares, and other things can cause a user to report an empty share when user shares aren't broken.

     

    What specifically are you looking at that makes you think the share is empty?

     

    Go to Main - Array Devices, click on the folder icon at the far right on the same line as the disk, and post a screenshot.

     

    Go to User Shares, click on the Compute... link next to the share in question, and after it gives the result, post a screenshot.

    Both of those screenshots are in my original post.  Also, if i connect to the server and check the Media share, it shows as empty as well.

     

    I also notice that this error shows up twice when i go into the media share in the web Gui: (It also shows up, but only once, when i go into the Media folder on disk 3, but not on any other disk)

    Jan 2 06:49:25 Tower kernel: XFS (md3): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x156c69f68 xfs_inode_buf_verify
    Jan 2 06:49:25 Tower kernel: XFS (md3): Unmount and run xfs_repair
    Jan 2 06:49:25 Tower kernel: XFS (md3): First 128 bytes of corrupted metadata buffer:
    Jan 2 06:49:25 Tower kernel: 000000005491da45: be fa cc 07 c4 c8 71 c1 d6 3e 51 3e a0 cb af dc ......q..>Q>....
    Jan 2 06:49:25 Tower kernel: 0000000033c25846: d1 56 aa 91 0b c1 90 9f 95 2f af 7d 54 ee d1 a9 .V......./.}T...
    Jan 2 06:49:25 Tower kernel: 0000000040618539: 1d 5d 78 9e 52 83 f6 b8 30 a5 de 46 6c 4d 1e f3 .]x.R...0..FlM..
    Jan 2 06:49:25 Tower kernel: 000000009e9334aa: 2a 1d 6a 11 a3 33 f4 1a 4f cf bd 60 8c 3b 09 e6 *.j..3..O..`.;..
    Jan 2 06:49:25 Tower kernel: 000000009881fdfb: d4 38 5a e6 42 bf bf 8b 10 25 73 6a f1 58 5a f5 .8Z.B....%sj.XZ.
    Jan 2 06:49:25 Tower kernel: 000000004113fee1: 93 98 cb 16 97 71 05 c2 a0 08 32 6b 5a 4e ab 26 .....q....2kZN.&
    Jan 2 06:49:25 Tower kernel: 0000000049cb44db: 4e 32 80 f0 e3 72 0a 79 b8 0d 1a 64 68 c6 95 70 N2...r.y...dh..p
    Jan 2 06:49:25 Tower kernel: 00000000cc661843: 82 bb 13 a9 e6 a8 de 65 f7 b2 8f 14 6e 55 f4 ad .......e....nU..
    Jan 2 06:49:25 Tower kernel: XFS (md3): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x156c69f68 len 32 error 117
    Jan 2 06:49:25 Tower kernel: XFS (md3): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
    Jan 2 06:49:25 Tower kernel: XFS (md3): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x156c69f68 xfs_inode_buf_verify
    Jan 2 06:49:25 Tower kernel: XFS (md3): Unmount and run xfs_repair
    Jan 2 06:49:25 Tower kernel: XFS (md3): First 128 bytes of corrupted metadata buffer:
    Jan 2 06:49:25 Tower kernel: 00000000aa3c7d84: be fa cc 07 c4 c8 71 c1 d6 3e 51 3e a0 cb af dc ......q..>Q>....
    Jan 2 06:49:25 Tower kernel: 00000000c13b8090: d1 56 aa 91 0b c1 90 9f 95 2f af 7d 54 ee d1 a9 .V......./.}T...
    Jan 2 06:49:25 Tower kernel: 00000000cb0ed316: 1d 5d 78 9e 52 83 f6 b8 30 a5 de 46 6c 4d 1e f3 .]x.R...0..FlM..
    Jan 2 06:49:25 Tower kernel: 00000000de4d9b94: 2a 1d 6a 11 a3 33 f4 1a 4f cf bd 60 8c 3b 09 e6 *.j..3..O..`.;..
    Jan 2 06:49:25 Tower kernel: 0000000021fff399: d4 38 5a e6 42 bf bf 8b 10 25 73 6a f1 58 5a f5 .8Z.B....%sj.XZ.
    Jan 2 06:49:25 Tower kernel: 000000008e981e48: 93 98 cb 16 97 71 05 c2 a0 08 32 6b 5a 4e ab 26 .....q....2kZN.&
    Jan 2 06:49:25 Tower kernel: 00000000808a9410: 4e 32 80 f0 e3 72 0a 79 b8 0d 1a 64 68 c6 95 70 N2...r.y...dh..p
    Jan 2 06:49:25 Tower kernel: 00000000b2bf6473: 82 bb 13 a9 e6 a8 de 65 f7 b2 8f 14 6e 55 f4 ad .......e....nU..
    Jan 2 06:49:25 Tower kernel: XFS (md3): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x156c69f68 len 32 error 117
    Jan 2 06:49:25 Tower kernel: XFS (md3): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.

     

  7. So the xfs_repair is still running.  Been running for nearly 24 hrs.  Is this normal?  The disk is 3GB and would be probably 80% full.

     

    Most recent thing i see in the status window is:

    Phase 7 - verify and correct link counts...
    resetting inode 131 nlinks from 9 to 8
    resetting inode 4427235023 nlinks from 5 to 4
    resetting inode 222 nlinks from 5 to 4
    resetting inode 2147483776 nlinks from 421 to 417
    resetting inode 2147483866 nlinks from 5 to 4

     

×
×
  • Create New...