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

Re: issue with mdadm and mirroring drives



Sorry to load up on related issues in this mail, but have a big issue:
After having synced my mirrored drives in software raid -
I get the following error:
error: superfluous RAID member (2 found).

the boot drive is /dev/sdc1 but added another one to the mirror - /dev/sdd1
my questions :
1. should i put both drives in the bootup bios scan ?
2. should i set their partitions as bootable in fdisk ?
3. how do i fix this without having to zero out the drive and re-add
it to the mirror ?


On Tue, Jan 24, 2012 at 12:34 PM, Joey L <mjh2000@gmail.com> wrote:
> In related questions - i hope you can answer - are :
>
> 1. why do i get an error when trying to make swap partition - i get
> this error below after running fdisk, creating a primary partition
> /dev/sdd2 and then changing the type - with t -
> As in below ---
>
> 2. the /dev/sdd drive is the mirrored drive in the set - do i have to
> set /dev/sdd1 active in fdisk ???
>
>
> root@rider:~# mkswap /dev/sdd2
>
> mkswap: error: swap area needs to be at least 40 KiB
> Usage: mkswap [-c] [-pPAGESZ] [-L label] [-U UUID] /dev/name [blocks]
> root@rider:~# fdisk -l /dev/sdd
>
>
> Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0005d0fd
>
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdd1               1      121091   972663426   fd  Linux raid autodetect
> /dev/sdd2          121092      121601     4096575   82  Linux swap / Solaris
>
>
> thanks
> mjh
>
>
>
> On Thu, Jan 19, 2012 at 12:44 PM, Marc Auslander <marcausl@gmail.com> wrote:
>> Jon Dowland <jmtd@debian.org> writes:
>>
>>>
>>> Pretty sure at that stage it has loaded modules that let it interpret
>>> a selection of filesystem types, in order to fetch grub.cfg (and
>>> further
>>
>> How does it decide which partition (on which disk) and what pathname
>> to use to find grub.cfg.  I assume one it chooses a partition it can
>> look at partitions, figure out what kind they are, and figure out how
>> to read them.
>>
>> Also - if the chosen partition is raid1 does it "assemble" the array
>> or just use the chosen partition as if it where a degraded array.
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>> Archive: [🔎] 87d3afegeh.fsf@aptiva.optonline.net">http://lists.debian.org/[🔎] 87d3afegeh.fsf@aptiva.optonline.net
>>


Reply to: