I haven't tried this in a while so I might be doing something wrong here.
I'm trying to build a couple arrays in degraded mode (RAID 1 & RAID 5).
This is on a system running kernel 2.2.6 & raid0145-19990421-2.2.6 patch.
A sample RAID-1 config that I'm playing with is below. I though that we
co
mkraid does this:
[root@penguin rothwell]# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sda2, 8369865kB, raid superblock at 8369792kB
/dev/sda2 appears to contain an ext2 filesystem -- use -f to override
mkraid: aborted
[root@penguin rothwell]# mkraid --really
we have a server:
dual intel PII 400Mhz
512MB RAM
BusLogic BT-958 scsi
running:
kernel 2.2.5 w/ raid0145-19990309 patch.
debian 2.1r2
dump 0.4b4-13
the problem:
we are having problems with dump causing a panic with kswapd. this is a
repeatable condition. with a raid0 device configur
Greetings,
Since 2.2.6 had some networking problems that played havoc with a new
server I'm trying to put up I decided to try to put 2.2.7 on it. The
4/21 RAID patches are almost clean--some offsets, and only one
rejection. That rejection concerns me, though. For stock 2.2.7, in
linux/include/
Hi
Some suggestions/questions:
- Did you patch the kernel?
- If yes, try mkraid --really-force /dev/mdX
- Are you using the right raidtools (0.90)?
Greetings, Dietmar
>- Ursprüngliche Nachricht -
>Absender: [EMAIL PROTECTED]
>Betreff: mkraid: aborted
>Empfänger: [EMAIL PROTECTED]
>Datu
