- Using an 8TB drive for a Gen2 MyCloud works
- Using virtualbox + system-rescue-cd (live linux) + usb3.0-to-sata HDD adapter for preparing the drive and the wdrecovery-stuff CAN WORK if you power of the drive while still attached to the live-linux WITHOUT giving windows the oppurtunity to f**k up the partitions
Hi there everyone,
i read a couple of threads here on how to replace a drive in a MyCloud or how to unbrick a device, e.g.
- [GUIDE] How To Unbrick your 2TB/3TB/4TB My Cloud
- Rebuild your My Cloud or upgrade the HDD on it
- [GUIDE] Debrick a completely dead MyCloud
- How I replace the HDD of mycloud gen2
So i was confident that my plan (buy an empty case and 8TB wd red, setup the partitions, copy the wdrecovery and fire it up with the current firmware) will work smoothly and could be archieved in a couple of hours. In the end it works but not as easy as i thought. I encountered an error which was not that obvious for me. So i decided to write down my experience, in case others are struggeling with a similar problem and to provide new food for their thoughts.
The methods to setup the harddrive in a Mycloud and get it running with the current firmware (e.g. described in the threads mentioned above), could be summarized like:
- Boot up a Linux system
- Prepare some partitions on the drive following a particular schema, if they’re not present anyways
- Copy the wdrecovery-files (keywords: uImage and uRamdisk) onto a particular partition OR copy a raw-image of Mycloud drive back onto the drive (which includes the software, e.g. see here)
I tested both methods, but i prefered (and in the end i used) the method with the wdrecovery-files, cause it feels more like setting up the device from scratch. Using an image could also be another source of error.
While reading all the threads in the WD community, a couple of times a Google Drive with a lot of information is mentioned and many thanks to user Fox_exe to gather all the information.
- Google Drive MyCloud https://drive.google.com/drive/folders/0B_6OlQ_H0PxVRXF4aFpYS2dzMEE
In the subdir WDMyCloud-Gen2, there is a text file with a full description of the method/commands i followed and the required wdrecovery-files i used.
Hardware i bought and used to setup the Mycloud device:
- An empty MyCloud case (P/N: WDBCTL0060HWT-10 … original 6TB Gen2 using FW=2.xx)
- 8TB WD Red drive (WD80EFZX)
Used OS environment:
While my main machine is running Windows 10 x64, i tried to boot an older laptop with a Live-Linux via USB but this fails. I thought about why not using Linux in a VM. So i used Virtualbox (current sw: 5.2.6-120293-Win) without the guest extensions and a ISO of SystemRescueCd (current version: 5.2.0 x86).
- OS type=Linux; Version=Other Linux (64-bit)
- RAM=1024MB; Virtual hard disk with fixed size of 1GB (not required so could be less)
- USB: enable USB controller; USB 3.0 (xHCI) controller - required so i can use my usb-sata-adapter at the USB3.0 ports of my machine and give the control of the device to the VM (error message: failed to attach the USB device to the virtual machine )
- Attach the ISO to the optical drive, boot-up the VM and select Option #6 (start graphical environment) … wait till GUI is loaded
- Attach the usb-sata-adapter to the VM
- I got the following error and had to activate the USB3.0 controller in the VM settings
Prepare the paritions on the drive:
Find out which device is the drive (e.g via gparted)
Create partitions following the commands in the instruction
Hint: Use the cmd ‘print device’ in parted in terminal to check you selected the correct drive before messing something up
Created partitions in GParted (including swap on sdX1)
Copy wdrecovery-files to sdX3: I used a USB stick to transfer them into the VM (attach USB stick to VM, mkdir and mount device to dir)
Unmount drive from mounting-point and DO NOT DETACH the drive from to VM back to Windows, cause this f***ed up the partitions somehow (maybe when discovering the new drive/partitions) an lead into errorcode=600 later on. I just turned off the power from the usb-sata-adapter
Upload firmware and set up storage
- Attach the curcuitboard back onto the drive, attach network and power cable and fire it up
- Wait some minutes until the mycloud has booted into “Safe Mode” (the blinking LED switchs from blue to red)
- the device will use try to get an IP via DHCP (or if not avaible if think it will use the IP-range of zeroconf) and is accessible via Web-Gui (LED is still blinking red)
- Log onto the Web-Gui and upload current firmware for Gen2 (for me it was My_Cloud_GLCR_2.30.181.bin)
- Wait some minutes till the firmware is uploaded and the device has rebooted
- Reload the Web-Gui to get to the known WD dashboard and start the initial setup process ‘first steps’ (accept license, set password for admin and so on)
- When done with the initial setup, the dashboard asks to set up the RAID Mode for the storage
If you switch to Home it shows that no capacity is available at the moment and the diagnostics says ‘Caution’ but nothing is shown when displayed
Reload Web-Gui to get back to the RAID Mode dialog
- Set up RIAD Mode: Select ‘Switch to JBOD’, press next
- Wait till drive self test is finished, press next
- Check summary, press next
- Understand text, agree re-format with ‘Finish’
- Partitioning, Initializing format of drive … Hard Drive Formatting Failure (Error Code: 600) … f****k -_-
This error occurs if i detach the drive from Linux back to Windows after creating the partitions and shutdown the power of the usb-sata-adapter after ejecting it under windows. This error occurs NOT if i power down the usb-sata-adapter while still attachted to the Linux-VM. It is possible to activate SSH before setting up the RAID stuff, so maybe it would be possible to fix this error via SSH on the device, but i didn’t tried so far.
It seems that pre-formatting all partitions to ext4 (except swap) could avoid the error.
- Wait until volume if formatted (if no error occurs), click close
- Switch to Home tab to check available storage
I hope somebody is getting a clue via this text about what to do and maybe also a little help.
So long …