Unmountable: Unsupported partition layout Error After power outage. All my data is gone.


Recommended Posts

I was just setting up my server after it was off for a week, and this is what I see now. image.thumb.png.1dda86350b3b61be1f67cf81ef929ee1.png

 

I was in the process up updating some containers when my daughter, 18 months old, walked over and hit the power button on the UPS. I don't even know where to start on troubleshooting this. I have read through a bunch of other posts and nothing seems to fit my situation. 

tower-diagnostics-20220117-1623.zip

Link to comment

Looks like the sort of problems people have when they try to use RAID controllers with Unraid.

 

I think the solution is to get rid of the RAID controller, figure out your disks assignments without that controller in the system, then see if you can rebuild each data disk one at a time from parity.

 

Wait for additional opinions since I don't really have personal experience with this situation.

Link to comment

I swapped out my Adaptec 71605 with an 8 port SATA card as and as I suspected I am no longer able to see my SAS drives. The controller is listed on the compatible list. https://wiki.unraid.net/Hardware_Compatibility I moved recently, and lost my second parity drive to failure when I booted everything back up. I also just moved it out of my server rack into a tower case. In doing so I lost the capability to use a backplane. I will go back through and test every setting on the controller and see if I can get it to work again. 

Link to comment

Still likely the reason for the problem, depending on what/how much of the partitions was damaged data might still be recoverable, you can try this, assuming parity is still valid:

 

-Stop the array

-Unassign one of the data disks

-Start the array

-Post new diags

 

Unraid will recreate the partition, depending on what is missing/damaged on the other disks it might work or not, if the emulated disk mounts and contents look correct you can just rebuild the disk, then repeat for the other ones, one at a time.

 

 

Link to comment
2 hours ago, JorgeB said:

Still likely the reason for the problem, depending on what/how much of the partitions was damaged data might still be recoverable, you can try this, assuming parity is still valid:

 

-Stop the array

-Unassign one of the data disks

-Start the array

-Post new diags

 

Unraid will recreate the partition, depending on what is missing/damaged on the other disks it might work or not, if the emulated disk mounts and contents look correct you can just rebuild the disk, then repeat for the other ones, one at a time.

 

 

Here are the new Diags.

tower-diagnostics-20220118-0823.zip

Additionally it looks like it may still have all the data there, but I will need to rebuild each disk one at a time? 

image.thumb.png.d78afb6e17a9b2a0be6c8a3ef7882e5d.png

Link to comment

Ok so I finished running the repair and all the disks show this:

image.thumb.png.c9603aa8710facf4358c5d59c9ab174e.png

 

They all seem to be "repaired". But I am still having issues getting them to show up in the array. I am guessing the Array is working and good because I can remove a disk and rebuild it no problem, but I would like to get all of the working in one fell swoop vs rebuilding each disk one by one.

image.thumb.png.1e6cfe4b25ef4f2a99cd59b4fd7505e0.png

As you can see I rebuilt two of them and they seem to be fine, this screenshot was taken in maintenance mode. Any ideas from here?

 

 

tower-diagnostics-20220120-1405.zip

Link to comment

According to diags disks 1 and 2 mounted, or did you format them? Screenshot is maybe in maintenance mode?

 

