Jump to content
  • [6.9.2] Unsupported partition layout


    bwnautilus
    • Closed Urgent

    After upgrading from 6.8.3 to 6.9.2 two of my disks are indicating Unsupported partition layout in the main tab.  Rather than taking them out of the array and running a filesystem check I decided to downgrade back to 6.8.3.  The error went away.  I've attached pics and diagnostics of the system running on 6.9.2 and 6.8.3.  Is this a bug in 6.9.2 or is my system misconfigured?  FYI I did reboot 6.9.2 in safe mode but the disk error still persisted.  Thank you.

     

    UPDATE: replaced the two drives that wouldn't mount under 6.9.2, rebuilt the array, 6.9.2 now recognizes the drives.

    Unraid6.9.2.jpg

    Unraid6.8.3.jpg

    6.9.2-tower-diagnostics-20210426-2047.zip 6.8.3-tower-diagnostics-20210426-2100.zip




    User Feedback

    Recommended Comments

    Got the same problem. So I landed here. See:

    Only now when I upgrade the BTRFS cache pool is broken too:image.thumb.png.ab4628e6e2da49bec84da4b4169a731c.png
     

    in detail from first cache SSD, file system status shows:

    image.png.e403309c525bf1adafc8819dd2533d3c.png

     

    Somehow on 6.8.3 in the Docker tab I cannot update the Dockers anymore:
    ** placeholder until I can revert to 6.8.3 and make a screenshot **

     

    Hexdump on Disk1: 

    hexdump -C -n 512 /dev/sdc
    00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    000001c0  02 00 00 ff ff ff 01 00  00 00 ff ff ff ff 00 00  |................|
    000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
    00000200

     

    Hexdump on 1st Cache drive:

    hexdump -C -n 512 /dev/sdd
    00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    000001c0  00 00 83 00 00 00 40 00  00 00 70 6d 70 74 00 00  |[email protected]..|
    000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
    00000200

     

    Hexdump on 2nd Cache drive:

    hexdump -C -n 512 /dev/sdb
    00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    000001c0  00 00 83 00 00 00 40 00  00 00 70 6d 70 74 00 00  |[email protected]..|
    000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
    00000200

     

    Anonymized system report added. 

     

    In 

    There is mentioned that this will be fixed. Will this be done on in 6.9.4? 


    I am a bit nervous about not being able to update because of missing the latest security patches and such. 


    I'll have to look for a few reasonable (most of them where in this server and have some errors) working hard disks to backup Disk1 to and format it afterwards and restore the backups to it. Still this feels like a big hurdle for upgrading to the latest version. 

     

    I don't mind reformatting the BTRFS cache pool as I have done so more than once because my system is rather sensitive it seems.

     

    I am still saving for an upgrade to a new AMD system (a Ryzen 7 3700X on ASRock Fatal1ty X370 Pro Gaming with ECC RAM Corsair Vengeance RGB Pro Black 32GB DDR4-3200 CL16 ECC quad kit - don't need RGB as I like to keep it dark in the room, but only one I could find that has ECC), cos I'm thinking about running Plex and a few VMs adding to the current Dockers its running atm. And with my current build (I swapped out with another system, because of the PCI-E add-in card seemed unreliable) only has SATA300 ports and it can't run the SSDs at full speed. -- this might be for another thread... is there one?

     

     

     

     

    pcus-diagnostics-20210518-0901.zip

    Edited by Ymetro
    Link to comment

    Sigh, this will never be read will it? Even not sure if the report I send in Unraids' internal feedback system will be picked up. (No confirmation of whatsoever). I get it - it's not a full time job for the developers, but still...

     

    So I got back 2x 16TB Seagate IronWolf Pros from my RMA'd 2x 14TB Seagate IronWolfs (🤔can't remember if these are Pros or not) - A Big Thank You To Seagate! 👍 (and a FU to Amazon 😡) - I decided to copy the disk that isn't recognized by 6.9.2 and copy it back from the new 16TB disk (Precleared first) after upgrading to 6.9.2 and formatting it. 

     

    So the 1st replaces my 2x 6TB the 2nd one is for secure the array with parity. 


    Now I am in the process of copying the almost 14TB dat to the 16TB drive via Midnight Commander in a detachable screen console, as rsync didn't finish with the '--info=progress2' option and broke in the terminal. (Too much data?) 
    This takes days...

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...