Date: Thu, 14 Sep 2023 08:04:24 -0500 From: Guy Helmer <guy.helmer@gmail.com> To: Graham Perrin <grahamperrin@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Unable to access GPT disk partitions - No such file or directory Message-ID: <B6D253FD-EC6B-4630-814A-AF0F321DA8D1@gmail.com> In-Reply-To: <aa69153e-36f6-6250-1885-5e3e2434ee9f@gmail.com> References: <0CAE8FD0-9F09-4CF6-A402-DF30B039DF23@gmail.com> <b2f77c59-72a5-d690-31b5-262beaab2c62@grosbein.net> <B3D4268C-88CD-41A7-B508-ED76F41E9D10@gmail.com> <aa69153e-36f6-6250-1885-5e3e2434ee9f@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 13, 2023, at 10:54 PM, Graham Perrin <grahamperrin@gmail.com> = wrote: >=20 > On 13/09/2023 19:52, Guy Helmer wrote: >> =E2=80=A6 >>=20 >> dmesg -a: >>=20 >> $ dmesg -a >> ---<<BOOT>>--- >> =E2=80=A6 >> FreeBSD 12.0-STABLE r348375 GENERIC amd64 >> =E2=80=A6 > Maybe not relevant to the problem, your opening post mentioned FreeBSD = 13 systems alone. Right, I had attached the broken virtual disk to a FreeBSD 12 VM I had = available on the same VMware server to research and attempt to recover = the filesystems. I've since updated this working VM to 13.2 and I'm = getting a bit more informative error messages out of tools like = fsck_ufs. It's looking like either something trashed the superblocks, or the = partition offsets were changed.=20 It's quite a mystery at the moment. Regards, Guy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B6D253FD-EC6B-4630-814A-AF0F321DA8D1>