isw device for volume broken after opensuse livecd boot

Tiago Freitas tiago.frt at
Thu Sep 27 22:57:11 UTC 2007

Ok I will try to rebuild, the problem I see is that OROM reports two
RAID0 and two RAID1 volumes with the same size, but there is only one
of each. That's the biggest problem with the metadata now.
As I said:
> >0  RAID0:1   80Gb       Failed
> >1  RAID1:1  109.0Gb   Degraded
> >2  RAID0     80Gb        Failed
> >3  RAID1     109.0Gb   Degraded
> >
> >Port
> >0     Hitachi        149.1GB     Member Disk(0,1)
> >1     Hitachi        149.1GB     Member Disk(2,3)

Also, I did not move the pc when I rebooted, so I don't think it was
the cables, maybe a power issue? I have a good 550W I need a

Anyway when one drive is not detected by OROM, maybe it should ask the
user to reconnect the drive or change sata ports before marking the
volume as Failed?

On 9/27/07, Fang, Ying <ying.fang at> wrote:
> Thanks, Tiago,
> If you have backed up data, you can go ahead to rebuild your disks.
> Since the rebuilding in iMSM only recovers data in RAID1, you will lose
> all data in RAID0. It's not worth to do it.
> Regarding OROM, I don't suggest to choose the rebuild option until
> you're sure that one disk is broken. In your case, one of your raid
> disks wasn't detected during a reboot and OROM told you that RAID0
> failed and RAID1 degraded. OROM can fix it if your missing disk
> reconnected after another reboot. But if you choose a spare disk for
> rebuilding, it's hard for a program to determine which disk's data are
> valid. Anyway, I have forwarded your metadata to the OROM team and the
> iMSM team. If they come up with some tips, I'll let you know.
> I appreciate your help.
> Ying
> >-----Original Message-----
> >From: coolkcah at [mailto:coolkcah at] On Behalf Of Tiago
> >Freitas
> >Sent: Thursday, September 27, 2007 2:59 PM
> >To: Fang, Ying
> >Cc: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions
> >Subject: Re: isw device for volume broken after opensuse livecd boot
> >
> >The third disk was already in but not part of the array, and I chose
> >it to rebuild in OROM bios. As I never did a rebuild before (the pc is
> >two weeks old and this is my first raid) I don't know how the process
> >is done.
> >Should I have chosen one of the array members to rebuild?
> >
> >I have all the data backed up in an external disk, I just wanted to
> >help fix the bug in OROM because it's weird and may happen again. But
> >I can't wait too much time because I will need the pc up and running
> >soon.
> >
> >The size difference is really weird too because both disks were
> >manufactured in Jully 2007 and have the exact same model...maybe
> >that's what triggered the failure?
> >I'm gonna test the disks in Hitachi Fitness tool to be sure they are
> good.
> >
> >On 9/27/07, Fang, Ying <ying.fang at> wrote:
> >> Tiago,
> >>
> >> Eric Hall and I try to reproduce your issue and if we succeed, will
> test
> >> a rescue procedure.
> >>
> >> I'd like to confirm if you put the third disk in and chose to the
> >> rebuild option in OROM.
> >>
> >> I don't know why one disk is smaller than the other. The total sector
> >> number is reported to DMRAID by the SCSI device driver. Both DMRAID
> and
> >> iMSM take the smallest size for a RAID array if the sizes of an array
> >> are different.
> >>
> >> Thanks,
> >> Ying
> >>

More information about the Ataraid-list mailing list