Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261948AbVANKut (ORCPT ); Fri, 14 Jan 2005 05:50:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261954AbVANKut (ORCPT ); Fri, 14 Jan 2005 05:50:49 -0500 Received: from tornado.reub.net ([60.234.136.108]:19600 "EHLO tornado.reub.net") by vger.kernel.org with ESMTP id S261948AbVANKun (ORCPT ); Fri, 14 Jan 2005 05:50:43 -0500 Message-Id: <6.2.0.14.2.20050114233439.01cbb8d8@tornado.reub.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Fri, 14 Jan 2005 23:50:39 +1300 To: linux-kernel@vger.kernel.org From: Reuben Farrelly Subject: Breakage with raid in 2.6.11-rc1-mm1 [Regression in mm] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1674 Lines: 46 Something seems to have broken with 2.6.11-rc1-mm1, which worked ok with 2.6.10-mm3. NET: Registered protocol family 17 Starting balanced_irq BIOS EDD facility v0.16 2004-Jun-25, 2 devices found md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Waiting 19sec for root device... VFS: Waiting 18sec for root device... VFS: Waiting 17sec for root device... VFS: Waiting 16sec for root device... VFS: Waiting 15sec for root device... VFS: Waiting 14sec for root device... VFS: Waiting 13sec for root device... VFS: Waiting 12sec for root device... VFS: Waiting 11sec for root device... VFS: Waiting 10sec for root device... VFS: Waiting 9sec for root device... VFS: Waiting 8sec for root device... VFS: Waiting 7sec for root device... VFS: Waiting 6sec for root device... VFS: Waiting 5sec for root device... VFS: Waiting 4sec for root device... VFS: Waiting 3sec for root device... VFS: Waiting 2sec for root device... VFS: Waiting 1sec for root device... VFS: Cannot open root device "md2" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) The system is running 5 RAID-1 partitions, and md2 is the root as per grub.conf. Problem seems to be that raid autodetection finds no raid partitions :( The two ST380013AS SATA drives are detected earlier in the boot, so I don't think that's the problem.. Reuben - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/