RAID 1 / Power Loss / No SuperBlock

RAID 1 / Power Loss / No SuperBlock

[Adam J Morand]

Hello,

I apologize if this is the wrong place to talk about this.
I run a RH7.2 with software RAID 1, recently the power went out, and drained
the UPS before I got home.
I am unable to restart my RAID because fsck can not run without finding the
superblock

The error I get
[aj@r2d2 aj]$ fsck /dev/hdd1
Parallelizing fsck version 1.23 (15-Aug-2001)
e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/hdd1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Exit 8

Is there RAID tools available for a situation like this that can recreate
the superblocks?
I have tried the backup blocks, I do not know how else or where to look for
more information on reconstructed my dead RAID.

Thank you for any information or hints possible,

aj

Re: RAID 1 / Power Loss / No SuperBlock

[Mike Dresser]

On Sun, 2 Feb 2003, Adam J Morand wrote:

> The error I get
> [aj@r2d2 aj]$ fsck /dev/hdd1

Why would you be modifying the /dev/hdd device?

You're lucky this isn't working, you want to do a fsck /dev/md0 or
whatever your raid1 device is numbered.

Never touch the original partitions.

Mike

Re: RAID 1 / Power Loss / No SuperBlock

[Adam J Morand]

Mike,

I could not get the md0 to resync / reinitialize
raidstop / raidstart / etc...

so I am unable to do fsck /dev/md0
I was thinking if I could get one drive to work I could wipe the other one,
and then rebuild the pair, no??

aj




----- Original Message -----
From: "Mike Dresser" <mdresser_l@windsormachine.com>
To: "Adam J Morand" <Adam.Morand@illuminatedtechnologies.com>
Cc: <linux-raid@vger.kernel.org>
Sent: Sunday, February 02, 2003 1:08 PM
Subject: Re: RAID 1 / Power Loss / No SuperBlock



On Sun, 2 Feb 2003, Adam J Morand wrote:

> The error I get
> [aj@r2d2 aj]$ fsck /dev/hdd1

Why would you be modifying the /dev/hdd device?

You're lucky this isn't working, you want to do a fsck /dev/md0 or
whatever your raid1 device is numbered.

Never touch the original partitions.

Mike

Re: RAID 1 / Power Loss / No SuperBlock

[Mike Dresser]

On Sun, 2 Feb 2003, Adam J Morand wrote:

> Mike,
>
> I could not get the md0 to resync / reinitialize
> raidstop / raidstart / etc...
>
> so I am unable to do fsck /dev/md0
> I was thinking if I could get one drive to work I could wipe the other one,
> and then rebuild the pair, no??
>
> aj

Can you list your /etc/raidtab, and what errors you were getting?

mike

Re: RAID 1 / Power Loss / No SuperBlock

[Adam J Morand]

Mike,

errors included:
cannot determine md version: No such file or directory
and
mount: wrong fs type, bad option, bad superblock on /dev/md2,
       or too many mounted file systems

/etc/raidtab

raiddev             /dev/md2
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hdd1
    raid-disk     0
    device          /dev/hdb1
    raid-disk     1
raiddev             /dev/md1
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hdd2
    raid-disk     0
    device          /dev/hdb2
    raid-disk     1
raiddev             /dev/md0
raid-level                  0
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hdd3
    raid-disk     0
    device          /dev/hdb3
    raid-disk     1




----- Original Message -----
From: "Mike Dresser" <mdresser_l@windsormachine.com>
To: "Adam J Morand" <Adam.Morand@midnightmoon.ca>
Cc: <linux-raid@vger.kernel.org>
Sent: Sunday, February 02, 2003 1:21 PM
Subject: Re: RAID 1 / Power Loss / No SuperBlock


On Sun, 2 Feb 2003, Adam J Morand wrote:

> Mike,
>
> I could not get the md0 to resync / reinitialize
> raidstop / raidstart / etc...
>
> so I am unable to do fsck /dev/md0
> I was thinking if I could get one drive to work I could wipe the other
one,
> and then rebuild the pair, no??
>
> aj

Can you list your /etc/raidtab, and what errors you were getting?

mike

Re: RAID 1 / Power Loss / No SuperBlock

[Mike Dresser]

On Sun, 2 Feb 2003, Adam J Morand wrote:

> Mike,
>
> errors included:
> cannot determine md version: No such file or directory
> and
> mount: wrong fs type, bad option, bad superblock on /dev/md2,
>        or too many mounted file systems
>

