Am 30.03.2009 um 21:21 schrieb Juan Miscaro:
Hi gang,
I'm running a remote 6.2 system which recently got shut down
unexpectedly (tower was physically nudged and apparently lost power).
I am running a 2-disk striped array with the geom_stripe.ko module.
So my fstab line is
/dev/stripe/st0a
2009/3/31 hv h...@tuebingen.mpg.de:
Am 30.03.2009 um 21:21 schrieb Juan Miscaro:
Hi gang,
I'm running a remote 6.2 system which recently got shut down
unexpectedly (tower was physically nudged and apparently lost power).
I am running a 2-disk striped array with the geom_stripe.ko module.
Juan Miscaro wrote:
Hi gang,
I'm running a remote 6.2 system which recently got shut down
unexpectedly (tower was physically nudged and apparently lost power).
I am running a 2-disk striped array with the geom_stripe.ko module.
So my fstab line is
/dev/stripe/st0a/data
2009/3/31 Ivan Voras ivo...@freebsd.org:
Juan Miscaro wrote:
Hi gang,
I'm running a remote 6.2 system which recently got shut down
unexpectedly (tower was physically nudged and apparently lost power).
I am running a 2-disk striped array with the geom_stripe.ko module.
So my fstab line is
Juan Miscaro wrote:
This is the end of dmesg (the drives in question are ad1 and ad3):
GEOM_STRIPE: Device st0 created (id=3091204740).
GEOM_STRIPE: Disk ad1 attached to st0.
GEOM_STRIPE: Disk ad1 removed from st0.
GEOM_STRIPE: Device st0 destroyed.
GEOM_STRIPE: Device st0 created
Ivan Voras wrote:
If gstripe list doesn't mention ad3, you need to establish what
happened to metadata on ad3. Try extracting the last sector from ad3 by
hand (using dd) into a file and inspect it (send output of hd filename).
I just noticed there could be an easier way to do it: use gstripe
2009/3/31 Ivan Voras ivo...@freebsd.org:
Ivan Voras wrote:
If gstripe list doesn't mention ad3, you need to establish what
happened to metadata on ad3. Try extracting the last sector from ad3 by
hand (using dd) into a file and inspect it (send output of hd filename).
I just noticed there
2009/3/31 Ivan Voras ivo...@freebsd.org:
Juan Miscaro wrote:
This is the end of dmesg (the drives in question are ad1 and ad3):
GEOM_STRIPE: Device st0 created (id=3091204740).
GEOM_STRIPE: Disk ad1 attached to st0.
GEOM_STRIPE: Disk ad1 removed from st0.
GEOM_STRIPE: Device st0 destroyed.
Juan Miscaro wrote:
What does gstripe list say? What does sysctl -b kern.geom.confxml say?
'gstripe list' does not return any output at all.
Output to the sysctl command is attached.
gstripe list cannot output nothing, since the sysctl output you posted
says a partial GEOM_STRIPE instance
2009/3/31 Ivan Voras ivo...@freebsd.org:
Juan Miscaro wrote:
What does gstripe list say? What does sysctl -b kern.geom.confxml say?
'gstripe list' does not return any output at all.
Output to the sysctl command is attached.
gstripe list cannot output nothing, since the sysctl output you
Juan Miscaro wrote:
It looks like you created a both a fdisk partition table and a bsdlabel
partition table on the ad3 drive. If so, your data is probably already
corrupted.
What is a generic configuration? Or can you explain how you come to
that conclusion?
RAID 0 means striping data
2009/3/31 Ivan Voras ivo...@freebsd.org:
Juan Miscaro wrote:
It looks like you created a both a fdisk partition table and a bsdlabel
partition table on the ad3 drive. If so, your data is probably already
corrupted.
What is a generic configuration? Or can you explain how you come to
that
Juan Miscaro wrote:
# dd if=/dev/ad3 of=ad3last count=1 skip=625142447
# hd ad3last
Thanks for that great explanation.
The file ad3last.txt is attached.
...
24 47 41 46 52 10 41 08 00 00 00 00 00 00 00 00
|$GAFR.A.|
0010 00 00 00 00 00 00 00 00 00 00 6f e2 42
13 matches
Mail list logo
