From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 19:55:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD3DF16A4CE for ; Sun, 25 Jan 2004 19:55:48 -0800 (PST) Received: from pegmatite.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E33E143D3F for ; Sun, 25 Jan 2004 19:55:46 -0800 (PST) (envelope-from dgerow@afflictions.org) Received: by pegmatite.sentex.ca (Postfix, from userid 1001) id 60705171E3; Sun, 25 Jan 2004 22:55:40 -0500 (EST) Date: Sun, 25 Jan 2004 22:55:40 -0500 From: Damian Gerow To: current@freebsd.org Message-ID: <20040126035539.GP1456@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG-Key-Id: 0xB841F142 X-GPG-Fingerprint: C7C1 E1D1 EC06 7C86 AF7C 57E6 173D 9CF6 B841 F142 X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i Subject: Boot problems going from 5.2-R to -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 03:55:48 -0000 I've just set up a new system, using 5.2-R as my starting point. Right after installing, I supped to -CURRENT, rebuilt, and rebooted. I was running headless, and the box didn't come back up properly after about 5 minutes, so I hit reset. Next boot, same problem, so I moved a monitor over, and it had hung after trying to mount root (from /dev/ad0s1a). (cvsup time was early this afternoon.) The system was pretty much frozen -- num/caps/scroll lock responded, but that's it. So I hit reboot again, and tried to boot into single user mode. Then I got this: WARNING: R/W mount of / is denied. Filesystem is not clean - run fsck. WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted WARNING: R/W mount of / is denied. Filesystem is not clean - run fsck. WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted . . . And so on. They just kept on coming. So I hit reset, and booted into 'Safe Mode'. I was successfully able to bring up the system, and dropped down to single-user mode, unmounted /usr, and fsck'ed it. But I couldn't unmount /var, and I've never tried re-mounting a partition ro under FreeBSD, so that didn't go over well (but that's where my starting point will be for bringing the system back up). Anyhow, next reboot, try it normally. Upon mounting /, I get the same behaviour as I did initially. This time, two lines were spit out about fsck_ufs: pid 86 (fsck_ufs), uid0: exited on signal 8 pid 87 (fsck_ufs), uid0: exited on signal 8 And I'm now getting the repetitive lines about R/W mount of / being denied. I remember seeing a commit about opening a device R/W even if R/O access is requested, which feels like it might be involved...? This is a pretty straight VIA C3 CPU, on a DFI motherboard sporting a VIA chipset. I'd never previously had any ATA issues, and system had booted into 5.2-R a number of times without issue. No fancy hardware -- 40GB Samsung ATA100 drive, fxp0, and that's about it.