RE: sw_raid5-failed_disc(s)-2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It seems like a trick question! :)
You don't use "missing" on assemble, it is a keyword for the create command.

For assemble. just don't list that device.
mdadm --assemble --run --force /dev/md2 /dev/hdi1 /dev/hdk1 /dev/hdo1

mdadm will know which disk is which.

Guy


-----Original Message-----
From: linux-raid-owner@xxxxxxxxxxxxxxx
[mailto:linux-raid-owner@xxxxxxxxxxxxxxx] On Behalf Of Ronny Plattner
Sent: Saturday, March 12, 2005 8:37 AM
To: linux-raid@xxxxxxxxxxxxxxx
Subject: Re: sw_raid5-failed_disc(s)-2

Hi !

Today i tried following:

-snip-
server:~# mdadm --assemble --run --force /dev/md2 /dev/hdi1 /dev/hdk1
missing /dev/hdo1
mdadm: cannot open device missing: No such file or directory
mdadm: missing has no superblock - assembly aborted

server:~# cat /var/log/messages
Mar 12 14:27:49 server kernel: md: md2 stopped.
Mar 12 14:28:05 server kernel: md: md2 stopped.
-snap-


Maybe this information is useful.

Regards
Ronny

-
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux