April 11, 20224 yr I'm working on shrinking my array as I recently got larger capacity drives. I followed the guide for performing the shrink and after performing a new config and verifying the drives were assigned correctly I went to start the array and got that error message on one of the disks that was working previously. I've gone through and started the array in maintenance mode and run a disk check on the drive but that didn't resolve the issue. Any ideas on what I can do to resolve the issue or should I just start running through recovery options?
April 11, 20224 yr Community Expert 1 minute ago, Crazywatermelon said: I've gone through and started the array in maintenance mode and run a disk check on the drive but that didn't resolve the issue. That's a partition error, not filesystem, so fsck won't fix it. If parity is valid you can make Unraid rebuild that disk, and at that time the partition will be correctly recreated, to check you can unassign that disk and start the array, if the emulated disk mounts you can then rebuild on top.
April 11, 20224 yr Author Parity isn't valid since I was doing an array shrink. Any options to try to repair the partition?
April 11, 20224 yr Community Expert Depends on what exactly is wrong with the partition, Unraid requires a specific MBR signature, if the problem is there it will still mount with UD, you can them copy the data, if the partition itself is damaged you can try to fix it with testdisk, or use a file recovery util like UFS explorer to try and recover the data.
April 11, 20224 yr Author Tesdisk sees the partition and I can write the partition to the disk but its still showing with the same error. Unassigned disk also won't mount it. I'll see if theres anything else I can think of and if not go through recovery options.
April 11, 20224 yr Community Expert 13 minutes ago, Crazywatermelon said: Unassigned disk also won't mount it. Even after fixing with testdisk? Try rebooting if you didn't yet, if it still doesn't work you can try mounting manually while specifying the filesystem, if it still doesn't work file recovery util is the best bet.
April 11, 20224 yr Author 1 minute ago, JorgeB said: Even after fixing with testdisk? Try rebooting if you didn't yet, if it still doesn't work you can try mounting manually while specifying the filesystem, if it still doesn't work file recovery util is the best bet. Yes the issue is TestDisk is writing the partition as ~ 2MB. Its an 8 TB disk so a full scan is going to take much longer but I think I'll run that and see if TestDisk pulls up any other partitions.
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.