Cloud Pod Troubleshooting

Hi everyone,

I am experiencing a series of issues with the BM Cloud Pod.
The issues started to appear when I updated to the latest firmware (1.02)
I have two SSD drives (formatted in ExFat) attached to the Cloud Pod, and I never had any problem before the firmware upgrade, I was able to access the drives in my private (1G) network at more than acceptable speed.

After the update, the unit started to act weird: after a few minutes the red light turns on (steady) and the files suddenly disappear from Finder (or it says that I have privilege issues and I can't access the files). The weird thing is that this seems to happen only with this pair of drives. If I use a different SSD (MacOs or Ex Fat) the unit seems to operate normally.
The drives are 100% operational and error-free.
It almost seems that the unit has planted some sort of config issue in the SSDs and I now can't connect them to the Pod anymore, even though they perfectly work if I connected them via USB to my laptop.

Thanks and I really appreciate any help.

Hi everyone,

I think I was able to identify the cause of the problem:
When I perform certain operations on the drive, like zipping files or unzipping, and especially when I save a file from the Chrome browser to the Cloud Pod it seems to generate an error on the disk that makes the whole unit nonfunctional (the light becomes steady red and the only way to make the pod work again is by unplugging the power cord and then plug it again).

After the error, even after resetting the unit, as soon as I try to access the file that I saved from Chrome, the Pod immediately halts again.

I was able to make the unit operational again by removing the drive and performing a disk error check that gave me the following results:

Checking file system and repairing if necessary and if possible.

Volume was successfully unmounted.

Performing fsck_exfat -y -x /dev/rdisk4s1

Checking volume.

Checking main boot region.

Checking system files.

Volume name is DL_WORK2.

Checking upper case translation table.

Checking file system hierarchy.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Found an unexpected secondary directory entry in %1$@.

Directory /OPEN_PROJECTS/are_architects_good_math/2_Assets/updated contains a duplicate name (._Plan01.pdf).

Checking active bitmap.

The bitmap needs to be repaired.

Rechecking main boot region.

Rechecking alternate boot region.

The volume DL_WORK2 was repaired successfully.

File system check exit code is 0.

Restoring the original state found as mounted.



Operation successful.





———————





Running First Aid on “DL_WORK2” (disk4s1)



Checking file system and repairing if necessary and if possible.

Volume was successfully unmounted.

Performing fsck_exfat -y -x /dev/rdisk4s1

Checking volume.

Checking main boot region.

Checking system files.

Volume name is DL_WORK2.

Checking upper case translation table.

Checking file system hierarchy.

Directory /OPEN_PROJECTS/are_architects_good_math/2_Assets/updated contains a duplicate name (._Plan02.pdf).

Checking active bitmap.

The bitmap needs to be repaired.

Rechecking main boot region.

Rechecking alternate boot region.

The volume DL_WORK2 was repaired successfully.

File system check exit code is 0.

Restoring the original state found as mounted.




Operation successful.



_____________________________________





After the scan, I plugged the unit into the pod again and for now, it seems stable, as long as I don't try to save files from the Chrome browser otherwise I will have to repeat the disk check again.



The SSD drive perfectly works as a regular USB drive and it doesn't have any hardware issues, including saving files from chrome.


More info regarding my system:
ExFat formatted. I am using MacOs Monetery on a Mac Book Pro M1
The SSD drive is Samsung T5 - 1 TB
Connected to a 1G ethernet switch.

Hope that helps!

Thanks for posting the solution. I seemed to be experiencing the same problem. In my case, I was trying to download recordings from Zoom in Chrome and I was getting an error that file names couldn't be longer than 31 characters.

I was able to save to the SSD when it was plugged directly into my machine, but not when it was plugged into the Cloud Pod.

Once the initial error occurred, I couldn't navigate to that folder without locking the Cloud Pod with the solid red light.

I also had "bitmap needs to be repaired" and now I seem to be able to access those files just fine.

Thanks again.

Hi, just FYI I've been in constant communication with the support team and they were able to identify and reproduce the problem, so it is officially a bug on the Cloud Pod. It will be addressed in the next iteration of the firmware.

For now, the solution to the problem seems to avoid saving files from Google Chrome and zipping/unzipping operations on the Cloud Pod.

Chrome temporarily renames the files during the download process. It adds a double extension (nameoffile.extension.crdownload) that is probably causing the error.

If you download the files from Chrome to any other device and then transfer the files from there you will not encounter any problems.