* error during raid config
@ 2004-01-16 18:18 gannan10
2004-01-16 18:26 ` Steven Ihde
0 siblings, 1 reply; 6+ messages in thread
From: gannan10 @ 2004-01-16 18:18 UTC (permalink / raw)
To: linux-raid
From: gannan10@comcast.net [ Save Address ]
To: linux-raid@vger.rutgers.edu
Subject: error during raid config
Date: Fri, 16 Jan 2004 05:27:40 +0000
Hello,
I get the following error when I tried to setup my raid:
# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hda1, 489951kB, raid superblock at 489856kB
/dev/hda1 is mounted
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
Here is my config information:
# cat /proc/mdstat
Personalities :
read_ahead not set
unused devices: <none>
cat /etc/raidtab
# Persistent raid-1 configuration - md0
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hda1
raid-disk 0
device /dev/hdb1
raid-disk 1
# Persistent raid-1 configuration - md1
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hda3
raid-disk 0
device /dev/hdb3
raid-disk 1
# Persistent raid-1 configuration - md2
raiddev /dev/md2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hda5
raid-disk 0
device /dev/hdb5
raid-disk 1
# Persistent raid-1 configuration - md3
raiddev /dev/md3
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hda6
raid-disk 0
device /dev/hdb6
raid-disk 1
# Persistent raid-1 configuration - md4
raiddev /dev/md4
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hda7
raid-disk 0
device /dev/hdb7
raid-disk 1
# fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 4111 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 61 489951 fd Linux raid autodetect
/dev/hda2 62 122 489982+ 82 Linux swap
/dev/hda3 123 495 2996122+ fd Linux raid autodetect
/dev/hda4 496 4111 29045520 5 Extended
/dev/hda5 496 1700 9679131 fd Linux raid autodetect
/dev/hda6 1701 2905 9679131 fd Linux raid autodetect
/dev/hda7 2906 4111 9687163+ fd Linux raid autodetect
# fdisk -l /dev/hdb
Disk /dev/hdb: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 61 489951 fd Linux raid autodetect
/dev/hdb2 62 122 489982+ 82 Linux swap
/dev/hdb3 123 495 2996122+ fd Linux raid autodetect
/dev/hdb4 496 4111 29045520 5 Extended
/dev/hdb5 496 1700 9679131 fd Linux raid autodetect
/dev/hdb6 1701 2905 9679131 fd Linux raid autodetect
/dev/hdb7 2906 4111 9687163+ fd Linux raid autodetect
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: error during raid config
2004-01-16 18:18 error during raid config gannan10
@ 2004-01-16 18:26 ` Steven Ihde
0 siblings, 0 replies; 6+ messages in thread
From: Steven Ihde @ 2004-01-16 18:26 UTC (permalink / raw)
To: gannan10; +Cc: linux-raid
On Fri, Jan 16, 2004 at 06:18:07PM +0000, gannan10@comcast.net wrote:
> Hello,
>
> I get the following error when I tried to setup my raid:
>
> # mkraid /dev/md0
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hda1, 489951kB, raid superblock at 489856kB
> /dev/hda1 is mounted
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
I use mdadm, not mkraid, but it appears the problem is right there:
"/dev/hda1 is mounted". Probably if you have a mounted filesystem on
/dev/hda1, you cannot add it to the raid array. Once you've created
the raid array you can mount /dev/md0 instead of /dev/hda1.
-Steve
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: error during raid config
@ 2004-01-16 20:13 gannan10
2004-01-16 20:31 ` Guy
0 siblings, 1 reply; 6+ messages in thread
From: gannan10 @ 2004-01-16 20:13 UTC (permalink / raw)
To: Steven Ihde; +Cc: linux-raid
so what do I do now???
> On Fri, Jan 16, 2004 at 06:18:07PM +0000, gannan10@comcast.net wrote:
> > Hello,
> >
> > I get the following error when I tried to setup my raid:
> >
> > # mkraid /dev/md0
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/hda1, 489951kB, raid superblock at 489856kB
> > /dev/hda1 is mounted
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> I use mdadm, not mkraid, but it appears the problem is right there:
> "/dev/hda1 is mounted". Probably if you have a mounted filesystem on
> /dev/hda1, you cannot add it to the raid array. Once you've created
> the raid array you can mount /dev/md0 instead of /dev/hda1.
>
> -Steve
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: error during raid config
@ 2004-01-16 20:19 gannan10
2004-01-16 20:39 ` Guy
0 siblings, 1 reply; 6+ messages in thread
From: gannan10 @ 2004-01-16 20:19 UTC (permalink / raw)
To: Steven Ihde; +Cc: linux-raid
the command worked for other md(1 - 4) and the cat /proc/mdstat looks like the following:
# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md4 : active raid1 hdb7[0]
9687040 blocks [2/1] [U_]
md3 : active raid1 hdb6[0]
9679040 blocks [2/1] [U_]
md2 : active raid1 hdb5[0]
9679040 blocks [2/1] [U_]
md1 : active raid1 hdb3[0]
2996032 blocks [2/1] [U_]
md0 : inactive
unused devices: <none>
Now when I use mkraid for md0 I get the following error:
# mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hdb1, 489951kB, raid superblock at 489856kB
disk 1: /dev/hda1, failed
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
the syslog shows this:
---Jan 16 14:16:17 adobea kernel: md: array md0 already exists!
I alos tried mounting it and I get the following error:
~# mount -t ext2 /dev/md0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
Please help.. I am using procedure at: http://tldp.org/HOWTO/Boot+Root+Raid+LILO-4.html
Thanks
Gordon.
> On Fri, Jan 16, 2004 at 06:18:07PM +0000, gannan10@comcast.net wrote:
> > Hello,
> >
> > I get the following error when I tried to setup my raid:
> >
> > # mkraid /dev/md0
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/hda1, 489951kB, raid superblock at 489856kB
> > /dev/hda1 is mounted
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> I use mdadm, not mkraid, but it appears the problem is right there:
> "/dev/hda1 is mounted". Probably if you have a mounted filesystem on
> /dev/hda1, you cannot add it to the raid array. Once you've created
> the raid array you can mount /dev/md0 instead of /dev/hda1.
>
> -Steve
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: error during raid config
2004-01-16 20:13 gannan10
@ 2004-01-16 20:31 ` Guy
0 siblings, 0 replies; 6+ messages in thread
From: Guy @ 2004-01-16 20:31 UTC (permalink / raw)
To: gannan10, 'Steven Ihde'; +Cc: linux-raid
Give output of df command. If hda1 is listed, then unmount it!
-----Original Message-----
From: linux-raid-owner@vger.kernel.org
[mailto:linux-raid-owner@vger.kernel.org] On Behalf Of gannan10@comcast.net
Sent: Friday, January 16, 2004 3:14 PM
To: Steven Ihde
Cc: linux-raid@vger.kernel.org
Subject: Re: error during raid config
so what do I do now???
> On Fri, Jan 16, 2004 at 06:18:07PM +0000, gannan10@comcast.net wrote:
> > Hello,
> >
> > I get the following error when I tried to setup my raid:
> >
> > # mkraid /dev/md0
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/hda1, 489951kB, raid superblock at 489856kB
> > /dev/hda1 is mounted
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> I use mdadm, not mkraid, but it appears the problem is right there:
> "/dev/hda1 is mounted". Probably if you have a mounted filesystem on
> /dev/hda1, you cannot add it to the raid array. Once you've created
> the raid array you can mount /dev/md0 instead of /dev/hda1.
>
> -Steve
>
>
>
-
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: error during raid config
2004-01-16 20:19 gannan10
@ 2004-01-16 20:39 ` Guy
0 siblings, 0 replies; 6+ messages in thread
From: Guy @ 2004-01-16 20:39 UTC (permalink / raw)
To: gannan10, 'Steven Ihde'; +Cc: linux-raid
md1-4 all have 1 disk missing! Maybe that is a clue!
Is your disk hda bad?
Most people say mkraid is bad. You should use mdadm. I agree.
-----Original Message-----
From: linux-raid-owner@vger.kernel.org
[mailto:linux-raid-owner@vger.kernel.org] On Behalf Of gannan10@comcast.net
Sent: Friday, January 16, 2004 3:19 PM
To: Steven Ihde
Cc: linux-raid@vger.kernel.org
Subject: Re: error during raid config
the command worked for other md(1 - 4) and the cat /proc/mdstat looks like
the following:
# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md4 : active raid1 hdb7[0]
9687040 blocks [2/1] [U_]
md3 : active raid1 hdb6[0]
9679040 blocks [2/1] [U_]
md2 : active raid1 hdb5[0]
9679040 blocks [2/1] [U_]
md1 : active raid1 hdb3[0]
2996032 blocks [2/1] [U_]
md0 : inactive
unused devices: <none>
Now when I use mkraid for md0 I get the following error:
# mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hdb1, 489951kB, raid superblock at 489856kB
disk 1: /dev/hda1, failed
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
the syslog shows this:
---Jan 16 14:16:17 adobea kernel: md: array md0 already exists!
I alos tried mounting it and I get the following error:
~# mount -t ext2 /dev/md0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
Please help.. I am using procedure at:
http://tldp.org/HOWTO/Boot+Root+Raid+LILO-4.html
Thanks
Gordon.
> On Fri, Jan 16, 2004 at 06:18:07PM +0000, gannan10@comcast.net wrote:
> > Hello,
> >
> > I get the following error when I tried to setup my raid:
> >
> > # mkraid /dev/md0
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/hda1, 489951kB, raid superblock at 489856kB
> > /dev/hda1 is mounted
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> I use mdadm, not mkraid, but it appears the problem is right there:
> "/dev/hda1 is mounted". Probably if you have a mounted filesystem on
> /dev/hda1, you cannot add it to the raid array. Once you've created
> the raid array you can mount /dev/md0 instead of /dev/hda1.
>
> -Steve
>
>
>
-
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-01-16 20:39 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-16 18:18 error during raid config gannan10
2004-01-16 18:26 ` Steven Ihde
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 20:13 gannan10
2004-01-16 20:31 ` Guy
2004-01-16 20:19 gannan10
2004-01-16 20:39 ` Guy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).