@dj_kenzo982 Thanks for the info, I will update the guide a bit as soon as I get to my desktop today 
1 Like
Guide updated, thanks again to all that have contributed to the efforts
Just want to report a successful debrick attemp with some special caveats and tweaks.
I had my Duo configured in raid 1 (not sure if this was a good idea after all this experience). One of the disks started to fail (just 9 months old >:- ! , and it rendered the complete box unoperational after a power outage (led always in yellow, and no network access to the device), no matter if I removed the failed disk or whatever. I had a PC with one ubuntu partition and some sata slots, so I was able to connect the drives to it and make some research that confirmed the problems in that disk… and broke a few things
Just in case anyone faces the same, I guess the main problem was in the swap partition, that was not correctly reported by parted, so I suppose it got corrupted and unusable. After e2fschk I was able to mount partitions 1 and 4 with success. However, due to my ignorance, and wanting to avoid the failed disk to corrupt the good one again, I zeroed the superblock of the data partition. So it was mountable as a regular partition, but said bye to any raid option…
I then debricked the healthy disk from my ubuntu ( I copied the files to some local folders, no need to use the usb stick) with no destroy option and everything went fine. However, as it would be expected, the data partition was not mounted on startup, as the sda4 partition was not in raid, so there where no /dev/md3 device to mount.
However, changing the “dataVolumeDevice” variable in /etc/system.conf to /dev/sda4 made the trick, and now I can use the Duo in a quite degraded state due to the lack of raid, but fully operational and with my old data in perfect state.
Thank you very much to NFODIZ and all those that have added their experience to this guide. It’s been really, really helpful
2 Likes
Very informative post, thanks for sharing picopaco
Awesome guide, thank you very much!
Just a few notes about my experience:
–When using an unpartitioned drive, you’ll need to run the script twice with a reboot in between. The first time you get a few errors until the disk gets partitioned.
–You may still get yellow or red lights after booting your MBLD eventhough it’s working. I didn’t get a green light until I performed a factory reset.
thank you very much !
when i plug my duo’s drive A or B into my usb sata adapter…they both read as unallocated. this is in Windows or Linux. would you happen to know what that may be? when inside the duo’s case…all i’m getting is a yellow light, and no connection via ethernet.
You might want to try a direct sata connection to your motherboard or an eSTAT to SATA cable of Dock if your motherboard or laptop has an eSATA port… USB to SATA cables seem to be finicky on these larger drives
Noob here… My MBL is bricked but the data seems to be intact. I downloaded, installed, and ran the DiskInternals Linux Reader and can see the files in /CacheVolume/shares. How do I copy those files to somewhere safe? Can I copy to another NAS?
BTW, I do see a “SAVE” command but there is little documentation to tell me what that does and I don’t want to do anymore damage than I have to.
[UPDATE] Nevermind. I searched the web and found that SAVE is the way to copy the files. It is also capable of copying to another NAS.
Not the fastest in the world but it does the job.
Hey NFODIZ, Dont know if your still on this forum but I need some help. After 4 days and every bit of my free time dedicated to this I still can’t seem to access the dashboard. I used the guide on wikidot first and it screwed up my hard drives and spent time just wiping them clean. (Reinitializing the disks) But I have been able to succesfully go through the entire process but when I put the drives back in, Connect it to switch which is connected to router It doesnt get an IP and stays yellow. I am using 2x4TB seagate drives in a 6tb WD enclosure. I did the flash with it connected via SATA one at a time. The readouts from the debricking look the same as ones posted here. I read on your Mybook Live (single) debricking forum that someone connected it via ethernet to their comp and did stuff. Havent tried that yet and don’t know how.The Ethernet lights on the back of the drive blink as if they were working and the lights on my switch confirm this. but no ip. Please help.
Thanks for your time,
Scuba
I’m still around but I’m not sure what would be causing your issue. These scripts seem hit and miss for some folks. Another user in this thread said he had to run the debrick script twice on the disks. That might be worth a shot…
Another option would be to find somebody to dd image a disk from a 8TB MBLD just past the OS partitions, then I could show you how to restore that way. I don’t own a DUO or I would do this for you myself
I have a 8TB one (2x4TB) I had to run it twice because i didn’t have any partitions after i wiped the disks. I am at a loss. The fact that they are seagate drives shouldn’t matter right?
It doesn’t on the single drive MBL as I have debricked to a Seagate hard drive and it booted right up
What is the difference between guide 2 and 3? Also I didnt do the step where we backup stuff becasue there was nothing to backup. Do i need to install these programs anyway?
There is a member I used to chat with quite often and he debricked his DUO with the mybookworldwiki images a ton of times. It might be worth PM’ing him. Do a user search for Timmy1024
Guide 3 is another members guide in this thread that differed slightly from mine so I linked it on the main page
I have the images from wikidot (that was the first guide i tried) but i couldnt make out the protocol to dd? them to the drives.
If you boot up the system rescue cd and put that folder on an ntfs partitioned hard drive or thumb drive and mount the drive, it should just be a matter of typing their commands in the terminal window 1 line at a time. I have never done it myself but Timmy1024 should be able to help you without a doubt
Here is my print out after I’ve run the script 3 times on the hdd (Drive A):
root@sysresccd /root % mkdir /mnt/usb
root@sysresccd /root % mount -t vfat /dev/sdd1 /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/sdc destroy
********************** DISK **********************
script will use the following disk:
Model: ATA ST4000DM000-1F21 (scsi)
Disk /dev/sdc: 4001GB
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 raid
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
4 4624MB 4001GB 3996GB ext4 primary raid
is this REALLY the disk you want? [y] y
********************** IMAGE **********************
********************** IMPLEMENTATION **********************
everything is now prepared!
device: /dev/sdc
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.62921 s, 53.3 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.343883 s, 97.6 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.211119 s, 159 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.245016 s, 137 MB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.1
Using /dev/sdc
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) set 3 raid on
(parted) set 4 raid on
(parted) quit
Information: You may need to update /etc/fstab.
Warning: blocksize 65536 not usable on most systems.
mke2fs 1.42.7 (21-Jan-2013)
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
60775680 inodes, 60976592 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=133677056
931 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, 40955000, 47769912
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.7 (21-Jan-2013)
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/sdc2
synchronize raid… done
copying image to disk…
3999616+0 records in
3999616+0 records out
2047803392 bytes (2.0 GB) copied, 146.352 s, 14.0 MB/s
mdadm: stopped /dev/md0
all done! device should be debricked!
root@sysresccd /mnt/usb %
I did an immeiate shutdown after i posted disk A and then I did disk B here is the readout:
root@sysresccd /root % mkdir /mnt/usb
root@sysresccd /root % mount -t vfat /dev/sdd1 /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/sdc destroy
********************** DISK **********************
script will use the following disk:
Model: ATA ST4000DM000-1F21 (scsi)
Disk /dev/sdc: 4001GB
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 raid
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
4 4624MB 4001GB 3996GB ext4 primary raid
is this REALLY the disk you want? [y] y
********************** IMAGE **********************
********************** IMPLEMENTATION **********************
everything is now prepared!
device: /dev/sdc
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.510073 s, 65.8 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.142367 s, 236 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.286108 s, 117 MB/s
32+0 records in
32+0 records out
33554432 bytes (34 MB) copied, 0.273973 s, 122 MB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.1
Using /dev/sdc
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) set 3 raid on
(parted) set 4 raid on
(parted) quit
Information: You may need to update /etc/fstab.
Warning: blocksize 65536 not usable on most systems.
mke2fs 1.42.7 (21-Jan-2013)
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
60775680 inodes, 60976592 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=133677056
931 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, 40955000, 47769912
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.7 (21-Jan-2013)
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/sdc2
synchronize raid… done
copying image to disk…
3999616+0 records in
3999616+0 records out
2047803392 bytes (2.0 GB) copied, 146.559 s, 14.0 MB/s
mdadm: stopped /dev/md0
all done! device should be debricked!
root@sysresccd /mnt/usb %
