Problem with the Sil3112 on ASUS A7N8X-Deluxe - sataraidevents.log (0/1)

[Andreas Westendoerpf]

Hello!

I have a problem with the Sil3112 SATA-RAID controller on my ASUS
A7N8X-Deluxe motherboard.

I tried to rebuild my RAID set (2 SEAGATE ST380023AS drives) in the
RAID BIOS as well as with the JavaSATARAID tool unter WinXP but it
doesn't work out.

Just when it's about 54% it stops without an errormessage. When I
reboot, one drive is missing in the RAIDBIOS.
After a poweroff it's there again but needs to be
rebuilt (same problem).

With the JavaSATARAID tool I get the following errorlog:
---------------------------------------------------

Time: 2004.09.28 at 11:03:43 Controller ID: 0 SeqNumber: 0
Severity: 1 Description: SATARaid Configuration tool started.
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 1
Severity: 3 Description: SCSI Error-Medium Error. Error occured on
Channel 1 device on adapter 1. Channel 1 - Key 03 - ASC 00, ASCQ 00 -
CDB 0x28 0x00 0x05 0x0a 0x68 0x00 0x00 0x00 0x80 0x00 0x00 0x00 - INFO
05 0a 68 60
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 2
Severity: 3 Description: SCSI Error-Medium Error. Error occured on
Channel 1 device on adapter 1. Channel 1 - Key 03 - ASC 00, ASCQ 00 -
CDB 0x28 0x00 0x05 0x0a 0x68 0x60 0x00 0x00 0x01 0x00 0x00 0x00 - INFO
05 0a 68 60
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 3
Severity: 3 Description: Device remove. The Channel 0 device on
adapter 1, ST380023AS, was removed.
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 4
Severity: 3 Description: Member dropped. Set 0 dropped Channel 0
device on adapter 1 due to a port error. SRB status was Device
Selection Timed Out.
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 5
Severity: 3 Description: BBR Error - Flag Failed. An error ocurred on
Channel 0 device of adapter 1 while flagging block 0x50a6860.
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 6
Severity: 1 Description: New device. The Channel 0 device on adapter
1, ST380023AS, is the new device.
Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 7
Severity: 1 Description: Rebuild started. Set 0 started a rebuild for
Channel 0 device on adapter 1.
Time: 2004.09.28 at 11:04:54 Controller ID: 0 SeqNumber: 0
Severity: 1 Description: SATARaid Configuration tool closed.
---------------------------------------------------
I'm running the latest motherboard BIOS from ASUS and Windows Drivers
(including the modWrite patch for older Seagate HDDs).

Does one of my HDDs has a problem or is it the Sil3112? If it's one of
the HDDs, which one is it?

Is it the channel 0 device because of:

SCSI Error-Medium Error. Error occured on Channel 1 device on adapter
1. Channel 1 - Key 03 - ASC 00, ASCQ 00 - CDB 0x28 0x00 0x05 0x0a 0x68
0x60 0x00 0x00 0x01 0x00 0x00 0x00 - INFO 05 0a 68 60

or the channel 0 device because of:

An error ocurred on Channel 0 device of adapter 1 while flagging block
0x50a6860.

Please help me, I've spent some time here and am desperate for help

TIA!
Cheers, Andreas

 

[geno_cyber]

I have a RAID-0 setup on an ADAPTEC 1210SA controller with two 80GB SATA Seagate HDUs just like you,
ST380023AS.
They worked flawlessly for more than 1 year but 3 days ago the one on channel 0 started appearing as
MISSING.
I tried changing SATA and SATA Power Adapter cables with new ones. The problem is still there.
The drive on channel 0 doesn't seem to spin-up correctly anymore.
I have to power off and then power on the system 2-3 times on average before the drive finally
spins-up. But when it does spin-up the RAID-0 array is still there, perfectly working just like
nothing happened before. No data errors/corruption, no need to rebuild the array, all the data in
the 160GB combined RAID Array unit is still there.
My PSU it's an ANTEC TruePower 550Watt , btw.
If I'm not wrong the Adaptec 1210SA is based on either Sil3112 or 3114 but with Bios made by Adaptec
and Adaptec OEM PCI ID....
I doubt that's the controller failing or the PSU, at least because I don't have any data corruption
and everything is rock solid other than this failing Seagate HDU.

The worst thing is that the S.M.A.R.T. is reporting Healthy condition on both HDUs and the Array
condition reported as Optimal. Obviously this happens only when the HDU on channel 0 actually spins
up.

It seems that's an heat-related problem and so I suspect that's due to some ICs soldering being
defective on the HDU board... In fact the drive doesn't spin-up and appears missing when the system
has been turned off for a few hours and it's cold but if I turn it off after some hours and then try
to turn it on again the failing HDU keeps spinning up correctly.... which is weird , indeed.

I bet that is going to fail completely pretty soon anyway, so I backed up all my data to another PC
and I think I'm going to buy another HDU as a replacement for now.
I contacted Seagate tech support to ask them about warranty policies with such an issue and what I
should expect to replace it.
I surely can't use my PC with a failing unit like this anymore :-(

 

[geno_cyber]

I have a RAID-0 setup on an ADAPTEC 1210SA controller with two 80GB SATA Seagate HDUs just like you,
ST380023AS.
They worked flawlessly for more than 1 year but 3 days ago the one on channel 0 started appearing as
MISSING.
I tried changing SATA and SATA Power Adapter cables with new ones. The problem is still there.
The drive on channel 0 doesn't seem to spin-up correctly anymore.
I have to power off and then power on the system 2-3 times on average before the drive finally
spins-up. But when it does spin-up the RAID-0 array is still there, perfectly working just like
nothing happened before. No data errors/corruption, no need to rebuild the array, all the data in
the 160GB combined RAID Array unit is still there.
My PSU it's an ANTEC TruePower 550Watt , btw.
If I'm not wrong the Adaptec 1210SA is based on either Sil3112 or 3114 but with Bios made by Adaptec
and Adaptec OEM PCI ID....
I doubt that's the controller failing or the PSU, at least because I don't have any data corruption
and everything is rock solid other than this failing Seagate HDU.

The worst thing is that the S.M.A.R.T. is reporting Healthy condition on both HDUs and the Array
condition reported as Optimal. Obviously this happens only when the HDU on channel 0 actually spins
up.

It seems that's an heat-related problem and so I suspect that's due to some ICs soldering being
defective on the HDU board... In fact the drive doesn't spin-up and appears missing when the system
has been turned off for a few hours and it's cold but if I turn it off after some hours and then try
to turn it on again the failing HDU keeps spinning up correctly.... which is weird , indeed.

I bet that is going to fail completely pretty soon anyway, so I backed up all my data to another PC
and I think I'm going to buy another HDU as a replacement for now.
I contacted Seagate tech support to ask them about warranty policies with such an issue and what I
should expect to replace it.
I surely can't use my PC with a failing unit like this anymore :-(

 

[Folkert Rienstra]

Hello!

I have a problem with the Sil3112 SATA-RAID controller on my ASUS
A7N8X-Deluxe motherboard.

I tried to rebuild my RAID set (2 SEAGATE ST380023AS drives) in the
RAID BIOS as well as with the JavaSATARAID tool unter WinXP but it
doesn't work out.

Just when it's about 54% it stops without an errormessage.
When I reboot, one drive is missing in the RAIDBIOS.
After a poweroff it's there again but needs to be
rebuilt (same problem).

With the JavaSATARAID tool I get the following errorlog:

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 1
Severity: 3 Description: SCSI Error-Medium Error. Error occured on
Channel 1 device on adapter 1. Channel 1 - Key 03 - ASC 00, ASCQ 00 -

CDB 0x28 0x00 0x05 0x0a 0x68 0x00 0x00 0x00 0x80 0x00 0x00 0x00 - INFO 05 0a 68 60

CDB 0x28 Read (10) 12?
0x00 Lun +++
0x05 0x0A 0x68 0x00 LBA (sector number) 84568064
0x00
0x00 0x80 Transfer length: 128 sectors
0x00
0x00 0x00
- INFO 050A6860

Media error on a read. Presumably a bad block (see later) but the additional
error description actually is "NO ADDITIONAL SENSE INFORMATION".
"Info", apparently, is the blocknumber.

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 2
Severity: 3 Description: SCSI Error-Medium Error. Error occured on
Channel 1 device on adapter 1. Channel 1 - Key 03 - ASC 00, ASCQ 00 -

CDB 0x28 0x00 0x05 0x0a 0x68 0x60 0x00 0x00 0x01 0x00 0x00 0x00 - INFO 05 0a 68 60

CDB 0x28 Read (10)
0x00 Lun +++
0x05 0x0A 0x68 0x60 LBA 84568160
0x00
0x00 0x01 Transfer length: 1 sector
0x00
0x00 0x00
- INFO 050A6860

Apparently a retry, but now with a 1 sector length and 96 sectors into the previous read.

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 3 Severity: 3
Description: Device remove. The Channel 0 device on adapter 1, ST380023AS, was removed.

Self evident except for maybe the cause.

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 4 Severity: 3
Description: Member dropped.
Set 0 dropped Channel 0 device on adapter 1 due to a port error.
SRB status was Device Selection Timed Out.

Ditto. Sounds like a programming (design) error.

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 5
Severity: 3 Description: BBR Error - Flag Failed.
An error ocurred on Channel 0 device of adapter 1 while flagging block 0x50a6860.

Ditto as for the previous error:
First remove and drop it and then complain about it not being there anymore.

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 6
Severity: 1 Description: New device.
The Channel 0 device on adapter 1, ST380023AS, is the new device.

Self evident.

Time: 2004.09.28 at 11:03:48 Controller ID: 1 SeqNumber: 7
Severity: 1 Description: Rebuild started.
Set 0 started a rebuild for Channel 0 device on adapter 1.

Self evident.

Time: 2004.09.28 at 11:04:54 Controller ID: 0 SeqNumber: 0
Severity: 1 Description: SATARaid Configuration tool closed.

Apparently it repaired itself (or at least it thinks that it did),
making a lot of fuzz about it.

---------------------------------------------------
I'm running the latest motherboard BIOS from ASUS and Windows Drivers
(including the modWrite patch for older Seagate HDDs).

Does one of my HDDs has a problem or is it the Sil3112?

Probably it's software or driver.

If it's one of the HDDs, which one is it?

The channel 1 device.

Is it the channel 0 device because of:

SCSI Error-Medium Error. Error occured on Channel 1 device on adapter
1. Channel 1 - Key 03 - ASC 00, ASCQ 00 - CDB 0x28 0x00 0x05 0x0a 0x68
0x60 0x00 0x00 0x01 0x00 0x00 0x00 - INFO 05 0a 68 60

or the channel 0 device because of:

An error ocurred on Channel 0 device of adapter 1 while flagging block 0x50a6860.

Both: Cause and effect.
It finds a bad block and then tries to flag it as bad 'somewhere', the other drive.
But because it dropped the other drive, that 'somewhere' disappeared.
Why it tries to flag it on the 'other' drive is a mystery and probably why your
problem persists.

 

[Folkert Rienstra]

Anything else I can do for you or did you commit suicide?


[snip]