And one last thing, what does /proc/mdstat say?

Re: RAID 1 / Power Loss / No SuperBlock

[Adam J Morand]

right now it is all gibbled, I do not have a copy of the proc when it was
working, but says this

cat /proc/mdstat
Personalities : [raid0] [raid1]
read_ahead 1024 sectors
md0 : active raid0 hda3[1] hdb3[0]
      26619520 blocks 64k chunks

md2 : active raid1 hdb1[0]
      5116544 blocks [2/1] [_U]

md1 : active raid1 hda2[1]
      20482752 blocks [2/1] [U_]

unused devices: <none>




----- Original Message -----
From: "Mike Dresser" <mdresser_l@windsormachine.com>
To: "Adam J Morand" <Adam.Morand@midnightmoon.ca>
Cc: <linux-raid@vger.kernel.org>
Sent: Sunday, February 02, 2003 1:32 PM
Subject: Re: RAID 1 / Power Loss / No SuperBlock




On Sun, 2 Feb 2003, Adam J Morand wrote:

> Mike,
>
> errors included:
> cannot determine md version: No such file or directory
> and
> mount: wrong fs type, bad option, bad superblock on /dev/md2,
>        or too many mounted file systems
>

And one last thing, what does /proc/mdstat say?

-
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

Re: RAID 1 / Power Loss / No SuperBlock

[Mike Dresser]

On Sun, 2 Feb 2003, Adam J Morand wrote:

> right now it is all gibbled, I do not have a copy of the proc when it was
> working, but says this
>
> cat /proc/mdstat
> Personalities : [raid0] [raid1]
> read_ahead 1024 sectors
> md0 : active raid0 hda3[1] hdb3[0]
>       26619520 blocks 64k chunks
>
> md2 : active raid1 hdb1[0]
>       5116544 blocks [2/1] [_U]
>
> md1 : active raid1 hda2[1]
>       20482752 blocks [2/1] [U_]
>
> unused devices: <none>

Just printed out the two files for me to look at side by side.


You've got md0 set in /etc/raidtab, to use hdd3, and hdb3.

It's actually using hda3 and hdb3.

You've got md1 set in /etc/raidtab, to use hdd2 and hdb2

It's actually using hda2 and nothing.

you've got md2 set in /etc/raidtab, to use hdd1 and hdb1

It's actually using hdb1 and nothing.



Top of my head guess, is that your /dev/hdd has become /dev/hda.

Now, how that's possible, I'm really not sure because that implies a
cable change to move from the second controller to the first.  It looks
like your md0 found the new drive location just fine, but the md1 and md2
weren't able to?

Check your cabling.

Mike

Re: Promise sx6000

[Linux Lists]

Hi :

I have followed your advises and finally , it seem to be ok with my 
promise sx6000 card.
I have installed Red Hat 8 with 2.4.18-14 ,i2o support as module, but i 
can not find my card anywhere.

Here  i am sending you my dmesg and my modules.conf .
Notes I have a  120GB in hda where i have installed red hat , and 5 
hardrives in the promise card .
.............
.........

VP_IDE: IDE controller on PCI bus 00 dev 21
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
PDC20276: IDE controller on PCI bus 02 dev 00
PDC20276: chipset revision 1
ide: Found promise 20265 in RAID mode.
PDC20276: not 100% native mode: will probe irqs later
PDC20276: simplex device:  DMA disabled
ide2: PDC20276 Bus-Master DMA disabled (BIOS)
PDC20276: simplex device:  DMA disabled
ide3: PDC20276 Bus-Master DMA disabled (BIOS)
PDC20276: IDE controller on PCI bus 02 dev 08
PDC20276: chipset revision 1
ide: Found promise 20265 in RAID mode.
PDC20276: not 100% native mode: will probe irqs later
PDC20276: simplex device:  DMA disabled
ide4: PDC20276 Bus-Master DMA disabled (BIOS)
PDC20276: simplex device:  DMA disabled
ide5: PDC20276 Bus-Master DMA disabled (BIOS)
PDC20276: IDE controller on PCI bus 02 dev 10
PDC20276: chipset revision 1
ide: Found promise 20265 in RAID mode.
PDC20276: not 100% native mode: will probe irqs later
PDC20276: simplex device:  DMA disabled
ide6: PDC20276 Bus-Master DMA disabled (BIOS)
PDC20276: simplex device:  DMA disabled
ide7: PDC20276 Bus-Master DMA disabled (BIOS)
hda: WDC WD1200JB-75CRA0, ATA DISK drive
hdb: no response (status = 0xa1), resetting drive
hdb: no response (status = 0xa1)
hdc: AOPEN 16XDVD-ROM/AMH 20020328, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: setmax LBA 234441648, native  234375000
hda: 234375000 sectors (120000 MB) w/8192KiB Cache, CHS=14589/255/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
pci_hotplug: PCI Hot Plug PCI Core version: 0.4
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 220k freed
VFS: Mounted root (ext2 filesystem).
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
I2O Core - (C) Copyright 1999 Red Hat Software
I2O: Event thread created as pid 17
I2O Block Storage OSM v0.9
   (c) Copyright 1999-2001 Red Hat Software.
