[GUIDE] How to unbrick a totally dead MBL

WD Legacy Products My Book Live
41

Can you paste the entire script output here?

42

nfodiz wrote:

Can you paste the entire script output here?

Also most as at new28006, exactly

43

OK, I’m putting something else together now that might work. Give me an hour…

Do you have an 8GB or larger thumbdrive or external hard drive?

44

nfodiz wrote:

OK, I’m putting something else together now that might work. Give me an hour…

Do you have an 8GB or larger thumbdrive or external hard drive?

Yes, I have 8GB thumbdrive

45

First try Version 2 of the script

EDIT: v2 script deleted as it didn’t work

46

nfodiz wrote:

First try Version 2 of the script

 

http://www.mediafire.com/?jd78qi8oiq8w35s

 

Please report back

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


/dev/md0 already exists! you need to stop and remove it.

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 WDC WD20EARS-00M (scsi)
Disk /dev/sda: 2000GB
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 2000GB 1996GB ext4 primary

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) copied, 0.739789 s, 45.4 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.475673 s, 70.5 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.42701 s, 78.6 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.556052 s, 60.3 MB/s
Testing with pattern 0x00: done                                                 
Reading and comparing: done                                                 
GNU Parted 3.1
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.6 (21-Sep-2012)
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
Filesystem label=
OS type: Linux
Block size=65536 (log=6)
Fragment size=65536 (log=6)
Stride=0 blocks, Stripe width=0 blocks
30355200 inodes, 30453088 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=133677056
465 block groups
65528 blocks per group, 65528 fragments per group
65280 inodes per group
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 (32768 blocks): done
Writing superblocks and filesystem accounting information: done   


destroying was done, would you like to continue with installation? [y] y

mdadm: size set to 1999808K
mdadm: array /dev/md0 started.
mke2fs 1.42.6 (21-Sep-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
125184 inodes, 499952 blocks
24997 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=515899392
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
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... 
dd: writing to ‘/dev/md0’: Input/output error
659593+0 records in
659592+0 records out
337711104 bytes (338 MB) copied, 45.0055 s, 7.5 MB/s
cp: accessing ‘/mnt/md0/boot/boot.scr’: Input/output error
./debrick.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: Input/output error
mdadm: stopped /dev/md0

all done! device should be debricked!

root@sysresccd /mnt/usb %

 Again failure. I tried that that you threw off, but again the same mistake

47

Ok lets try another approach

  1. Download virgin disk image (02.11.09-053) (171MB) from
    http://www.mediafire.com/?9bqu8r1m4k84lfh

  2. Extract with 7-zip and you should have a file called mybook.img

  3. Format 8GB thumbdrive to NTFS and copy mybook.img to it

  4. Boot SystemRescueCd

  5. In terminal type:
    mkdir /mnt/mybook
    mount -t ntfs /dev/sdb1 /mnt/mybook
    dd if=/mnt/mybook/mybook.img of=/dev/sda bs=1M

  6. Look for any errors in the terminal window (output should look similar to below)
    4700+0 records in
    4700+0 records out
    4928307200 bytes (4.9 GB) copied, 185.112 s, 26.6 MB/s

  7. If there are no errors, put the drive back together and boot

  8. In dashboard do Quick Factory Restore

  9. Done

Post back if any errors

48

nfodiz wrote:

Ok lets try another approach

 

  1. Download virgin disk images from

http://www.mediafire.com/?d12jt5pp1wd61jm

http://www.mediafire.com/?m6u58r7vbbs9z7h

2 Extract with 7-zip and you should have file called mybook.img

  1. Format 8GB thumbdrive to NTFS and copy mybook.img to it
  1. Boot SystemRescueCd
  1. In terminal type:

mkdir /mnt/mybook

mount -t ntfs /dev/sdb1 /mnt/mybook

dd if=/mnt/mybook/mybook.img of=/dev/sda bs=1M

  1. Look for any errors
  1. If none, put drive back together and boot
  1. In dashboard do Quick Factory Restore
  1. Done

 

Post back if any errors

 

I not absolutely understood point 7. Can describe in more detail

49

@Volgar I am wondering also if this might have got you going with the original script as it seems like something keeps starting /dev/md0

If you feel like trying, post back results

mkdir /mnt/usb
mount -t vfat /dev/sdb1 /mnt/usb
cd /mnt/usb
mdadm --stop /dev/md0
mdadm --remove /dev/md0
./debrick.sh rootfs.img /dev/sda destroy

50

I not absolutely understood point 7. Can describe in more detail

51

Did this command complete without error?
dd if=/mnt/mybook/mybook.img of=/dev/sda bs=1M

Terminal should say something close to this
4700+0 records in
4700+0 records out
4928307200 bytes (4.9 GB) copied, 185.112 s, 26.6 MB/s

If so you can put the board back on the drive and try booting up the drive

Please keep me updated :slight_smile:

52

nfodiz wrote:
@Volgar I am wondering also if this might have got you going with the original script as it seems like something keeps starting /dev/md0
 
If you feel like trying, post back results

mkdir /mn/usb
mount -t vfat  /dev/sdb1 /mnt/usb
cd /mnt/usb
mdadm --stop /dev/md0
mdadm --remove /dev/md0
./debrick.sh rootfs.img /dev/sda destroy

Here that as a result it turned out. Without a hard disk

Terminal should say something close to this

4700+0 records in

4700+0 records out

4928307200 bytes (4.9 GB) copied, 185.112 s, 26.6 MB/s

Now I will try to connect a hard disk

53

Ok post back and let me know how it goes and exactly which method you used to get going. I’m not sure which method you are trying

54

nfodiz wrote:
Ok post back and let me know how it goes and exactly which method you used to get going. I’m not sure which method you are trying

Here that as a result it turned out 

root@sysresccd /root % mkdir /mnt/usb
mkdir: cannot create directory ‘/mnt/usb’: File exists
root@sysresccd /root % mount -t ntfs /dev/sdb1 /mnt/usb
root@sysresccd /root % cd /mnt/usb
root@sysresccd /mnt/usb % mdadm --stop /dev/md0
mdadm: stopped /dev/md0
root@sysresccd /mnt/usb % mdadm --remove /dev/md0
mdadm: error opening /dev/md0: No such file or directory
root@sysresccd /mnt/usb % mdadm --remove /dev/md0
mdadm: error opening /dev/md0: No such file or directory
root@sysresccd /mnt/usb % mdadm --stop /dev/md0  
mdadm: error opening /dev/md0: No such file or directory
root@sysresccd /mnt/usb % mdadm --remove /dev/md0
mdadm: error opening /dev/md0: No such file or directory
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sda destroy

**********************DISK**********************

script will use the following disk: 

Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sda: 2000GB
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 2000GB 1996GB ext4 primary

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) copied, 0.737373 s, 45.5 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.343878 s, 97.6 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.378995 s, 88.5 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.556014 s, 60.3 MB/s
Testing with pattern 0x00: done                                                 
Reading and comparing: done                                                 
GNU Parted 3.1
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.6 (21-Sep-2012)
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
Filesystem label=
OS type: Linux
Block size=65536 (log=6)
Fragment size=65536 (log=6)
Stride=0 blocks, Stripe width=0 blocks
30355200 inodes, 30453088 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=133677056
465 block groups
65528 blocks per group, 65528 fragments per group
65280 inodes per group
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 (32768 blocks): done
Writing superblocks and filesystem accounting information: done   


