Gvinum RAID5 volume don't work after a simple reboot
Olivier Cochard
olivier at freenas.org
Mon Feb 27 12:57:25 PST 2006
Hi all,
One of my user have a big problem with gvinum and RAID5:
He builts a RAID 5 volume that worked great for two days.
But, when he reboot the PC it takes about 2 hours to get the disks to the
"UP" state:
Here is an example of output during the starting of the volume:
=============================
3 drives:
D disk_ad1 State: up /dev/ad1s1 A: 0/238475 MB (0%)
D disk_ad2 State: up /dev/ad2s1 A: 0/238475 MB (0%)
D disk_ad3 State: up /dev/ad3s1 A: 0/238475 MB (0%)
1 volume:
V fatty State: down Plexes: 1 Size: 465 GB
1 plex:
P fatty.p0 R5 State: down Subdisks: 3 Size: 465 GB
3 subdisks:
S fatty.p0.s2 State: I 70% D: disk_ad3 Size: 232 GB
S fatty.p0.s1 State: I 70% D: disk_ad2 Size: 232 GB
S fatty.p0.s0 State: up D: disk_ad1 Size: 232 GB
=============================
But, Once it gets to "UP", it's impossible to mount the volume:
mount: /dev/gvinum/fatty on /mnt/home1: incorrect super block.
then, I try an fsck:
==========================================
fsck -t ufs /dev/gvinum/fatty
Cannot find file system superblock
** /dev/gvinum/fatty
/dev/gvinum/fatty: CANNOT FIGURE OUT FILE SYSTEM PARTITION
============================================
How could he retrieves all the data stored on the RAID volume ?
Thanks,
Olivier
--
Olivier Cochard
FreeNAS main developer
http://www.freenas.org
Skype: callto://ocochard
More information about the freebsd-geom
mailing list