>       root@excel linux]# more /etc/raidtab
> raiddev                 /dev/md0
>         # General parameters
>         raid-level              0
>         nr-raid-disks           2
>         chunk-size              1024
>

Where is the persistent-superblock line?

RAID-0 used to default to no persistent-superblocks for RAID-0 for backwards
compatibility's sake. I forget whether this is still the case, and if not, at
which version of the raidtools it changed.

If your RAID-0 was setup without persistent superblocks, is it possible that
raidstart can see older RAID-1 superblocks on the partitions? That is, of
course, assuming that you had used these partitions for RAID-1 before.

If your RAID-0 is without persistent-superblocks, I believe you will have to
mkraid it every time you want to start it.

Cheers,


Bruno Prior         [EMAIL PROTECTED]

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: 14 May 1999 22:18
> To: [EMAIL PROTECTED]
> Subject: Aggghhh, raid1 when I want raid0
>
>
>
>
>       For the past 4-5 weeks I have had a successfully running raid0
> array on 2 4gb scsi disks.
>
>       Today, I took the system down to install a new tape drive so that
> I could do backups on said raid0 array.
>
>       To make a long sad story short, the array insists on thinking its
> a raid1 array, and not a raid0 array. I am **POSITIVE** that it was
> configured as a raid0 array, as it had about 6gb of data on it out of teh
> total 8gb available (2x4gb drives).
>
>       Here is my /etc/raidtab
>
>       root@excel linux]# more /etc/raidtab
> raiddev                 /dev/md0
>         # General parameters
>         raid-level              0
>         nr-raid-disks           2
>         chunk-size              1024
>
>         # RAID disks
>         device                  /dev/sdb1
>         raid-disk               0
>         device                  /dev/sdc1
>         raid-disk               1
>
>
>       This system had been rebooted 2-3 times since I had
> installed the raid0 array.
>
>       When I execute a 'raidstart /dev/md0', here is what
> /var/log/messages tells me;
>
>       May 14 15:17:28 excel kernel: (read) sdb1's sb offset: 4192832
> [events: 00000079]
> May 14 15:17:28 excel kernel: autorun ...
> May 14 15:17:28 excel kernel: considering sdb1 ...
> May 14 15:17:28 excel kernel:   adding sdb1 ...
> May 14 15:17:28 excel kernel: created md0
> May 14 15:17:28 excel kernel: bind<sdb1,1>
> May 14 15:17:28 excel kernel: running: <sdb1>
> May 14 15:17:28 excel kernel: now!
> May 14 15:17:28 excel kernel: sdb1's event counter: 00000079
> May 14 15:17:28 excel kernel: md0: max total readahead window set to 128k
> May 14 15:17:28 excel kernel: md0: 1 data-disks, max readahead per
> data-disk: 128k
> May 14 15:17:28 excel kernel: raid1: device sdb1 operational as mirror 0
> May 14 15:17:28 excel kernel: raid1: md0, not all disks are operational --
> trying to recover array
> May 14 15:17:28 excel kernel: raid1: raid set md0 active with 1 out of 2
> mirrors
> May 14 15:17:28 excel kernel: md: updating md0 RAID superblock on device
> May 14 15:17:28 excel kernel: sdb1 [events: 0000007a](write) sdb1's sb
> offset: 4192832
> May 14 15:17:28 excel kernel: md: recovery thread got woken up ...
> May 14 15:17:28 excel kernel: md0: no spare disk to reconstruct array! --
> continuing in degraded mode
> May 14 15:17:28 excel kernel: md: recovery thread finished ...
> May 14 15:17:29 excel kernel: .
> May 14 15:17:29 excel kernel: ... autorun DONE.
>
>
>       What the heck I am gonna do with this???????? I sure hope I have
> not lost teh data that was on my raid0 array..
>
>       Chris

Reply via email to