Jan 20 13:57:00 Tower emhttpd: shcmd (6033): xfs_growfs /mnt/disk1
Jan 20 13:57:00 Tower kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff)
Jan 20 13:57:00 Tower root: meta-data=/dev/md1               isize=512    agcount=4, agsize=244188659 blks
Jan 20 13:57:00 Tower root:          =                       sectsz=512   attr=2, projid32bit=1
Jan 20 13:57:00 Tower root:          =                       crc=1        finobt=1, sparse=1, rmapbt=0
Jan 20 13:57:00 Tower root:          =                       reflink=1
Jan 20 13:57:00 Tower root: data     =                       bsize=4096   blocks=976754633, imaxpct=5
Jan 20 13:57:00 Tower root:          =                       sunit=0      swidth=0 blks
Jan 20 13:57:00 Tower root: naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
Jan 20 13:57:00 Tower root: log      =internal log           bsize=4096   blocks=476930, version=2
Jan 20 13:57:00 Tower root:          =                       sectsz=512   sunit=0 blks, lazy-count=1
Jan 20 13:57:00 Tower root: realtime =none                   extsz=4096   blocks=0, rtextents=0
Jan 20 13:57:00 Tower emhttpd: shcmd (6034): mkdir -p /mnt/disk2
Jan 20 13:57:00 Tower emhttpd: shcmd (6035): mount -t xfs -o noatime /dev/md2 /mnt/disk2
Jan 20 13:57:00 Tower kernel: XFS (md2): Mounting V5 Filesystem
Jan 20 13:57:00 Tower kernel: XFS (md2): Ending clean mount
Jan 20 13:57:01 Tower kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff)
Jan 20 13:57:01 Tower emhttpd: shcmd (6036): xfs_growfs /mnt/disk2
Jan 20 13:57:01 Tower root: meta-data=/dev/md2               isize=512    agcount=4, agsize=244188659 blks
Jan 20 13:57:01 Tower root:          =                       sectsz=512   attr=2, projid32bit=1
Jan 20 13:57:01 Tower root:          =                       crc=1        finobt=1, sparse=1, rmapbt=0
Jan 20 13:57:01 Tower root:          =                       reflink=1
Jan 20 13:57:01 Tower root: data     =                       bsize=4096   blocks=976754633, imaxpct=5
Jan 20 13:57:01 Tower root:          =                       sunit=0      swidth=0 blks
Jan 20 13:57:01 Tower root: naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
Jan 20 13:57:01 Tower root: log      =internal log           bsize=4096   blocks=476930, version=2
Jan 20 13:57:01 Tower root:          =                       sectsz=512   sunit=0 blks, lazy-count=1
Jan 20 13:57:01 Tower root: realtime =none                   extsz=4096   blocks=0, rtextents=0

 

Link to comment

I rebuilt those disks by un-assigning them and the re-adding them. 

1 minute ago, JorgeB said:

According to diags disks 1 and 2 mounted, or did you format them? Screenshot is maybe in maintenance mode?

 

Jan 20 13:57:00 Tower emhttpd: shcmd (6033): xfs_growfs /mnt/disk1
Jan 20 13:57:00 Tower kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff)
Jan 20 13:57:00 Tower root: meta-data=/dev/md1               isize=512    agcount=4, agsize=244188659 blks
Jan 20 13:57:00 Tower root:          =                       sectsz=512   attr=2, projid32bit=1
Jan 20 13:57:00 Tower root:          =                       crc=1        finobt=1, sparse=1, rmapbt=0
Jan 20 13:57:00 Tower root:          =                       reflink=1
Jan 20 13:57:00 Tower root: data     =                       bsize=4096   blocks=976754633, imaxpct=5
Jan 20 13:57:00 Tower root:          =                       sunit=0      swidth=0 blks
Jan 20 13:57:00 Tower root: naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
Jan 20 13:57:00 Tower root: log      =internal log           bsize=4096   blocks=476930, version=2
Jan 20 13:57:00 Tower root:          =                       sectsz=512   sunit=0 blks, lazy-count=1
Jan 20 13:57:00 Tower root: realtime =none                   extsz=4096   blocks=0, rtextents=0
Jan 20 13:57:00 Tower emhttpd: shcmd (6034): mkdir -p /mnt/disk2
Jan 20 13:57:00 Tower emhttpd: shcmd (6035): mount -t xfs -o noatime /dev/md2 /mnt/disk2
Jan 20 13:57:00 Tower kernel: XFS (md2): Mounting V5 Filesystem
Jan 20 13:57:00 Tower kernel: XFS (md2): Ending clean mount
Jan 20 13:57:01 Tower kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff)
Jan 20 13:57:01 Tower emhttpd: shcmd (6036): xfs_growfs /mnt/disk2
Jan 20 13:57:01 Tower root: meta-data=/dev/md2               isize=512    agcount=4, agsize=244188659 blks
Jan 20 13:57:01 Tower root:          =                       sectsz=512   attr=2, projid32bit=1
Jan 20 13:57:01 Tower root:          =                       crc=1        finobt=1, sparse=1, rmapbt=0
Jan 20 13:57:01 Tower root:          =                       reflink=1
Jan 20 13:57:01 Tower root: data     =                       bsize=4096   blocks=976754633, imaxpct=5
Jan 20 13:57:01 Tower root:          =                       sunit=0      swidth=0 blks
Jan 20 13:57:01 Tower root: naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
Jan 20 13:57:01 Tower root: log      =internal log           bsize=4096   blocks=476930, version=2
Jan 20 13:57:01 Tower root:          =                       sectsz=512   sunit=0 blks, lazy-count=1
Jan 20 13:57:01 Tower root: realtime =none                   extsz=4096   blocks=0, rtextents=0

 

 

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
Reply to this topic...

×   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.