Sam Varshavchik píše v St 14. 12. 2011 v 18:41 -0500:
j...@bubble.org writes:
False raid detection is often caused by wrong partition type.
It suppose to be
fd Linux raid autodetect
What do you have?
fdisk -l /dev/sda
or
fdisk -l /dev/sdb
Pavel
--
Pavel Lisy p...@tmapy.cz
T-MAPY spol. s
Pavel Lisy writes:
Sam Varshavchik píše v St 14. 12. 2011 v 18:41 -0500:
j...@bubble.org writes:
False raid detection is often caused by wrong partition type.
It suppose to be
fd Linux raid autodetect
What do you have?
fdisk -l /dev/sda
or
fdisk -l /dev/sdb
What it should be. My
I have two RAID1 drives with multiple partitions.
Each time I reboot, one of the partitions comes up degraded with only one of
the two devices. The only thing that the kernel logs is:
[ 13.327731] md/raid1:md3: active with 1 out of 2 mirrors
I can hot-add the other partition, and wait for
I have two RAID1 drives with multiple partitions.
Each time I reboot, one of the partitions comes up degraded with only one
of
the two devices. The only thing that the kernel logs is:
[ 13.327731] md/raid1:md3: active with 1 out of 2 mirrors
I can hot-add the other partition, and wait
j...@bubble.org writes:
I have two RAID1 drives with multiple partitions.
Each time I reboot, one of the partitions comes up degraded with only one
of
the two devices. The only thing that the kernel logs is:
[ 13.327731] md/raid1:md3: active with 1 out of 2 mirrors
I can hot-add the
