Re: confusing mkraid problems

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

 



On Saturday March 2, l-berland@northwestern.edu wrote:
> Brand new just-compiled 2.2.20 kernel, including md, but mkraid never ever 
> works. 
> 
> /etc/raidtab: 
> raiddev /dev/md0 
> raid-level linear 
> nr-raid-disks 2 
> chunk-size 32 
> persistent-superblock 1 
> device /dev/hdd1 
> raid-disk 0 
> device /dev/sdb1 
> raid-disk 1 

2.2.20 needs patches for mkraid (and persistent-superblock) to work.
A copy if the patch is at

  http://www.cse.unsw.edu.au/~neilb/patches/raid-2.2.20/raid-2.2.20.patch

but I would strongly recommend 2.4.18 if that is at all an option.

NeilBrown

> 
> complete output of mkraid: 
> handling MD device /dev/md0 
> analyzing super-block 
> disk 0: /dev/hdd1, 10022008kB, raid superblock at 10021888kB 
> disk 1: /dev/sdb1, 36081959kB, raid superblock at 36081856kB 
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues. 
> 
> The syslog contains nothing even related 
> 
> /proc/mdstat 
> Personalities : [1 linear] [2 raid0] [3 raid1] 
> read_ahead 128 sectors 
> md0: inactive 
> (same for md1-3) 
> 
> Does anyone have any clue what could be wrong? 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> 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@vger.kernel.org
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