Date: Tue, 13 Oct 1998 13:50:22 -0700 From: Mike Smith <mike@smith.net.au> To: Vijay Ramasubramanian <ramasubr@ews.uiuc.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installation probs w/3.0-BETA Message-ID: <199810132050.NAA01261@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 13 Oct 1998 00:41:44 CDT." <Pine.GSO.3.96.981012233828.28041B-100000@eesn17.ews.uiuc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> AdvanSys ABP-940 SCSI host adapter, SCSI ID 7 > IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 0 > IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 1 > Fujitsu 405 MB Fast SCSI-2 drive, SCSI ID 2 ... > Drive 0 (IBM 2.2 GB): > > 400MB FAT16 (Windows 95 resides here) > Remainder FreeBSD FS, mount at: / > Leave MBR alone (I had planned on installing System Commander later) ... > I had planned to run the /var and /usr directories off the root FS > partition. ... > Once I get the installation via FTP started (from ftp.freebsd.org), it > progresses to 34% and then crashes. The progress bar reads "Extracting > bin into / directory..." > The stats bar at the bottom reads: "9438208 bytes read from bin dist, > chunk 40 of 116 @ 13.4kB/sec" > The error messages are as follows: > > Panic: ufs_dirbad: bad dir This is the principal problem. The filesystem that you're writing to is corrupted. The possible causes for this problem are: - Bad RAM (quite likely) - Bad cache (less likely, but still possible) - A bad disk (fairly unlikely) - A bug in the Advansys driver (possible, as it hasn't had much testing yet). > Syncing disks... 143 143 143 70 40 1 1 1 1 1 1 1 1 1 1 1 1 giving up > (da2:adv0:0:2:0): . CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:adv0:0:2:0): ILLEGAL REQUEST asc: 20,0 > (da2:adv0:0:2:0): This is just the Fujitsu drive complaining about something; I suspect it's the Synchronise Cache command that we send before rebooting. It's irritating but quite harmless. > So, I tried yanking the Fujitsu and just installing the / FS to the 1st > IBM drive, and putting Swap on the 2nd drive. The installation then died > at 35% with the message: > > Panic: ffs_alloccg : bad map This is consistent again with filesystem corruption. > This may not be exactly the error message (the part after ffs_alloccg) as > the machine rebooted before I could get of the info, and I have no desire > to try a 15th installation attempt to get the message again. > > The hardware has been run under 95 so far without any problems, although > most people would probably say that running under 95 is not much of a test > of hardware. > > Can anyone tell me how to go about getting this resolved? > > If you think it may be bad hardware, can you suggest diagnostic-type > programs that I can test with? I have relatively limited hardware > resources, and can't do stuff like swapping out the CPU, RAM, etc. There's no really good RAM test, unfortunately. You might try some of the freebie ones floating around on the 'net, but these will quite often pass RAM as good when in fact it's not. The better ones will admit this in their documentation. Check you're not overclocking anything for starters, but bad RAM is the most likely problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810132050.NAA01261>