Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Friday, December 28, 2012

Failing disks on AMD RAID

[Default userid :: password is admin :: admin]
  produces the following reply:
Unable to connect
Firefox can't establish a connection to the server at localhost:25902 

CEB solution:
1) Start allways the AMD RAIDXpert with the program link at START - All the Programs -AMD
2) Look for security certificates or something like WOT or NoScript!
(sitio de confianza puesto en duda por usar protocolo https: que usa SSL como opción segura del web server de AMD RAID)
Lets start with some explanations. ATI RAIDXpert looks like it is originally the Promise WEBPAM a bit modified. This would make this plugin usable for WEBPAM as well (just modify some strings in the posted code). RAIDXpert/WEBPAM is a web-application running in jetty. For access you have to include a decent browser in your BartPE (IE6 will do, but show errors). I'm using sherpya's Firefox plugin.RAIDXpert uses a service for starting the webapp. There is RAIDXpertservice.exe starting RAIDXpert.exe which accesses jvm.dll and starts jetty with the necessary properties set. Information for this process is collected directly from the service-settings (great trap: all quotes must be set right etc). If something isn't working you can start the webapp in the jetty directory for debugging using

..\_jvm\bin\java -Ddebug=true -jar start.jar amd.xml
The service relies on an ip-stack - XPE will manage this for you, nu2shell with PENETCFG will only start networking with an recognized network adapter. The plugin takes care of this, but you have to change PENETCFG-autorun for this to work. I moved it from autorun0 to autorun5 (this helps bginfo too). To do so you have to rename autorun0penetcfg.cmd to autorun5penetcfg.cmd and make this change in autorun-penetcfg.inf, too.
Localhost is another name for your own computer. You don't even need a network connection.
Apparently, your RAIDXpert server application either isn't running on your computer, or it's running but isn't listening on port 25902. Firewall is blocking this port??
Trying to launch RaidXpert from the shortcut, received HTTP ERROR: 500, org.apache.jsp.index_jsp. That was how I happened to find this blog.
I discovered I already had a browser window open with the RaidXpert html running. I thought maybe that was the problem, but before closing the browser, I bookmarked the URL. However, when I tried again to launch from the shortcut, I still got the same problem. So I tried launching the app from the bookmark, and that works fine.
If you enter the URL directly into browser (http://localhost:25902/amd/login.jsp) it works fine. Or bookmark it.
A patch code was released in order to solve the compatibility problem between some mainboard with the AMD SB850 chipset and Samsung HDD (F3 and F3EG model only).
This patch program works only to
F3     (HD323HJ / HD502HJ / HD503HI / HD103SJ / HD105SI)
F3EG (HD153WI / HD203WI)
my motherboard: sata-raid-array-890gxm-possible
Is this before installing Windows 7 or in Windows 7? Both links are to the 64-bit Windows 7 driver.
If before, use this one:
If in Windows 7:
Technically, you can use the drivers in the first link after Windows is installed too. All you need to do is go into the Device Manager, find the SATA/RAID device, open properties on it, click on "Update Driver," then browse to the folder with the RAID drivers extracted.
AMD Chipset Drivers
AMD Radeon™ Graphics Drivers
Automatically Detect and Install
AMD Radeon™ Desktop Video Card Drivers 
AMD Catalyst™ 12.6 Beta Driver 126 Beta drivers
RAIDXpert Guide
AMD RAIDXpert Easily configure your RAID setup from remote locations to personalize your media for extra performance or enhanced reliability.
The RAIDXpert is a remote RAID configuration tool, for changing the RAID level of the RAID setup connected via SATA 3.0 Gbit/s ports (connected to SB600, excluding extra SATA 3.0 Gbit/s ports through additional SATA chip on some motherboard implementations), including RAID 0, RAID 1, and RAID 0+1.
Die AMD AHCI Driver scheinen schon ins Rentenalter zu kommen.
Der letzte mir offiziell bekannte war der von 2009. Kann mich da aber auch irren. Jedenfalls arbeite ich z.Zt. mit der Version 3.2.1540.75 vom Juni 2010 und von von den Ergebnissen wirklich übberrascht.
Eigentlich ist dieser Treiber für die neueren SB850 Chips gedacht b.z.w im Lieferumfang einiger Systeme enthalten.
T-Rex hat ja schon in einem anderen Beitrag vom Performance Plus dieser Chipsätze durch SATA III unterstützung berichtet und darum beschränke ich mich auf die AMD#S SB750 Reihe. Kurz und knapp folgt nun ein Testergebis mit dem im o.g. im Lieferumfang enthhaltenen Treiber und danach mit dem neuen.
Und hier geht es zu den zweiunddreißig und vierundsechzig Bit Treiberlingen für Windows 7even & Vista:
Und hier für XP 64/32-bit:
Selbst wenn man die SSD als Singledrive am Raid laufen lässt, kann man eienen Performance-Zuwachs feststellen.
Der neue SATA Treiber von AMD unterstützt zwar die TRIM-Funktion,,, jedoch konnte ich persönlich keinen Unterschied nach 2 Wochen SSD Dauerstress feststellen. Ob Trim läuft oder nicht spielt mMn für die SF controlled SSD absolut keine Rolle. 9%89%E0%B8%A7
=======================  7
For your information: the "very latest" Windows 7 WHQL AMD RAID drivers for SB7XX/8XX platforms (release 3.2.1540.75) are located at:$FILE/

Same drivers, but for Windows Server 2003 (and, I suppose for XP, too...):,SB8xx~Windows%AEServer2003

The latest RAIDXpert utility (v3.2.1540.10) for array management is available at:
* *
* AMD AHCI Compatible RAID Driver Diskette *
* *
Contents on the disk
README TXT This readme file
AHCIx86 Microsoft Windows miniport disk label file
AHCIx64 Microsoft Windows miniport disk label file
TXTSETUP OEM Microsoft Windows miniport text mode setup file
x86\AHCIx86 INF Microsoft Windows miniport setup file
x86\AHCIx86 SYS Microsoft Windows miniport driver for x86 compatible platforms
x86\AHCIx86 CAT Microsoft Windows WHQL Certified catalog file
x64\AHCIx64 INF Microsoft Windows miniport setup file
x64\AHCIx64 SYS Microsoft Windows miniport driver for x64 platforms
x64\AHCIx64 CAT Microsoft Windows WHQL Certified catalog file
Software Version
Microsoft Windows miniport driver 3.2.1540.75
Intel at this point is supporting 90% of their hardware on Asus motherboards for Windows 7, x86 or x64.
I never thought it would be this easy installing an operating system

  • Intel

  • Read.Me

  • A different story with AMD.
    The website support center seems to be only supporting older models however Windows 7 from my observation is very limited.
    Asus with AMD chipsets seem to have a vast of newer chipset supported on their website.
    I will not link the AMD support center.
    AMD has updated their support for motherboard chipset's. These packages should include most of the chipset model's. Here's the link:

  • AMD
  • VIA seems to be a little sidetracking but they are supporting Windows 7 for older and newer chipsets.

  • VIA
  • Nvidia is on the same page as Intel.

  • Nvidia

  • Windows SIM
  • ============================
    15-09-2010, 11:01
    AMD ha reso pubblici i drivers Catalyst 8.73 per le piattaforme "GPU/Chipset Embedded" (E4690, E2400, AMD 785E/SB8X0 Chipset e AMD 780E/SB710 Chipset).
    Il file è un unico archivio in formato ZIP.
    All'interno vi si possono trovare anche i drivers specifici per il RAID implementato nel chipset della ns. motherboard (versione serie 3.1). Posso però confermare che anche i più recenti 3.2 per i chipsets SB8XX (sempre contenuti nel suddetto file) funzionano alla perfezione con il SB750.
    Nell'archivio c'è anche un aggiornamento al software di gestione di Promise (RAIDXpert), in versioni separate per i driver RAID 3.1 e 3.2.
    Sul mio sistema il tutto funziona alla perfezione.
    Visto che, come accennato poc'anzi, non ci sono problemi di compatibilità, ho installato i drivers per l'SB8XX ed il corrispettivo RAIDXpert.
    Nel caso qualcuno volesse ulteriori ragguagli sarò lieto di rispondervi pubblicamente (appena avrò un pò di tempo...).
    Ecco i link alla pagina web di AMD:
    Windows 7 (32 e 64 bit) (
    Windows XP (32 e 64 bit) (
    I had installed the Win 7 x64 RAID drivers version 3.2.1540.14 when I installed the O/S. Those drivers apparently fail to install the AMD RAID Console driver. I had also installed RAIDXpert version 2.something
    What WORKS is the following:
    1) Get the file from the AMD website
    Nuovo aggiornamento dei drivers AHCI/RAID per SB7XX/8XX, certificati WHQL.
    La versione è la 3.2.1540.75, per Windows Vista/7, x86 ed x86-64.
    Upgrade your drive controller to that.
    Note: After you reboot, the Op. Sys. should now find the AMD RAID Console device.
    2) Get the SB8xx_RAIDXpert_3.2.1540.15 install.
    "AMD AHCI Compatible RAID Controller":
    [Win7 x64 MSI (SB850 chip) RAID controller drivers]
    NameFile SizeRevision NumberRelease
    AMD Chipset Drivers26.6 MB12.1010/22/2012Download
    This package is for motherboards with 700 series or newer AMD chipsets, and includes:
                           AMD Chipset Drivers
                           AMD AHCI Driver
                           AMD USB 3.0 Driver
    AMD Raid Drivers29.7 MB12.1010/22/2012Download
    Package Includes:
                            AMD SB7xx RAID Drivers
                            AMD SB8xx RAID Drivers
                            AMD SB9xx RAID Drivers
                            AMD A-Series APU Chipset RAID Drivers
                            AMD E-Series APU Chipset RAID Drivers
    AMD RAIDXpert Utility55.3 MB3.3.1540.193/28/2012Download
                  The AMD RAIDXpert utility gives you complete control of your RAID arrays within a simple web browser based application.  This tool allows you to monitor and manage your RAID arrays in the Microsoft Windows environment or via remote login to your system.  For detailed instructions on how to use the AMD RAIDXpert utility, please refer to the associated user's guide.

    3) Uninstall RAIDXpert (this, too, can be a very fun experience... try using command line and /removeonly or /x flags on C:\WINDOWS\Downloaded Installations\{....}\RAIDXpert.msi if all else fails. e.g. "MSIEXEC.exe /x RAIDXpert.msi"
    4) Install the newly-downloaded RAIDXpert.
    Bingo. It works.
    Promise Technology sucks?
    My other machines are all Mac's so I mostly followed the instructions in THIS THREAD. The first two times I tried to back up my iMac to the server with TM it completely crashed it so I reinstalled from scratch. The second time it crashed the RAID, but (I think) it was only SDB that it had listed as failed. I was able to unmount and recover the RAID with mdadm. The third time I left it to back up over night and woke to find two disks (I think sdb and sdc, but not sure) listed as failed. After much tooth gnashing I found the "failed" disks listed as part of md127 and was able to reconstruct the RAID from scratch. 
    This last time I went to bed and disabled sleep on my iMac. TM successfully backed up over night. Now I just came home from the beach to find the raid rebuilding from a failed sdc and a fresh, successful, TM backup as of 30 minutes ago.
    So, I'm trying to figure out why it's "failing" the disks erroneously and how to fix it. 
    It's not a cable issue, because your SMART data would reflect it on this line.
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
    You have zero CRC errors, so that's not the problem. 
    Sorry, here's a bunch of questions to get started:
    1. How do you have your disks hooked up (directly to the motherboard or to a HBA card)? 
    2. Does this only happen with that drive or are drives randomly failing out of the array? 
    3. Have you tried checking dmesg after this happens?
    4. What do you have in /etc/mdadm/mdadm.conf?
    cat /etc/mdadm/mdadm.conf
    That should be enough to get me up to speed
    If you have the same problem of Signature Collision try to go to "Manage Computer" and then "Disk Management", find your drive and then right click to make it go "online". If it wont work then go to a command prompt and type the following in " ", hit return to move through:
    "Disk Part"
    (this brings up a separate window in Win 7)
    "List Disk"
    (This will show you which disks can by physically seen, offline and online)
    "select disk X"
    (Where x is the number of the disk you want to make online)
    "online disk"
    (This should bring you a message saying your disk is now online)
    This takes you back to windows and you should now see your disk through Windows Explorer.
    See if this helps:
    My suggestion would be to go back into Disk Management, right click the smaller box next to the second external drive, and see if you can use the option to turn the drive to 'Online' mode.
    Each volume has its own unique identifier, called a signature. Though very rare, you can run into a situation (which mostly happens after cloning data to another drive) where both drives have the same signature.
    If it will not allow you to switch the drive to 'Online' mode, then take the external drive to another computer, format the volume completely, and then take it back and it should work.
    I have found that the cause of my problem was setting two drives to act as a "Raid Mirror" set up, which caused the drives to get the same signature. When I decided not to use them in a "Raid Mirror" setup they retained the same signature. Temporarily setting them as "Raid Stripe" seemed to resolve the problem (probably because different signatures were assigned to each drive)
    Unless you know the drive is empty: 
    Use the Windows Diskpart command.  Select the Offline Disk.  Enter the command Online Disk.  Diskpart is much more powerful than the Disk Management.  I had this problem and Diskpart brought the drive online with NO issues where Disk Manager continued reporting a Signature Collision.
    Sorry to sound harsh but to format the disk?  I would think removing the disk and doing an Import Foreign Media would probably work allowing you to then place the disk bakc into the original computer.  If you still get Signature Collision...use the above it works fine.
    My Signature collision was cause by Acronis Disk Suite...HORRIBLE software if you have Windows 7....have had noting but problems...seems any disk it touches corrupts the MBR and Signaure area.

    No comments: