Hello,

After booting the NAS, one of the drive was not detected

 

 

I shut down the NAS, checked the SATA connector and changed the molex connector, but now Unraid doesn't even detect a file system

 

Any help would be appreciated.

fractal-diagnostics-20231228-2135.zip

Dec 28 21:16:33 fractal kernel: BTRFS error (device md1p1): parent transid verify failed on logical 812187648 mirror 1 wanted 1434549 found 544
Dec 28 21:16:33 fractal kernel: BTRFS error (device md1p1): parent transid verify failed on logical 812187648 mirror 2 wanted 1434549 found 544

 

This error is usually fatal, and the transid is wrong by a lot, this is not normal when just a few writes are lost, you can try btrfs restore from here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

 

Forgot to mention, since disk1 looks healthy you can also see if the actual disk still mounts.

Hello,

Thanks for the help.
When you say "you can also see if the actual disk still mounts." do you means using the Format option in the GUI or via the mount command you linked before ?

Never format, you can unassign the disk and see if it mounts with UD

Both options failed

 

 

So I guess I can either check the btrfs mailing list or switch the disk and rebuild the array ?

Edited December 29, 20232 yr by Guybrush

Try connecting the disk to a different SATA port using different cables, that errors is not logged as a disk problem and SMART looks OK

I changed the sata cable and port and restore seems to be working for now, also based on the error it seems even the new cable might have an issue

 

Edited December 30, 20232 yr by Guybrush
added image

That still looks like a cabling issue.    Make sure the power side of the cabling is also OK and avoid using power splitters if possible.  You could try swapping cables over between drives to see if the issue follows the drives or the cables.

 

Just a thought - you have not recently added a new drive so that the PSU might now be struggling under max load?

I replaced some of the drive, but it was 3 months ago.
PSU is 350 watts which should be enough for 7 drives, but unfortunately it's not modular, so splitters are the only away for now.

2 minutes ago, Guybrush said:

so splitters are the only away for now.

 

If you must use them then try and avoid putting too many drives on a splitter as this can lead to voltage sags under load.   SATA->SATA splitters are more prone to this than Molex->SATA splitters.

I switched the PSU to a bigger one, and also I don't have disk errors anymore, I still get the "Unmountable: Unsupported partition layout" error

fractal-diagnostics-20240101-1134.zip

If the partition is the only issue a rebuild should fix it, if parity is valid, stop the array, unassign disk1, start the array and post new diags.

I finished the rebuild but get the same issue, also now i only have the option to format the drive

fractal-diagnostics-20240102-1336.zip

On 1/1/2024 at 12:01 PM, JorgeB said:

start the array and post new diags.

 

Here are the diag after starting the array

fractal-diagnostics-20240102-1534.zip

You assigned disk1 again.

My mistake, here the diag with the array started and disk 1 unassigned

fractal-diagnostics-20240102-1739.zip

The emulated disk is corrupt, also the actual disk appears to have a corrupt MBR, post the output of 

sgdisk /dev/sdb

 

Sorry, it should have been:

 

gdisk /dev/sdb

 

Here is the result

Hit ctrl+c to abort and now post output of

fdisk -l /dev/sdb

 

Seems like it's detecting a 2TB partition instead of the expected 9.1T

 

Edited January 3, 20242 yr by Guybrush

Yep, and it's not a GPT partition how it should be, and not even starting on the correct sector, not sure what happened there, you can try to create a partition with the correct layout, if the filesystem is still there it *should* work:

 

sgdisk -o -a 8 -n 1:32K:0 /dev/sdX

 

Then reboot first and see if the disk mounts with UD