you need a powered adapter. What you have is not going to work.
Thanks for your reply.
So something like this would do the trick?
http://www.amazon.com/Anker%C2%AE-Converter-Adapter-Cable-included/dp/B005B3VO24
Hey, tried the procedure once again with the script at this location File sharing and storage made simple
worked, I go this link from the [GUIDE] How to unbrick a totally dead MBL, which is the same place which I had tried earlier, but it seems the script was updated or it was sheer my luck that it worked as expected this time…
Rob
Script completed but device still stalls with red light just as before
After following guide i have a green light but its clearly not right as its not showing anywhere on network.
This what comes out:
script will use the following disk:
Model: ATA SAMSUNG SP2004C (scsi)
Disk /dev/sda: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
is this REALLY the disk you want? [y] y
********************** IMAGE **********************
********************** IMPLEMENTATION **********************
everything is now prepared!
device: /dev/sda
image_img: rootfs.img
destroy: true
this is the point of no return, continue? [y] y
dd: error writing ‘/dev/sda1’: No space left on device
10+0 records in
9+0 records out
10395648 bytes (10 MB) copied, 0.00757493 s, 1.4 GB/s
dd: error writing ‘/dev/sda2’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00156103 s, 0.0 kB/s
dd: error writing ‘/dev/sda3’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000588233 s, 0.0 kB/s
dd: error writing ‘/dev/sda4’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000601259 s, 0.0 kB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
(parted) mkpart primary 528M 2576M
(parted) mkpart primary 2576M 4624M
(parted) mkpart primary 16M 528M
(parted) mkpart primary 4624M -1M
(parted) set 1 raid on
(parted) set 2 raid on
(parted) quit
Information: You may need to update /etc/fstab.
Warning: blocksize 65536 not usable on most systems.
mke2fs 1.42.13 (17-May-2015)
mkfs.ext4: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
destroying was done, would you like to continue with installation? [y] y
mdadm: /dev/sda1 is not a block device
mdadm: Cannot find /dev/md0: No such file or directory
mke2fs 1.42.13 (17-May-2015)
The file /dev/md0 does not exist and no size was specified.
mdadm: error opening /dev/md0: No such file or directory
synchronize raid... mdadm: Cannot find /dev/md0: No such file or directory
done
copying image to disk...
dd: writing to ‘/dev/md0’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00200309 s, 0.0 kB/s
mount: /dev/md0 is not a block device (maybe try `-o loop'?)
cp: cannot stat ‘/mnt/md0/usr/local/share/bootmd0.scr’: No such file or directory
./debrick.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: No such file or directory
umount: /mnt/md0: not mounted
mdadm: /dev/md0 does not appear to be an md device
BLKGETSIZE: Inappropriate ioctl for device
BLKGETSIZE: Inappropriate ioctl for device
all done! device should be debricked!
Excelente hermano, muchas gracias, recupere mi MBL que tenía en el baul de los recuerdos desde el 2012 cuando dejó de funcionar.
[Rough translation - Trancer]
“This is excellent brother, thank you very much, I was able to recover my MBL which was in a safe ever since it stopped working in 2012”.
@nfodiz does this guide work correctly for a MBL 2TB? Our drive has recently bricked itself and the light was solid blue and flashing red. I have attempted to follow a guide that said to use mdadm to build the raid and mount it in Linux as well as using fsck to repair any errors. It stated the the raid was created but I was unable to mount it and I was only able to use fsck for the data partition which showed little errors.
I would like to keep the data so was hoping this guide will work as the only other one that seems like it will work will take days to download the replacement raid partitions.
Cheers
James
Works fine with any size of MBL
I’m in the middle of running the script and at the read-only check I and getting errors. Is it possible to interups the script and force a disk check and fix the errors before proceeding. I’m sure the drive is fine and it’s just a messed up OS.
I tried rerunning the script and it passes the test stage but is now erroring straight after. Might need a third run to get through.
@nfodiz any input with your experience as to what I could try would be much appreciated.
Worked perfect for me on a MBL 2TB with fixed white led after a failed firmware upgrade, without touchind the data partition.
For de data Bakcup I´ve found R-Linux more reliable, since Linux Reader didn´t do all the job. Anyway, i could access all data after running the script.
Thanks a lot for the great Work
Unfortunately the MyBookLive 2TB has a constant blue light after going thru this steps.
Have changed the defective 2TB Sata with a 3TB Sata, both are green ones from WD.
The device cannot be reached thru the network.
Anything i could do to figure out what’s going on?
HI to all
After some time i decided to follow this and try it.
so i have tried 4 times, the last one i destroy the data and no success again.
so i save the logs to post and try to get help.
Will appreciate all the help to put ut working
cheers
info:
blue led
no rj45 lights
was like this before troubleshooting.
[quote=“RUBEN_MARQUES, post:533, topic:56658, full:true”]
HI to all
After some time i decided to follow this and try it.
so i have tried 4 times, the last one i destroy the data and no success again.
so i save the logs to post and try to get help.
Will appreciate all the help to put ut working
cheers
root@sysresccd /root % mkdir /mnt/usb
root@sysresccd /root % mount -t vfat /dev/sdb1 /mnt/usb
root@sysresccd /root % cd /mnt/usb
root@sysresccd /mnt/usb % mdad, -S /dev/md0
zsh: correct ‘mdad,’ to ‘mdadm’ [nyae]? y
mdadm: stopped /dev/md0
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sd
unknown argument: /dev/sd
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sda destroy
********************** DISK **********************
script will use the following disk:
Model: ATA WDC WD20EURS-63S (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
3 15.7MB 528MB 513MB primary msftdata
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
4 4624MB 2000GB 1996GB ext4 primary msftdata
is this REALLY the disk you want? [y] y
********************** IMAGE **********************
********************** IMPLEMENTATION **********************
everything is now prepared!
device: /dev/sda
image_img: rootfs.img
destroy: true
this is the point of no return, continue? [y] y
32+0 records in
32+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.337337 s, 99.5 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.373534 s, 89.8 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.372427 s, 90.1 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.397019 s, 84.5 MB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) mklabel gpt
(parted) mkpart primary 528M 2576M
(parted) mkpart primary 2576M 4624M
(parted) mkpart primary 16M 528M
(parted) mkpart primary 4624M -1M
(parted) set 1 raid on
(parted) set 2 raid on
(parted) quit
Information: You may need to update /etc/fstab.
Warning: blocksize 65536 not usable on most systems.
mke2fs 1.43.3 (04-Sep-2016)
mkfs.ext4: 65536-byte blocks too big for system (max 4096)
Proceed anyway? (y,n) y
Warning: 65536-byte blocks too big for system (max 4096), forced to continue
Creating filesystem with 30453088 64k blocks and 30355200 inodes
Filesystem UUID: 0656e2e5-08de-4169-9450-0597bfd77708
Superblock backups stored on blocks:
65528, 196584, 327640, 458696, 589752, 1638200, 1769256, 3210872,
5307768, 8191000, 15923304, 22476104
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): y
done
Writing superblocks and filesystem accounting information: done
destroying was done, would you like to continue with installation? [y]
mdadm: size set to 1999808K
mdadm: array /dev/md0 started.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 499952 4k blocks and 125184 inodes
Filesystem UUID: 33aaa994-28b9-48c6-99c4-2aaa8e461ed2
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Checking for bad blocks (read-only test): 0.00% done, 0:00 elapsed. (0/0/0 errdone
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
mdadm: added /dev/sda2
synchronize raid… done
copying image to disk…
3999616+0 records in
3999616+0 records out
2047803392 bytes (2.0 GB, 1.9 GiB) copied, 151.063 s, 13.6 MB/s
mdadm: stopped /dev/md0
all done! device should be debricked!
root@sysresccd /mnt/usb %
root@sysresccd /mnt/usb %
[/quote]
Hi if I just want to pull out my data from my My Book Live and do not wish for debrick.
Am I right to say I should just follow step 1 and 2?
I’m not able to install the OS to a new hard drive to MyBookLive 1TB. My old WD drive has so many bad sectors that I decided to buy a new hard drive. I bought a WD Red 1TB, but I can’t get MBL to boot. I have tried:
- Using the V2 instructions to install the image
- Using the V1 instructions with debrick V1 and V2 scripts
- I’ve tried using with and without destroy command
- Using a firmware version 1 and 2
I’m using a USB2.0 SATA hard drive dock and SystemRescueCd on a USB stick. I don’t seem to get any particular errors during the installation process. Everything completes to my eye as they should.
When I hook the new drive to MBL a put the power on, MBL shows immediately only a solid blue led. This doesn’t change or blink. It seems as if the device doesn’t boot the OS. I get green blinking in the network connector, but the router doesn’t recognize the device.
Any help on what could be the problem or what I should try next?
nofodiz,
I have a 3TB My Book Live NAS drive that has a physically bad HD. I purchased a new HD and tried to follow this procedure without success. I have tried a couple times and decided to ask for help. I am including a print of the command line output as well as a print of the gparted information at the end of the run. I am using the apnc-021109-053-20120413 version of the disk image and started with an unallocated disk.
MODIFIED: I had not seen information on Version II of this procedure. I was able to use it and successfully setup the drive. Thank you and I hope I didn’t waste any of your time.
root@sysresccd /root % mkdir /mnt/usb
root@sysresccd /root % mount -t vfat /dev/sdb1 /mnt/usb
root@sysresccd /root % cd /mnt/usb
root@sysresccd /mnt/usb % mdadm -S /dev/md0
mdadm: stopped /dev/md0
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sda destroy
********************** DISK **********************
script will use the following disk:
Model: ATA ST3000DM001-1ER1 (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
is this REALLY the disk you want? [y] y
********************** IMAGE **********************
********************** IMPLEMENTATION **********************
everything is now prepared!
device: /dev/sda
image_img: rootfs.img
destroy: true
this is the point of no return, continue? [y] y
dd: error writing ‘/dev/sda1’: No space left on device
10+0 records in
9+0 records out
10391552 bytes (10 MB, 9.9 MiB) copied, 0.0111794 s, 930 MB/s
dd: error writing ‘/dev/sda2’: No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0.000826888 s, 0.0 kB/s
dd: error writing ‘/dev/sda3’: No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0.000744732 s, 0.0 kB/s
dd: error writing ‘/dev/sda4’: No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0.000771238 s, 0.0 kB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) mklabel gpt
(parted) mkpart primary 528M 2576M
(parted) mkpart primary 2576M 4624M
(parted) mkpart primary 16M 528M
(parted) mkpart primary 4624M -1M
(parted) set 1 raid on
(parted) set 2 raid on
(parted) quit
Information: You may need to update /etc/fstab.
Warning: blocksize 65536 not usable on most systems.
mke2fs 1.43.3 (04-Sep-2016)
mkfs.ext4: Device size reported to be zero. Invalid partition specified, or
partition table wasn’t reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
destroying was done, would you like to continue with installation? [y] y
mdadm: /dev/sda1 is not a block device
mdadm: Cannot find /dev/md0: No such file or directory
mke2fs 1.43.3 (04-Sep-2016)
The file /dev/md0 does not exist and no size was specified.
mdadm: error opening /dev/md0: No such file or directory
synchronize raid… mdadm: Cannot find /dev/md0: No such file or directory
done
copying image to disk…
dd: writing to ‘/dev/md0’: No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0.00211356 s, 0.0 kB/s
mount: /dev/md0 is not a block device (maybe try `-o loop’?)
cp: cannot stat ‘/mnt/md0/usr/local/share/bootmd0.scr’: No such file or directory
./debrick.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: No such file or directory
umount: /mnt/md0: not mounted
mdadm: /dev/md0 does not appear to be an md device
BLKGETSIZE: Inappropriate ioctl for device
BLKGETSIZE: Inappropriate ioctl for device
all done! device should be debricked!
Partition Name File System Size Used Unused Flags
unallocated !primary unknown 15.00 MiB — —
/dev/sda3 !primary unknown 1.91 GiB — —
/dev/sda1 !primary unknown 1.91 GiB — — raid
/dev/sda2 !primary unknown 1.91 GiB — — raid
/dev/sda4 !primary unknown 2.72 TiB — —
I appreciate anything you can tell me.
Hi everybody! hope this topic stays alive…
Let me share my story with you guys so maybe you can help me. First time in YEARS that I’ve never had problems with this drive (a 2TB MBL) using just the Public to save all my files and some twonky and reads from smb (wd tv live)
the firmware was the original, 1.0 version.
I’ve taken notice that I was lakin of backup here so read some more and found SAFEPOINTS but as you probably know, safepoints were not abailable on 1.0 soft, just starting at 2.0 (at least that was WD Customer Service told me) so I started to update my firmware.
Get to the last 1.xxx version ok until one time before updating for first version of 2.xxx the notice said that “will recomend to backup all your data before proceed”
Decided to NOGO that time and let everything untouched because I’d to get another 2TB drive to copy my files.
Well, I get the other drive (usb one) but in the meantime… power cut and the MBL never came back. disc spinning no leds in front (because burn out several years ago) but no IP aquired.
So I managed to follow this guide, the one that keeps your data untouched. Before I made a backup (took several days using Windows Linux Reader)
And today I installed, by my cal, the same firwmare that I have, just because also Customer Care recommended me to update one by one, not to just install the latest… (???)
Well I have to say that GPARTED told me something about my “GPT Partition backup bad, but the primary is ok so will going to use that”
Someone knows what that means? I decided to run the script anyway and well it worked! at least for a few minutes.
I get the fresh dashboard, configured some thigs like the Workgroup, etc
then passing some more minutes I saw Twonky on my cell, but lost the dashboard again, then lost the shares, then get back the shares I tried to copy one file and took 5 minutes to move 1mb.
So I decided to wait, then when Dashboard goes back online I turned off the MBL, well, it never started again… So Im gonna debrick it again with another firmware I guess.
But can someone tell me something about that Linux error?
Or I just have to plug it and let it there an hour or two to get this thing back alive?
Thanks guys!!!
Ok just in case someone still navigating this, I’ve succesfully debricked and now after several reboots got a working drive (empty one) using the V2 of this guide.
Nodfz, you’re awesome man!!! thank you very much, I indeed learned a lot of linux this past days hehe.
I have still troubles here to get the MBL working again. Using a 1TB HDD hooked up to my ubuntu server with a SATA/USB cable.
The data of the HDD is:
Model: WDC WD30 EZRX-00DC0B0 (scsi)
Disk /dev/sdh: 802GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
3 15,7MB 528MB 513MB primary
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
4 4624MB 802GB 797GB ext4 primary
I executed the debrick script v2.0.
So after the disk dump command I get this output:
root@Shuttle:~# dd if=/mnt/usb/mybook.img of=/dev/sdh bs=1M
4420+0 records in
4420+0 records out
4634705920 bytes (4,6 GB, 4,3 GiB) copied, 309,275 s, 15,0 MB/s
root@Shuttle:~#
Than I connected MBL to my LAN and booted the MBL
After that, I can not access the UI to do a quick factory reset to format the (data) partition. The MBL shows 1st a blue light followed by a steady RED light and is not traceable (arp).
I assume after the dd command the MBL will get an IP by DHCP since my LAN is in the 192.168.2.x range.
What can I do to get the MBL working again?
Dear all,
I’ve done all the procedure and I’ve “unbricked” my MBL, but when I put it back in the enclosure LED light is stucked on blue. What can I do? I’ve tried the first procedure then the second one. I’ve tried different firmware, still the same problem. Could you help me?
Thanks