i2o_block: registered device at major 80
i2o_block: Checking for Boot device...
i2o_block: Checking for I2O Block devices...
Journalled Block Device driver loaded

Why is not my RAID under /dev/i2o/hda ?

David

Re: RAID 1 / Power Loss / No SuperBlock

[Norman Schmidt]

Hi Adam!

My guesses:

1. When the computer was switched off hard (i.e. without shutting 
down/disassemble the md devices first), they were not marked clean and 
stayed dirty. During the next boot, the kernel driver found out about 
this and only used the one of the two mirrors for each partition to work 
(thus the entry in /proc/mdstat). Your arrays work in degraded mode.

2. Somewhere you mounted one of the underlying devices of /dev/md2, 
namely /dev/hdd1, and did an fsck on it. That is a VERY bad idea. You 
should NEVER mount any of the underlying devices, unless you mark it as 
failed-disk and know exactly what you do.

To sort out your problem in the first place, it would be very helpful if 
you would provide the following outputs/files of the actual working 
configuration (the one you get when you boot your computer now):

/etc/lilo.conf
/etc/fstab
/etc/mtab

And give the version number of lilo!

And state again exactly what your problem is, i.e. what doesn´t work how 
it used to.

Another question: Why don´t you use mdadm instead of the raidtools? 
Mdadm really is the successor of the raidtools, has a 1.0 version 
number, and I LOVE mdadm (thanks Neil!).

Ah, yes: With the raidtools, some of the following should get you your 
second drive back in sync: raidhotadd /dev/md2 /dev/hdd1 and the same 
for the other disk:

Bye, Norman.

Adam J Morand schrieb:
> Mike,
> 
> errors included:
> cannot determine md version: No such file or directory
> and
> mount: wrong fs type, bad option, bad superblock on /dev/md2,
>        or too many mounted file systems
> 

> The error I get
> [aj@r2d2 aj]$ fsck /dev/hdd1
> Parallelizing fsck version 1.23 (15-Aug-2001)
> e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/hdd1
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
> 
> Exit 8
> 
> Is there RAID tools available for a situation like this that can recreate
> the superblocks?
> I have tried the backup blocks, I do not know how else or where to look for
> more information on reconstructed my dead RAID.
> 
> Thank you for any information or hints possible,

 > /etc/raidtab
 >
> raiddev             /dev/md2
> raid-level                  1
> nr-raid-disks               2
> chunk-size                  64k
> persistent-superblock       1
> nr-spare-disks              0
>     device          /dev/hdd1
>     raid-disk     0
>     device          /dev/hdb1
>     raid-disk     1
> raiddev             /dev/md1
> raid-level                  1
> nr-raid-disks               2
> chunk-size                  64k
> persistent-superblock       1
> nr-spare-disks              0
>     device          /dev/hdd2
>     raid-disk     0
>     device          /dev/hdb2
>     raid-disk     1

> cat /proc/mdstat
> Personalities : [raid0] [raid1]
> read_ahead 1024 sectors
> md0 : active raid0 hda3[1] hdb3[0]
>       26619520 blocks 64k chunks
> 
> md2 : active raid1 hdb1[0]
>       5116544 blocks [2/1] [_U]
> 
> md1 : active raid1 hda2[1]
>       20482752 blocks [2/1] [U_]



-- 

-- 
Norman Schmidt             Universitaet Erlangen-Nuernberg            _
cand.chem.                 Sysadmin Wohnheimnetzwerk RatNET        _ //
mailto:schmidt@naa.net                                             \X/

-
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

Re: RAID 1 / Power Loss / No SuperBlock

[Adam J Morand]

Hello again,

this is using mdadm, I now have 1 of the 3 RAIDs kind of working,
I am open to any suggestions at this point,

this is the error I get now
# mount /dev/md2 /mnt/raid/part2
mount: you must specify the filesystem type

# mount /dev/md3 /mnt/raid/part3
mount: you must specify the filesystem type

/dev/md1 works just fine
# mount /dev/md1 /mnt/raid/part1

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda3              36G   26G  8.3G  76% /
/dev/hda1              23M  2.7M   18M  13% /boot
none                  502M     0  502M   0% /dev/shm
/dev/md1               19G  8.8G  9.5G  48% /mnt/raid/part1



[root@r2d2 part1]# cat /proc/mdstat
Personalities : [raid0] [raid1]
read_ahead 1024 sectors
md1 : active raid1 hdb2[0]
      20482752 blocks [2/1] [U_]

md2 : active raid0 hdb3[0] hdd3[1]
      26619520 blocks 64k chunks

md3 : active raid1 hdd1[1]
      5116544 blocks [2/1] [_U]

unused devices: <none>
[root@r2d2 part1]# cat /etc/mdadm.conf
DEVICE          /dev/hdb1 /dev/hdb2 /dev/hdb3 /dev/hdd1 /dev/hdd2 /dev/hdd3
ARRAY           /dev/md3 devices=/dev/hdb1,/dev/hdd1
ARRAY           /dev/md1 devices=/dev/hdb2,/dev/hdd2
ARRAY           /dev/md2 devices=/dev/hdb3,/dev/hdd3

[root@r2d2 part1]#



fdisk -l

Disk /dev/hda: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1         3     24066   83  Linux
/dev/hda2             4       134   1052257+  82  Linux swap
/dev/hda3           135      4866  38009790   83  Linux

Disk /dev/hdb: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1   *         1       637   5116671   83  Linux
/dev/hdb2           638      3187  20482875   83  Linux
/dev/hdb3          3188      4844  13309852+  83  Linux
/dev/hdb4          4845      4866    176715    f  Win95 Ext'd (LBA)
/dev/hdb5          4845      4866    176683+  82  Linux swap

Disk /dev/hdd: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdd1   *         1       637   5116671   83  Linux
/dev/hdd2           638      3187  20482875   83  Linux
/dev/hdd3          3188      4844  13309852+  83  Linux
/dev/hdd4          4845      4866    176715    f  Win95 Ext'd (LBA)
/dev/hdd5          4845      4866    176683+  82  Linux swap








Adam J. Morand
Illuminated Technologies Inc.
Direct Line: 604.488.0226
Vancouver: 604.692.5716
Calgary: 403.802.8581
Edmonton: 780.401.5474
aj@illuminatedtechnologies.com
http://www.illuminatedtechnologies.com

"Illuminated Technologies - developing information and communication systems
for revenue stream solutions."


----- Original Message -----
From: "Norman Schmidt" <norman.schmidt@ratnet.stw.uni-erlangen.de>
To: <linux-raid@vger.kernel.org>
Cc: "Adam J Morand" <Adam.Morand@midnightmoon.ca>
Sent: Sunday, February 02, 2003 2:07 PM
Subject: Re: RAID 1 / Power Loss / No SuperBlock


Hi Adam!

My guesses:

1. When the computer was switched off hard (i.e. without shutting
down/disassemble the md devices first), they were not marked clean and
stayed dirty. During the next boot, the kernel driver found out about
this and only used the one of the two mirrors for each partition to work
(thus the entry in /proc/mdstat). Your arrays work in degraded mode.

2. Somewhere you mounted one of the underlying devices of /dev/md2,
namely /dev/hdd1, and did an fsck on it. That is a VERY bad idea. You
should NEVER mount any of the underlying devices, unless you mark it as
failed-disk and know exactly what you do.

To sort out your problem in the first place, it would be very helpful if
you would provide the following outputs/files of the actual working
configuration (the one you get when you boot your computer now):

/etc/lilo.conf
/etc/fstab
/etc/mtab

And give the version number of lilo!

And state again exactly what your problem is, i.e. what doesn´t work how
it used to.

Another question: Why don´t you use mdadm instead of the raidtools?
Mdadm really is the successor of the raidtools, has a 1.0 version
number, and I LOVE mdadm (thanks Neil!).

Ah, yes: With the raidtools, some of the following should get you your
second drive back in sync: raidhotadd /dev/md2 /dev/hdd1 and the same
for the other disk:

