Raid5 down after upgrade from 12.3 to 13.1 versions

English Install/Boot/Login
#1

I just upgraded my server to OpenSuSE 13.1 and now my RAID5 array is not working correctly. The Syba HW Raid5 card is working, the drives are present in the hardware info daemon, but not mounted as a file system that I can work with. I have attempted to gather information on the system with DMRAID and MDRAD and Expert Partitioner as shown below.dmraid -l output:

LINUXSERVER:/home/brad # dmraid -l
asr : Adaptec HostRAID ASR (0,1,10)
ddf1 : SNIA DDF1 (0,1,4,5,linear)
hpt37x : Highpoint HPT37X (S,0,1,10,01)
hpt45x : Highpoint HPT45X (S,0,1,10)
isw : Intel Software RAID (0,1,5,01)
jmicron : JMicron ATARAID (S,0,1)
lsi : LSI Logic MegaRAID (0,1,10)
nvidia : NVidia RAID (S,0,1,10,5)
pdc : Promise FastTrack (S,0,1,10)
sil : Silicon Image™ Medley™ (0,1,10)
via : VIA Software RAID (S,0,1,10)
dos : DOS partitions on SW RAIDs

dmraid -r
no raid disks

mdrad --detail /dev/sdb
mdadm: /dev/sdb does not appear to be an md device

My RAID partitions are highlighted in red - but they are not showing up in the system nor can I mount them in SAMBA. They also appear to have lost “label” information, should read “Media”, “Client” and “Backup”, it is unknown if the data contatined is also damaged.>:)

Device: (RAID Disk Array)

  • Device: /dev/sdb

  • Size: 5.46 TB

  • Device Path: pci-0000:01:00.0-scsi-0:0:0:0

  • Device ID 1: ata-JMicron_H_W_RAID5_C2KN2MMX8TUUN34PNT8H
    Device ID 2: scsi-141544120202020204a4d6963726f6e20482f57205241494435202020202020202020202020202020202020202020202043324b4e324d4d58385455554e3334504e543848
    Device ID 3: scsi-SATA_JMicron_H_W_RAIDC2KN2MMX8TUUN34PNT8H

Hard Disk:

  • Vendor: JMicron

  • Model: H/W RAID

  • Number of Cylinders: 729585

  • Cylinder Size: 7.84 MB

  • Bus: SATA

  • Sector Size: 512 B

  • Disk Label: GPT

Device:

  • Device: /dev/sdb1

  • Size: 2.00 TB

  • Encrypted: No

  • Device Path: pci-0000:01:00.0-scsi-0:0:0:0-part1

  • Device ID 1: ata-JMicron_H_W_RAID5_C2KN2MMX8TUUN34PNT8H-part1
    Device ID 2: scsi-141544120202020204a4d6963726f6e20482f57205241494435202020202020202020202020202020202020202020202043324b4e324d4d58385455554e3334504e543848-part1
    Device ID 3: scsi-SATA_JMicron_H_W_RAIDC2KN2MMX8TUUN34PNT8H-part1

  • FS ID: 0x83 Linux native

File System:

  • File System: Ext4

  • Mount Point:

  • Label:

Device:

  • Device: /dev/sdb2

  • Size: 2.00 TB

  • Encrypted: No

  • Device Path: pci-0000:01:00.0-scsi-0:0:0:0-part2

  • Device ID 1: ata-JMicron_H_W_RAID5_C2KN2MMX8TUUN34PNT8H-part2
    Device ID 2: scsi-141544120202020204a4d6963726f6e20482f57205241494435202020202020202020202020202020202020202020202043324b4e324d4d58385455554e3334504e543848-part2
    Device ID 3: scsi-SATA_JMicron_H_W_RAIDC2KN2MMX8TUUN34PNT8H-part2

  • FS ID: 0x83 Linux native

File System:

  • File System: Ext4

  • Mount Point:

  • Label:

Device:

  • Device: /dev/sdb3

  • Size: 1.46 TB

  • Encrypted: No

  • Device Path: pci-0000:01:00.0-scsi-0:0:0:0-part3

  • Device ID 1: ata-JMicron_H_W_RAID5_C2KN2MMX8TUUN34PNT8H-part3
    Device ID 2: scsi-141544120202020204a4d6963726f6e20482f57205241494435202020202020202020202020202020202020202020202043324b4e324d4d58385455554e3334504e543848-part3
    Device ID 3: scsi-SATA_JMicron_H_W_RAIDC2KN2MMX8TUUN34PNT8H-part3

  • FS ID: 0x83 Linux native

File System:

  • File System: Ext4

  • Mount Point:

  • Label:

#2

What exactly did you do?
Did you use zypper?
As far as I can see, you don’t say that.

That may as well depend on what you exactly did.

Good luck!
Mike

#3

Upgrade was completed by downloading the full ISO installer package and running it as new, telling it to upgrade the 12.3 version.

That may as well depend on what you exactly did.

Good luck!
Mike

I was running OpenSuSE 12.3 as a media / file server using a group of 4 2tb disks in RAID5 to host the shares in SAMBA. I had someone tell me that 13.1 carried some significant improvements that would be worth upgrading the server. I checked on the hardware requirements and found all to be good and proceeded with the upgrade process. Once the upgrade finished I could not find the RAID volume nor get our SAMBA shares to work correctly.

As I have shown above, the RAID is present and appears to be intact, but is not showing up on the list of mount points for SAMBA nor can the different programs / apps manipulate it as I had been previously able to do in the 12.3 release.

I am not really wanting to destroy and rebuild the drive array, would rather get it to work if possible.

#4

On 2014-05-09 03:56, CBHedricks wrote:
>
> ratzi;2642000 Wrote:
>> What exactly did you do?
>> Did you use zypper?
>> As far as I can see, you don’t say that.
>>
> Upgrade was completed by downloading the full ISO installer package and
> running it as new, telling it to upgrade the 12.3 version.

So, you did an offline system upgrade.

Offline upgrade
method

As the DVD does not contain all the packages, you have to upgrade the
rest online. You should probably do:


zypper patch
zypper up
zypper dup

With only the four official repos enabled. You can detect which packages
are from the wrong version by running this query:


rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist | less -S

or

rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist \
| egrep -v "openSUSE.13\.1" | less -S

(not containing 13.1)

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#5

I discovered during the upgrade option the installation process failed to recognize and bring in support for the RAID, and would not allow me to bring it on line after the fact. Based on input / assistance from a local LUG I re-installed from scratch, it found the RAID and installed everything needed to support it. Now I am working with SAMBA and user accounts to get it back on my network. Seems that upgrading from 12.3 to 13.1 presented some unique and interesting side issues with SAMBA also - now I am finding out that my original configuration file is not working with 4.1.0 “out of the box” and I am having to rebuild.

With this upgrade issue I am glad it was not a mission critical server. :wink:

Some info on the SAMBA site seems to indicate that some of the SAMBA III settings are no longer needed / supported. Took me a bit to get this into my head, was tunneled into a potential hardware issue, rather than a “services” issue. Now I am looking at what I need to make the share’s available to my Windows 7 machines, and one lone Windows 8 notebook that are on my home network setup.