FreeBSD, gmirror, hosed disklabel, or something

taco_truck_tom

Okay so, here is my situation: I had a gmirror instance set up for two 2TB drives, ad4 and ad6. Yesterday, my system decided to refuse to reboot, complaining about a problem with ad4. The drive seemed to be spinning up then spinning down repeatedly. I assumed it was dead, and shut down the server and removed it. I went to RMA it, (It's only 7~ months old), and the seagate website required a code from having SeaTools analyze the drive to ensure...

Originally asked by tip120 on Stack Exchange (superuser) (CC BY-SA 4.0).

uphilltech

Great question — answering as the UphillTech team:

I managed to fix this on my own with the following steps: Delete/Destroy the ad6s1 slice with gpart. Delete/Destroy the ad6 geom with gpart. Re-create both the geom, and then the slice. Edit the disklabel and add the parition back. Mount. The partition is mounted and all my files seem to be intact, however, fsck is complaining rather loudly about soft updates, but the problem seems to have been resolved.

Full answer by tip120: https://superuser.stackexchange.com/a/421435 (CC BY-SA 4.0).

Need it done for your business? UphillTech.