4/29/2023 0 Comments Sync folders pro exfat![]() ![]() The reader it self can do 60MB/s, the Hard Drive alone can do 80MB/sīut if you simply test the sequential dd command test from SD reader to Hard Drive, it never get over 40MB/s, which shows there is bottleneck somewhere, that’s why I wonder.Īnd by the way I do send support ticket to question about this to WD, and their support desk only sent me WiFi connection speed FAQ which is complete unrelated, then they just tell me to send my unit back for RMA, I did a simple test by ssh into the Pro model, I can’t find any review indicate pro model can do 60MB/s, only SSD version can do that number, many review doesn’t give the number about the backup speed, mostly just repeat the marketing words about 60MB/s Now WD does list the SD read perf on the SSD model as up to 65MB/sec, but the real world difference is likely less than ~5% for most use cases. To back this up, pics of the PCBs and component layout in tear downs of production units look pretty much the same to the naked eye. Also PuDLeZ has mentioned the electronics (ARM SOC, SD card reader, etc) are pretty much the same between the wireless pro and his SSD review unit. And while random write perf for SSDs tend to be much better than HDDs, the random reads even for higher end SD cards still tend to be only ~5 - 12 MB/sec and will be the majority of the bottle neck as writes to HDD will be buffered in the HDD electronics and/or likely even cached by the SOC for write perf reasons.Īs for SD backup in the SSD model - Reviews I’ve seen don’t show SD card backup to be much if any faster. writes via USB3 are closer to 100MB/sec… so the bottle neck is NOT the HDD at least for sequential xfers. (Video, large raw files, etc.) Also this is more of a limitation of the SD Card reader and SOC than the write characteristics of the HDD. Of course this will be dependent on the read speed of your particular SD card(s) and would only apply to the best case scenario of sequential reads of large files. However, after reading a number of reviews going all the way back to the 2TB model, I get the impression the SD card reader in the wireless pro models are capable of backing up data from SD card to internal HDD at close to the advertised ~60MB/sec SD read spec. Makes you wonder if there was a supply chain/manufacturing issue and/or any electronics changes. Unfortunately they have been largely out of stock at the large retailers (Amazon, Best Buy, B&H, Adorama) for up to a month and are just now coming back in stock. I can’t speak from personal experience (yet) as I’ve had a 4tb model on back-order for weeks. The official update script uses this location before it flashes it to the ROM/storage on the board. Sdc1 - fat - holds the bootloader/kernel stuff. All you need to do is format it and the OS will take care of the rest. Sdb2 - ext4 - is use as a log partition of sorts. I believe it doesn’t matter what version is on here so put the newest. My MPWP has MyPassportWirelessGen2_1.01.07.bin while the SSD version had a newer version. Sdb1 - ext4 - a backup firmware image/file. Sda1 - exfat - this is where your data goes and that’s accessible via the MPWP usb connection Format them accordingly, copy of the files, and extract the to the two sdX4 partitions. From there, you can pretend sdX2 is /dev/sdb, sdX3 is /dev/sdc, and sdX4 is /dev/sdd on the MPWP. Once you’ve completed these steps, use ‘losetup’ to get access to the partitions within the partitions. For the 2G partition, the first partition should be +1G with the remaining space going to the 2nd partition. For the two 1G partitions, the first should be +512M with the remaining space going to the second partition. Once you write those changes to the disk, pretend like the second, third, & fourth partitions are a drive themselves (ex: fdisk /dev/sdX2) and make partitions within the partition. ![]() The Fourth partition is the remaining 2G. First partition is the total size of the disk minus 4G for the hidden partitions. Format the drive with MBR partition and all partitions primary. Keeping this high level to hopefully discourage folks that aren’t familiar from attempting to do it…Ĭonnect the drive to your PC outside of the MPWP, like a standard sata to usb adapter. Granted it was an older firmware but I doubt it’s changed. My reasoning behind this is because I was able to manually create the partitions on my Linux box on a HDD and boot from it fine. While I don’t know 100% yet but I think the root cause is that the partitions are not the sizes the firmware is expecting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |