[GUIDE] Debrick a MyBookLive DUO - Cloud Storage / My Book Live Duo - WD Community
Posted: Monday, August 7, 2017 by Tyler Durden in
0
[GUIDE] Debrick a MyBookLive DUO - Cloud Storage / My Book Live Duo - WD Community
https://community.wd.com/t/4tb-to-12tb-hdd-capacity-upgrade/87865/15
THANKS TO ALL THE USERS IN THIS THREAD FOR THEIR FEEDBACK!
THIS GUIDE IS PRETTY SOLID NOW BUT PLEASE KEEP THE FEEDBACK COMING
GUIDE 1 WILL NOT DELETE YOUR DATA
PLEASE SEE STEP 1 FOR HELP WITH BACKING UP YOUR DATA TO BE SAFE
Myself and fusecat have been working together the last few days and have finally been able to debrick a MBL DUO with a modified debrick script provided by michealcell at the mybookworldwiki forums based on the original script by dan kvelstad
I will try my best to support this guide but without access to a MBLDUO it is hard
I will be more than happy to make changes to the guide based on user feedback
GUIDE 1 is confirmed working by MKranjc if you are running a RAID1 array
GUIDE 1 is also confirmed working by djkenzo982 if you are running Spanning
The drive will rebuild the RAID1 array when you boot up your MBLD after the debrick
This process can take 15+hours for RAID1
This process takes about 10 minutes for Spanning
Check Storage Settings in your dashboard to get a % complete on the array build
GUIDE 2 is confirmed working by fusecat but WILL DELETE YOUR DATA
This is the guide you want to follow if you are putting new drives in the enclosure
You can also follow this guide if you have all of your data backed up to another drive and want to start fresh
GUIDE 3 Herokolco has also put together a guide to install 2 new drives into the MBLD enclosure
As always you use this guide at your own risk... Any loss of data or damage to your drive is YOUR responsibility
If you run into any issues with the script, see this post by djkenzo982
POWER DOWN THE MBLD AND PULL DRIVE A OUT OF THE NAS
GUIDE 1
This guide is for people looking to keep their existing data
Your DataVolume will rebuild at boot (Spanning or RAID1)
Please follow step 1 and backup your current data so it is safe
STEP 1 (DATA BACKUP/RECOVERY)
At this point if you would like to pull your data off the MyBookLive Duo for safe keeping, download Disk Internals Linux Reader for Windows 660http://www.diskinternals.com/linux-reader/660 and install the program. Hook up the drive to your computer or a SATA dock and copy your data to another drive with enough space on your computer.
If that doesn't work try using R-Linux 395http://www.r-tt.com/free_linux_recovery/Download.shtml395
At this point if you would like to pull your data off the MyBookLive Duo for safe keeping, download Disk Internals Linux Reader for Windows 660http://www.diskinternals.com/linux-reader/660 and install the program. Hook up the drive to your computer or a SATA dock and copy your data to another drive with enough space on your computer.
If that doesn't work try using R-Linux 395http://www.r-tt.com/free_linux_recovery/Download.shtml395
djkenzo982 wrote "Backing up with Linux Reader and R-linux doesn't seem to work if your RAID0 is busted as much as mine was. I tried an mdadm create/assemble to try and get the data but it didn't work."
Both programs are free and have been proven to work
STEP 2 (DEBRICK PREPARATION)
Download 7zip from http://www.7-zip.org/download.html415
Download SystemRescueCd from http://www.sysresccd.org/Download698
Download SystemRescueCd from http://www.sysresccd.org/Download698
Download the debrick script from 983http://www.mediafire.com/download.php?sy3mf53i0vcy886983
Download the latest MyBookLive DUO firmware from 925http://download.wdc.com/nas/ap2nc-024006-048-20121206.zip925
Unzip ap2nc-024006-048-20121206.zip and you should end up with ap2nc-024006-048-20121206.deb
Install 7zip and point it to your MyBookLive DUO firmware "ap2nc-024006-048-20121206.deb" and double click and you will see "data.tar" where you will again double click and be presented with a "." Double click the "." then double click "cache volume" then double click "upgrade" and then highlight "rootfs.img" and hit extract.
Next burn the SystemRescueCd ISO to a blank CD
Use 7zip or WinRAR to extract the debricking script "debrick.sh" from the "debrick_mbld.zip" file you downloaded above
Format your thumbdrive to FAT32 (4GB or larger)
Copy "debrick.sh" and "rootfs.img" to your thumbdrive
Use 7zip or WinRAR to extract the debricking script "debrick.sh" from the "debrick_mbld.zip" file you downloaded above
Format your thumbdrive to FAT32 (4GB or larger)
Copy "debrick.sh" and "rootfs.img" to your thumbdrive
STEP 3 (PREPARING TO BOOT THE SYSTEM RESCUE CD)
Make sure your thumbdrive containing the two files is plugged in, your MyBookLive hard drive is hooked up to your computer via e-sata to sata or sata to sata cable and you disconnect any other hard drives to ensure you don't accidentally delete data on those drives
STEP 4 (BOOTING THE SYSTEM RESCUE CD AND DEBRICKING THE HARD DRIVE)
Now we want to boot off the SystemRescue CD you burned above. When the system menu comes up select to "directly start the graphical environment"
Once you get to the desktop, open gparted and check to see where your MyBookLive shows under. In my case it shows up under /dev/sda
The drive should contain several EXT3 partitions and a rather large EXT4 partition
If your drive shows up under sdb, sdc, sdd etc. just substitute the proper name for the drive when getting to
./debrick.sh rootfs.img /dev/sda
Now in gparted check to see where your thumbdrive shows up. In my case it shows up under /dev/sdb1
If it shows up under sdc1, sdd1, sde1, etc. just substitute the proper name for the drive when getting to
mount -t vfat /dev/sdb1 /mnt/usb
Terminal should already be opened on the screen, if not open terminal and type the following commands.
Bold text indicates that you should use the changes from above for that particular part of the command if your devices show up under gparted differently than they did for me...
Once you get to the desktop, open gparted and check to see where your MyBookLive shows under. In my case it shows up under /dev/sda
The drive should contain several EXT3 partitions and a rather large EXT4 partition
If your drive shows up under sdb, sdc, sdd etc. just substitute the proper name for the drive when getting to
./debrick.sh rootfs.img /dev/sda
Now in gparted check to see where your thumbdrive shows up. In my case it shows up under /dev/sdb1
If it shows up under sdc1, sdd1, sde1, etc. just substitute the proper name for the drive when getting to
mount -t vfat /dev/sdb1 /mnt/usb
Terminal should already be opened on the screen, if not open terminal and type the following commands.
Bold text indicates that you should use the changes from above for that particular part of the command if your devices show up under gparted differently than they did for me...
STEP 5 (DEBRICKING DISK A)
Open Terminal and type
mkdir /mnt/usb
mount -t vfat /dev/sdb1 /mnt/usb
cd /mnt/usb
mdadm -S /dev/md0
mdadm -S /dev/md2
mdadm -S /dev/md3
./debrick.sh rootfs.img /dev/sda
Now shut down the System Rescue CD and unplug the debricked hard drive
Now drop Drive A back in the enclosure and power up
Your drive should start rebuilding the Span or RAID1 array automatically (RAID1 can take a long time to complete)
Check Storage Settings in your dashboard to get a % complete on the array build
Once completed, a reboot should get both drives to display GOOD in the MBLD dashboard
If you get a smart fail error message in the dashboard then run these commands to fix it AFTER the array is done rebuilding.
smartctl -s on /dev/sda
smartctl -s on /dev/sdb
reboot
When your drive is in a state that everything above have been done you have a solid green LED:
Re-create your users from the MBLD Dashboard (Thanks MKranjc and dj_kenzo982)
If your shares are still listed in the MyBookLive dashboard but are not accessible, rename the shares and then rename them back to get them linked properly again. Example: Movies > Movies1 > Movies
If your shares are missing in the MBLD dashboard, recreate them in the dashboard and you will be able to access your data again.
If your shares are missing in the MBLD dashboard, recreate them in the dashboard and you will be able to access your data again.
A reboot is required to get the share and drive usage totals to reflect the actual data usage after these changes
Done
______________________________________________________________________________________________________
GUIDE 2
This section of the guide is for folks who want to start fresh or want to install 2 new drives in the MBLD enclosure
This WILL DELETE all data on your disks
Follow steps 1-4 above
STEP 5 (DEBRICKING DISK A AND B)
This step needs to be done one drive at a time
1st debrick disk A with the commands shown below (Remember the drives in bold may differ so refer to step 4 in Guide1)
When it's done, shut down the System Rescue CD and disconnect the drive and set it aside
mkdir /mnt/usb
mount -t vfat /dev/sdb1 /mnt/usb
cd /mnt/usb
mdadm -S /dev/md0
mdadm -S /dev/md2
mdadm -S /dev/md3
./debrick.sh rootfs.img /dev/sda destroy
Hook up disk B and again boot up the System Rescue CD
Again run the commands below (Remember the drives in bold may differ so refer to step 4 in Guide1)
mkdir /mnt/usb
mount -t vfat /dev/sdb1 /mnt/usb
cd /mnt/usb
mdadm -S /dev/md0
mdadm -S /dev/md2
mdadm -S /dev/md3
./debrick.sh rootfs.img /dev/sda destroy
Once the script finishes, shut down the System Rescue Cd
Remove disk B and drop both disk A and B back into the enclosure and power on the NAS
Once the MBLD has booted up go to the dashboard and do a quick factory restore
Now we need to SSH back into the drive to setup your swap partition (Thanks for testing this fusecat)
mkswap /dev/md2
reboot
If this command complains that /dev/md2 is missing you will need to create the array manually through SSH
mdadm --create -e 0 --verbose /dev/md2 --level=raid1 --raid-devices=2 /dev/sda3 /dev/sdb3reboot
After the drive has fully rebooted try the following command again
mkswap /dev/md2
reboot
Once the MBLD reboots, SSH back into the drive and check to make sure your swap is active
swapon -s
It should look something like this
Filename Type Size Used Priority
/dev/md2 partition 500544 896 -1
If you get a smart fail error message in the dashboard then run these commands to fix it
smartctl -s on /dev/sda
smartctl -s on /dev/sdb
reboot
Done!
Thanks to dan kvelstad and michealcell for the script
Without their hard work and testing, none of this would have been possible