Sil3114 SATA card


batfink

Recommended Posts

Is anyone using this SATA PCI card successfully? It's a cheap, generic PCI SATA card based on a Silicon Image chip (Sil3114CTU). My UnRAID doesn't seem to like it. I've tried to find documentation (user manual) on it but no luck. There is a "JP4" jumper on the top left - anyone know what it's for (eg, disable onboard RAID?)?

Thanks

Link to comment

I have exactly the same card, and am trying to find the latest "non-raid" bios.  On SiL's website, they have what they call SATARAID5 bios, and SATARAID bios.  The all seem to have raid functionality built in...???  In fact, I have just flash both versions of the bios and I can't see any difference!

 

 

 

 

Link to comment

On the Silicon Image, 3114 BIOS page, I believe you want to download the third item (SiI3114 IDE, SATARAID5 and system BIOS, v5.4.0.3), which is BIO-003114-x10_5403.zip.  Extract from that zip the file b5403.bin, which is the *base* BIOS (the non-RAID BIOS).  Copy it wherever you need to, to flash the card.

 

There's also a *Legacy* version below it, but someone else will have to advise whether you need that instead.

Link to comment

Finally got round to flashing the bios. Disc is currently "clearing" so all seems fine.

 

For reference and in case it helps someone else, the following worked for me (proceed at your own risk!):

 

Assumning you are flashing from DOS, dowload

"BIOS Update Utility for DOS" and

"SiI3114 IDE, SATARAID5 and system BIOS"

from

http://www.siliconimage.com/support/searchresults.aspx?pid=28&cat=15

Extract the "UPDFLASH.EXE" and the "b5403.bin" files to your boot media (I used a bootable USB)

At the dos prompt type "updflash b5403.bin -a" and wait for the update to complete.

That's it!

Link to comment

OK, maybe not!

At some stage I guess the "clearing" is falling over. Twice now the server seems to simply stop responding (cannot access remotely not directly).

Have swapped the disk for another just in case (although both actually came of of the Unraid box when I added two new 1TB drives), swapped power and SATA cables and have started it again. Will report back on what happens.

Presuably I can access a log of activity? Do I have to initiate the log or will it be on the USB key by default.

Sorry for all the questions - haven't messed about with the box since I first built ita year or so ago and have forgotten most of what I knew when I built it!

Thanks

 

Link to comment

I've seen this issue a number of times with my promise PCI TX4 controller on MSI motherboards.

It usually has something to do with IRQ's, sharing or APCI.

 

Check your IRQ sharing.

You may have to turn off ACPI or APIC in tbe bios and/or use boot parameters

Try adding each of these to the following command line in syslinux.cfg to see if it helps.

 

When using PCI controllers, I've found I had to use "some" of the options in order to avoid lockups.

 

pci=noacpi noapic nolapic

 

append initrd=bzrootd rootdelay=10 (add parameters here)

 

 

Post your syslog. It's not on the usb key by default.

http://lime-technology.com/wiki/index.php?title=Troubleshooting#Capturing_your_syslog

 

Link to comment

Thanks very much for your reply.

 

Right..... I turned off ACPI/APIC in the bios and restarted the server to start the clearing process. Same result (eventually locked up)

So, i added the paramaters you show above so the syslinux.cfg had the line:

 

append initrd=bzrootd rootdelay=10 pci=noacpi noapic nolapic    (is this right?)

 

restarted and let the clear start. Kept an eye on the refresh and it went all of the way to 99% before it locked up again. Tried to capture the log as it roled from 98 to 99% but didn't catch it in time. The attached is the latest log I managed to capture. Does it help at all (no idea what I'm looking for!). [HAVING TROUBLE ATTACHING, WILL TRY IN ANOTHER POST BELOW]

 

Is it worth turning ACPI/APIC back on and restarting?

 

Thanks for your help!

Link to comment

Can't add an attachement for some reason.  ???

This is the last part.

 

Jan 30 21:11:24 Tower emhttp: ... clearing 77% complete

Jan 30 21:12:55 Tower emhttp: ... clearing 78% complete

Jan 30 21:14:26 Tower emhttp: ... clearing 79% complete

Jan 30 21:15:57 Tower emhttp: ... clearing 80% complete

Jan 30 21:17:28 Tower emhttp: ... clearing 81% complete

Jan 30 21:18:58 Tower emhttp: ... clearing 82% complete

Jan 30 21:20:30 Tower emhttp: ... clearing 83% complete

Jan 30 21:22:03 Tower emhttp: ... clearing 84% complete

Jan 30 21:23:35 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD103UJ                          S13PJ1MQ723596      offset: 63 size: 976762552

Jan 30 21:23:35 Tower kernel: md: import disk1: [8,16] (sdb) SAMSUNG HD501LJ                          S0MUJ1KPA48447      offset: 63 size: 488386552

Jan 30 21:23:35 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD501LJ                          S0MUJ1KPA48448      offset: 63 size: 488386552

Jan 30 21:23:35 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG HD103UJ                          S1PVJ1CQ708508      offset: 63 size: 976762552

Jan 30 21:23:35 Tower kernel: md: import disk4: [3,0] (hda) Maxtor 6L200P0 L40ATEJH offset: 63 size: 199148512

Jan 30 21:23:35 Tower kernel: md: import disk5: [3,64] (hdb) IC35L180AVV207-1 VNVF05G6G3M2YG offset: 63 size: 180941008

Jan 30 21:23:35 Tower kernel: md: import disk6: [8,80] (sdf) SAMSUNG HD501LJ                                S0ZFJ1NP600121 offset: 63 size: 488386552

Jan 30 21:23:35 Tower kernel: md: disk6 new disk

Jan 30 21:23:37 Tower emhttp: ... clearing 85% complete

Jan 30 21:25:10 Tower emhttp: ... clearing 86% complete

Jan 30 21:26:14 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD103UJ                          S13PJ1MQ723596      offset: 63 size: 976762552

Jan 30 21:26:14 Tower kernel: md: import disk1: [8,16] (sdb) SAMSUNG HD501LJ                          S0MUJ1KPA48447      offset: 63 size: 488386552

Jan 30 21:26:14 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD501LJ                          S0MUJ1KPA48448      offset: 63 size: 488386552

Jan 30 21:26:14 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG HD103UJ                          S1PVJ1CQ708508      offset: 63 size: 976762552

Jan 30 21:26:14 Tower kernel: md: import disk4: [3,0] (hda) Maxtor 6L200P0 L40ATEJH offset: 63 size: 199148512

Jan 30 21:26:14 Tower kernel: md: import disk5: [3,64] (hdb) IC35L180AVV207-1 VNVF05G6G3M2YG offset: 63 size: 180941008

Jan 30 21:26:14 Tower kernel: md: import disk6: [8,80] (sdf) SAMSUNG HD501LJ                                S0ZFJ1NP600121 offset: 63 size: 488386552

Jan 30 21:26:14 Tower kernel: md: disk6 new disk

Jan 30 21:26:46 Tower emhttp: ... clearing 87% complete

Jan 30 21:27:51 Tower in.telnetd[1437]: connect from 192.168.0.4 (192.168.0.4)

Jan 30 21:27:56 Tower login[1438]: ROOT LOGIN  on `pts/0' from `192.168.0.4'

Jan 30 21:28:23 Tower emhttp: ... clearing 88% complete

Jan 30 21:29:59 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD103UJ                          S13PJ1MQ723596      offset: 63 size: 976762552

Jan 30 21:29:59 Tower kernel: md: import disk1: [8,16] (sdb) SAMSUNG HD501LJ                          S0MUJ1KPA48447      offset: 63 size: 488386552

Jan 30 21:29:59 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD501LJ                          S0MUJ1KPA48448      offset: 63 size: 488386552

Jan 30 21:29:59 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG HD103UJ                          S1PVJ1CQ708508      offset: 63 size: 976762552

Jan 30 21:29:59 Tower kernel: md: import disk4: [3,0] (hda) Maxtor 6L200P0 L40ATEJH offset: 63 size: 199148512

Jan 30 21:29:59 Tower kernel: md: import disk5: [3,64] (hdb) IC35L180AVV207-1 VNVF05G6G3M2YG offset: 63 size: 180941008

Jan 30 21:29:59 Tower kernel: md: import disk6: [8,80] (sdf) SAMSUNG HD501LJ                                S0ZFJ1NP600121 offset: 63 size: 488386552

Jan 30 21:29:59 Tower kernel: md: disk6 new disk

Jan 30 21:30:00 Tower emhttp: ... clearing 89% complete

Jan 30 21:31:41 Tower emhttp: ... clearing 90% complete

Jan 30 21:33:23 Tower emhttp: ... clearing 91% complete

Jan 30 21:34:45 Tower kernel: md: import disk0: [8,0] (sda) SAMSUNG HD103UJ                          S13PJ1MQ723596      offset: 63 size: 976762552

Jan 30 21:34:45 Tower kernel: md: import disk1: [8,16] (sdb) SAMSUNG HD501LJ                          S0MUJ1KPA48447      offset: 63 size: 488386552

Jan 30 21:34:45 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD501LJ                          S0MUJ1KPA48448      offset: 63 size: 488386552

Jan 30 21:34:45 Tower kernel: md: import disk3: [8,48] (sdd) SAMSUNG HD103UJ                          S1PVJ1CQ708508      offset: 63 size: 976762552

Jan 30 21:34:45 Tower kernel: md: import disk4: [3,0] (hda) Maxtor 6L200P0 L40ATEJH offset: 63 size: 199148512

Jan 30 21:34:45 Tower kernel: md: import disk5: [3,64] (hdb) IC35L180AVV207-1 VNVF05G6G3M2YG offset: 63 size: 180941008

Jan 30 21:34:45 Tower kernel: md: import disk6: [8,80] (sdf) SAMSUNG HD501LJ                                S0ZFJ1NP600121 offset: 63 size: 488386552

Jan 30 21:34:45 Tower kernel: md: disk6 new disk

Jan 30 21:34:56 Tower in.telnetd[1457]: connect from 192.168.0.4 (192.168.0.4)

Jan 30 21:34:58 Tower login[1458]: ROOT LOGIN  on `pts/0' from `192.168.0.4'

Jan 30 21:35:05 Tower emhttp: ... clearing 92% complete

Link to comment

I suspect that Tom may have run out of his monthly allotment.  As you probably suspected, nothing wrong in that syslog scrap.

 

For completeness, you might run a SMART Long test on this drive, just to make sure there isn't a problem with it.  See the Troubleshooting page, Obtaining a SMART report section.

 

I have to admit being curious about what that 180GB drive is, /dev/hdb, with model name of IC35L180AVV207-1.

Link to comment

Thanks, I'll try the SMART test. Also looking at possibly doing the "clearing" on another box (I'm sure I saw a thread on this somewhere - looking now).

 

The 180GB drive is an old IDE drive I had lying around. Will 'replace' it with a larger SATA drive when (if) I can get the PCI card working as I don't have any more SATA ports on the board I'm using (I actualy have a spare PC with 4xSATA onboard plus 4 RAID SATA which I may experiment with if I ever have time...)

 

Have to say I don't feel confident in tinkering too much but am running out of space because I decided to rip my DVD library to unRaid so have to do something!

 

Cheers

Link to comment

Oh dear.....when trying to run the SMART test from Telnet i get:

 

smartctl: error while loading shared libraries: libstdc++so.6: cannot open shared object file: No such file or directory

 

Not having much luck am I....

You are missing the required C++ libs accidentally left out of the lastest versions of unRAID but required for SMART to work properly.

 

This post will explain how to install it manually:

http://lime-technology.com/forum/index.php?topic=2817.msg23548#msg23548

 

Cheers,

Matt

 

If you are not already using the unMENU interface, I would recommend you at least look into it, it helps make adding on packages much easier and straight-forward than via the command line.  The post about unMENU is here: http://lime-technology.com/forum/index.php?topic=2595.0

Link to comment

Thanks. Noticed I missed an ACPI option in the bios so am giving the restart another shot. Will add the C++ lib after if need be.

Looked at the unmenu option earlier today. Was going to give it a shot once I had this problem sorted..... not confident enough to tinker with two things at once!

Thanks

Link to comment

I added the c++ library and ran the SMART utility, results below. Unless I'm missing something it loks OK. I'm going to try the "pre-clear" option now as I guess that's the next step?

 

Thanks to all !!!

 

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

Home page is http://smartmontools.sourceforge.net/

 

=== START OF INFORMATION SECTION ===

Model Family:    SAMSUNG SpinPoint T166 series

Device Model:    SAMSUNG HD501LJ

Serial Number:    S0ZFJ1NP600121

Firmware Version: CR100-11

User Capacity:    500,107,862,016 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:  8

ATA Standard is:  ATA-8-ACS revision 3b

Local Time is:    Sat Jan 31 19:09:39 2009 GMT

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status:  (0x82) Offline data collection activity

was completed without error.

Auto Offline Data Collection: Enabled.

Self-test execution status:      (  0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: (8888) seconds.

Offline data collection

capabilities: (0x5b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities:            (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability:        (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: (  2) minutes.

Extended self-test routine

recommended polling time: ( 152) minutes.

SCT capabilities:       (0x003f) SCT Status supported.

SCT Feature Control supported.

SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x000f  253  100  051    Pre-fail  Always      -      0

  3 Spin_Up_Time            0x0007  100  100  015    Pre-fail  Always      -      7360

  4 Start_Stop_Count        0x0032  100  100  000    Old_age  Always      -      573

  5 Reallocated_Sector_Ct  0x0033  253  253  010    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000e  253  253  000    Old_age  Always      -      0

  8 Seek_Time_Performance  0x0024  253  253  000    Old_age  Offline      -      0

  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      752

10 Spin_Retry_Count        0x0032  253  253  000    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0012  253  253  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      223

13 Read_Soft_Error_Rate    0x000e  100  100  000    Old_age  Always      -      549

187 Reported_Uncorrect      0x0032  253  253  000    Old_age  Always      -      0

188 Unknown_Attribute      0x0032  100  100  000    Old_age  Always      -      1

190 Airflow_Temperature_Cel 0x0022  079  060  000    Old_age  Always      -      21

194 Temperature_Celsius    0x0022  175  118  000    Old_age  Always      -      21

195 Hardware_ECC_Recovered  0x001a  100  100  000    Old_age  Always      -      549

196 Reallocated_Event_Count 0x0032  253  253  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0012  253  253  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0030  253  253  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x000a  253  100  000    Old_age  Always      -      0

201 Soft_Read_Error_Rate    0x000a  253  100  000    Old_age  Always      -      0

202 TA_Increase_Count      0x0032  253  253  000    Old_age  Always      -      0

 

SMART Error Log Version: 1

No Errors Logged

 

SMART Self-test log structure revision number 1

No self-tests have been logged.  [To run self-tests, use: smartctl -t]

 

 

SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1

SMART Selective self-test log data structure revision number 0

Warning: ATA Specification requires selective self-test log data structure revision number = 1

SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

    1        0        0  Not_testing

    2        0        0  Not_testing

    3        0        0  Not_testing

    4        0        0  Not_testing

    5        0        0  Not_testing

Selective self-test flags (0x0):

  After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

 

 

Link to comment

God I must be thick or something.... nothing seems to work.

 

I'm guessing the message I'm getting isn't normal !?!?  Cannot seem to upload a screenshot for some reason, so have typed below (telnet also locked up so cannot copy/paste).

 

Thought I would try this pre-clear script to bypass the unRAID clearing but alas no such luck!

 

Means nothing to me so would be grateful for any help. Cheers.

 

Pre clear DONE

Step 1 of 10 DONE

blah blah blah.....

Step 2 of 10 - Copying zeros to remainder of disk to clear it

**** This will take a while... you can follow progress below:

 

 

Elapsed Time:  4:33:52

238432+0 records in

238432_0 records out

500028145664 bytes (500GB) copied, 8550.05 s, 58.5 MB/s

dd: writing '/dev/sdf': No space left on device

 

I have also made this post in the actual pre-clear thread as not sure whether I should post here or there (so apologies for effectively double posting).

Thanks!

Link to comment

I'd like to help, but some times it takes the right person, and some times more information is needed.  For the pre_clear issue, you will probably need Joe to help, since he wrote it, and I'm sure he probably will, when he has time.  Unlike some of us, he actually has a LIFE!  All I can say is the messages you typed look pretty normal, until something reported out of space on sdf, nothing to over-react about.  It would help if you could detail what was next on the screen, what else pre_clear reported.

 

For your screen pic, we need more info, more explanation of it, what was happening when this occurred.  It does not look at all related to the pre_clear script.  And from what I can see, it is the bottom of a kernel panic, with an execution trace showing, something to do with disk I/O, but nothing very specific.  It could be useful to relate what is at the top of this trace, and what were the last regular messages before this trace and the kernel panic messages.

 

These are new technologies, new equipment, new drivers and software, and things are constantly going wrong, until most of the bugs are eliminated, with new releases, new firmware, etc.  It does require a more adventurous personality, so stay mellow and objective, expecting challenges, ready for the next thing to go wrong, ready and prepared to work it out.

Link to comment

Thanks RobJ.

 

My problem is that the box seems to lock up when trying the unraid clear and also the pre-clear script so what you see is all I can get (at least with my knowledge). It's difficult to know what you guys need in terms of 'evidence' to trace the problem but I really appreciate everyone's help up to now.

 

Maybe I'll give up for now (I still have about 500Gb free at the mo and don't HAVE to rip all my DVD's quite yet). I'm (hopefully) going to move home in a few weeks so maybe I'll come back to it in a couple of months. For now I'll just lurk around here, read up as and when I can, and come back to it when I have a little more knowledge.

 

Thanks again.

 

Link to comment
  • 2 weeks later...

Thanks RobJ.

 

My problem is that the box seems to lock up when trying the unraid clear and also the pre-clear script so what you see is all I can get (at least with my knowledge). It's difficult to know what you guys need in terms of 'evidence' to trace the problem but I really appreciate everyone's help up to now.

 

Maybe I'll give up for now (I still have about 500Gb free at the mo and don't HAVE to rip all my DVD's quite yet). I'm (hopefully) going to move home in a few weeks so maybe I'll come back to it in a couple of months. For now I'll just lurk around here, read up as and when I can, and come back to it when I have a little more knowledge.

 

Thanks again.

 

Kernel panics are almost always related to memory issues.  The very first thing I would do is verify the BIOS settings for both memory timing and memory voltage.  If you have more than one memory stick, swap them in the sockets.  Or try with only one installed, then the other.

 

If the memory voltage and timing settings are correct FOR YOUR SPECIFIC MEMORY CHIPS, then you might want to run a memory test overnight. (It is on the initial unRAID boot menu)    If you have not already verified, make sure the voltage and timing is set correctly for your CPU too. 

 

The preclear_disk script simply does a lot of IO and will use a lot of the memory as it reads and writes to the disk.  (The disk reads and writes are buffered by the operating system, and it only re-uses the buffer memory when it is unable to buffer more.  That does not take long if you have only a few Gig of memory and 1000 Gig drives)

 

Your box will have probably similar issues when doing a parity check.  It too uses a lot of buffer memory as it reads the disks.

 

Memory is inexpensive enough to replace.  Don't install premium memory without also adjusting the memory voltage and timings.  Typically, they will need increased voltage to work properly.  Inexpensive "Value" memory is a better match for most motherboards, and can easily handle the speeds needed for the unRAID server.

 

I understand the frustration with the lock-ups, but they almost always point to hardware, and it is great you were able to supply a screen image.  It really helps to see what you are seeing.

 

Joe L.

Link to comment
  • 5 months later...

I just got a Sil3114 SATA card.  Isn't it likely that it would have the most current BIOS (5.4.0.3) out of the box and not need updating?  If it needs updating is it best to do it in a PC or can it easily be done in the unRAID?

 

My experience is  (own two silicon Image SATA cards), it is very unlikely you will get one with latest BIOS and it is better to do the BIOS re-flash in Windows environment then move to unRaid box and browse through syslog to make sure card is detected and driver is loaded.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.