problem with gvinum stripeset after crash

[feczo at geek.hu]

When Im trying to access my stripeset I got:
FOOO: g_access failed: 1

it is 5.3-STABLE
I have not made any changes to the system sources, including Vinum

the output of the vinum list command
3 drives:
D drive1                State: up       /dev/ad3s1a     A: 0/152625 MB (0%)
D drive3                State: up       /dev/ad2s1a     A: 0/152625 MB (0%)
D drive2                State: up       /dev/ad1s1a     A: 0/152625 MB (0%)

1 volumes:
V vol                   State: up       Plexes:       1 Size:        447 GB

1 plexes:
P vol.p0              S State: up       Subdisks:     3 Size:        447 GB

3 subdisks:
S vol.p0.s0             State: up       D: drive1       Size:        149 GB
S vol.p0.s1             State: up       D: drive2       Size:        149 GB
S vol.p0.s2             State: up       D: drive3       Size:        149 GB

extract of the Vinum history file.
13 Oct 2004 21:49:52.734589 stripe -n vol -v /dev/ad1s1a /dev/ad2s1a /dev/ad3s1a
13 Oct 2004 21:49:55.746202 *** vinum started ***
13 Oct 2004 21:49:55.746945 list
13 Oct 2004 21:49:59.163631 *** vinum started ***
13 Oct 2004 21:50:15.521495 rename vinumdrive0 drive1
13 Oct 2004 21:50:22.533035 rename vinumdrive1 drive2
13 Oct 2004 21:50:29.122598 rename vinumdrive2 drive3
13 Oct 2004 21:50:29.921378 l
13 Oct 2004 21:50:35.235949 saveconfig
13 Oct 2004 21:50:36.532067 quit
1 Nov 2004 16:20:54.600221 *** vinum started ***
1 Nov 2004 16:28:32.936914 printconfig vinum.config.latest
1 Nov 2004 16:28:55.735478 *** vinum started ***
1 Nov 2004 16:28:55.736784 resetconfig
1 Nov 2004 16:29:00.435392 *** vinum started ***
1 Nov 2004 16:29:00.436696 list
1 Nov 2004 16:29:20.155428 *** vinum started ***
1 Nov 2004 16:29:20.156748 stripe -n vol -v /dev/ad1s1a /dev/ad2s1a /dev/ad3s1a
1 Nov 2004 16:29:23.345479 *** vinum started ***
1 Nov 2004 16:32:16.857648 list
1 Nov 2004 16:32:40.506239 *** vinum started ***
1 Nov 2004 16:32:40.508210 resetconfig
1 Nov 2004 16:32:48.476489 *** vinum started ***
1 Nov 2004 16:32:48.477827 create -f vinum.config.latest
# Vinum configuration of nmi.rulez.org, saved at Mon Nov  1 16:28:32 2004
drive drive1 device /dev/ad3s1a
drive drive3 device /dev/ad2s1a
drive drive2 device /dev/ad1s1a
volume vol
plex name vol.p0 org striped 558s vol vol
sd name vol.p0.s0 drive drive1 plex vol.p0 len 312575976s driveoffset 265s plexoffset 0s
sd name vol.p0.s1 drive drive2 plex vol.p0 len 312575976s driveoffset 265s plexoffset 558s
sd name vol.p0.s2 drive drive3 plex vol.p0 len 312575976s driveoffset 265s plexoffset 1116s
1 Nov 2004 16:32:52.026505 *** vinum started ***
1 Nov 2004 16:32:52.027829 list

an extract of the file /var/log/messages
Nov  1 16:20:54 nmi kernel: vinum: loaded
Nov  1 16:20:56 nmi kernel: vinum: reading configuration from /dev/ad1s1a
Nov  1 16:20:56 nmi kernel: vinum: updating configuration from /dev/ad2s1a
Nov  1 16:20:56 nmi kernel: vinum: updating configuration from /dev/ad3s1a
Nov  1 16:21:45 nmi kernel: GEOM_VINUM: subdisk vol.p0.s0 is up
Nov  1 16:21:45 nmi kernel: GEOM_VINUM: subdisk vol.p0.s2 is up
Nov  1 16:21:45 nmi kernel: GEOM_VINUM: subdisk vol.p0.s1 is up
Nov  1 16:21:51 nmi kernel: FOOO: g_access failed: 1

-I had a crash, but I had generic kernel that time and can not reproduce it
though some info from the screen :

ad3: FAILURE - READ_DMA status=51(READ,DSC,ERROR) error=40(UNCORRECTABLE) LBA=228127468
GEOM_VINUM: subdisk vol.p0.s0 is down
GEOM_VINUM: plex vol.p0 is down


Fatal trap 12: page fault while in kernel mode
fatal virtual address   = 0xf8
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc5eee5ad
stack pointer           = 0x10:0xe4e17cf4
frame pointer           = 0x10:0xe4e17d00
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0. pres 1. def32 1, gran 1
processors eflags       = interrupt enabled, resume, IOPL = 0
current process         = 21704 (gv_v vol)
trap number             = 12
panic: page default
Uptime: 1d8h45m17s

I see its a hardware error, but still any chance to recover some of
the 447Gb would be great

The problem is more complicated since I have used gbde to encrypt the 
volume which has worked fine, though I first have to attach the drive
to run fsck or anything and the command 
gbde attach /dev/gvinum/vol -l /tmp/key
It says: gbde: Attach to gvinum/vol failed: could not access consumer

Any help would be appreciated


-- 
  _(_)_
 (_. o_)            F3CZ0
   (_,)     http://feczo.nmi.rulez.org
  (    )    __________________________
  // //