Date: Fri, 4 May 2007 11:25:54 -0700 (PDT) From: Arne "Wörner" <arne_woerner@yahoo.com> To: deniswork <deniswork@uzvik.kiev.ua>, freebsd-geom@freebsd.org Subject: Re: graid5 after-reboot problem Message-ID: <386758.54024.qm@web30314.mail.mud.yahoo.com> In-Reply-To: <1015033466.20070504204946@uzvik.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
--- deniswork@uzvik.kiev.ua wrote: > hello, after reboot i meet strange problem, i can't mount raid : ( > > [root@82 /usr/home/denis]# mount /dev/raid5/data /home/esc/daemon/upload/dl2 > mount: /dev/raid5/data: Operation not permitted > > [root@82 /usr/home/denis]# tail -f /var/log/messages > May 4 20:37:48 82 kernel: GEOM_RAID5: registered shutdown event handler. > May 4 20:37:48 82 kernel: GEOM_RAID5: data: device created > (stripesize=131072). > May 4 20:37:48 82 kernel: GEOM_RAID5: data: ad10(3): disk attached. > May 4 20:37:48 82 kernel: GEOM_RAID5: data: ad8(2): disk attached. > May 4 20:37:48 82 kernel: GEOM_RAID5: data: ad6(1): disk attached. > May 4 20:37:48 82 kernel: GEOM_RAID5: data: ad4(0): disk attached. > May 4 20:37:48 82 kernel: GEOM_RAID5: data: activated. > May 4 20:37:48 82 kernel: WARNING: R/W mount of > /usr/home/esc/daemon/upload/dl2 denied. Filesystem is not clean - run fsck > May 4 20:37:56 82 kernel: WARNING: R/W mount of > /usr/home/esc/daemon/upload/dl2 denied. Filesystem is not clean - run fsck > May 4 20:40:04 82 last message repeated 4 times > > > When I try fsck I get: > [root@82 /usr/home/denis]# fsck /dev/raid5/data > fsck: Could not determine filesystem type > > [root@82 /usr/home/denis]# fsck_ufs /dev/raid5/data > ** /dev/raid5/data > BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE > ioctl (GCINFO): Inappropriate ioctl for device > fsck_ufs: /dev/raid5/data: can't read disk label > > How to mount raid? > > Thanks > > p.s. mounting in read-only mode pass successful but it is not what I > want : ( > That is strange... Obviously ur file system is damaged... I do not know, how that happened... Did u abort the device rebuild process? If ur box can do a "graid5 remove" without crashing u could try this: Try to do that fsck in degraded mode (in the hope that just one disk contains silly data)... U should start with removing disk#0... Then do the fsck... But before u put back disk#0 u should remove disk#1 in order to avoid a further rebuild process, which might damage the data further... Maybe u could try sysutils/scan_ffs (from the ports) in order to repair the disklabel? And then do a fsck again? I mount my 3 graid5 devices every day without such problems... Even "power-failures" (when my CPU gets too hot, the PSU shuts the box down :-] ) r no real problem... -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?386758.54024.qm>