On Saturday 23 June 2001 05:24, you wrote:
> hi ya iain...
>
> what does your /etc/fstab and /etc/raidtab look like ???
My apologies
initial /etc/raidtab
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
persistent-superblock 1
device /dev/sdc1
raid-disk 0
device /dev/sdd1
raid-disk 1
Boot will fail to raidstart and drop to shell prompt if I use this raidtab
after /dev/sdc1 has failed and been replaced
If I change to this raidtab the boot completes with the array in degraded
mode, allowing me to fdisk the new drive and then raidhotadd it
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
persistent-superblock 1
device /dev/sdd1
raid-disk 1
device /dev/sdc1
raid-disk 0
At this point there are no file systems involved, so no /etc/fstab entries
reference /dev/md1
Any ideas??
>
> thanx
> alvin
> http://www.Linux-1U.net ... 500Gb 1U Raid5 ...
>
> On Sat, 23 Jun 2001, Iain Campbell wrote:
> > Scenario:
> >
> > 1. Simple 2 disk RAID1
> > 2. Disk 0 fails
> > 3. Bring machine down and replace disk (same SCSI id as old one)
> > 4. Boot hangs on raidstart with "/dev/md1: invalid argument" error
> >
> > I can fix the problem by switching disks in /etc/raidtab, ie by making
> > the old disk1 disk0, then the array starts fine in degraded mode and I
> > can go from there.
> >
> > I am running kernel 2.4.2 (old, I know). Is this likely to have been
> > fixed in more recent kernels?
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
