I believe you can, but if you run into a problem with Twonky missing you may have to use an older firmware and then upgrade. I can’t remember if Twonky is included in the newer firmware updates.
1 Like
Hi NFODIZ,
I have used the guide previously and it worked well however this time I cannot seem to get my 2T MBL up and running.
My MBL had been working well with the new media player for several weeks and in my opinion was AOK. I also have CrashPlan backup installed (my guide posted on the community) and transmission. For some reason my MBL started “playing up” and I found that my TV would disconnect when watchin from the Medial Player. After some mins it would come back online but again would be slow and drop out. I had problems in the past when using transmission that there might have been to many connections so I shut down transmission but the problem continued. I then stopped CrashPlan and looking to the CPU/mem there was plenty available however the system was very slow responding and appeared to be having issues. I restarted MBL however the scenario appeared the same with very slow response through SSH and the dashboard whilst TOP showed available resources. Another restart and the system never came back up.
I would be suspicious of the disk but as per the below output it responds ok with USB/SATA connection. The network link light comes on and the traffic light flashes but my router does not identify a device. I completed the debrick and all looks good below however there is no IP taken up by MBL from the router and it does not appear to be up. I did update the 3 partition before this debrick to use all the allocated space as it did not have the format/type and there was 15mb unalocated space. Any suggestions here?
Thanks so much!
********************** DISK **********************
script will use the following disk:
Model: WDC WD20 EARS-00MVWB0 (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
3 1049kB 528MB 527MB linux-swap(v1)
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/sdb
image_img: rootfs.img
destroy: false
this is the point of no return, continue? [y] y
mdadm: /dev/sdb1 appears to contain an ext2fs file system
size=1999808K mtime=Wed Nov 6 21:10:00 2013
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
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/sdb2
synchronize raid… done
copying image to disk…
3999616+0 records in
3999616+0 records out
2047803392 bytes (2.0 GB) copied, 12216.8 s, 168 kB/s
mdadm: stopped /dev/md0
all done! device should be debricked!
Everything looks great in your posted output. Have you tried assigning a static IP address instead of having it set to DHCP and assigning a DHCP reservation for that IP in your router? To eliminate the hard drive as the issue, do you have another 1, 2, or 3TB hard drive you could run the script on and see if it works then? Only other thing I can think of is the NIC on the MBL PCB going bad or a bad network cable? You could also try the V2 version of the guide and see if you have different results.
Just some thoughts but let me know how you make out 
WIthout the system up I don’t know how to change the network config. Is it possible to manipulate a config file on the boot partition to set the ip and can you provide any guidance for that? I presume partition 1 primary raid has the OS and relevant config files… I will check out guide 2, I thought it was a wipe only so will review that further.
Thanks!
I flwd this guide without errors. When I plug in the drive into the MBL the RED LED lights after th blue. How can I unbrick it. I tried it for 3 months and it works perfect. I have only pluged off power for 3 days
I just noted that there is a 4th partition which is primary (489MB) but with the file system ‘unknown’…
Besides that there is a little 15Mb unalocated part.
So I have 4 drives, 1 primary and 3 extented (2x EXT 3 and 1 EXT4)
Should I use debrick script for the Primary drive ?
regards,
Guido
I just noted that there is a 4th partition which is primary (489MB) but with the file system ‘unknown’…
Besides that there is a little 15Mb unalocated part.
So I have 4 drives, 1 primary and 3 extented (2x EXT 3 and 1 EXT4)
I should use the debrick script for the Primary drive I guess ??
regards,
Guido
@Ned673 That was stupid on my part to suggest changing to static IP in the dashboard. Kinda hard to do when you can’t get to the dashboard lol. Have you made any progress with your drive?
@Grovers, I’m not quite sure what you’re asking. Could you try to explain what you are wanting to know better?
@ginibini, have you tried V2 of the guide linked on the first page of this thread? You haven’t really given me enough information to try to help you.
2 Likes
well, finally I have to give the command in which you point to your MBL drive.
I have 4 partitions when I look at “Gparted”, the question is which one off the dev/xxx to use…?
Partition: File System Label Size Flags
unallocated Unalocated 15Mb
dev/sde3 Unknown Primary 489Mb
dev/sde1 EXT3 1,91Gb Raid
dev/sde2 EXT3 1,91Gb Raid
dev/sde4 EXT4 1,82Tb
or should I use just the dev/sde without the number ?
regards
I Tried v2 without error. When i Start mbl i have the red led after the blue and cannot login to dashboard
Grovers wrote:
well, finally I have to give the command in which you point to your MBL drive.
I have 4 partitions when I look at “Gparted”, the question is which one off the dev/xxx to use…?
Partition: File System Label Size Flags
unallocated Unalocated 15Mb
dev/sde3 Unknown Primary 489Mb
dev/sde1 EXT3 1,91Gb Raid
dev/sde2 EXT3 1,91Gb Raid
dev/sde4 EXT4 1,82Tb
or should I use just the dev/sde without the number ?
regards
Yes exactly, use dev/sde without the number. Have you already recovered the data off the drive? If so it may be best to format the drive and run the script with the destroy flag, as this will rebuild the partitions again from scratch in case there’s an issue.
1 Like
ginibini wrote:
I Tried v2 without error. When i Start mbl i have the red led after the blue and cannot login to dashboard
A solid red LED is caused by the following
The following faults trigger this state:
• Disk SMART failure
• Data Volume does not exist
• System Volume does not exist
• System thermal shutdown
• Unsupported drive detected
So you could be looking at a bad hard drive. I would suggest running some tests on the hard drive using one of the many programs out there. One such tool is available from WD for free http://support.wdc.com/product/download.asp?groupid=810&lang=en
The Test passes without an error. The HDD is ok.
rhartinger wrote:
The Test passes without an error. The HDD is ok.
Did you by chance use a USB-2-Sata cable? I know it has caused issues for others where the drive would not boot if you debricked using one of those cables. I am really baffled otherwise and don’t know what else we could try.
Ok, tried it with keeping the data, no change same result as before, device not booting. Precedure went ok.
Second try with destroy all data. First deleted all partitions to one big unallocated drive.
Then started the procedure again but I get several errors, see below :
root@sysresccd /root % mkdir /mnt/usb
root@sysresccd /root % mount -t vfat /dev/sda1 /mnt/usb
root@sysresccd /root % cd /mnt/usb
root@sysresccd /mnt/usb % mdadm-S /dev/md0
zsh: command not found: mdadm-S
root@sysresccd /mnt/usb % mdadm -S /dev/md0
mdadm: stopped /dev/md0
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sde destroy
**********************DISK **********************
script will use the following disk:
Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sde: 2000GB
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/sde
image_img: rootfs.img
destroy: true
this is the point of no return, continue? [y] y
dd: writing ‘/dev/sde1’: No space left on device
11+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.0180326 s, 581 MB/s
dd: writing ‘/dev/sde2’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00125738 s, 0.0 kB/s
dd: writing ‘/dev/sde3’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00121124 s, 0.0 kB/s
dd: writing ‘/dev/sde4’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00119676 s, 0.0 kB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.1
Using /dev/sde
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.8 (20-Jun-2013)
/dev/sde4 is not a block special device.
Proceed anyway? (y,n) y
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/sde1 is not a block device
mdadm: Cannot find /dev/md0: No such file or directory
mke2fs 1.42.8 (20-Jun-2013)
Could not stat /dev/md0 — No such file or directory
The device apparently does not exist; did you specify it correctly?
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.00164466 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!
root@sysresccd /mnt/usb %
Any suggestions before I send it back to WD ?
regards,
@grovers, try formatting the drive as one big NTFS partition and then try running the script again with the destroy flag
Also when you deleted the partitions did you use gparted on the system rescue cd? Sometimes after you make changes using that you have to shutdown and reboot into system rescue cd again. I think I have hit that issue before
Funny, as I format the drive to one big partition, unallocated, and I use the dbrick script, i get all the errors but my drive is again partitioned exactly the way as before with even my data available again ?
Same result as make a formatted NTFS partition…, strange.
I have a MBL duo which cannot boot up and I am trying follow your guidance to fix it.
I used mdadm 3.2.5 and created a array with metadata=0.90, and clone the rootfs.img to the array,
and run mdadm --examine xxx xxx xxx xxx to ensure the metadata version and magic number, all thing seems ok.
Then I connect it to my PC via URAT on the board of MBL duo and execute u-boot command:
sata init; ext2load sata 1:1 100000 /usr/local/share/bootmd0.scr; source
Finally I got some error message below, what can I do next?
PS: I am very sure the metadata version on each part is 0.90, and have not changed the original infomation of partitions via gdisk or fdisk. why cannot be auto detected?
and I remembered that first time I connect HDDs to my PC, the rootfs (md0) cannot be detected automatically, but DataVolume can be auto detected as /dev/md126… may be something special in the superblock of md0?
I use a very old development board to connet MBL duo.
----- Message -----
sdb1 sdb2 sdb3 sdb4
sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] Attached SCSI disk
md: Waiting for all devices to be available before autodetect
md: If you don’t use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: invalid raid superblock magic on sdb1
md: sdb1 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb2
md: sdb2 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb3
md: sdb3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb4
md: sdb4 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda1
md: sda1 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda2
md: sda2 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda3
md: sda3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda4
md: sda4 does not have a valid v0.90 superblock, not importing!
md: Scanned 8 and added 0 devices.
md: autorun …
md: … autorun DONE.
EXT3-fs: unable to read superblock
List of all partitions:
0800 1953514584 sda driver: sd
0801 1999872 sda1
0802 1999872 sda2
0803 500736 sda3
0804 1948998656 sda4
0810 1953514584 sdb driver: sd
0811 1999872 sdb1
0812 1999872 sdb2
0813 500736 sdb3
0814 1948998656 sdb4
No filesystem could mount root, tried: ext3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
Rebooting in 180 seconds…
Sorry for my pool english 
For the MyBookLive DUO try following the MBL DUO debrick guide linked below
http://community.wd.com/t5/My-Book-Live-Duo/GUIDE-Debrick-a-MyBookLive-DUO/td-p/544860
1 Like
