I recently had the experience of moving a pair of RAID1 storage disks from one server to another. It was not without difficulty.
Both server’s had the OS on a third non RAIDed drive, so i didn’t have to worry about being able to boot from them (thank god!)
The server they came from, an old MSI AMD motherboard had a Promise RAID controller built in. The Gigabyte board I was moving to did not, so I had to add an additional RAID controller on a PCI card.
The board chosen used a chipset from SilconImage – the Sil3114. This is an inexpensive card offering RAID0,1,5,10 & JBOD.
The card as delivered plugged into an empty PCI slot easy enough. However the motherboard recognised this only some of the time. (This was subsequently either resolved by a BIOS update to the card – more on this later – or pushing down hard on the card to ensure it was fully in – not sure which).
The Sil3114 card can be used in one of two configurations. As a RAID controller for up to 4 SATA drives. This requires a SATA RAID bios to be installed on the card (the default) and some SATARAID5 manager software to be installed in Windows.
OR – it can be used as a straight disk controller for up to 4 SATA drives (no RAID) – this is called “SATA Link” and requires SATA Link software in Windows. You can also install a SATA Link “base” BIOS to the card as well, instead of the RAID one, but since the SATARAID BIOS has a pass thru mode which allows the use of drives in a non RAID configuration, it makes you wonder why you’d bother.
Driver file size, bytes 3112 satalink image - storage - silicon image sii satalink controller, windows 7,windows 8,windows and later drivers, drivers other hardware, 7/23/. Silicon image sii 3132 satalink controller drivers were collected from official websites of. 32-bit SuSE Pro 9.3 BASE (non-raid) Driver for 32-bit AMD and 32-bit EMT64T This download includes driver support for SuSE Pro 9.3 linux distribution, kernel revision 2.6.11.4-20a on 32-bit AMD and 32-bit EMT64T platforms. Use this driver with the latest IDE BIOS to access non-RAID hard disk drives, CD-ROMs, CDRWs, DVD-ROMs, and DVD-RWs.
The job then was to plug the drives in, set them up as a RAID group without losing the data already on them and then get them visible and useable in Windows.
- SATALINK SIL3112ACT144 DRIVER (satalinksil3112act1445207.zip) Download Now SATALINK SIL3112ACT144 DRIVER. Manual 65 pages summary of this manual is working properly. Rp spray guns comply with the legislation of the eu voc directive. Visit our community and share your experiences and solutions with other sony customers. Silicon image sii 3512.
- Download Silicon Image SiI3112/Sil3512 RAID Driver 1.0.0.5 (Other Drivers & Tools).
- 「Silicon Image Serial-ATA RAID Drivers for K8N Diamond」v 1.1.0.1 – SiliconImageSil3132NV10.zip 「Silicon Image Serial-ATA RAID Drivers for K8N Neo4 Platinum」v 1.1.0.1 – Silicon. Silicon ImageのHP「」を見ても、一向にドライバが更新されない。.
After plugging the drives in, I went into the Silicon Image SATA RAID BIOS utility. Here I was able to create a RAID1 group containing the two drives. I allowed it to re-mirror the data from one drive to the other as part of this. The mirroring process took several hours for my Samsung Spinpoint 500GB drives.
After booting into Windows, Windows 7 automatically downloaded a bunch of driver software which it seemed to think would work. It also added an item to the Windows Control Panel called “Silicon Logic SATA RAID”. Despite clicking on this item many times – it never did anything.
In addition to this you need to install the SATARAID5 manager software which allows you to configure the disks in windows. This can be downloaded from the SiliconImage website here:
http://www.siliconimage.com/support/searchresults.aspx?pid=28&cat=3
Make sure you have at least version 1.5.20.3 of this.
These downloads inexplicably include an old copy of the Java virtual machine runtime environment. Ironically this doesn’t actually work with the SATARAID5 manager software it comes with. Genius! Although it will allow you to view the status of your disks – it won’t allow you to actually do anything with them, all the menu items just do nothing (I subsequently managed to run the manager in a console mode and found that all the menu items were throwing exceptions – ie: broken).
However if you install the latest version of the Java runtime from Sun (available here) – the manager software does work properly.
So now I was able to examine my disks using the SATARAID5 manager. They were marked as a Legacy RAID Group and painted red. In the Windows “Disk Management” window (right click on “Computer” in Windows Explorer, select “Manage” and then clicking “Disk Storage”) they were not visible at all.
So – problem! My disks are there, presumably with data and I can’t read them. And what the hell is a legacy RAID group?
After much reading of the siliconimage website, I downloaded updated versions of the Sil3114 BIOS
Specifically BIOS version: 5.4.0.3 available from here.
The combination of BIOS 5.4.0.3 and SATARAID5 Manager 1.5.20.3 was the one I settled on that finally worked.
The BIOS can be updated by opening Windows “Device Manager”, finding the Sil3114 under “Storage Controlers”, right clicking and selecting “Properties”. One of the tabs has a button for updating the BIOS here – it’s straightforward.
One option offered by the SATARAID5 manager software was to “Convert the Legacy RAID group” to a “New RAID group” – I wasn’t quite sure what this would do but as far as I could tell a Legacy group can be read natively by the card, whereas the New group uses the manager software / drivers instead.
Hardware vs Software RAID then? Not sure. But I’m pretty certain that a New RAID group would be much tougher to setup as a boot drive. So legacy would seem better – if only it could be made to be seen in the Windows “Disk Management” window.
So – I took one of the two drives out and let the system boot. Still couldn’t see it.
Deleted the RAID group in the BIOS and let the system boot. Now we could see the drive. SATARAID5 recognised it as a normal non-RAID disk, went into PASSTHRU mode and allowed it’s use. (It is this PASSTHRU mode that makes the alternative SATA Link BIOS software pretty pointless in my view as it acheives the same result),
NB: Whilst deleting a RAID group only seems to delete the RAID metadata from the hard drives with the Sil3114, leaving the data intact, the same might not be the case with other RAID controllers. Beware!
I now reinstalled the other disk, delete the RAID group from that as well and let the system boot.
The system could now see both drives in PASSTHRU mode, the partitions were intact, but the “Disk Management” window informed me that it couldn’t mount the second drive as it had the same identifier as the first. Which of course it would – so that seemed reasonable.
SO – rebooted again – went back into the RAID BIOS and recreated the RAID group, I didn’t bother to make it copy the data again as it was clearly going to be the same, and then let the system boot.
This time success. The drives were still recognised as a Legacy RAID group, but this time were painted green in the SATARAID5 manager software and were visible and useable in Windows 7. A check in “Disk Management” showed that a single drive was being recognised (ie: the two disks are successfully operating as a RAID1 mirror pair).
I have no idea why they were painted red the first time and green the second, other than that maybe the RAID BIOS was very old when I created the first pair and the metadata was a bit rubbish.
Anyway – all well in the end.
So yes – it is possible to get the Sil3114 to drive a pair of RAID1 disks in Windows 7. (Phew!)
Memory requirements
Linux requires at least 32 MB RAM to be able to boot up and decompress it's kernel.For a functional system with some applications you should better have 64 MB or more.
Workstations
PA-RISC Linux supports all HP PA-RISC workstations. Not everything is perfectly functional - but nearly all of it works.The unlettered 700-series workstations (eg 712/715/735) and the B/C/J class machines (e.g. B132L, Tadpole B160L laptop, C180L, C200, B1000, B2000, C3000, J5000, C8000) systems are supported.Fast-Wide Differential SCSI does not work on 735 or 755 (but does on other machiines).
Most standard HP graphic cards work (Visualize-EG, Artist, HCRX, ...) in 8 and 24bpp modes.Support for the Vis-FX series is still missing and will probably not be supported.
Sil3132 Driver
PA-RISC VME boards are based on workstation designs. PA-RISC Linux does boot on a 743.
Search the mailing lists to see if your workstation (or server) has any known problems.Please submit bugs (or patches!) for missing/broken functionality to the parisc-linux mailing list.
Servers
The earliest PA-RISC servers have proprietary HP devices attached to proprietary HP bus architectures. Documentation on these busses and devices will not become available soon since no one in HP is finding, 'scrubbing', and releasing the docs. Machines in this category are the F, G, H, I class (aka Nova) and T500 series (Emerald) machines as well as some earlier, unlettered servers.
Sil3124 Driver
The T600 is unlikely to ever be supported. Though T600 uses some of the same GSC devices (eg card-mode Dino 100BT, Zalon FWD SCSI) as K-class, T600 has the Java I/O MMU, instead of U2, which is NOT I/O coherent. Linux PCI drivers require I/O coherency.
Support for the E class is being pursued. Similar to K class in some ways, it requires the Mux driver for console and does not yet have SCSI or Centronics support. Network support is the same as 712. GSC add-in cards should work, HP-PB cards will not yet.
The D, K and R class machines are at least partially supported. These machines are architecturally similar to the older B, C and J class workstations and share most of the I/O devices, busses (GSC) and processors. The console on K class and the optional console card on D/R class are now supported. Most of the other HP-PB (aka NIO) devices aren't supported due to lack of documentation -- the same documentation which makes the Nova/Emerald machines unsupportable.
The A180, L1000/2000/3000, N4000, and A400/A500 servers are supported.
Support for Superdome might someday follow but requires some additional VM work. Superdomes have a cellboard based architecture. There was never enough documentation released that the according memory management could be programmed in Linux.So probably Superdomes may not work. Maybe on an physical partition level, there might be a chance, since the single cellboard is pretty similar to the L-Class. One idea is to try to get the partition management running and install one partition HP-UX and then try to work with linux on an additional partition.
People ask about V-class. V-class has a very different architecture from other HP machines. See the Server Architecture Reference for details. One major known problem with supporting V-class is the complexity of its PCI bus adapter (EPIC and SAGA). Support for the V-class isn't going to happen until some really masochistic person who has access to a V-class is, uh, challenged by this.
Emulators
QEMU support is progressing quite fast. Check the Qemu page for more information.
SATA Controllers
NOTE: PARISC machines boot from SCSI or built-in IDE drives only.
The following SATA PCI controllers have been reported to work on Linux, after the kernel was booted:
- Silicon Image SiI 3112 PCI Serial ATA Controller (rev 02) (reported by Helge in C8000), does not support SATA-TRIM, may need 'sata_sil.slow_down=1' kernel module option
- Silicon Image SiI 3124 PCI-X Serial ATA Controller (rev 02) (reported by Dave in rp3440, reported by Sven in C8000)
- RAID bus controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01), in C8000 (phantom)
- VIA Technologies VT6421 IDE/SATA Controller (rev 50) (reported by Rolf Eike Beer in C3600 and C8000)
- Adaptec 1210SA, Silicon Image Sil3112 (reported by Carlo Pisani <carlojpisani@gmail.com> in C3600)
- SYBA SY-PCX40009 PCI-X SATA II Controller (SiL3124) (reported by Carlo Pisani <carlojpisani@gmail.com> in C3600)
- HighPoint RocketRAID 2224 (reported by Carlo Pisani <carlojpisani@gmail.com> in C3600)
- Highpoint RocketRAID 1640 (reported by Carlo Pisani <carlojpisani@gmail.com> in C3600)
Sil3114 Driver
External Resources
- http://www.openpa.net/systems/index.html - OpenPA.net Overview of PA-RISC Computers