LaCie 6Big - M1 Mac Mini Driver

Whelp, I learned a lovely lesson about Lacie today. Their customer driver extensions on MacOS are ultimately as bad as I figured they would be and it seems to have bitten them in the ***. It seems their current drivers aren't compatible with M1 Mac minis (and I haven't seen a single post/article mentioning this). I was planning on migrating my Plex server from an i3 Mac mini to an M1 based device, but now I have to reshuffle my setup with another one of my computers due to lack of driver compatibility (and no advertised lack of support). I'm seriously considering getting rid of my Lacie 6Big at this point and swapping it out for an OWC thunderbolt 3 rack supported DAC. -_-. I'm hoping other people just read this because honestly, I have nothing but nasty remarks towards Lacie in this regarding considering their #1 use for their RAIDs involves the people who will be buying M1 Macs. Does anyone have a workaround for this?

Replies

I'm having the exact same issue with a new 6Big. I can get the unit to work over USB 3.1, but not Thunderbolt 3. It appears to me that Big Sur is refusing to allow the driver to be installed, but in either case the 6Big DOES NOT WORK over Thunderbolt 3. The Mac Mini M1 doesn't even see it.

Lacie's support is atrocious, I can't get ahold of anyone or get them to respond to emails. I think I'll return it.
Hi guys, i'm having also the exact same issue with a new 6Big. I can install the Lacie Raid App but not the KEXT. Any workaround already?
LaCie support was zero help. There was effectively no trouble shooting whatsoever. They had me run a firmware update (it was already updated to the latest version), then check Privacy&Security to see if OS11 was preventing anything from running (when I first installed LaCie RAID Manager I got a warning saying OS11 blocked something from running, but there is now no mention of this in system preferences), then try a different Thunderbolt 3 cable.

That was it. After that, LaCie said it should work, couldn't understand why it wasn't working, and that since I just purchased the unit I should return it.

Somebody has to have figured this out by now, right? Please help!
I think I found what's going on. Under "Disabled Software", this is what appears. It looks like OS11 is preventing this from running. I've been on the phone with Apple support and they are blaming LaCie (which might be justified).

Is there any way to allow this software to run, and see if it resolves the issue, or figure out why it was blocked?

7NPX47N25H - com.lacie.driver.mvumi:
Version: 1.3.21
Reason: No User Consent
Date Disabled: Unknown
Post not yet marked as solved Up vote reply of AJK7 Down vote reply of AJK7
If you show the package contents of LaCie RAID Manager in your applications directory and manually run the bash script to install the driver (InstallDriver.sh) in Terminal you'll likely get a message saying it's only x86 compatible. At least, that's the case with my big 5 bay LaCie. After 3.5 hours on the phone with support this is being blamed on Marvell and LaCie says they can't support it and don't know that Marvell will choose to on 'legacy' devices like this. I got a message (similar to the usual kext security messages) on install informing me of the incompatibility (when using the regular install GUI). It's fairly easy to miss and you'll only get it on the first install. Did you see anything like that?

I'm not sure if the root cause is the same on your TB3 6-bay but this is the dead end I hit on my TB2 LaCie. If they're both using the Marvell controller it seems likely.
Had same problem with M1 Mac mini. Apple support was very helpful taking me through two levels of support. Got escalated to engineers that identified the problem as a change in how drivers are installed. Supposedly the information was provided to LacIe well ahead of time to prepare, they did not prepare.
Reached out to LaCie, after several techs having no clue, I got a written response back acknowledging the problem and stating that they were working on it. I sent a follow up complaint as their website under support still was not acknowledging the problem a month into it and finally they posted its as a known problem a couple of weeks back.
So wait and see, but it is a problem with the Marvel drivers and there is no work around until re-written as I was told.
LaCie/seagate support has been useless. I bought an M1 mini to use with my 6big RAID and nobody seems to know anything as to how to fix it. People seem to think that it’s 32.

there are other drivers than Marvell that should support 64 byte, are there not? LaCie needs to get their act together and remedy this. It’s not like Apple didn’t provide the tools prior to the rollout of the M1 chip for them to know there’d be a problem.

Has anyone come up with a solution or have any information on when/if a fix might be available? Are there any workarounds?
Lacies customer support is horrible. I bought the 6Big with the new M1. Now I consider returning it... Have anyone received any info from Lacie at all?
I have been trying to solve my issue with Lacie 5BIG TB2 and Big Sur on iMac for 2 months. When accessing the Lacie Raid Manager, I would get the message that a driver needs to be installed. When I manually ran the install script, I noticed that I was getting an error when trying to load the driver. I noticed some references to old kext.

I use the System Report to look at all non Apple extensions and see when they were installed, if they were loadable and x64.

I opened a terminal and
  • sudo su

  • cd /Library/Extensions

  • deleted all old extensions that I no longer needs such as Blackberry, Epson and Logitech. (rm -rf {name of the directory you want to delete}

I then received a notification from Security and Privacy about something was updated (don't remember the exact message) and needed to restart my iMac. I restarted my iMac and to my surprise my Lacie 5BIG TB2 came back online :-)

Bottom line for me, there was an extension that prevented others (like the Lacie one) to get loaded. Cleaning up these old extensions did the trick. Hope it can help some of you address that issue.
In reply to Clouzeau, this gives me hope of being able to use my new Mac Mini M1 with my 5Big TB2 on Big Sur. I am not a developer, I am a photographer with heaps of media assets on the 5Big that I cannot access at the moment.

I have reached out to LaCie help desk by email but their help has been ultra basic and nothing that I haven't found myself by searching. They now say that the 5Big TB2 is not compatible with the M1, but your post gives me hope.

Your instructions have given me a roadblock though. I open Terminal, type in sudo su and then it prompts me for a password. I type in my Apple password but it doesn't let me in. Then I searched further and found I could change my password which I did.



Then I typed cd /Library/Extensions but then I got this message :  

No such file or directory
sh-3.2

Is there something else I can try?



sorry I'm not sure why my last line was in a headline form, I can't seem to change it.
Bluedisk, unfortunately my work around only works for older Mac that had a number of OS major upgrades. It will not work for a brand new machine or brand new clean installation. The fact that you cannot access the Extensions directory means that you have not installed any non-apple extensions. My work around demonstrated that 5BIG works on Big Sur with an intel chip. Your Mac mini is based on the M1 chip and will need a different driver.
As of March 1, 2021, LaCie's 2big, 6big, and 12big Thunderbolt 3 products, as well as their 5big and 10big Thunderbolt 2 products, are not compatible with Apple Silicon (M1) Macs. Their website states that "LaCie is working to address compatibility issues."
April 8 - 2021. 5 few days ago I received a notice that LaCie had issued an update to the LaCie RAID manger that would work under Big Sur 11.2.3. Today, April 8th, I set aside the afternoon to download and install the RAID driver and physically move my 5BIG from my Intel Mac Pro 6,1 (2013) Thunderbolt-2 to my Mac Mini M1 (16GB ram/2TB storage). So this is LaCie Raid Manager 2.9.3.207. This time the install under Big Sur went fine - I had to approve the software's source with Privacy as expected and this time it went okay. The drive was recognized and I could read and write to it. However, it's performance is seriously impacted. On my Intel MacPro (TrashCan 6,1 Thunderbolt 2) I get at least, 400/400 MB/sec by any measure (transfer a really big video file and stopwatch it, Blackmagic, etc) - but on moving the drive to the M1 my speeds are roughly write 55MB/sec; read 270 MB/sec...there is some variability but this is the essence of it - not much better than a USB2 drive and on par with a FW 800.

So this is a serious problem. This drive, while readable, is useless for ay serious photographic/video work.
I spent some hours on the phone with tech support today and they do not have an answer for this. I swapped every TB2 cable and Apple adapter I have* - so it's not a cable or adapter issue. It's a driver issue - entangled with caches/buffers/optimization and all that.
  • I have 3 Apple TB 2<-->3 dongles I have 2M and half-metre cables from different manufacturers - I counter-swapped, and all these work fine on the TrashCan - and when connected on the clearest/simplest path on the M1 Mac - much less performance.

Two questions

what numbers are you seeing*
How do we mount a claim on this.
  • the reason I am asking this is if your 5Big (whatever) is performing differently than mine - I have done 2 failed drive swaps over the years and although I have replaced with IronWolf, maybe I have introduced something incompatible or less optimized. Nonetheless, the LaCie Techs cannot discern this and the drive currently does do 400+/400+ on the Intel and 55/270 on the M1.

I do not relish dumping this drive system - but it is useless on the new future of Macs. The LaCie tech sort-of admitted to this but has no solution and so we must apply some pressure.

Nest Steps. BTW - I am sure this applies to 6Big and 12Big as well....so this is not a small community that has had their hardware back-watered very prematurely.

jc - April 8-2021
Same problem here. M1 Mini, 16GB, Big Sur 11.2.3, LaCie 6Big with 20 TB Raid 5 connected via TB3.
A few days ago I installed the new driver and Raidmanager 2.9.3.207, at least the raid was accessible via TB3
  • write: around 31 MB/s

  • read: around 460 MB/s

Today, April 11, it seems there was an update for the kernel driver but no speed changes.