harddisk problem and/or fsck problem?
Greetings, fellow FreeBSD users! Everything so far works fine for me, until I drop into single- user mode to prep for making world. Even then, it seems OK, except for this alarming output of fsck -p: /dev/da0s1a: NO WRITE ACCESS /dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I run fsck /dev/da0s1a, and I'm just told of NO WRITE for the fs, and the phases shown without error. But I *can* write there -- my / partition. OK, FYI -- This happens on 4.9-RELEASE and 5.2.1-RELEASE-i386 both. I have an IBM UltraStar Ultra160 SCSI disk, model no. IC35L018UDW210-0 ... Runs on a Tyan S2462 Thunder K7 dual Athlon-MP board, using the GENERIC kernel. I've run the onboard Adaptec-controller's format and verify utilities, which I presume run without error, since they just do their thing without error messages and just say when they're done. I install the above via the miniinst CDs, cvsup the lastest sources, and that's it for usage. But the machine boots and runs fine otherwise. Is this something to really worry about? Is it safe to proceed with making world? Should I try forcing fsck to do anything? Or, should I try running fsck having booted from CD? Other ideas or suggestions? Thanks all for any help offered! Cheers, -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem and/or fsck problem?
On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote: On Friday 26 March 2004 10:06 am, Richard Dawes wrote: Greetings, fellow FreeBSD users! Everything so far works fine for me, until I drop into single- user mode to prep for making world. Even then, it seems OK, except for this alarming output of fsck -p: Well, you missed reading something because you are supposed to boot -s into single user mode. Then, you don't have write access and the fsck works. BTW, the whole point of booting into single user mode is to avoid a bad kernel. When you drop into single user mode, you aren't testing the new kernel. Kent Doh! Yes, I guess I was reading too quickly. And of course it makes sense that I'd not need to fsck and mount things if I just drop into single-user mode. But I wasn't yet testing a new kernel... I haven't yet made the buildworld target. I see later on, though, where I'm supposed to boot -s after installing a newly built kernel. Thanks for your help! -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: harddisk problem and/or fsck problem?
On Fri, Mar 26, 2004 at 02:09:35PM -0800, Kent Stewart wrote: The sequence that is designed to keep your out of trouble is buildworld, buildkernel, installkernel, boot -s, and installworld, followed by a mergemaster. There are times as the statfs change to current that would render your system useless until you repair if if you do the installworld before booting to the new kernel. The sequence is /usr/src/UPDATING is there for a reason. You can change the order but if it breaks your system, you could have to repair it using the fixit disk or re-install. Kent Yes, I'm hip to all that... Thanks, again! -Rich -- Richard Dawes Enhanced Performance Systems [EMAIL PROTECTED] +01 619 743-0506 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
