Hi Michael:
I still ran your advice and got this result:
creator:~# mdadm -D /dev/md1
/dev/md1:
Version : 00.90
Is it a big problem running version 0.9? I use the version of the tools
that comes with Debian - and as they are "some" conservative their
versions lags some behind.
I have now upgraded my Debian Etch to Debian Lenny and have this mdadm:
creator:~# mdadm --version
mdadm - v2.6.7.2 - 14th November 2008
When I fix the firmware issues on my motherboard or buys a sepparate
sata controller.... will the superblock be one of the version you
suggests when I create the raid again? If not is it that large problem
and I should upgrade my tools beyond what Debian provides?
Best Regards,
Arild
Michael Evans wrote:
One other thing besides what's already been mentioned. You are seeing
issues with Raid1 and -not- your Raid5 volume. If you run mdadm -D
/dev/md(whatever the number is) what version (for the superblock) is
reported? Preferably you will be using either superblock 1.1 or 1.2
(preferably 1.1). The only reason to use mdadm 1.0 or 0.9 are special
cases, such as for /boot style volumes.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
