Date: Wed, 30 Sep 1998 04:27:10 +0800 From: chas <panda@peace.com.my> To: freebsd-questions@FreeBSD.ORG Subject: Answer - RAID died. Re: Device not configured / Can't check filesystem. Message-ID: <3.0.32.19980930042710.00ace9b8@mail.peace.com.my>
next in thread | raw e-mail | index | archive | help
Just answering my own initial post - FreeBSD was innocent, the RAID controller seems to have died. Zero communication between that and the FreeBSD box. Moral of the story : backup, even if it's on redundant RAID 5. (learned the hard way ) chas >Woke up this morning to find one of my FreeBSD boxes offline. >Rebooting produced the following : > >/dev/rwd0s1a: clean, 32630 free >Can't open /dev/rsd0s1e: device not configured >/dev/rsd0s1e: CAN'T CHECK FILE SYSTEM >/dev/rsd0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. >/dev/rwd0s1f: clean, 3086375 free >/dev/rwd0s1e: clean, 19596 free >Automatic file system check failed... help! > >fsck also failed with the following error : >Can't open /dev/rsd0s1e. Device not configured. > >I've rebuilt the parity on the external RAID array - it reported >zero errors ! The RAID system's patrol service also reported >zero errors. So, the 3 HD's that comprise the array seem to be fine >... yet I feel the problem lies in the RAID and not the FreeBSD >box. > >Anyway, just wondering if anyone recognises these symptoms or has >any other ideas ? I guess it could be the RAID controller (which >will be a bummer since StreamLogic is now out of business, last I >heard). > >chas > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.32.19980930042710.00ace9b8>