|
From: | Doug Nazar |
Subject: | Re: Big Endian fix patch |
Date: | Wed, 28 Jul 2010 14:17:10 -0400 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 |
On 2010-07-28 1:52 PM, Lennart Sorensen wrote:
Another thing that puzzles me is that when I boot linux, I always get a message that says the state is wrong with the superblock on the sda partitions, but the sdb partitions have the right state. I have no idea if grub messes with this, or if the system isn't shutting down the raid properly on reboots. It manages to assemble the raid and fix it automatically, but the error is strange since I have never seen that before. Of course I haven't really used 1.x raid before either, so maybe that's part of it.
It really shouldn't be doing that. Grub shouldn't be doing any writes at all during boot (unless you're using some of the more exotic commands or save_env) and the raid code specifically errors on writes to it.
If it was linux I'd expect both drives to be wrong unless there is something silly in the init scripts.
When you say it fixes it, is that a full re-sync or something else? Could you check the superblocks? In grub use the following on each device for 1.2 arrays.
hexdump -s 4096 -n 256 (dev,p) Doug
[Prev in Thread] | Current Thread | [Next in Thread] |