Flame storage not mounted

Flame Hardware Questions
1

Hello,

I could really use some help from the tech minded people who know more than I. I have a session tomorrow and my flame doesn’t want to launch.

I launched my flame and all my projects are greyed out. I don’t think it sees the storage as mounted even though I can see it on my desktop and access the drive.

I have a Mac Studio M2 ultra and my flame storage is an OWC Thunderbolt Raid.

Side note: It was working earlier. The only thing that changed is I had to install Lucid which required me to boot up the mac in recovery mode and change some security settings. This does not seem like it should affect my framestore but it was working before i did this so thought I would mention it.

Any help would be greatly appreciated!

2

Are you SURE the external drive is mounted after the reboot? External drives on Macs LOVE to change their actual name under the hood but show you a different name on the desktop. Lemme dig up some forum posts for ya.

1 Like
3

Try dis…

4

Hey Randy. Well i can see it and access files on it but oddly enough after the reboot I did get a notification from backblaze saying it couldn’t back up because of a diff name but the name hasn’t changed on the desktop.

5

The Desktop name doesn’t matter. It’s lying to you. And Backblaze is pissed? Yeah, the name under the hood is different.

In a terminal, type this:

ls -al /Volumes

report back

6

Ignore the one that called Flame_Storage. My framestore is just called storage but you are correct now there is an extra one called storage 1.

Screenshot 2025-01-09 at 8.33.47 PM
Screenshot 2025-01-09 at 8.33.47 PM816×426 26 KB

7

yup. okay, That’s the problem.

So, here’s my disclaimer. Im not there. Im not your sysadmin. Do this at your own risk.

In a terminal, type:

cd /Volumes

sudo mv storage storage_BAK

sudo mv storage\ 1\ storage

And that should fix it.

1 Like
8

So i put in the first sudo command and got this. Is this correct? Keep going?

Screenshot 2025-01-09 at 8.44.58 PM
Screenshot 2025-01-09 at 8.44.58 PM820×429 34 KB

9

Nah ya mistyped it. Don’t worry, you didn’t mess anything up.

the command you typed was missing a word.

Ya gotta do this…

sudo mv storage storage_BAK

10

Ok. Just gonna apologize ahead of time since i think i did something wrong again. And thank you for your patience. The command line is not in my wheelhouse.

Screenshot 2025-01-09 at 8.53.28 PM
Screenshot 2025-01-09 at 8.53.28 PM822×433 44 KB

11

You’re doing fine. What you can do instead is solve this a different way. Backblaze style.

If you want, you can always open a Backblaze support ticket.

https://discussions.apple.com/thread/254908811?sortBy=rank

12

Only problem with that is I have a session in the morning and I’m not sure how long that would take. Thanks for trying though. I appreciate it.

13

Spaces are always baffling. It’s my kryptonite.

You have a duplicate mount point thanks to Backblaze. If terminal commands are foreign, and they always take a bit of fiddling, then you’re best best is to follow this procedure…

https://discussions.apple.com/thread/254908811?sortBy=rank

14

Thanks I’ll take a look.

15

stop backblaze from
autostarting the reboot should also fix it, seems like backblaze is creating that mount before the actual external drive is mounted?

another thing is

  1. stop backblaze
  2. eject external drive
  3. ls -al /Volumes to see if both “storage” and “storage -1” are now gone.
  4. remount external drive
  5. ls -al /Volumes to see if that fixed it
  6. restart backblaze
16

I think you mean

mv ./storage\ 1 ./storage

IE there was an extra \ in Randy’s command after the 1. I put ./ in there to make it clearer (which will still work, just meaning “current directory”

1 Like
17

Autodesk suggested this: ln -s storage\ 1/ storage
So this did fix the issue but now when i look at volumes i have 3: storage_BAK, storage and storage 1

Seems that ln -s created a symlink versus mv renaming it? Would it be better to do it again and use mv?

Thanks again for all the help.

18

I find that ln -s works good. if you mv it, it may just increment again.

For reference [LINK]

1 Like