Date: Tue, 24 May 2005 11:51:21 -0400 From: "Jonathan M. Slivko" <freebsd-lists@slivko.org> To: Franco Bruno Borghesi <fborghesi@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: 3Ware SATA RAID 8000 - Supported on 5.3-R? Message-ID: <42934D79.8070407@slivko.org> In-Reply-To: <e13c14ec05052408462757e2cd@mail.gmail.com> References: <50408.70.18.16.72.1116942842.squirrel@www.slivko.org> <e13c14ec050524075978735028@mail.gmail.com> <429341E4.5000108@slivko.org> <e13c14ec050524080654677a58@mail.gmail.com> <42934389.9020307@slivko.org> <e13c14ec05052408462757e2cd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Whether I run fsck manually or if I run it automagically at boot via rc (which happens every reboot), it fails. As I'm not at console, I can't tell whether the same things happen if the box is physically taken down. and fsck'd in single user mode. The better part of the question is, could this be the RAID card throwing out false errors due to not having complete support for 5.3-R?, as it says that it only supports the 4.x series. -- Jonathan Franco Bruno Borghesi wrote: > Your fstab is OK. > > I don't exactly understand the problem. When you boot fsck will run > automatically if the system did not correctly shut down. This is done > *before* disks are mounted rw, so there's no way you will see the "(NO > WRITE)" message. > > If system was not correctly shut down, fsck will run, and it *will* (and > should) slow down system boot process. > > So, is it the problem that fsck is running *every* time you boot? Or is > it that you get this "(NO WRITE)" message when you run it manually? > > > 2005/5/24, Jonathan M. Slivko <freebsd-lists@slivko.org > <mailto:freebsd-lists@slivko.org>>: > > root@bonjour(~)% cat /etc/fstab > # Device Mountpoint FStype Options Dump > Pass# > /dev/twed0s1b > none swap sw 0 0 > /dev/twed0s1a / ufs > rw 1 1 > /dev/twed0s1g /home ufs rw,userquota,groupquota > 2 2 > /dev/twed0s1d /tmp ufs > rw 2 2 > /dev/twed0s1e /usr ufs > rw 2 2 > /dev/twed0s1f /var ufs > rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto > 0 0 > none /proc > procfs rw 0 0 > root@bonjour(~)% > > > Franco Bruno Borghesi wrote: > > Could you post your /etc/fstab? > > > > 2005/5/24, Jonathan M. Slivko <freebsd-lists@slivko.org > <mailto:freebsd-lists@slivko.org> >: > > > >>Yes, this is actually the autoboot fsck thats breaking, the one > that is > >>called from /etc/rc (via /etc/rc.d/). I can physically take the > box down > >>and do an offline fsck of it and that works fine, it's just when > it's in > >>multi-user mode thats the problem. > >> > >>-- Jonathan > >> > >>Franco Bruno Borghesi wrote: > >> > >>>For fsck to work (to actually correct any problems you may have), > >>>partitions should be umounted first. Are you sure you have umounted > >>>/dev/twedXXXX before running fsck? > >>> > >>> > >>>2005/5/24, Jonathan M. Slivko < freebsd-lists@slivko.org > <mailto:freebsd-lists@slivko.org> > >>><mailto:freebsd-lists@slivko.org > <mailto:freebsd-lists@slivko.org>>>: > >>> > >>>Hello, > >>> > >>>I have an interesting question, I have a Pentium 4 2.4Ghz (No HT > >>>Enabled), > >>>2x80GB SATA Hard Drives in RAID 1. The box boots, works, etc. > However, > >>>whenever you try and do an fsck -y, it says: > >>> > >>>root@bonjour (~)% fsck -y > >>>** /dev/twed0s1a (NO WRITE) > >>>** Last Mounted on / > >>>** Root file system > >>>** Phase 1 - Check Blocks and Sizes > >>>** Phase 2 - Check Pathnames > >>>** Phase 3 - Check Connectivity > >>>** Phase 4 - Check Reference Counts > >>>** Phase 5 - Check Cyl groups > >>>2821 files, 31805 used, 474682 free (322 frags, 59295 blocks, 0.1% > >>>fragmentation) > >>> > >>>** /dev/twed0s1g (NO WRITE) > >>>** Last Mounted on /home > >>>** Phase 1 - Check Blocks and Sizes > >>>** Phase 2 - Check Pathnames > >>>** Phase 3 - Check Connectivity > >>>** Phase 4 - Check Reference Counts > >>>** Phase 5 - Check Cyl groups > >>>82057 files, 557735 used, 12912399 free (2343 frags, 1613757 > blocks, > >>>0.0% > >>>fragmentation) > >>> > >>>** /dev/twed0s1d (NO WRITE) > >>>** Last Mounted on /tmp > >>>** Phase 1 - Check Blocks and Sizes > >>>** Phase 2 - Check Pathnames > >>>** Phase 3 - Check Connectivity > >>>** Phase 4 - Check Reference Counts > >>>** Phase 5 - Check Cyl groups > >>>30 files, 1787 used, 504700 free (20 frags, 63085 blocks, 0.0% > >>>fragmentation) > >>> > >>>** /dev/twed0s1e (NO WRITE) > >>>** Last Mounted on /usr > >>>** Phase 1 - Check Blocks and Sizes > >>>** Phase 2 - Check Pathnames > >>>** Phase 3 - Check Connectivity > >>>** Phase 4 - Check Reference Counts > >>>** Phase 5 - Check Cyl groups > >>>251160 files, 1318908 used, 13912410 free (73346 frags, 1729883 > blocks, > >>>0.5% fragmentation) > >>> > >>>** /dev/twed0s1f (NO WRITE) > >>>** Last Mounted on /var > >>>** Phase 1 - Check Blocks and Sizes > >>>** Phase 2 - Check Pathnames > >>>** Phase 3 - Check Connectivity > >>>** Phase 4 - Check Reference Counts > >>>** Phase 5 - Check Cyl groups > >>>4424 files, 63321 used, 7042830 free (2462 frags, 880046 blocks, > 0.0% > >>>fragmentation) > >>> > >>>The drives are Seagate SATA's (7200RPM) with a 3Ware SATA RAID > >>>Controller > >>>(8006-2LP) using the twe kernel driver. The drives themselves > allow data > >>>to be read to/written from them, but fsck will not work (and is > hanging > >>>things on boot). > >>> > >>>Anyone got any ideas? I looked at www.3ware.com > <http://www.3ware.com>; <http://www.3ware.com>; > >>><http://www.3ware.com>; earlier and it says that > >>>the 8006-2LP's support FreeBSD 4.x , but not 5.x - could this be > a result > >>>of that, seeing as otherwise the drives/RAID work fine (AFAIK, > it could > >>>not be and I'm just not sure how to test it). > >>> > >>>TIA, > >>>-- Jonathan > >>>_______________________________________________ > >>>freebsd-questions@freebsd.org > <mailto:freebsd-questions@freebsd.org> <mailto: > freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org>> > >>>mailing list > >>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>>To unsubscribe, send any mail to " > >>>freebsd-questions-unsubscribe@freebsd.org > <mailto:freebsd-questions-unsubscribe@freebsd.org> > >>><mailto:freebsd-questions-unsubscribe@freebsd.org > <mailto:freebsd-questions-unsubscribe@freebsd.org>>" > >>> > >>> > >> > >>-- > >>Jonathan M. Slivko - jonathan@slivko.org <mailto:jonathan@slivko.org> > >>"Linux: The Choice for the GNU Generation" > >>- http://www.linux.org/ - > >> > >>Don't fear the penguin. > >>.^. > >>/V\ > >>/( )\ > >>^^-^^ > >>He's here to help. > >> > > > > _______________________________________________ > > freebsd-questions@freebsd.org > <mailto:freebsd-questions@freebsd.org> mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org > <mailto:freebsd-questions-unsubscribe@freebsd.org>" > > -- > Jonathan M. Slivko - jonathan@slivko.org <mailto:jonathan@slivko.org> > "Linux: The Choice for the GNU Generation" > - http://www.linux.org/ <http://www.linux.org/>; - > > Don't fear the penguin. > .^. > /V\ > /( )\ > ^^-^^ > He's here to help. > > -- Jonathan M. Slivko - jonathan@slivko.org "Linux: The Choice for the GNU Generation" - http://www.linux.org/ - Don't fear the penguin. .^. /V\ /( )\ ^^-^^ He's here to help.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42934D79.8070407>