On Mon, 2004-Jul-26 14:30:08 -0400, Charles Sprickman wrote:
>I did get confirmation from Adaptec that it does go from the outside
>sectors in.
In which case one of the first things to be over-written would have
been the first superblock and fsck should complain and stop immediately
if this is inv
On Thu, 22 Jul 2004, Peter Jeremy wrote:
> >command does, but they are fairly certain that it writes it's config at
> >the end of the disk, then zeros it from the outside in.
>
> Which puts an upper limit on the amount of damage done. The only
> difficulty with this is that (ISTR) your filesystem
Charles Sprickman wrote:
... there seem to be a ton of superblock backups.
How do I find out where they are and compare them?
This is an FAQ, and probably in the handbook somewhere
(google for "alternate superblock"):
* According to "man fsck_ffs", block 32 is usually
an alternate superblock
Hi Charles,
I sent this message. But SpamCop.net had listed
my ISP address. I received undelivered message.
So I will send again.
Eitarou
Eitarou Kamo wrote:
Hi,
How about this?
1. You mount dd.img as vn0 like this in your free space.
#vnconfig vn0 dd.img
# mount /dev/vn0c /mnt
2. archive or dump w
On Tue, 2004-Jul-20 14:01:06 -0400, Charles Sprickman wrote:
>On Tue, 20 Jul 2004, Peter Jeremy wrote:
>
>> It's difficult to see how a sanely written RAID utility could totally
>> screw up an array in a short time
Upon reflection, one obvious way is to change the array layout. I
don't know enoug
On Tue, 20 Jul 2004, Eitarou Kamo wrote:
> >Here's what fsck says:
> >
> >[EMAIL PROTECTED]/mnt/tmp/vpopmail/domains]# fsck /dev/vn0c ** /dev/vn0c
> >BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
> >ALTERNATE
> >ioctl (GCINFO): Invalid argument
> >fsck: /dev/vn0c: can't read
On Tue, 20 Jul 2004, Peter Jeremy wrote:
> 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 t
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
Hi,
Just following up to myself. I have a bit more info. I used vnconfig
like so to attach my dd "image":
vnconfig -s labels -c vn0 xena-home.dd
And while fsck and disklable both refuse to believe it's at all valid, I
can do the following:
mount -o ro -f /dev/vn0c /mnt/tmp
And for the most p
Hi,
I'm sorry for hitting this list, but I'm trying to target people with some
good old-fashioned recovery procedures in their toolboxes, and people that
have a better understanding of UFS than I do.
I'll try to keep this brief. We are looking for either some "here you go"
help, or if there's so
10 matches
Mail list logo
