From nobody@FreeBSD.org Tue Apr 30 00:37:04 2002 Return-Path: Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 855A437B41E for ; Tue, 30 Apr 2002 00:36:58 -0700 (PDT) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3U7aw837865; Tue, 30 Apr 2002 00:36:58 -0700 (PDT) (envelope-from nobody) Message-Id: <200204300736.g3U7aw837865@freefall.freebsd.org> Date: Tue, 30 Apr 2002 00:36:58 -0700 (PDT) From: Jesse Peterson To: freebsd-gnats-submit@FreeBSD.org Subject: newfs failing in 5.0-DP1 initial install X-Send-Pr-Version: www-1.0 >Number: 37586 >Category: misc >Synopsis: newfs failing in 5.0-DP1 initial install >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-qa >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 30 00:40:02 PDT 2002 >Closed-Date: Sun Aug 29 05:40:35 GMT 2004 >Last-Modified: Sun Aug 29 05:40:35 GMT 2004 >Originator: Jesse Peterson >Release: FreeBSD 5.0 Developer Preview 1 (5.0-DP1) >Organization: >Environment: Can't get interactive. >Description: Setup all options for installing DP1. Go to 'Commit' and everything seems ok. I always immediately switch to ttyv1 to catch all the actual work and the newfs of root, var, tmp work fine. But when it gets to /usr, it stops right before the first super-block backup, and the machine becomes unresponsive. >How-To-Repeat: Same as above. >Fix: No fix. >Release-Note: >Audit-Trail: From: Peter Pentchev To: Jesse Peterson Cc: bug-followup@FreeBSD.org Subject: Re: misc/37586: newfs failing in 5.0-DP1 initial install Date: Tue, 30 Apr 2002 11:05:48 +0300 On Tue, Apr 30, 2002 at 12:36:58AM -0700, Jesse Peterson wrote: > > >Number: 37586 > >Category: misc > >Synopsis: newfs failing in 5.0-DP1 initial install > >Originator: Jesse Peterson > >Release: FreeBSD 5.0 Developer Preview 1 (5.0-DP1) > >Environment: > Can't get interactive. > >Description: > Setup all options for installing DP1. Go to 'Commit' and everything seems ok. > I always immediately switch to ttyv1 to catch all the actual work and the newfs of root, var, tmp work fine. But when it gets to /usr, it stops right before the first super-block backup, and the machine becomes unresponsive. > >How-To-Repeat: > Same as above. > >Fix: > No fix. A couple more details might be useful :) Like, what hardware are you running this on (CPU, hard disk make & model), how have you chosen to partition your disks, and similar. G'luck, Peter PS. Please send a copy of your follow-ups to bug reports to bug-followup@FreeBSD.org, so that they may be preserved in the PR audit trail and others may refer to them later. -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 Thit sentence is not self-referential because "thit" is not a word. From: Jesse Peterson To: bug-followup@FreeBSD.org Cc: Subject: [Fwd: Re: misc/37586: newfs failing in 5.0-DP1 initial install] Date: Tue, 16 Jul 2002 12:34:23 -0700 This is a multi-part message in MIME format. --------------030601060906090601080102 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit -------- Original Message -------- Subject: Re: misc/37586: newfs failing in 5.0-DP1 initial install Date: Tue, 30 Apr 2002 03:54:31 -0700 From: Jesse Peterson To: Peter Pentchev CC: erage@softhome.net References: <200204300736.g3U7aw837865@freefall.freebsd.org> <20020430110547.H365@straylight.oblivion.bg> Yeah, I'm sorry for the vagueness in my initial report =). I happened to finaly get the machine to install on the HD. uname -a: FreeBSD dhcp5.kcomm.wan 5.0-DP1 FreeBSD 5.0-DP1 #0: Sun Apr 7 02:51:42 GMT 2002 murray@builder.freebsdmall.com:/usr/src/sys/i386/compile/GENERIC i386 dmesg: attached. I'm not sure what I did to change the behaviour of the install floppies to get them to actualy install. I thought i'd be out of luck and have to wait till -RELEASE to get a sneak peak at 5.0. At first, I was using a single slice and the 'a' command for auto in the visual disklabel-thingy thats on the floppies. Making a 128m /, 48m (1.5*ram?) swap,256m /var and /tmp, and the remaining of ad0 (768m i think) to /usr. That didn't work twice. So then i decided to make a dedicated disk. Didn't work either. As a last resort I tried once more to maybe try my luck, and whaddya know? It worked. =) Also on a side-note. I made an inital vinum volume on ad2 and ad3, with an error -- no biggie, i normaly just "vinum resetconfig" and do it all again. However, after the initial resetconfig I get with vinum: Version mismatch. The kernel module is version 0 of Vinum, but this program is designed for version 1 Please upgrade your kernel module. A little odd, if i unload the vinum kld, and recreate the volume, all is good. Peter Pentchev wrote: >On Tue, Apr 30, 2002 at 12:36:58AM -0700, Jesse Peterson wrote: > >>>Number: 37586 >>>Category: misc >>>Synopsis: newfs failing in 5.0-DP1 initial install >>>Originator: Jesse Peterson >>>Release: FreeBSD 5.0 Developer Preview 1 (5.0-DP1) >>>Environment: >>> >>Can't get interactive. >> >>>Description: >>> >> Setup all options for installing DP1. Go to 'Commit' and everything seems ok. >>I always immediately switch to ttyv1 to catch all the actual work and the newfs of root, var, tmp work fine. But when it gets to /usr, it stops right before the first super-block backup, and the machine becomes unresponsive. >> >>>How-To-Repeat: >>> >> Same as above. >> >>>Fix: >>> >> No fix. >> > >A couple more details might be useful :) Like, what hardware are you >running this on (CPU, hard disk make & model), how have you chosen to >partition your disks, and similar. > >G'luck, >Peter > >PS. Please send a copy of your follow-ups to bug reports to >bug-followup@FreeBSD.org, so that they may be preserved in the PR audit >trail and others may refer to them later. > -- Jesse Peterson erage@softhome.net --------------030601060906090601080102 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-DP1 #0: Sun Apr 7 02:51:42 GMT 2002 murray@builder.freebsdmall.com:/usr/src/sys/i386/compile/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0504000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 167046414 Hz CPU: Pentium/P54C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 27582464 (26936K bytes) Intel Pentium detected, installing workaround for F00F bug Using $PIR table, 5 entries at 0xc00fd910 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x6400-0x641f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x6500-0x653f irq 10 at device 14.0 on pci0 xl0: Ethernet address: 00:60:08:3f:fc:d4 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 18.0 (no driver attached) orm0: