Jump to content

Sil3124 Raid 0 Controller Issues...


waterlou

Recommended Posts

Hey Guys -

 

I've been running a 4 drive raid cabinet for 2 years with little to no issue. 2 Raid-0 arrays were configured and are connected via eSata to a card in my file server.

 

So the psu on my Raid cabinet started to fail and the disks would power suddenly down. So, I conveniently replaced it with a new one (350W).

Everything is fine on boot, the Raid conroller BIOS sees all 4 drives (WD 250 x2, WD 320 x2)

 

Then things get hoaky in windows. First, windows takes forever mins to boot up... I think due to the following log file detail.

 

I decided to unplug two drives (WD320) to try and get one raid array up and running. When I go to the Sil Sata Raid manager, and attempt to recreate the raid group from drives that ALREADY were in a group (but no longer identified). Here is the log file from the raid manager software.

 

01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Controller	Informational	Begin group discovery
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:24.31 PM	Controller 0 - Sil3124r5	Controller	Informational	Initialization Complete
01/10/08	02:31.07 PM	Controller 0 - Sil3124r5	Application	Informational	Database initialized..
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	Device	Informational	Segment created, PathId 2, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 1
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	Device	Informational	Segment created, PathId 3, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 1
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	RAID	Informational	Start Create, Group 0
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	RAID	Informational	Configure RAID Group task
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	Device	Error	SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	RAID	Error	Create aborted, Group 0
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	RAID	Warning	Member 0 (Path ID = 2, Target ID = 0 dropped from group 0 "Volume A"
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	Device	Informational	Segment deleted, PathId 2, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 0
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	RAID	Warning	Group 0 "Volume A" is OFFLINE
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	RAID	Warning	Member 1 (Path ID = 3, Target ID = 0 dropped from group 0 "Volume A"
01/10/08	02:31.51 PM	Controller 0 - Sil3124r5	Device	Informational	Segment deleted, PathId 3, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 0

 

I've been running raid for years. And this one is baffling me. Looks like it's finding some sort of corrupted metadata and refuses to over-ride it. So I can't recreate the group, and thus can't create a new drive in windows.

 

When all 4 drives are connected, and I go into the RAID BIOS on bootup, one of the new WD320 shows as a "logical" drive and all the others as "reserved".

 

Any advice would be welcome!

Share this post


Link to post
Share on other sites

you may have to just to do a clean install, by how you explain it, the first raid is recreating the second raid? therfore somethings is corrupt preventing it. i know you said that but it makes sense. try an disc image program and see if you can get your files back that way.

 

"

01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Informational Start Create, Group 0

01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Informational Configure RAID Group task

01/10/08 02:31.51 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried)

01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Error Create aborted, Group 0

01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Warning Member 0 (Path ID = 2, Target ID = 0 dropped from group 0 "Volume A"""

"

Share this post


Link to post
Share on other sites

you may have to just to do a clean install, by how you explain it, the first raid is recreating the second raid? therfore somethings is corrupt preventing it. i know you said that but it makes sense. try an disc image program and see if you can get your files back that way.

 

No, sorry. There are 4 disks. 2 sets of 2. Each group is configured as a Raid-0 array. I just succeeded in creating an array with the WD320s once I brought them on line. And I think I am close to getting the WD250s raid going. When I go into the Raid config manager it notifies me that all 4 of the drives are "reserved", which tells me they are "stamped" with something. I updated the Windows based Sil RaidSata5 utility and it shows a "blue" disk flagged as a "pass through". So I think the metadata that the disks are stamped with (ie: the Raid config data in the boot sector) is corrupted. And it's showing one of the disks as a pass-through (or JBOD) and hence an invalid raid array. Causing windows to take forever to boot up...

 

Any advice is appreciated on the subject!

 

Thanks!

 

ps: the good news is that all my "valuable" data (pics, movies, music, etc) is backed up on a USB drive on a weekly basis!

Share this post


Link to post
Share on other sites

well, since its not letting you raid it "the Raid config data in the boot sector) is corrupted" what about taking each drive by themselfs (non raid) into windows and reformat, leaving the drive blank of anything than you can try the raid once more. since you backed up your stuff its worth a try.

Share this post


Link to post
Share on other sites

I think I found out what the problem is. I re-flashed the BIOS on the card to non-raid so I could run some diagnostics on the drive. And it looks like the PSU fried the drive because none of the diagnostic tests can run. ARGH!

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...