From mboxrd@z Thu Jan 1 00:00:00 1970 From: "GeneralNMX" Subject: Raid starts dirty every boot on Ubuntu Date: Sun, 1 Feb 2009 12:23:16 -0500 Message-ID: <004101c98491$c575dd10$50619730$@com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: References: In-Reply-To: Content-Language: en-us Sender: linux-raid-owner@vger.kernel.org To: linux-raid@vger.kernel.org List-Id: linux-raid.ids On my Ubuntu server, ALL my raids start dirty every single time and kic= ks one drive (any one of the four), re-adds it, then reconstructs the raid array. For the example below, this is a raid1 with two spares. =A0When = it finishes booting, the device that was kicked is still in the array, as = a spare. This makes the boot literally take hours, and I don=92t know exa= ctly what it=92s doing since it just sits there without a progress indicator= =2E I don=92t think it=92s fsck because it doesn=92t even get to fsck yet in = the runlevel. It goes like this: md: md7 stopped. md: unbind md: export_rdev(sda9) md: ubind md: export_rdev(sdb9) md: bind md: bind md: bind md: bind md: Kicking non-fresh sdd9 from array! md: unbind md: export_rdev(sdd9) raid1: raid set md7 active with 2 out of 2 mirrors -- To unsubscribe from this list: send the line "unsubscribe linux-raid" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html