Gvinum RAID5 volume don't work after a simple reboot
Olivier Cochard
olivier at freenas.org
Mon Feb 27 13:16:15 PST 2006
No, I don't use bsdlabel, after creating the RAID volume, I use this
command:
/sbin/newfs -U /dev/gvinum/fatty
And I mount it and use it without problem (put lot's of files on it).
Olivier
2006/2/27, Lukas Ertl <le at freebsd.org>:
>
> On Mon, 27 Feb 2006, Olivier Cochard wrote:
>
> > 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%)
>
> Are there no bsdlabels on the disks? I.e., is this device listing
> intended (ad1s1 instead of ad1s1a).
>
> > But, Once it gets to "UP", it's impossible to mount the volume:
> >
> > mount: /dev/gvinum/fatty on /mnt/home1: incorrect super block.
>
> This question might sound stupid, but is there a filesystem on the device?
> If it initializes, the filesystem is gone, if there ever was one.
>
> regards,
> le
>
> --
> Lukas Ertl http://homepage.univie.ac.at/l.ertl/
> le at FreeBSD.org http://people.freebsd.org/~le/
>
More information about the freebsd-geom
mailing list