Re: /dev/md2 stopped after changing SAS controller

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

 



On Sat, May 14, 2011 at 12:21 PM, Louis-David Mitterrand
<vindex+lists-linux-raid@xxxxxxxxxxx> wrote:
> On Sat, May 14, 2011 at 07:33:47AM +1000, NeilBrown wrote:
>> On Fri, 13 May 2011 22:29:01 +0200 Louis-David Mitterrand
>> <vindex+lists-linux-raid@xxxxxxxxxxx> wrote:
>> > Each disk is configured thus:
>> >
>> >     Disk /dev/sda: 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: 0x05022e04
>> >
>> >        Device Boot      Start         End      Blocks   Id  System
>> >     /dev/sda1               1          32      257008+  fd  Linux raid autodetect
>> >     /dev/sda2              33       17500   140311710   fd  Linux raid autodetect
>> >     /dev/sda3           17501      121601   836191282+  fd  Linux raid autodetect
>> >
>>
>> Is this the config reported with the old controller or with the new
>> controller?
>
> Sorry for the confusion, the above was with the old (LSI) controller.
> This is the disk geometry with the new (Adaptec) controller:
>
>        Disk /dev/sda: 1000.1 GB, 1000104157184 bytes
>        255 heads, 63 sectors/track, 121589 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: 0x6397e8f6
>
>           Device Boot      Start         End      Blocks   Id  System
>        /dev/sda1               1          32      257008+  fd  Linux raid autodetect
>        /dev/sda2              33       17500   140311710   fd  Linux raid autodetect
>        /dev/sda3           17501      121601   836191282+  fd  Linux raid autodetect
>
> Ah! 121589 vs 121601 cylinders...
>
>> Because my guess is that the new controller makes the devices look a little
>> bit smaller.  That would cause the kernel to reject them, but quite possibly
>> allow mdadm to think they look OK.
>>
>> It would also explain why the first 2 partitions work fine and only the last
>> one is a problem.
>>
>> If this were the case I would expect a message like:
>>          "%s: p%d size %llu extends beyond EOD
>
> Spot on:
>
>        May 14 10:15:46 zenon kernel: sda: p3 size 1672382565 extends beyond EOD, trunca
> ted
>
> Is there any solution other than backuping my /dev/md2 somewhere with
> the old controller and re-creating a (slightly) smaller one with the new
> controller?
This is just one more live example for partitions vs disks setups.

>
> Thanks,
> --
> 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
>



-- 
Best regards,
[COOLCOLD-RIPN]
--
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