How to check raid1 in freebsd when booting from LiveCd?

Question

FreeBSD

Good day.
A terrible thing happened.
FreeBSD (RAID1 as I understand it))
Hetzner had problems with the network, during this time the server was forcibly rebooted (themselves).
As a result, we got a non-working system.
KVM is not working. LARA immediately hangs on loading. Those. displays what is on the screen, but the keyboard does not respond. At the same time, everything is fine until the system boots, and then it only displays.
Here's what I get after the system boots.

At the same time, the keyboard no longer responds (even changed the piece of iron, it did not help).
And if you boot from livecd we see that

gpart list
Geom name: ada0
modified: false
state: CORRUPT
fwheads: 16
fwsectors: 63
last: 3907029133
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: ada0p1
   Mediasize: 65536 (64K)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1048576
   Mode: r0w0e0
   rawuuid: 804eac94-4ad1-11e3-9df1-001e67995201
   rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
   label: (null)
   length: 65536
   offset: 1048576
   type: freebsd-boot
   index: 1
   end: 2175
   start: 2048
2. Name: ada0p2
   Mediasize: 4294967296 (4.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 8059aba1-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: swap
   length: 4294967296
   offset: 1114112
   type: freebsd-swap
   index: 2
   end: 8390783
   start: 2176
3. Name: ada0p3
   Mediasize: 1996102835200 (1.8T)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 806e24e2-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
   label: boot
   length: 1996102835200
   offset: 4296081408
   type: freebsd-ufs
   index: 3
   end: 3907029133
   start: 8390784
Consumers:
1. Name: ada0
   Mediasize: 2000398934016 (1.8T)
   Sectorsize: 512
   Mode: r0w0e0

Geom name: ada1
modified: false
state: CORRUPT
fwheads: 16
fwsectors: 63
last: 3907029133
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: ada1p1
   Mediasize: 65536 (64K)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1048576
   Mode: r0w0e0
   rawuuid: 804eac94-4ad1-11e3-9df1-001e67995201
   rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
   label: (null)
   length: 65536
   offset: 1048576
   type: freebsd-boot
   index: 1
   end: 2175
   start: 2048
2. Name: ada1p2
   Mediasize: 4294967296 (4.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 8059aba1-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: swap
   length: 4294967296
   offset: 1114112
   type: freebsd-swap
   index: 2
   end: 8390783
   start: 2176
3. Name: ada1p3
   Mediasize: 1996102835200 (1.8T)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 806e24e2-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
   label: boot
   length: 1996102835200
   offset: 4296081408
   type: freebsd-ufs
   index: 3
   end: 3907029133
   start: 8390784
Consumers:
1. Name: ada1
   Mediasize: 2000398934016 (1.8T)
   Sectorsize: 512
   Mode: r0w0e0

Geom name: diskid/DISK-Z1X0V2H6
modified: false
state: CORRUPT
fwheads: 16
fwsectors: 63
last: 3907029133
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: diskid/DISK-Z1X0V2H6p1
   Mediasize: 65536 (64K)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1048576
   Mode: r0w0e0
   rawuuid: 804eac94-4ad1-11e3-9df1-001e67995201
   rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
   label: (null)
   length: 65536
   offset: 1048576
   type: freebsd-boot
   index: 1
   end: 2175
   start: 2048
2. Name: diskid/DISK-Z1X0V2H6p2
   Mediasize: 4294967296 (4.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 8059aba1-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: swap
   length: 4294967296
   offset: 1114112
   type: freebsd-swap
   index: 2
   end: 8390783
   start: 2176
3. Name: diskid/DISK-Z1X0V2H6p3
   Mediasize: 1996102835200 (1.8T)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 806e24e2-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
   label: boot
   length: 1996102835200
   offset: 4296081408
   type: freebsd-ufs
   index: 3
   end: 3907029133
   start: 8390784
Consumers:
1. Name: diskid/DISK-Z1X0V2H6
   Mediasize: 2000398934016 (1.8T)
   Sectorsize: 512
   Mode: r0w0e0

Geom name: diskid/DISK-Z1X0TYDC
modified: false
state: CORRUPT
fwheads: 16
fwsectors: 63
last: 3907029133
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: diskid/DISK-Z1X0TYDCp1
   Mediasize: 65536 (64K)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1048576
   Mode: r0w0e0
   rawuuid: 804eac94-4ad1-11e3-9df1-001e67995201
   rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
   label: (null)
   length: 65536
   offset: 1048576
   type: freebsd-boot
   index: 1
   end: 2175
   start: 2048
2. Name: diskid/DISK-Z1X0TYDCp2
   Mediasize: 4294967296 (4.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 8059aba1-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: swap
   length: 4294967296
   offset: 1114112
   type: freebsd-swap
   index: 2
   end: 8390783
   start: 2176
3. Name: diskid/DISK-Z1X0TYDCp3
   Mediasize: 1996102835200 (1.8T)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1114112
   Mode: r0w0e0
   rawuuid: 806e24e2-4ad1-11e3-9df1-001e67995201
   rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
   label: boot
   length: 1996102835200
   offset: 4296081408
   type: freebsd-ufs
   index: 3
   end: 3907029133
   start: 8390784
Consumers:
1. Name: diskid/DISK-Z1X0TYDC
   Mediasize: 2000398934016 (1.8T)
   Sectorsize: 512
   Mode: r0w0e0

On a working system, I needed to check the
gm0p3 partition
And when booting from livecd, do I need to check 2 partitions?
ada0p3
ada1p3
Something tells me that it would be more correct to build RAID1 and then check it. But how to do that?
Or check one of the RAID1 partitions? and then make settings so that only one disk works, and then just reassemble the mirror?
What do you advise?
what is the course of action?

Answer 1

We boot from a lifeseat or a singleuser, then gmirror load load the free module to work with the raid, look at the state of the gmirror status raid, then if there is degradation and interest, then fsck -y on the gm partition, in no case not on the physical one, but then you can't screw up the system. If there is no interest, and one of the disks stupidly fell out, then gmirror forget gm0 - we make the raid forget the dead disk, put a new disk get some live data somewhere.

Answer 2

Have you tried running fsck for partitions from single user mode?
To answer yes to all requests, you will need to specify the -y switch