Date: Wed, 19 Apr 2000 21:48:39 -0700 From: "J.D. Falk" <jdfalk@mail-abuse.org> To: freebsd-hackers@freebsd.org Subject: Corrupted disk label and related issues (fwd) Message-ID: <20000419214839.B13391@mail-abuse.org>
next in thread | raw e-mail | index | archive | help
I sent this to freebsd-questions yesterday, and didn't get any responses...looks like Andrew had a similar situation about a month ago, and found a solution which I'm trying to adapt to my own problem. Thing is, I can't even get to the individual partitions like he did -- I keep getting "Device not configured" and the like. Any advice? ----- Forwarded message from "J.D. Falk" <jdfalk@mail-abuse.org> ----- Date: Wed, 19 Apr 2000 03:47:48 -0700 From: "J.D. Falk" <jdfalk@mail-abuse.org> To: freebsd-questions@freebsd.org Subject: Corrupted disk label and related issues Message-ID: <20000419034747.A5527@mail-abuse.org> Yesterday a drive which I'd been meaning to replace died in a generally unhappy manner -- after much research and general (mostly unrelated) replacement of hardware, I (with help from some friends) tracked it down to disklabel problems and did a bunch of work trying to fix that. The way things stand now, `disklabel -r ad3` comes up with the correct information about eight times out of ten; other times, it'll say "bad pack magic number (label is damaged, or pack is unlabeled)". I managed to dd the entire contents of the disk to another, more functional slice elsewhere. So, the data is still all there in one form or another. If I could find out the exact start (after boot foo) of the partitions, I could dd each of them seperately and work from there, but I'm not sure if it'd really buy me all that much. Another possible datapoint: attempting to mount or fsck any of the partitions will, more often than not, result in a "Device not configured" message. My main goal at this point, after more than sixteen hours of working on it and nearly 25 hours of downtime -- is to regain the data. If anyone could offer advice, I sure would appreciate it. I have a feeling that I'm missing something simple -- I used to be a sysadmin, but I never had this kind of problem with a BSD system before. *sigh* (Note: the machine in question is my own, not my employer's.) ----- End forwarded message ----- -- J.D. Falk "Laughter is the sound Product Manager that knowledge makes when it's born." Mail Abuse Prevention System LLC -- The Cluetrain Manifesto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000419214839.B13391>