Bye, Norman.

Adam J Morand schrieb:
> Mike,
>
> errors included:
> cannot determine md version: No such file or directory
> and
> mount: wrong fs type, bad option, bad superblock on /dev/md2,
>        or too many mounted file systems
>

> The error I get
> [aj@r2d2 aj]$ fsck /dev/hdd1
> Parallelizing fsck version 1.23 (15-Aug-2001)
> e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/hdd1
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
>
> Exit 8
>
> Is there RAID tools available for a situation like this that can recreate
> the superblocks?
> I have tried the backup blocks, I do not know how else or where to look
for
> more information on reconstructed my dead RAID.
>
> Thank you for any information or hints possible,

 > /etc/raidtab
 >
> raiddev             /dev/md2
> raid-level                  1
> nr-raid-disks               2
> chunk-size                  64k
> persistent-superblock       1
> nr-spare-disks              0
>     device          /dev/hdd1
>     raid-disk     0
>     device          /dev/hdb1
>     raid-disk     1
> raiddev             /dev/md1
> raid-level                  1
> nr-raid-disks               2
> chunk-size                  64k
> persistent-superblock       1
> nr-spare-disks              0
>     device          /dev/hdd2
>     raid-disk     0
>     device          /dev/hdb2
>     raid-disk     1

> cat /proc/mdstat
> Personalities : [raid0] [raid1]
> read_ahead 1024 sectors
> md0 : active raid0 hda3[1] hdb3[0]
>       26619520 blocks 64k chunks
>
> md2 : active raid1 hdb1[0]
>       5116544 blocks [2/1] [_U]
>
> md1 : active raid1 hda2[1]
>       20482752 blocks [2/1] [U_]



--

--
Norman Schmidt             Universitaet Erlangen-Nuernberg            _
cand.chem.                 Sysadmin Wohnheimnetzwerk RatNET        _ //
mailto:schmidt@naa.net                                             \X/

-
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

Re: RAID 1 / Power Loss / No SuperBlock

[Adam J Morand]

Sorry,
to add to the previous message, when I specify the filesystem type I get:
[root@r2d2 part1]# mount -t ext3 /dev/md2 /mnt/raid/part2
mount: wrong fs type, bad option, bad superblock on /dev/md2,
       or too many mounted file systems
[root@r2d2 part1]#
[root@r2d2 part1]# mount -t ext2 /dev/md2 /mnt/raid/part2
mount: wrong fs type, bad option, bad superblock on /dev/md2,
       or too many mounted file systems





----- Original Message -----
From: "Adam J Morand" <Adam.Morand@illuminatedtechnologies.com>
To: <schmidt@naa.net>; <linux-raid@vger.kernel.org>
Sent: Sunday, February 02, 2003 7:36 PM
Subject: Re: RAID 1 / Power Loss / No SuperBlock


Hello again,

this is using mdadm, I now have 1 of the 3 RAIDs kind of working,
I am open to any suggestions at this point,

this is the error I get now
# mount /dev/md2 /mnt/raid/part2
mount: you must specify the filesystem type

# mount /dev/md3 /mnt/raid/part3
mount: you must specify the filesystem type

/dev/md1 works just fine
# mount /dev/md1 /mnt/raid/part1

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda3              36G   26G  8.3G  76% /
/dev/hda1              23M  2.7M   18M  13% /boot
none                  502M     0  502M   0% /dev/shm
/dev/md1               19G  8.8G  9.5G  48% /mnt/raid/part1



[root@r2d2 part1]# cat /proc/mdstat
Personalities : [raid0] [raid1]
read_ahead 1024 sectors
md1 : active raid1 hdb2[0]
      20482752 blocks [2/1] [U_]

md2 : active raid0 hdb3[0] hdd3[1]
      26619520 blocks 64k chunks

md3 : active raid1 hdd1[1]
      5116544 blocks [2/1] [_U]

unused devices: <none>
[root@r2d2 part1]# cat /etc/mdadm.conf
DEVICE          /dev/hdb1 /dev/hdb2 /dev/hdb3 /dev/hdd1 /dev/hdd2 /dev/hdd3
ARRAY           /dev/md3 devices=/dev/hdb1,/dev/hdd1
ARRAY           /dev/md1 devices=/dev/hdb2,/dev/hdd2
ARRAY           /dev/md2 devices=/dev/hdb3,/dev/hdd3

[root@r2d2 part1]#



fdisk -l

