From owner-freebsd-questions@FreeBSD.ORG Sat Aug 5 23:30:56 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A017716A4E9 for ; Sat, 5 Aug 2006 23:30:56 +0000 (UTC) (envelope-from ruralriver@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3C4643D4C for ; Sat, 5 Aug 2006 23:30:54 +0000 (GMT) (envelope-from ruralriver@gmail.com) Received: by nf-out-0910.google.com with SMTP id g2so889466nfe for ; Sat, 05 Aug 2006 16:30:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GFzMeNf8zSgNm8lo+qdPPbW8Tik0jTPfNdD2UjKtFeUp0a+MhvK1SgoX/VJcOPbYtSelysRlER3sdcuCR+Q+7xEL1wojn0S2fQxEW1M0wm7PM9Ub3SallQfq2IRchOrZbjRIKGUe7Qjz6JnkHCyulvhtEdZMXT6KIcB2V6eNgXU= Received: by 10.78.133.10 with SMTP id g10mr2001164hud; Sat, 05 Aug 2006 16:30:53 -0700 (PDT) Received: by 10.78.129.17 with HTTP; Sat, 5 Aug 2006 16:30:53 -0700 (PDT) Message-ID: <100416c30608051630h77d99f7dkdcc1e5be23af614b@mail.gmail.com> Date: Sat, 5 Aug 2006 19:30:53 -0400 From: "John Rogers" To: "Colin Percival" In-Reply-To: <44D2DE70.4020002@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <100416c30608031503n721c1583labb86a1e8abe7978@mail.gmail.com> <44D2DE70.4020002@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: binary upgrade issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Aug 2006 23:30:56 -0000 Hi, you are right - there was indeed the following messages: kernel: ad0: FAILURE - READ_DMA status=51 error=40 And this message appeared starting from the date I ran CFS, an encrypted filesystem. It's a half year old WesternDigital250GB disk. I now disabled dma (was UDMA100 actually) by adding "hw.ata.ata_dma=0" to /boot/loader.conf . Before I saw your reply, I just manually created those old-index etc by following upgrade.sh, and ran the rest of the upgrade.sh from the "Removing schg flag from existing files..." part. After that I have ran portupgrade, portsnap etc, and so far don't see problem. Do I still need to go back to 6.0 and run upgrade.sh? Thanks. On 8/4/06, Colin Percival wrote: > John Rogers wrote: > > Installing new kernel into /boot/GENERIC... done. > > Moving /boot/kernel to /boot/kernel.old... done. > > Moving /boot/GENERIC to /boot/kernel... done. > > Removing schg flag from existing files... > > > > Then my connection to the server froze and I found the server rebooted > > itself. After login I found it was 6.1-RELEASE FreeBSD 6.1-RELEASE > > #0: Sun May 7 04:32:43 UTC 2006. > > > > Don't know why it rebooted, and my concern it: had it finished > > upgrading? > > Probably not. > > > I looked into the upgrade.sh and found it should continue > > working on files referred in old-index, new-index-nonkern, new-index. > > However none of these files were found in the directory. Also I am > > worried whether the schg flags were recovered. How can I check these? > > Sounds like a generic case of 'system crashed and recently created files > weren't written to disk yet'. I'm really suspicious of the hardware here, > but I'd suggest > 1. mv /boot/kernel /boot/kernel.new > 2. mv /boot/kernel.old /boot/kernel > 3. reboot (back into 6.0-RELEASE) > 4. Run the script again and hope that it manages to finish installing everything > this time. > > Colin Percival >