Date: Tue, 20 Jul 2004 19:28:48 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Charles Sprickman <spork@fasttrackmonkey.com> Cc: freebsd-hackers@freebsd.org Subject: Re: disk recovery help Message-ID: <20040720092848.GD3001@cirb503493.alcatel.com.au> In-Reply-To: <20040720021432.O28049@toad.nat.fasttrackmonkey.com> References: <20040719191408.V28049@toad.nat.fasttrackmonkey.com> <20040720021432.O28049@toad.nat.fasttrackmonkey.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2004-Jul-20 02:18:00 -0400, Charles Sprickman wrote: >And for the most part I can move around the filesystem, read files, etc. >But it is in a very inconsistent state. How can I make fsck work on this? >There's data there, but looking into certain dirs panics the box (it is It's difficult to see how a sanely written RAID utility could totally screw up an array in a short time - a 'build' utility presumably writes known data to the array but logically it would do so sequentially. The only thing I can think of is that the controller had a significant amount of cached data - which has been wiped, rather than written back to the disk. If you haven't run newfs and have the correct disklabel, the disk should be in a reasonably sane state. Have you tried running something like ports/sysutils/scan_ffs over the disk (or your copy of it)? Have you tried dumping vn0c? -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040720092848.GD3001>