Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!arclight.uoregon.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!uunet!in1.uu.net!206.63.63.70!nwnews.wa.com!news1.halcyon.com!usenet From: "Duane H. Hesser" <dhh@androcles.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Disk crash problem...any ideas of what is going wrong? Date: Fri, 13 Dec 1996 22:00:34 -0800 Organization: Northwest Nexus Inc. Lines: 86 Message-ID: <32B24282.2781E494@androcles.com> References: <32AF6751.41C6@ucdavis.edu> NNTP-Posting-Host: androcles.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0Gold (X11; U; FreeBSD 2.1.6-RELEASE i386) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32570 Michael White wrote: > > FreeBSD version: 2.1.5 installed from CD Rom > Disk: 1G WD Cavier > IDE controller: DC-4030VL > CPU: 66Mhz 486DX2 > > Sorry to bug everyone, but I am having a problem with keeping my > BSD machine running. Specifically the problem is that my disk > keeps having problems. I am running a Western Digital Cavier 1G > drive on a 486DX2 system with a DC-4030VL IDE controller. The > problem I seem to have is with the 3rd partition (only one slice). > The best I can figure is that once the disk gets past half full, > it starts clobbering inode information. > > My filesystems (which are okay) are: > > Filesystem 512-blocks used avail cap. > /dev/wd1a 38974 31806 4052 89% / > /dev/wd1s1e 793790 265758 464530 36% /usr > procfs 8 8 0 100% /proc > > The last partition had numerious inode errors (which I attempted > to fix with fsck... which hangs with a number that is too big and > can't even seem to patch up). > > I have looked at information at startup using newfs & fdisk: > > #newfs -N rwd1s1 > /dev/rwd1s1: 40960 sectors in 10 cylinders of 1 tracks, > 4096 sectors 20.0 MB in 1 cyl groups (16 c/g, 32.00 MB/g, 7680 i/g) > > Superblock backups (for fsck -b #) at: > 32, > (^- Note: only one backup is listed here). > > #fdisk /dev/rwd1 > ********* Working on device /dev/rwd1 ************ > parameters extracted from in-core disk Label are: > cylinders=2100 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=2100 heads=16 sectors/track=63 (1008 blks/cyl) > > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 0 is: > sysid 165, (freeBSD/NetBSD/386BSD) > start 63, size 2116737 (1033Meg), flag 80 > beg: cyl 0/ sector 1/ head 1 > end: cyl 1023/ sector 63/ head 15 > > The data for partition 1 is: > <UNUSED> > The data for partition 2 is: > <UNUSED> > The data for partition 3 is: > <UNUSED> > > I realize that I will probably have to clear everything off my > disk and re-do my partitions, but can anyone see what I have > done wrong (as this problem seems to keep coming up). Note: > eventhough the DC-4030VL is a VL-Bus IDE caching disk controller, > I have turned the cache off and am using the mainboard bios. > > Any help would be appreciated. > -- > - Mike > mdwhite@ucdavis.edu It's possible your disk has bad blocks--most likely in the filesystem area. You need to find something to scan your disk for bad blocks. If there aren't too many, you might be able to use 'bad144' to map them out. Otherwise (if there ARE bad blocks in the filesystem area) you should reformat. Which brings me to a question. Whatever happened to format(8) in freebsd? I seem to recall re-formatting a Jaz disk recently--but maybe that was on Linux? The memory really IS the first thing to go... -- Duane H. Hesser dhh@androcles.com