#Blackmagic design multidock 10g Pc#
#Blackmagic design multidock 10g windows#

Apple (the idiots) began reporting sizes in K = 1000 bytes for some apps and K = 1024 for others. Now that’s ambiguous unless you know the number of bytes in a K: traditionally K always meant 1024 bytes, but years ago beginning with disk manufacturers they decided their disk would look larger if they used K to be 1000 bytes. The one set of sizes all show the size in bytes so that’s very clear the other set shows the file sizes in KB. That might also account for the file size differences in the previous posts, but there’s one other possibility.

#Blackmagic design multidock 10g windows#

It’s possible Windows is formatting with a small allocation block perhaps 4KB but we know BMD uses 128KB allocation blocks in all their cameras. Formatting in Windows versus formatting in the UMP12K is just creating a larger directory structure. I don’t think you have a problem any more with the SSD in the camera. I hope this explains how I got to where this thread is now, and more importantly answers your question.įantastic solution you found to salvage the data!!! The only weird thing was the size of the files when I looked at them from an FTP connection. The when I placed in on the POD, it saw the filesystem, saw the files and allowed me to pull them off. When I connected it to the VA, it could see the disk was attached, but everything was weird, and the files could not be found. When I placed the SSD back on the 12K, the 12K could see and play the files without an issue. My initial post shows what happens when I run the diskmgmt program since the SSD did not show up in the explorer. If you can't get a disk to show in the explorer, you use 'diskmgmt.msc' to get a low level view of the devices attached to the computer. With a Windows box you connect to the thunderport/USB-C port and use a 'file explorer' to access the files. Not sure what you mean 'directly into the motherboard'. Well.what happens when you connect the SSD directly to a usb-c port on the motherboard?.

UnixMover wrote: I connected the SSD to the secondary USB-C connection since I connected the first to the BM MultiDock 10G (which was supposed to read 'any SSD'). This could be from allocation sizes, but why would BM change the allocation size? I compared the information in the FTP session with a Windows mounted file share. Now before I finish this post, I looked at the files in an FTP session. The only silver lining I can see is that I can pull the files off the POD at 415MB/s. Once I have the files safely off the SSD, I'll test what is what is what and where I must format the disk to make it readable by a PC.

#Blackmagic design multidock 10g Pc#

When I looked at the SSD from 'diskmgmt.msc' the PC still sees the disk as these independent filesystems however, Blackmagic (POD) sees the filesystem and can access the video files. I mounted the SMB/CIFS share from the POD and used the Windows machine to move the files onto the PC. BTW: I connected the SSD to the secondary USB-C connection since I connected the first to the BM MultiDock 10G (which was supposed to read 'any SSD'). I attached the Extreme SSD to a Cloud POD, and it showed all the video files on the disk. Well, you won't believe it, but I finally accessed the data on the card. I’d suggest reinstalling the bmOS for the UMP12K camera and hope you can then reformat the SSD correctly in exFAT as one 4TB partition. We have never seen anything so weird reported on the BMD Forum.