Disk /dev/hda: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1         3     24066   83  Linux
/dev/hda2             4       134   1052257+  82  Linux swap
/dev/hda3           135      4866  38009790   83  Linux

Disk /dev/hdb: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1   *         1       637   5116671   83  Linux
/dev/hdb2           638      3187  20482875   83  Linux
/dev/hdb3          3188      4844  13309852+  83  Linux
/dev/hdb4          4845      4866    176715    f  Win95 Ext'd (LBA)
/dev/hdb5          4845      4866    176683+  82  Linux swap

Disk /dev/hdd: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdd1   *         1       637   5116671   83  Linux
/dev/hdd2           638      3187  20482875   83  Linux
/dev/hdd3          3188      4844  13309852+  83  Linux
/dev/hdd4          4845      4866    176715    f  Win95 Ext'd (LBA)
/dev/hdd5          4845      4866    176683+  82  Linux swap





----- Original Message -----
From: "Norman Schmidt" <norman.schmidt@ratnet.stw.uni-erlangen.de>
To: <linux-raid@vger.kernel.org>
Cc: "Adam J Morand" <Adam.Morand@midnightmoon.ca>
Sent: Sunday, February 02, 2003 2:07 PM
Subject: Re: RAID 1 / Power Loss / No SuperBlock


Hi Adam!

My guesses:

1. When the computer was switched off hard (i.e. without shutting
down/disassemble the md devices first), they were not marked clean and
stayed dirty. During the next boot, the kernel driver found out about
this and only used the one of the two mirrors for each partition to work
(thus the entry in /proc/mdstat). Your arrays work in degraded mode.

2. Somewhere you mounted one of the underlying devices of /dev/md2,
namely /dev/hdd1, and did an fsck on it. That is a VERY bad idea. You
should NEVER mount any of the underlying devices, unless you mark it as
failed-disk and know exactly what you do.

To sort out your problem in the first place, it would be very helpful if
you would provide the following outputs/files of the actual working
configuration (the one you get when you boot your computer now):

/etc/lilo.conf
/etc/fstab
/etc/mtab

And give the version number of lilo!

And state again exactly what your problem is, i.e. what doesn´t work how
it used to.

Another question: Why don´t you use mdadm instead of the raidtools?
Mdadm really is the successor of the raidtools, has a 1.0 version
number, and I LOVE mdadm (thanks Neil!).

Ah, yes: With the raidtools, some of the following should get you your
second drive back in sync: raidhotadd /dev/md2 /dev/hdd1 and the same
for the other disk:

Bye, Norman.

Adam J Morand schrieb:
> Mike,
>
> errors included:
> cannot determine md version: No such file or directory
> and
> mount: wrong fs type, bad option, bad superblock on /dev/md2,
>        or too many mounted file systems
>

> The error I get
> [aj@r2d2 aj]$ fsck /dev/hdd1
> Parallelizing fsck version 1.23 (15-Aug-2001)
> e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/hdd1
>
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
>
> Exit 8
>
> Is there RAID tools available for a situation like this that can recreate
> the superblocks?
> I have tried the backup blocks, I do not know how else or where to look
for
> more information on reconstructed my dead RAID.
>
> Thank you for any information or hints possible,

 > /etc/raidtab
 >
> raiddev             /dev/md2
> raid-level                  1
> nr-raid-disks               2
> chunk-size                  64k
> persistent-superblock       1
> nr-spare-disks              0
>     device          /dev/hdd1
>     raid-disk     0
>     device          /dev/hdb1
>     raid-disk     1
> raiddev             /dev/md1
> raid-level                  1
> nr-raid-disks               2
> chunk-size                  64k
> persistent-superblock       1
> nr-spare-disks              0
>     device          /dev/hdd2
>     raid-disk     0
>     device          /dev/hdb2
>     raid-disk     1

> cat /proc/mdstat
> Personalities : [raid0] [raid1]
> read_ahead 1024 sectors
> md0 : active raid0 hda3[1] hdb3[0]
>       26619520 blocks 64k chunks
>
> md2 : active raid1 hdb1[0]
>       5116544 blocks [2/1] [_U]
>
> md1 : active raid1 hda2[1]
>       20482752 blocks [2/1] [U_]



--

--
Norman Schmidt             Universitaet Erlangen-Nuernberg            _
cand.chem.                 Sysadmin Wohnheimnetzwerk RatNET        _ //
mailto:schmidt@naa.net                                             \X/

-
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

-
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