Update OpenSuSE 10.3 to 11.1, problem with hardware RAID

English Install/Boot/Login
1

Hello.

I have some trouble after updating my system from OpenSuSE 10.3 to 11.1.
It would be great, if somebody could help me.

Problem description
After updating my system from 10.3 to 11.1 without errors, I get into trouble
after rebooting.
I need the data which is stored on a hardware RAID array (Areca 1220).

Before I update the system I could mount the RAID-System with


sudo -s
mount /dev/sdb1 /media/RAID_ICE

After updating to 11.1 …problems…

System
Hardware RAID Array with one partition, ext3.
Separate harddisk with operating systems.


parted -l
Modell: Areca VOLUME_SET_ICE01 (scsi)
Festplatte  /dev/sda:  6000GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt

Nummer  Anfang  Ende    Größe   Dateisystem  Name  Flags
 1      17,4kB  6000GB  6000GB                     , , , , , , , , , , ,


Modell: ATA ST3500320AS (scsi)
Festplatte  /dev/sdb:  500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos

Nummer  Anfang  Ende   Größe   Typ       Dateisystem  Flags
 1      32,3kB  168GB  168GB   primary   ntfs         , , , , , , , , , type=07, ,
 2      168GB   172GB  3997MB  primary   linux-swap   , , , , , , , , , type=82, ,
 3      172GB   332GB  160GB   primary   ext3         boot, , , , , , , , , type=83, ,
 4      332GB   500GB  168GB   extended               , , , , , , lba, , , type=0f, ,
 5      332GB   500GB  168GB   logical   ntfs         , , , , , , , , , type=07, ,

Notice

  • Before update: Hardware RAID array on /dev/sdb

  • After update: Hardware RAID array on /dev/sda

  • starting rescue-modus from dvd 11.1 the hardware RAID array is on /dev/sdb

  • After update: all entries in Grub doesn’t work
    OpenSuSE 11.1
    Failsafe - - OpenSuSE 11.1
    OpenSuSE 11.1
    Failsafe - - OpenSuSE 11.1
    Windows

    This is not important to me, I need the data from the raid array
    After changing manualy from hdd(1,2) to hdd(0,2) OpenSuSE starts.

What I tried

OpenSuSE 11.1


sudo -s
mount /dev/sda1 /media/RAID_ICE
>mount: specify file system type (Dateisystemtyp)



mount -t ext3 /dev/sda1 /media/RAID_ICE
>mount: wrong fs type, bad option, bad superblock on /dev/sda1,
>missing codepage or helper program, or other error
>Try dmesg | tail



dmesg | tail
>VFS: Can't find ext3 filesystem on dev sda1.

Rescue-System startet from DVD OpenSuSE 11.1


dumpe2fs /dev/sdb1 | grep -i "block size"

>dumpe2fs 1.41.1 (01-Sep-2008)
>dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1



dumpe2fs /dev/sdb1 | grep -i superblock

>dumpe2fs 1.41.1 (01-Sep-2008)
>dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1



e2fsck /dev/sdb1
>dumpe2fs 1.41.1 (01-Sep-2008)
>dumpe2fs: Superblock invalid, trying backup blocks
>dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1
>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>



e2fsck -b 32768 /dev/sdb1
>dumpe2fs 1.41.1 (01-Sep-2008)
>dumpe2fs: Superblock invalid, trying backup blocks
>dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1
>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>



e2fsck -b 8193 /dev/sdb1
>dumpe2fs 1.41.1 (01-Sep-2008)
>dumpe2fs: Superblock invalid, trying backup blocks
>dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1
>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>

OpenSuSE 11.1 YAST2

YAST2/partition

assign mountpoint ends with error:
Device without known file system type can’t assign to mountpoint.

Some informations


parted -l
Modell: Areca VOLUME_SET_ICE01 (scsi)
Festplatte  /dev/sda:  6000GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt

Nummer  Anfang  Ende    Größe   Dateisystem  Name  Flags
 1      17,4kB  6000GB  6000GB                     , , , , , , , , , , ,


Modell: ATA ST3500320AS (scsi)
Festplatte  /dev/sdb:  500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos

Nummer  Anfang  Ende   Größe   Typ       Dateisystem  Flags
 1      32,3kB  168GB  168GB   primary   ntfs         , , , , , , , , , type=07, ,
 2      168GB   172GB  3997MB  primary   linux-swap   , , , , , , , , , type=82, ,
 3      172GB   332GB  160GB   primary   ext3         boot, , , , , , , , , type=83, ,
 4      332GB   500GB  168GB   extended               , , , , , , lba, , , type=0f, ,
 5      332GB   500GB  168GB   logical   ntfs         , , , , , , , , , type=07, ,

############################################

…

############################################

There’s not enough space on my system to make a backup with dd,
so I don’t have many chances to repair the system.

It would be great, if somebody could help me.