From owner-freebsd-questions@FreeBSD.ORG Tue Nov 23 09:57:22 2004 Return-Path: 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 7036A16A4CE for ; Tue, 23 Nov 2004 09:57:22 +0000 (GMT) Received: from ptb-relay01.plus.net (ptb-relay01.plus.net [212.159.14.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E908E43D1F for ; Tue, 23 Nov 2004 09:57:21 +0000 (GMT) (envelope-from eric@epetech.plus.com) Received: from epetech.plus.com ([212.56.102.148] helo=[127.0.0.1]) by ptb-relay01.plus.net with esmtp (Exim) id 1CWXQD-000PO3-FS for freebsd-questions@freebsd.org; Tue, 23 Nov 2004 09:57:17 +0000 Received: from [127.0.0.1] ([127.0.0.1]) by [127.0.0.1] with ESMTP (SpamPal v1.583) sender ; 23 Nov 2004 09:55:40 +0100 Message-ID: <41A3091B.30506@epetech.plus.com> Date: Tue, 23 Nov 2004 09:55:39 +0000 From: Eric Penfold User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en, en-us MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ffs_mountroot: can't find rootvp, after source update to RELENG_5_3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 09:57:22 -0000 Hi, I maintain two FreeBSD servers currently running 5.2p8, and was attempting to update one of them to the 5.3 release. I have cvsup-ed to RELENG_5_3, build world and kernel (GENERIC, and was also using GENERIC kernel with 5.2), and then installed kernel. On reboot, it came up with the following message: Mounting root from ufs:/dev/ar0s1a no such device 'ar' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 If I listed boot devices, at the prompt after the above message, it showed the ad4s1a, ad6s1a that ar0s1a maps onto, etc. I was able to unload the kernel and revert back to 5.2, so it would appear to be a problem with the new kernel not recognising the raid array on the server. The controller is detected as: kernel: atapci1: port 0x4010 -0x401f,0x4038-0x403b,0x4040-0x4047,0x403c-0x403f,0x4048-0x404f mem 0xfc300400-0 xfc3005ff irq 27 at device 3.0 on pci3 Unfortunately I dont have the boot message from the failed 5.3 kernel, cos it didnt log it anywhere, and the server is remote - so repeating it isnt easy. I think I remember seeing a similar message under 5.3 though. After some research, I find that raid support for SiI0680 ATA controller is not working in this release. Although this is not the same controller as I have, the symptoms seem similar - "configuration stored under 5.2 or prior may be corrupted". Is it possible, likely, or even safe, that I would need to (re)run the "atacontrol create" commands to recreate the raid array under a 5.3 kernel - and can this be done without destorying the data/partitions already there? Any other suggestions as to how to work around it - without having to (re)install the OS from scratch? Cheers, Eric.