[Wd Raid Manager For Mac
Vida Hubbert
II have a M2 Mac mini ventura 13.4 machine and a Lacie 2BIG external drive and a Lacie rugged 2T external drive attached. Trying to install Lacie RAID manger v 2.9.4.437 and con not get the "Seagate Semiconductor LLC extension to load even after trying several uninstalls/re-installs of RAID Manager software. This included all the necessary ADMIN authorizations and RESTARTS that were called for. A extension "Marvel Seagate Semiconductor seems to load OK but not the Seagate Semiconductor LLC extension. Thus RAID Software cannot see the external drives. Apple Support (Engineering) has reviewed my Mac mini and says all is OK. Any and ALL guidance on problem resolution is most welcomed
I have not done any speed/performance testing of the Lacie drives, as I use them for one specific freelance project only, which is a 1080p show. I haven't had any performance issues, as it seems to run just like it did on my Intel iMac (before it died).
My 5Big LaCie (5 x 4TB) would not work on my M1 MacMini back in October 2020-same issue drivers/Kext's/not compatible kext's ... and all that. After 6 frustrating months with LaCie support, I converted it to a JBOD-which wiped it clean and installed OWC's Softraid; then re-loaded from backups - and I have used this configuration/software since then.
Thank you for response. I should have mentioned before, this procedure/settings was accomplished during the support call with apple support to no effect with seagate semiconductor llc extensions not loading it did allow the marvel seagate semiconductor llc extension. Again, LaCie senior support advisor had no solution/guidance (they sent me back to apple support)
I have the same issue with Mac Studio M1 ultra and Lacie 2big raid drives. After installing raid manager it wants to rebuild the cache, but this does not work, it goes into a loop of asking to rebuild cache every startup now unless I change the security setting back to normal. I've dealt with Lacie, trying to get this resolved with no luck. It works on my MacBook Air m1 with Ventura 13.01 but does not work with my Mac Studio with Ventura 13.4
I have a new MacBook pro M2 with Ventura 13.4 and have been trying with no success to install LaCie Raid Manager V2.9.4. Like others posting here I have followed all the instructions on the LaCie support pages. I keep getting sent around in loops to change security and privacy settings and to allow extensions from Marvel, while no such extensions are shown, and to restart. - Only to be shown an error message, regarding, you guessed it.
Basically, I am convinced after several attempts that this instal simply doesn't work, and if I want to monitor my raid drives on my macbook pro, I will have to purchase a raid system from some other vendor. Can you please advise (and please, don't just repeat the previous answers.
I have a LaCie Big 6 RAID and am trying to install LaCie RAID Manager so I can connect the RAID to my MacBook. As previously described, after enabling kernel extensions I end up in a loop where the os states (after restarting) "System Extension Error - An error occurred with your system extensions during startup and they need to be rebuilt before they can be used. Go to Privacy & Security System Setting to re-enable them." Doing so requires a restart which then displays the same error message. Loop-de-loop.
I've just received my refurbished Mac Studio. Was SO excited to get my workflow times down. Gone through a lot of today trying to set things up and now I'm facing this same issue that so many others are and I can't access my DROBO. This is a HUGE problem for me if I can't access it and will cost my business money. Apple needs to fix this issue or at least provide clarification or a work around ASAP. This is so poor that this has been happening for so long. How are people supposed to access their data? Crazy. Lift your game Apple.
Boot the Mac in Safe Mode. Then install LaCie Raid Manager. After doing this, you should see the "Seagate LLC" extension listed as "On" in the Login Items. After that, restart. You will get the "System Extension Blocked" popup. Go to System Preferences and click "Allow" for the Seagate extension. When given the option to "Restart" or "Not Now", choose "Not Now". The computer will pause for several seconds before the popup goes away. Then manually restart the Mac.
Hi,
I'm about to start using HP Proliant hardware with SUSE SLES 10. Can anyone point me to information (user manual or similar) for HP raid management software under Linux? I'm familiar with the IBM raid manager and would like to confirm that the HP version provides similar features, particularly e-mail notifications and graphical interface. I haven't been able to find anything through the HP website.
Thanks,
Greg Shearer
I'm in an awkward position where the customer doesn't want the server to come down. However, I'm in a spot where I need to see the Array status and there is no Dell Open Manage, or other RAID monitoring software on the machine.
Is there an alternative to the Open Manage software that can just tell me what's going on in the array? I don't need any kind of advanced features, just a monitor. Would obviously like to not reboot after installation, but I'm not sure if that's realistic.
If I do need the Dell Open Manage software, which one do I need? I see 15-20+ different flavors of Dell Open Manage on the downloads site. Is there a way to just install the storage manager part without installing everything else?
This is understandable, and Dell kept that in mind when designing the software ... it's lightweight, doesn't interfere with existing services, and they have eliminated the need for a reboot. The pros far outweigh what few cons there might be. OMSA services generally take less than 100MB of memory (usually around 80MB) and seldom any CPU cycles. If ever investigating issues on a server, OMSA is probably your most valuable tool, so that 100MB is a very small price to pay.
"With all that said, I'm making the customer sound inflexible, but it's all just all bad timing. Without rambling on for a few paragraphs, the customer is extremely busy at the first/last of the month. Next week I could bring it down without a lot of "resistance", but one of their HDDs has a fast flashing amber light, so I assume there's a fault there and that maybe even the array is degraded which is really concerning. It certainly warrants a reboot, but if I can get around it that would be great."
Ha ha ... they sometimes can be :) I'm glad they aren't, but you are wise to want to get on top of the failed drive (degraded array) as soon as possible ... every minute it is degraded, they are at risk of a second failure (array failure) or data corruption due to read/write errors.
Download and run to extract contents, then run C:\Openmanage\windows\setup.exe. Choose Custom to make sure that Storage Management is being installed (if firmware/drivers are out of date, the storage portion may be disabled from a default installation). Don't try to second guess what does/does not need to be installed, or it probably won't work, and then a reboot may be necessary to remove o repair it :) (OMSA will require SP2 to be installed on 2008.)
No. You need software that knows how to talk to the RAID controller. Dell controllers are rebranded LSI controllers, and LSI has management software that MIGHT work (and might not - PERC's have different firmware than LSI controllers), but your best bet is OMSA. OMSA can "usually" be installed without a reboot.
No. OMSA is required, Storage Services (SS) is an optional component and will not work without everything else. Since it normally does not require a reboot to install, is there some other issue preventing you from wanting to install OMSA? You should require OMSA be running on any Dell server you service for a client - set that expectation up front - that you cannot properly manage the server without it. Also, you should prepare them for the eventual possibility that the server will need to be rebooted to do what they are requesting (if you aren't sure), then you are a hero when a reboot is not required.
My concern with OMSA is really just that I prefer having as little as possible on machines. The download seemed kind of big - I think I saw one OMSA download that was 800MB. I guess I just didn't want to have to hog more resources than necessary to just check the RAID status.
With all that said, I'm making the customer sound inflexible, but it's all just all bad timing. Without rambling on for a few paragraphs, the customer is extremely busy at the first/last of the month. Next week I could bring it down without a lot of "resistance", but one of their HDDs has a fast flashing amber light, so I assume there's a fault there and that maybe even the array is degraded which is really concerning. It certainly warrants a reboot, but if I can get around it that would be great.
I downloaded/installed OMSA (having a direct link was nice). I do see now that one of my drives in my RAID5 array has failed. I'm gonna run get an HDD and swap it out right now. I'm guessing that I should be able to install a new drive with the system running.
1. You should use Dell-certified drives for maximum performance and reliability. These are drives that have had their firmware tweaked to certain specifications - and to match the specfications and demands of the controller(s), so Dell is able to guarantee them and their controllers.
2. You could use non-certified enterprise-class drives ... for example, you might find a generic/retail/non-Dell WD5002ABYS, but you run the risk of firmware incompatibilities - the drive may not know how to respond to the controller (timings may be off, some commands may be used or not used differently, etc.), but they will "usually" work. However, if you ever have need to contact Dell Support for an issue, they will wash their hands of it, no longer able to guarantee their product.
3. You could use desktop/consumer-class drives, but I wouldn't. They are not designed for the workload that an enterprise-class drive is (8x5 typically vs. 24x7), nor are they programmed to talk to RAID controller and know how to respond to the many enterprise commands coming from the controller, typically designed to be used alone or in a software RAID array, where those settings aren't as important. You may experience any number of issues with these drives - ranging from delayed writes, to random timeouts (resulting in drive going offline), to not even being detected by the controller. Again, they may work, but chance are much greater for issues with desktop drives.
795a8134c1