Probably the most convenient way to upgrade the drive for Linux users :) It works without problem under Debian Stretch/Sid. It's easily possible to extract the firmware update utility from that image, and it's only 2.5mb uncompressed and 1.1mb zip compressed: it's a Linux x86-64 executable and must be run as root. But the MacOS utility in fact contains a bootable Ubuntu Linux drive image and that's why it weighs ~700 mb. However it's represented by either DOS or MacOS utilities. There is a firmware update 01.01A02 for this drive on the official site. ![]() Naturally /home and swap are stored on the HDD as they consist of data that is accessed slowly. Similarly, /var/db/repos/gentoo sees writes on emerge -sync commands. var/tmp is a location that will see many writes on Gentoo due to compiling which can reduce the life of an SSD so it is stored on the HDD. The root file system and boot partitions are stored on the SSD for fast data read speeds. Here partitions 1 and 2 are located on the SSD while partitions 3-6 are on the HDD. Sector size (logical/physical): 512B/512B Welcome to GNU Parted! Type 'help' to view a list of commands. Root # parted -a optimal /dev/sda GNU Parted 2.3 The partitioning scheme after running the installer may look something like this if setup as an MBR drive If your numbers don't differ, just make sure your SSD partitions end with sector number 234441647, and that your HDD partitions begin with 234441648. In my case the exact number of 512-byte SSD sectors was 234441648 and total drive size was 2187966778 sectors. Use the SSD sector count from the previous step as the boundary between your SSD and HDD partitions. NOTE VitaliyFilippov ( talk) 09:51, 11 July 2015 (UTC): Although it's of course stupid to mix SSD and HDD in one partition, I didn't experience any issues when reading/writing across the boundary. This is why the tool available from Western Digital partitions the drive automatically, to protect itself from receiving a read/write command that would cross the boundary. Once the drive is unlocked, it may technically be used on any system or configuration as long as read/write commands do not cross over from the SSD to the HDD. ![]() If you're familiar with disassembly you can try to discover these commands by looking into the official MacOS utility: it contains a small and simple command-line utility called xlba (WD_Black2_Configuration_Utility/WD Black2 Dual Drive Initialize.app/Contents/Resources/xlba in the package) - it's written in C++ and it's relatively easy to disassemble. ![]() In fact WD utility only sends several VSC (Vendor-Specific Commands) to the drive. Confirm that you are able to see 1120GB capacity in the BIOS.Run the WD Black2 installer which can be downloaded from the product page.OR install Microsoft Windows onto the drive from scratch.Use a system that is already running Microsoft Windows and connect drive as a slave.scsi-to-ata translation) and boot into Microsoft Windows Connect the WD Black2 to a system with a free SATA port (impossible through USB cables, even those that support SMART i.e.You will use this number as your SSD-HDD partition boundary. Note that you should better check the drive sector count before enabling HDD, for example by connecting it to a Linux machine and checking dmesg (it will say something like ".If your drive already shows capacity of 1120GB in the BIOS, you may skip this section. Unfortunately, physical access to a machine running Microsoft Windows is required for this step.
0 Comments
Leave a Reply. |