From owner-freebsd-current Sat Apr 1 05:05:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA10255 for current-outgoing; Sat, 1 Apr 1995 05:05:32 -0800 Received: from vinkku.hut.fi (vode@vinkku.hut.fi [130.233.245.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA10247 for ; Sat, 1 Apr 1995 05:05:27 -0800 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id QAA05147; Sat, 1 Apr 1995 16:05:16 +0300 Date: Sat, 1 Apr 1995 16:05:16 +0300 From: Kai Vorma Message-Id: <199504011305.QAA05147@vinkku.hut.fi> To: current@FreeBSD.org Subject: panic: update: rofs mod Reply-to: Kai.Vorma@hut.fi Sender: current-owner@FreeBSD.org Precedence: bulk I upgraded my kernel today to latest level (sources supped at Sat Apr 1 12:21:11 EET DST) and rebooted my machine. Because it was my first kernel using disk slices I decided to play safe and boot into single-user mode. I got lots of warnings from sd0d sd0d: start 0, end 2117631, size 2117632 sd0: rejecting partition in BSD label: it isn't entirely within the slice but otherwise all seemed OK. I run 'disklabel sd0' to see that all partitions were still there and rebooted again: # reboot syncing disks... done fs = / panic: update: rofs mod [ I managed to get system core dump if somebody is interested ] Then I brought the system to multi-user and used disklabel -e to get rid of that offending sd0d partition. Then I rebooted again to singe-user and found out that reboot no longer causes panic. The only strange thing now is that the slice code prints out my partitions thrice: sd0s1: start 32, end = 204799, size 204768: OK sd0s2: start 204800, end = 2117631, size 1912832: OK sd0s1: start 32, end = 204799, size 204768: OK sd0s2: start 204800, end = 2117631, size 1912832: OK sd0s1: start 32, end = 204799, size 204768: OK sd0s2: start 204800, end = 2117631, size 1912832: OK Is that normal? ..vode