destroying was done, would you like to continue with installation? [y] y

mdadm: size set to 1999808K
mdadm: array /dev/md0 started.
mke2fs 1.42.6 (21-Sep-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
125184 inodes, 499952 blocks
24997 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=515899392
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
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... 
dd: writing to ‘/dev/md0’: Input/output error
659593+0 records in
659592+0 records out
337711104 bytes (338 MB) copied, 44.2149 s, 7.6 MB/s
cp: accessing ‘/mnt/md0/boot/boot.scr’: Input/output error
./debrick.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: Input/output error
mdadm: stopped /dev/md0

all done! device should be debricked!

root@sysresccd /mnt/usb %

Files were on a thumbdrive of 16 Gb 

55

Is DiskInternals Linux Reader as painfully slow for everyone else as it is for me??

56

Nope, super fast here.

57

@Volgar please use this guide instead. Should work like a charm

NOTE THIS WILL ONLY WORK ON A 1TB MBL

  1. Download virgin disk image (02.11.09-053) (171MB) from
    http://www.mediafire.com/?9bqu8r1m4k84lfh

  2. Extract with 7-zip and you should have a file called mybook.img

  3. Format 8GB thumbdrive to NTFS and copy mybook.img to it

  4. Boot SystemRescueCd

  5. In terminal type:
    mkdir /mnt/mybook
    mount -t ntfs /dev/sdb1 /mnt/mybook
    dd if=/mnt/mybook/mybook.img of=/dev/sda bs=1M

  6. Look for any errors in the terminal window (output should look similar to below)
    4700+0 records in
    4700+0 records out
    4928307200 bytes (4.9 GB) copied, 185.112 s, 26.6 MB/s

  7. If there are no errors, put the MyBookLive back together and boot

  8. In dashboard do a Quick Factory Restore

  9. Done

Post back results

58

When I will load a RescueDickCD, the hard disk should be connected? And concerning the 9th point how I can get in dashboard?

59

Yes when you load SystemRescueCD have the hard drive and thumbdrive connected. Access the dashboard from a computer after you put the mybooklive back together and hook it up to your network. The dashboard is accessed through your web browser at http://mybooklive and then go to settings/utilities/factory restore/quick factory restore

60

nfodiz wrote:
Yes when you load SystemRescueCD have the hard drive and thumbdrive connected. Access the dashboard from a computer after you put the mybooklive back together and hook it up to your network. The dashboard is accessed through your web browser at http://mybooklive and then go to settings/utilities/factory restore/quick factory restore

Thank you very much, I’m start MBL. I can get now access to dashboard. As you also spoke made restoration of factory settings. And it passed successfully. But as a result instead of 2 Tb at me shows capacity of a hard disk 1 of Tb, and below in a status line the Status - Bad is specified!!! How all this to correct?