Bill Davidsen wrote:
Daniel L. Miller wrote:
Current mdadm.conf:
DEVICE partitions
ARRAY /dev/.static/dev/md0 level=raid10 num-devices=4
UUID=9d94b17b:f5fac31a:577c252b:0d4c4b2a auto=part
still have the problem where on boot one drive is not part of the
array. Is there a log file I can check to find out WHY a drive is
not being added? It's been a while since the reboot, but I did find
some entries in dmesg - I'm appending both the md lines and the
physical disk related lines. The bottom shows one disk not being
added (this time is was sda) - and the disk that gets skipped on each
boot seems to be random - there's no consistent failure:
I suspect the base problem is that you are using whole disks instead
of partitions, and the problem with the partition table below is
probably an indication that you have something on that drive which
looks like a partition table but isn't. That prevents the drive from
being recognized as a whole drive. You're lucky, if the data looked
enough like a partition table to be valid the o/s probably would have
tried to do something with it.
[...]
This may be the rare case where you really do need to specify the
actual devices to get reliable operation.
OK - I'm officially confused now (I was just unofficially before). WHY
is it a problem using whole drives as RAID components? I would have
thought that building a RAID storage unit with identically sized drives
- and using each drive's full capacity - is exactly the way you're
supposed to! I should mention that the boot/system drive is IDE, and
NOT part of the RAID. So I'm not worried about losing the system - but
I AM concerned about the data. I'm using four drives in a RAID-10
configuration - I thought this would provide a good blend of safety and
performance for a small fileserver.
Because it's RAID-10 - I would ASSuME that I can drop one drive (after
all, I keep booting one drive short), partition if necessary, and add it
back in. But how would splitting these disks into partitions improve
either stability or performance?
--
Daniel
-
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
