Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Feb 1999 13:55:41 -0800
From:      "Daniel J. Frost" <lethvian@maine.rr.com>
To:        stable@freebsd.org
Subject:   3.1-R Fixit Flp
Message-ID:  <36C9E95D.ED2BA1D3@maine.rr.com>

next in thread | raw e-mail | index | archive | help
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.

-Dan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36C9E95D.ED2BA1D3>