Date: Sat, 5 Aug 2006 19:30:53 -0400 From: "John Rogers" <ruralriver@gmail.com> To: "Colin Percival" <cperciva@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: binary upgrade issues Message-ID: <100416c30608051630h77d99f7dkdcc1e5be23af614b@mail.gmail.com> In-Reply-To: <44D2DE70.4020002@freebsd.org> References: <100416c30608031503n721c1583labb86a1e8abe7978@mail.gmail.com> <44D2DE70.4020002@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, you are right - there was indeed the following messages: kernel: ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> 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 <cperciva@freebsd.org> 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?100416c30608051630h77d99f7dkdcc1e5be23af614b>