Marc L. de Bruin wrote:
Situation: /dev/md0, type raid1, containing 2 active devices
(/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
Those two spare 'partitions' are the only partitions on those disks
and therefore I'd like to spin down those disks using hdparm
Neil Brown wrote:
On Thursday June 22, [EMAIL PROTECTED] wrote:
Marc L. de Bruin wrote:
Situation: /dev/md0, type raid1, containing 2 active devices
(/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
Those two spare 'partitions' are the only partitions
Lo,
Situation: /dev/md0, type raid1, containing 2 active devices (/dev/hda1
and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
Those two spare 'partitions' are the only partitions on those disks and
therefore I'd like to spin down those disks using hdparm for obvious
reasons
dean gaudet wrote:
On Sun, 9 Apr 2006, Marc L. de Bruin wrote:
...
Okay, just pressing Control-D continues the boot process and AFAIK the root
filesystemen actually isn't corrupt. Running e2fsck returns no errors and
booting 2.6.11 works just fine, but I have no clue why it picked
dean gaudet wrote:
On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
dean gaudet wrote:
initramfs-tools generates an mdrun /dev which starts all the raids it can
find... but does not include the mdadm.conf in the initrd so i'm not sure it
will necessarily start them in the right minor devices
Hi,
(I just subscribed, sorry if this is a dupe. I did try to match the
subject from the archives, but couldn't find any...)
I ran into trouble after upgrading a Debian Sarge system from 2.6.11 to
2.6.15. To be more precise, it turned out that md/mdadm seems to not
function properly during
