Program Won't Start: Hangs @ "Scanning RAID Devices"?

[rexrzer727]

I installed the v1.20 client without much fanfare, however the program refuses to launch:

it hangs up @ "Scanning RAID Devices" in my PC No.1 that I would be using the client in,

and I've tried the following to no avail:

1) uninstall and reinstall, restarting each time

2) open with Admin command

3) open with simple double click on program icon/alias

4) open by clicking on program in Program Files, both normal and Admin Commands

I have no idea what is going on, but I still have a copy of Everest Ultimate in the system

and that still works. Is there a conflict there, perhaps? Should I uninstall Everest Ultimate?

I sort of wanted to keep both programs, but if it interferes with AIDA64 then I'll remove it.

My system has twin working RAID volumes, a 2TB boot volume; a 4TB big scratch disk for my audio

and video and sound works in progress, and application installation for Sony Vegas and Pinnacle

Studio...both are RAID 0. I have an Areca 1680IX-8 SAS to eSATA/SATA Hardware RAID Controller that

does all I/O in the OEM machine. It's build on an EVGA Classified E760 motherboard, with the usual

fare, twin GTX-285 video cards in SLI; X-Fi Fatal1ty Sound Card; DLink DWA-556 PCI-Express WiFi

network card, etc. It's running an Intel 920 2.67Ghz CPU overclocked to 4.2Ghz on AIR, stable as a

rock since 6/2009, and it runs 12GB of G.Skill 1600Mhz DD3 SDRAM (6x2GB DIMMS).

The OS is Windows 7 Ultimate 64-bit...if that makes a difference.

That's the rig the client is installed in. Now I do a couple things that may be an issue with AIDA64

that I'll mention now so that any responses toward this might be up front. I run three RAM Discs (VSuite program, xlnt program!) on

the computer, 128MB for Chrome browser; 4GB Scratch Disk; 2GB Scratch Disk--with 12GB RAM I have found

it speeds up my browser about 50% overall, in all areas, and it makes for certain types of file

processing very speedy also. They are dynamic RAM Discs, and do not take up RAM when not being accessed. The 4GB RAM Disc is held in cache, will appear at new or restarts automatically...as is the Chrome browser RAM Disc.

Could AIDA64 be having trouble with the RAM Discs?

It's either that or the Areca controller perhaps, but again, Everest has no issue with any of those items.

That's the basic situation, and I'd love to be running the new program of course, but as it stand I

have not been able to yet. Thanks in advance for any answers and if somebody has a quick solve it would be

very nice!

[Fiery]

I think it could be the Areca controller.

What version of EVEREST Ultimate Edition do you have that has no issues with the controller?

Thanks,

Fiery

[rexrzer727]

I think it could be the Areca controller.

What version of EVEREST Ultimate Edition do you have that has no issues with the controller?

Thanks,

Fiery

I have installed on that particular PC No.1 Everest Ultimate v5.02.1750, as I never did get around to upgrading the file to v5.5.x.x. That Everest has never had an issue with the setup on PC No.1, as I had installed it when I built the thing back in May, 2009, and it's been there ever since as configured with the controller...ie I built the PC with the controller and HD setup it's presently using, it's never been changed since the build.

So I dunno what to do at this point, is there anything you can suggest? Would you like a System Report from Everest perhaps? I can generate that and send it in to your company if you need it for compliance with the Areca controller.

The thing that puzzles me is that the Areca controller is not a new model, it's a 2009 model with 2010 firmware (I updated it once, this past February at the request of Areca, USA up in Fremont, CA 94538). So shouldn't your software accommodate it? I am not using the SAS Repeater function of the controller or anything exotic like that, and it's emulating an eSATA and SATA bus for Windows 7 compliance and booting...works a treat, too! I have both hardware (firmware, in BIOS) control, and browser control of the Areca controller, and it's capable of supporting a LOT more than I am using it for...up to 128 SAS devices, as I recall, with Repeaters in the mix.

I'm all eyes and ears on this one, so by all means let me know what you need, or if I can help you with your product development and compliance with this sort of controller, if that is in fact the issue. If a System Report from Everest will help that is easy to do...just let me know where to send it, and I'll be happy to do so.

Later,

rexrzer727

[Fiery]

I was just wondering the used EVEREST version, because we've implemented Areca RAID controller support in EVEREST Build 1824. In case you use an older version, then it would be great if you could give it a shot with EVEREST v5.50.2100:

http://www.lavalys.com:8081/everestultimate-discontinued-550-o1kx4dyabh.zip

You don't need to perform a full upgrade of EVEREST. Just download this ZIP file, extract it to an empty folder (it can even be a new folder on your Windows Desktop), and run EVEREST.EXE. In case this one hangs, it means the issue is with the Areca RAID members enumeration.

Thanks,

Fiery

[rexrzer727]

I was just wondering the used EVEREST version, because we've implemented Areca RAID controller support in EVEREST Build 1824. In case you use an older version, then it would be great if you could give it a shot with EVEREST v5.50.2100:

http://www.lavalys.com:8081/everestultimate-discontinued-550-o1kx4dyabh.zip

You don't need to perform a full upgrade of EVEREST. Just download this ZIP file, extract it to an empty folder (it can even be a new folder on your Windows Desktop), and run EVEREST.EXE. In case this one hangs, it means the issue is with the Areca RAID members enumeration.

Thanks,

Fiery

OK, I downloaded that file and guess what? It hangs! Will not open, and just is stuck there scanning for RAID devices just like AIDA64 is stuck doing the same thing.

So WHY does my older version work and this does not?

You say the problem is with the Areca RAID member enumeration? I see...

Well, your problem is then defined for you, sorry for me and my system as to using the new product...unless you custom make me an edition with Areca enumeration corrected! Hah!

Good Luck, and sorry you're having this issue...and I'm sorry for me, too!

Later,

rexrzer727

[Fiery]

Thank you for the feedback. It's definitely the Areca RAID members enumeration then. The old version (5.02.1750) had no support for Areca RAID arrays at all, and in this case no support means no headaches

We'll check our code and either we'll fix it, or we'll implement a workaround, or we'll completely remove the Areca-related code.

I'll let you know in this topic how it goes.

[rexrzer727]

Thank you for the feedback. It's definitely the Areca RAID members enumeration then. The old version (5.02.1750) had no support for Areca RAID arrays at all, and in this case no support means no headaches

We'll check our code and either we'll fix it, or we'll implement a workaround, or we'll completely remove the Areca-related code.

I'll let you know in this topic how it goes.

I never spent much time or energy with Everest and this PC No.1, but there is only limited data available from Everest v.1750 on my RAID arrays, although it does *identify* each one correctly, and identifies which one is Drive C, the active boot volume of course, the 2TB RAID 0.

Under Windows Storage it lists all the various devices in this computer, including all the Areca controller administered devices, but very little specific data on each RAID volume. For example, under SMART attributes there is no data whatsoever listed, it's just blank...

So in this case with "no support" for the Areca controlled system(s) in this computer it's sort of a stupid kind of support, sort of 1/2-support if at that level, but surprisingly there's nothing negative happening because of the arrays and Everest...there's just lots of blank spots...like SMART status, etc, which the Areca controller administers in its own way in any case, and I can read SMART status anytime I want to in my browser window for the controller.

Everest of course has nothing for me in most areas of import re the RAID devices themselves...

So, as I understand it you may just amend the present code to where it works with this system at some point? Or you may eliminate the Areca code altogether? I see the logic there, just like this one would have no support but at least it would function for other things...

Well, keep me informed and I'll be interested as time moves on here and your product becomes current and up to data on many things, including Areca controlled RAID systems. The controllers are really quite good, xlnt things, you know? It wouldn't be a bad idea for your AIDA64 to support the system, but there's a lot of code writing to be amended I'd guess if that is the case.

Thanks for the info, and have a great week!

Later,

rexrzer727