I just stumbled onto this thread. I have a MBLD that died some time back. I replaced it with a Snyology NAS. I would like to try and get the MBLD back up and running. I have some questions:
Before I invest in replacement drives I would like to follow the guides with some drives that I have laying around. I have a 200gig and a 250gig. Is there a size limit on the MBLD - i.e. can I use 2 small drives or do they need to be 1T and above? Can I use 2 drives of different size. If I can get the WDLD to boot I would redo the process with 2 3T drives.
I run Windows 7. I understand the process of booting into Linux via the sysreccd boot disk. In guide 2 it states:
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
Do I reboot my system and run dashboard from Win 7?’
SSH - where do I run SSH from - Win7? Linux? I am not familiar with SSH. Where do I get it?
I’m sure that I’ll have more questions as I go along but this will at least get me started. Thanks to everyone who have contributed to this thread. Hopefully I can get the WDLD running again.
There is no limitation on size (at least low drivers) to use on the MBLD.
The only ‘’ issue’’ is that the WD system will not recognize the total size of the small drives.
I have here
1 x 160gb
1 x 500gb
The system see the total as 650gb but shows 1tb on disk section but work 100% ok.
The process is simple.
You should boot with linux!
run the process of debrick on linux!
repeat the priocess with 2 drives, it will not work wiht just one drive fixes!
the ssh are after run the hole process, you should conect the MBLD on sabe router that will give the IP via DHCP to the MBLD, find this IP and access it on ssh like:
OK - my first attempt seems to be a failure. Light on MBLD stays yellow so it never completes the boot. I amy trying to set up with a 200 gig and a 250 gig. I,m attaching the drives using a usb to sata adapter. GParted sees the MBLD and thumb drives fine.]
Problem I had following guide 2 was with the commands
mdadm- S /dev/md0
mdadm -S /dev/md2
mdadm -S /dev/md3
md0 seems to be created but I get error messages on md2 amd md3 and they are not created
When I run the script it runs the destroy fine but seems to have trouble writing to the disk. It has trouble finding md0 md2 amd md3
My MBLD 8TB (RAID 1) just refused to boot up after a power reset. It stays on yellow light even after 20 minutes.
I followed the step from 1 to 4, I found that gparted report the GPT is damaged for both HDD A and B.
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
But if I use Ext2FSD on Windows 7, I can mount the data partition and backup all my data.
My question is:
If I follow GUIDE 2, will it recreate the partitions and GPT ?
I’ve followed Guide 2 and have a USB stick with the software loaded in the PC. GParted shows the USB drive and the MLD drive I’m trying to rebuild. The cd /mnt/usb runs without an error. I get the reeor messages when I run the mdadm for md2 and md3. Then when I run the last line (“./ debrick.sh rootfs.img /dev/sda destroy” ) I get the error message that it can’t find debrick.sh. I replace the sda with whatever GPartwd shows
I’ve followed Guide 2 and have a USB stick with the software loaded in the PC. GParted shows the USB drive and the MLD drive I’m trying to rebuild. The cd /mnt/usb runs without an error. I get the reeor messages when I run the mdadm for md2 and md3. Then when I run the last line (“./ debrick.sh rootfs.img /dev/sda destroy” ) I get the error message that it can’t find debrick.sh. I replace the sda with whatever GPartwd shows
You can as long as it is drive “A”. Drive “A” contains the firmware (OS). You can upgrade the drives to larger ones, but have to do it in stages. You replace drive “B” and have it mirror drive “A” and then you can swap drive “b” in drive “a” slot and then upgrade the empty drive “b” slot with a larger drive. WD doesn’t clearly explain that the firmware resides on drive “a” and to upgrade you have basically copy it over.
You can as long as it is drive “A”. Drive “A” contains the firmware (OS). You can upgrade the drives to larger ones, but have to do it in stages. You replace drive “B” and have it mirror drive “A” and then you can swap drive “b” in drive “a” slot and then upgrade the empty drive “b” slot with a larger drive. WD doesn’t clearly explain that the firmware resides on drive “a” and to upgrade you have basically copy it over.
Does the firmware check for the drive type ? e.g. WD green ?