Alternative firmware supporting Apple File Structure APFS

[sebastiaan69]

Hello,
I am new to this forum, but I am coming here after I found out that since macOS 12 Montery my Cloudbox no longer seems to support creating a disk image using APFS structure. When using a Macbook running macOS 10.15 Catalina alternative firmqaeI can still create a disk image using APFS structure and write data to it. But the newer macOS reports an error after creating such a disk image saying: "no mountable file systems". Apparently Apple change something according to APFS which is not being supported bij La Cie Cloudbox running on the latest firmware 2.6.11.0 from 2016-12-29

I would like to ask whether implementing the alternative firmware would solve this issue?

Regards

[Jocko]

Hi

I am sorry but several points must be clarified to understand your question.

The feature is to make TM image on your nas ?

macOS 10.15 Catalina alternative firmware

What is it the alternative firmware ?

Apparently Apple change something according to APFS which is not being supported

AFAIK with the last TM feature, you can not use a same TM image for several hosts. You have to create one for each host

Other point about TM :

my Cloudbox no longer seems to support creating a disk image using APFS structure.

AFAIK, lacie does not set a APFS image on the disk but still use its standard fs on its disk which handles compatibility with APFS. It is not required to have an APFS on your TM image (no doubt about it !)

But the newer macOS reports an error after creating such a disk image saying: "no mountable file systems"

This may occur if the samba version used by LACIE firmware is not patched to fix this bug (https://bugzilla.samba.org/show_bug.cgi?id=13622)
And indeed, our firmware has a clean behaviour with the last change on the TM feature but only for donator people which can use a patched samba version 4.10.18

[sebastiaan69]

Hi,

I'll try to clarify the mentioned points.

There is no intention to make a Time Machine backup on this NAS whatsoever. Main reason is that the Cloudbox is not within my local netwrok, but off site in another building.

I connect to the cloud box directly from the Finder using the commands: 'Connect Server', followed by afp://88.xxx.xxx.xx:5400/Sebastiaan

After that I use the Disk Utility to create a Disk Image in the home directory Sebastiaan on the remote Cloudbox.

See attached image for the settings I use:

$matches[2]

Several options are given for the structure of the Disk Image:

Schermafbeelding 2022-12-12 om 12.11.14.jpg

Previously I always used APFS and it worked fine (running macOS 10.15 Catalina). Although I understand from your reply that the file structure actually used on the Cloudbox may not be APFS at all.
Anyway, Since macOS Big Sur, Montery of Ventura the chosen file structure APFS results in the mentioned error.

From your post I do understand that APFS is not being reflected in the actual file structure used by Cloudbox. What would be the best file structure to use regarding the given options for an encrypted disk image on a remote cloud box ?

[sebastiaan69]

Hi Jocko
Are you able to reflect on the additional information and subsequent questions?
Regards

[Jocko]

Hi

Sorry, I skipped your last message.

According with your capture, I think your MAC creates fs image file on the nas and then should be also the case on our firmware. If you have an old disk even with a small size like 80GB, you can easily test that point by swapping the disk and install fvdw-sl on it. (see: https://plugout.net/viewtopic.php?f=7&t=3086 which will install version 18.1 and follow the additional information to upgrade to version 18.2 which fixes also some issues for MAC users https://plugout.net/viewtopic.php?f=7&t=3532).

There is no intention to make a Time Machine backup on this NAS whatsoever. Main reason is that the Cloudbox is not within my local netwrok, but off site in another building.

By enabling webdav server on the nas and using https protocol over the exchange, you will get also encrypted exchanges see :https://plugout.net/viewtopic.php?f=28&t=3670&p=37717#p37717
Note: To improve webdav performance, you have to allow the web server to use more resource (I can explain this point later : settings are available in the main setup menu : option "Memory size allocated to the Web server" )