Jump to content

footballmad

Members
  • Posts

    99
  • Joined

  • Last visited

Posts posted by footballmad

  1. This is the result for disk21

     

    root@MSSTORAGE:~# fdisk -l /dev/sdac
    The primary GPT table is corrupt, but the backup appears OK, so that will be used.
    Disk /dev/sdac: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
    Disk model: ST3000DM001-1ER1
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 205CED32-7A0F-4E32-81F6-36E483C5065F

    Device     Start        End    Sectors  Size Type
    /dev/sdac1    64 5860533134 5860533071  2.7T Linux filesystem

     

    Then I started the array and the error remains.

    image.thumb.png.3d0d166472d58d35892f6643673ffcf9.png

  2. 6 hours ago, JorgeB said:

    Why did you replace disk 17 now? Log is a mess, there are hardware errors for a disk and a strange errors with disk19, you didn't start the array in normal mode so disks weren't mounted, but for now stop the rebuild and post the output of:

     

    fdisk -l /dev/sdX

     

    for all the invalid partition disks.

    Because the disk was failing.

     

    I'll post the results once home.

  3. 14 minutes ago, trurl said:

    Not related, but you seem to be installing every package from NerdPack. Do you know what any of that is for? I recommend only installing those that you use regularly.

    I know what a lot of it is for, I guess the only reason is being a wannabe nerd, trying to learn as much as I can.

     

    I appreciate your time too trurl

  4. 4 hours ago, trurl said:

    Could see that from diagnostics. Might make recovery difficult.

    Oh no, not what I wanted to hear.

     

    4 hours ago, trurl said:

    The usual and documented method.

    Would you recommend using the -L flag?

     

    4 hours ago, trurl said:

    Where did you get this idea from?

    From another post here, what's your opinion on this?

     

    Do you think the fact that I tried a different expansion card could've caused this?

     

    Any ideas on how to attempt recovery?

  5. I ran this sgdisk command and these are the results.

     

    root@MSSTORAGE:~# sgdisk -v /dev/sdc
    Caution: invalid backup GPT header, but valid main header; regenerating
    backup header from main header.

    Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
    on the recovery & transformation menu to examine the two tables.

    Warning! One or more CRCs don't match. You should repair the disk!
    Main header: OK
    Backup header: ERROR
    Main partition table: OK
    Backup partition table: ERROR

    Invalid partition data!
    Verification may miss some problems or report too many!

    Caution: The CRC for the backup partition table is invalid. This table may
    be corrupt. This program will automatically create a new backup partition
    table when you save your partitions.

    Warning! Mismatched GPT and MBR partition! MBR partition 1, of type 0x83,
    has no corresponding GPT partition! You may continue, but this condition
    might cause data loss in the future!

    Identified 2 problems!

     

    Does this information help anyone that knows more than me about this?

  6. Hi,

     

    Since a week or so, I've been having problems with my server, disk 17 and 19 were reporting errors.

     

    I wanted to replace disk 17 with a new disk so shutdown the server and changed disks.

    Upon reboot there were more errors on other disks, all using the same icybox bay (5xhdds) and breakout cable, so I changed cables and no change, thinking it was maybe the card I plugged in an old Adaptec ASR-5405 I had lying around and connected the bay to this card and restarted, I then had the error "mount error: Unsupported partition layout" on 4 of the disks.

     

    Thinking that maybe the card wasn't compatible with UNRAID (yes I should have checked first), I disconnected the card and reconnected as before but the error remains on all these drives.

     

    I tried a xfs_repair (first with -n then without) and no change.

     

    I searched on the forum and found this thread that mentions the Adaptec ASR-5405 and mount error: Unsupported partition layout errors, so I tried connecting one of the drives directly to the motherboard through SATA and still no change.

    I also wanted to try mounting the drive using Unassigned devices but instead of "mount" it wants a format, so obviously I stopped there.

     

    Can anyone please help me recover these drives please?

     

     

    msstorage-diagnostics-20210806-1936.zip

  7. 15 minutes ago, JorgeB said:

    The only risk is if you assign a data disk to a parity slot, and if you were using single parity it will still remain valid even if the data disks are in different slots.

    So no risk for the encrypted disks in s potentially wrong slot?

  8. Hello,

     

    After updating to version 6.9.2 and rebooting, all disks were unassigned and a "Stale Configuration" message was displayed in the bottom left corner.

     

    I haven't yet started the array.

    What are the risks of assigning the disks back to how they were before (I have some old screenshots) but potentially assigning a previous disk to the wrong slot, i.e. Previously Disk 1 to Disk 2 ??

    I'm 99% sure that the 2 parity disks are as they were before and have assigned these but have the warning, "All existing data on this device will be OVERWRITTEN when array is Started"

     

    Any advice is very welcome and any ideas as to why this happened also welcome.

     

    EDIT: Changed "invalid" to "Stale"

    msstorage-diagnostics-20210502-1021.zip

  9. On 10/23/2018 at 9:27 PM, Jcloud said:

    I might be wrong, but I think saarg was saying to take out this part of XML:

    
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </hostdev>

    I'm no expert, but that looks like your old video card and is the bus giving you trouble. 

     

    More expert than i am, that worked, thanks a lot to you both.

  10. 7 minutes ago, saarg said:

    This might be a bug. Either report it or delete the hostdev tags for the devices in xml mode. On phone, so can't paste what you need to remove. 

    Thanks a lot for your advice so far, if you could post when you get a moment that'd be great, I made many mistakes deleting the wrong tags.

  11. 9 minutes ago, saarg said:

    The GPU is still there. You can remove the part from the xml. 

    Can you take a screenshot of the vm template and post it? 

    Also forgive me but which part should I remove? I searched for "GPU" and found nothing.

    Thanks

  12. 7 minutes ago, saarg said:

    The GPU is still there. You can remove the part from the xml. 

    Can you take a screenshot of the vm template and post it? 

    Quote

    I'm assuming that you mean this as I have nothing else for Windows 10.

    image.png.60037f6a0c6c8e022469a057e85ab381.png

     

×
×
  • Create New...