From owner-freebsd-stable Tue Feb 16 12:37:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail-atm.maine.rr.com (ns.maine.rr.com [204.210.64.1]) by hub.freebsd.org (Postfix) with ESMTP id D8EB31167B for ; Tue, 16 Feb 1999 12:37:36 -0800 (PST) (envelope-from lethvian@maine.rr.com) Received: from maine.rr.com (dt074n03.maine.rr.com [24.93.136.3]) by mail-atm.maine.rr.com (8.8.7/8.8.8) with ESMTP id PAA13181; Tue, 16 Feb 1999 15:36:55 -0500 (EST) Message-ID: <36C9FFBF.84D2590D@maine.rr.com> Date: Tue, 16 Feb 1999 15:31:11 -0800 From: "Daniel J. Frost" X-Mailer: Mozilla 4.06 [en] (Win98; I) MIME-Version: 1.0 To: "Wayne M. Barnes" Cc: stable mailing list at FreeBSD Subject: Re: 3.1-R References: <199902162020.OAA01692@barnes1.wustl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for the suggestion. But the local root device is read-only, and I can't mount anything. I've tried mount /dev/wd1s2 /usr only to get: pid 25 (mount), uid 0 : exited on signal 12 mount: /usr: Bad system call Any ideas on how to get it readable/writeable? Wayne M. Barnes wrote: > Dear Daniel, > > This sounds a little like a problem I had. To quote from my previous > missive: > ------------------------- > Here's how I got out of this jam: > # mount /dev/wd0s1 /usr # Now the / is writable as /usr > # cd /usr/dev # This is really /dev > # ./MAKEDEV wd0s1a > chgrp: not found # Is this going to hurt me someday? > # ls wd0* # all the slices a-g are there! > # reboot > ----------------- > > If I am right, > You would substitute wd1s2 for wd0s1 above, after inspecting > the output from > > mount > and > cat /etc/fstab > > , which you should still be able to read from the > single-user prompt with / mounted as read-only. > > -- Wayne M. Barnes wayne@barnes1.wustl.edu > -----------Dan's previous letter: > Date: Tue, 16 Feb 1999 13:55:41 -0800 > From: "Daniel J. Frost" > X-Mailer: Mozilla 4.06 [en] (Win98; I) > To: stable@FreeBSD.ORG > Subject: 3.1-R Fixit Flp > > Hello > While upgrading from 2.2.8-stable to 3.1-stable (make aout-to-elf-build > and make aout-to-elf-install), all went well until I rebooted. It was > apparent that I should have used the GENERIC kernel as opposed to my > custom made kernel back in 2.2.8-stable. > While booting up, here are the last few lines: > /dev/rw1s2:FILESYSTEM CLEAN; Skipping checks > /dev/rw1s2: clean, 642327 free (3311 frags, 79877 blocks, 0.3% > fragmentation) > mount: exec mount_ failed, startup aborted > > I was able to drop to a shell, but my /usr was on a partition not > mounted so I couldn't build a 3.1 kernel. So I tried to mount /usr > manually > > #mount -t ufs /dev/usr_partition /usr > pid 25 (mount), uid 0 : exited on signal 12 > mount: /usr : Bad system call > > I tried to boot in single user mode, but I still couldn't use mount. I > couldn't use mount in the sense that I couldn't mount anything...I kept > getting signal 12 > > One alternative suggested was to use a fixit.flp, but I still couldn't > mount anything even in a Fixit shell. (I got the fixit shell from > ftp.freebsd.org, used fdimage to write the image). > Fixit# mount -t ufs /dev/root_device /mnt /* /mnt is empty, /mnt2 > was where fd0 was mounted) */ > /: write failed, filesystem is full > mount: /mnt: Bad system call > Fixit# > > this is part of the df output: > root_device 95% > /dev/fd0 103% > > I hope I have provided enough information for someone to give me some > hints. Thanks. > -----------------End of Dan's letter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message