From owner-freebsd-bugs Fri Dec 7 9:40:10 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 06E4237B417 for ; Fri, 7 Dec 2001 09:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fB7He1Y44725; Fri, 7 Dec 2001 09:40:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8E0DB37B405 for ; Fri, 7 Dec 2001 09:33:07 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fB7HX7I44123; Fri, 7 Dec 2001 09:33:07 -0800 (PST) (envelope-from nobody) Message-Id: <200112071733.fB7HX7I44123@freefall.freebsd.org> Date: Fri, 7 Dec 2001 09:33:07 -0800 (PST) From: Mike Jakubik To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: conf/32583: System becomes unusable after performing disk operations using /stand/sysinstall Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 32583 >Category: conf >Synopsis: System becomes unusable after performing disk operations using /stand/sysinstall >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 07 09:40:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Mike Jakubik >Release: 4.4-RELEASE >Organization: Trigger Internet Solutions >Environment: 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001 murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 >Description: After using /stand/sysinstall to create a file system and partitions, the system practically ceases to exist. Commands are reported as not found, cd reports not found as well. New processes can not start, system becomes unusable and unstable. Soft reboot procedure is unable to complete properly (panics), data loss may occur. This can be a very serious problem when an admin attempts to do some disk configuration on a live system. >How-To-Repeat: System is an Intel D815EEA2 Desktop Board, 850Mhz Celeron CPU, 256MB RAM. Tested with an IBM and Seagate 20 gig hd. ad0 == root hd, ad2 == blank, unmounted hd. /stand/sysinstall Configure Fdisk ad2 A)ll S)et bootable W)rite Standard Quit, Cancel, Cancel, Exit /stand/sysinstall Configure Label ad2 C, 512M, Swap C, , FS, / W)rite, Y Quit, Cancel, Cancel, Exit root@qos:~# ls bash: ls: command not found root@qos:~# uname -a bash: /usr/bin/uname: No such file or directory root@qos:~# cd /usr/bin bash: cd: /usr/bin: No such file or directory root@qos:~# echo * * >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message