[GUIDE] How to unbrick a totally dead MBL

I’m a new client for WD community forum.

I’ve been trying for a couple of days to debrick my wd my book live 2T.

I used both scripts supplied in this feed… but always had an error when copying image to disk.

I’ve used virtual machines … I’ve used my raspberry pi… and now i’m using my system rescue boot… but always with the same outcome…

"********************** DISK           **********************

script will use the following disk: 

Model: WDC WD20 EURS-63S48Y0 (scsi)

Disk /dev/sdd: 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/sdd

image_img:    rootfs.img

destroy:      false

this is the point of no return, continue? [y] y

mdadm: /dev/sdd1 appears to contain an ext2fs file system

    size=1999808K  mtime=Tue Jun  3 00:56:43 2014

mdadm: size set to 1999808K

mdadm: creation continuing despite oddities due to --run

mdadm: array /dev/md0 started.

mke2fs 1.42.9 (28-Dec-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/sdd2

synchronize raid… done

copying image to disk… 

dd: writing to ‘/dev/md0’: Input/output error

2911409+0 records in

2911408+0 records out

1490640896 bytes (1.5 GB) copied, 266.204 s, 5.6 MB/s

cp: cannot create regular file ‘/mnt/md0/boot/boot.scr’: Input/output error

mdadm: stopped /dev/md0

all done! device should be debricked!"

And everything stays the same! still bricked!

Can anyone help me put my NAS back on track… without deleting the information in the disk?

Thank you in advance

Hi Daremo, hope you are still active here…

Having problems with r-linux … When scanning my MBL it has a few errors early on - I/O errors at the moment.

Do you scan “showing files” first?

I’m at a loss as i’ve never been this deep into it before. I have pictures i need to get off of the kids :frowning:

Any guidance greatly appreciated.

Hi,

I’m trying to unbrick my MBL using the guide.    

I get errors that I’m hoping someone can help me work through.

First, Gparted complains that…

"The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?
Not all of the space available to /dev/sdc appears to be used, you can fix the GPT to use all of the space (an extra 4294967296 blocks) or continue with the current setting? 

Unable to satisfy all constraints on the partition.


I tell gparted not to fix anything and I proceed with running the script. 

At the end, the script shows a bunch of error messages:

"mdadm: cannot find /dev/sdc2: No such file or directory

synchronize raid… done

copying image to disk… 

dd: writing to ‘/dev/md0’: Input/output error

1+0 records in

0+0 records out

0 bytes (0 B) copied, 0.00292232 s, 0.0 kB/s

mount: /dev/md0: can’t read superblock

cp: cannot stat ‘/mnt/md0/usr/local/share/bootmd0.scr’: No such file or directory

./debrick.sh: line 361: /mnt/md0/etc/nas/service_startup/ssh: No such file or directory

umount: /mnt/md0: not mounted

mdadm: stopped /dev/md0

/dev/sdc1: No such file or directory

/dev/sdc2: No such file or directory"

My device still appears to be bricked though.

Anything I should do differently?

Thanks!

-Z 

I have a dead-ish MBL - it goes to green light but can’t be seen on the network and the 1TB hard drive seems to have a corrupted partition table.

I’m currently running a scan using R-Linux and it’s picking up partitions, files etc. which is encouraging, but does this software actually rebuild the partition table and write it to the disk so the disk can then be used in its original state, or does it just recover data?

If it doesn’t automatically repair the partition table, is there another way to do this reliably?

tried at least twenty times fat32, fat, ntfs usb drive and sd card yet i always get the unable to mount after i enter

mount -t vfat /dev/sdb1 /mnt/usb

and the sdb1 does correspond to the proper drive with all the proper files intact on it.

i was totally able to get all the files off of it as it was still visible with the programs sugessted in the howto,

cannot seem to get anything started though as i can’t mount it.

any ideas anyone?

I follow instructions by typing the following commands because I have change my hard drive with a new one.

mkdir /mnt/usb

mount -t vfat /dev/sdb1 /mnt/usb

cd /mnt/usb

mdadm -S /dev/md0

./debrick.sh rootfs.img /dev/sda destroy

The output results from the debrick script is:

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

script will use the following disk:

Model: ATA WDC WD10EZRX-00L (scsi)

Disk /dev/sda: 1000GB

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: writing `/dev/sda1’: No space left on device

10+0 records in

9+0 records out

9863168 bytes (9.9 MB) copied, 0.0033813 s, 2.9 GB/s

dd: writing `/dev/sda2’: No space left on device

1+0 records in

0+0 records out

0 bytes (0 B) copied, 0.0003717 s, 0.0 kB/s

dd: writing `/dev/sda3’: No space left on device

1+0 records in

0+0 records out

0 bytes (0 B) copied, 0.000348085 s, 0.0 kB/s

dd: writing `/dev/sda4’: No space left on device

1+0 records in

0+0 records out

0 bytes (0 B) copied, 0.000368711 s, 0.0 kB/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.3 (14-May-2012)

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?

As you see, I receive this error for ext4 partition: “Device size reported to be zero. Invalid partition…” and I can’t proceed with installation.

Could you please tell me what I do wrong?

greetings all…i was wonder if you could assist a newbie,Warning: the backup superblock/group descriptors at block 458752 contain bad blocks. Warning: the backup superblock/group descriptors at block 491520 contain bad blocks. Allocating group tables: mkfs.ext3: Could not allocate block in ext2 filesystem while trying to allocate filesystem tables mdadm: cannot find /dev/sdb2: No such file or directory synchronize raid… done copying image to disk… dd: writing to ‘/dev/md0’: Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.0100238 s, 0.0 kB/s mount: /dev/md0: can’t read superblock 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: stopped /dev/md0 /dev/sdb1: No such file or directory /dev/sdb2: No such file or directory all done! device should be debricked!

Deat all,

the disk of my MBL is dead, ou can hear horrible sounds form it… :frowning:

I don’t a PC with SATA adapter, only a laptop and a SATA-to-USB adapter.

Can I use it to flash the software on a new disk and then install it in the enclosure?

Thanks,

Max

THe story.
I have a Mybook Live 3TB Nas, and due to power/circuit break in my house, it won’t start up.
Now i found a repair script that can help you unbrick it, but there’s a crucial superblock backup that is needed to make the script work. And from all the superblock backups, this specific superblock is damaged which interups the process to unbrick the Nas hdd. Nor do i know how to manually install a new firmware and partition it correctly.
Now i am at wit’s end, and lacking the knowledge to manually input the commands that are in the script to make it work via terminal.

Things i have done so far
Installed curl and mdam (default settings)

sudo apt-get install curl
sudo apt-get install mdadm

-made the script executable

chmod +x sudo repair_mybooklive.sh

Gave terminal root and administrative privileges, before starting the script

su root

sudo -i

made sure dev/md0 is not mounted or in use, before starting the script

mdadm --stop /dev/md0
mdadm --remove /dev/md0

made sure i have the right hdd to run the script

sudo fdsik -l

Model: WDC WD30 EZRX-00MMMB0 (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

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 primary raid
4 4624MB 3001GB 2996GB ext4 primary msftdata

Results from the script

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
Warning: the backup superblock/group descriptors at block 65536 contain bad blocks.

Warning: the backup superblock/group descriptors at block 98304 contain bad blocks.

Warning: the backup superblock/group descriptors at block 131072 contain bad blocks.

Warning: the backup superblock/group descriptors at block 425984 contain bad blocks.

Warning: the backup superblock/group descriptors at block 458752 contain bad blocks.

Warning: the backup superblock/group descriptors at block 491520 contain bad blocks.

Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/16
Warning, had trouble writing out superblocks.mdadm: added /dev/sdc2
copying image to disk…
dd: writing to ‘/dev/md0’: Input/output error
362273+0 records in
362272+0 records out
185483264 bytes (185 MB) copied, 486,404 s, 381 kB/s
cp: failed to access ‘/mnt/md0/boot/boot.scr’: Input/output error
./repair_mybooklive.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: Input/output error
mdadm: stopped /dev/md0

My request
Could someone please help me with the following:
Basically i have two issues, superblock backup 65536 is damaged, and i can’t install the image.

Please tell me step-by-step instructions how i can repair this hdd.

  1. fix the superblock size 65536 so this error goes away
    #blocksize 65536 is required by the hardware, you won’t be able to mount if different.
    mkfs.ext4 -b 65536 -m 0 $diskData

  2. what to delete from the script to make it run-without checking for bad superblock. (i already finished that test , took me 13 hours.)
    OR

  3. help me decript the script commands, so i can manually enter them in terminal

  4. How to implement this command to restore superblock from other superblock backup.

    sudo e2fsck -b block_number /dev/xxx

    script will use the following disk:

    Model: WDC WD30 EZRX-00MMMB0 (scsi)
    Disk /dev/sdc: 3001GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    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 primary raid
    4 4624MB 3001GB 2996GB ext4 primary msftdata

    is this REALLY the disk you want? [y] y

    IMAGE

    IMPLEMENTATION

    everything is now prepared!
    device: /dev/sdc
    image_img: ./CacheVolume/upgrade/rootfs.img
    destroy: false

    this is the point of no return, continue? [y] y

    mdadm: /dev/sdc1 appears to contain an ext2fs file system
    size=1999808K mtime=Thu Sep 18 09:10:04 2014
    mdadm: size set to 1999808K
    mdadm: creation continuing despite oddities due to --run
    mdadm: array /dev/md0 started.
    mke2fs 1.42.9 (4-Feb-2014)
    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
    Warning: the backup superblock/group descriptors at block 65536 contain
    bad blocks.

    Warning: the backup superblock/group descriptors at block 98304 contain
    bad blocks.

    Warning: the backup superblock/group descriptors at block 131072 contain
    bad blocks.

    Warning: the backup superblock/group descriptors at block 425984 contain
    bad blocks.

    Warning: the backup superblock/group descriptors at block 458752 contain
    bad blocks.

    Warning: the backup superblock/group descriptors at block 491520 contain
    bad blocks.

    Allocating group tables: done
    Writing inode tables: done
    Creating journal (8192 blocks): done
    Writing superblocks and filesystem accounting information: 0/16
    Warning, had trouble writing out superblocks.mdadm: added /dev/sdc2

    synchronize raid… done

    copying image to disk…
    dd: writing to ‘/dev/md0’: Input/output error
    362273+0 records in
    362272+0 records out
    185483264 bytes (185 MB) copied, 486,404 s, 381 kB/s
    cp: failed to access ‘/mnt/md0/boot/boot.scr’: Input/output error
    ./repair_mybooklive.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: Input/output error
    mdadm: stopped /dev/md0

    all done! device should be debricked!

Swell6 wrote:

I have a dead-ish MBL - it goes to green light but can’t be seen on the network and the 1TB hard drive seems to have a corrupted partition table.

 

I’m currently running a scan using R-Linux and it’s picking up partitions, files etc. which is encouraging, but does this software actually rebuild the partition table and write it to the disk so the disk can then be used in its original state, or does it just recover data?

 

If it doesn’t automatically repair the partition table, is there another way to do this reliably?

I’m having the same issue, I managed to recover all the data when connected to a desktop, and the script says it’s run succesfully, but when I boot the MBL, it doesn’t show up on the network, while the light is green. Anyone have any suggestions by any chance?

Hello all

During the compilation of the image I get this:

**** IMAGE****x

checking:     010507
searching:    ./*/*01*05*07*.img
found:        ./firmware/rootfs_010507.img
swap.c:1:20: fatal error: unistd.h: No such file or directory
 #include <unistd.h>
                    ^
compilation terminated.

********************** IMPLEMENTATION **********************

everything is now prepared!
device:       /dev/sdb
image_img:    ./firmware/rootfs_010507.img
destroy:      false

this is the point of no return, continue? [y] n

Can anyone guide me through this problem?

Thanks

Hey does anyone know how to fix the line 359 error? i tried debricking it 3 times but still stays on the yellow light.

here’s my log:

root@sysresccd /root % mkdir /mnt/usb
root@sysresccd /root % mount -t vfat /dev/sdb /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
zsh: correct '.debrick.sh' to 'debrick.sh' [nyae]? n
zsh: command not found: .debrick.sh
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sda

**********************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: false

this is the point of no return, continue? [y] y


mdadm: /dev/sda1 appears to contain an ext2fs file system
       size=1999808K mtime=Thu Nov 20 19:22:20 2014
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md0 started.
mke2fs 1.42.12 (29-Aug-2014)
/dev/md0 contains a ext3 file system
	last mounted on Thu Nov 20 19:22:20 2014
Proceed anyway? (y,n) y
Creating filesystem with 499952 4k blocks and 125184 inodes
Filesystem UUID: 374b922d-b227-44cd-8a92-b2f630d7f3f6
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
1049609+0 records in
1049608+0 records out
537399296 bytes (537 MB) copied, 102.354 s, 5.3 MB/s
cp: cannot stat ‘/mnt/md0/usr/local/share/bootmd0.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 %

Can anyone please help me??

I have a 2TB My Book Live.  When running the SystemRescue CD portion, I receive a couple of EDD: Error bb00 ready sector XXXXX.  Then it states its "Loading initram.igz…ready - After that it states “No setup signature found…”  Then it stops loading and sits at a prompt you can’t add anything too.

Any suggestions?

Thanks in advacnce.

Hi,

Sorry for my English but is not my native language…

So i want debrick the HDD of the MyBook LIve "TB…

I formatted the HDD with NTFS Filesystem because i used it on my PC Desktop with Win 7 but now i really want to use it again like original MyBook Live.

I followed that guide but i don’t know how to reset the right partitions on it. 

This is my status of HDD. Can anyone tell me what to do now?

i hope someone can help me.

Thank You 

Giuseppe :slight_smile:

I think i did biggest mistake to follow these thread to fix dashboad access

Scripts have some issues(trired both v1 & v2 ) and now i have losted my MBL forever. Already wasted 3 days with unrest sleep. And no help from anyone.

Please dont try to debrick your mbl , inst better to buy another if you love your life.

Thanks

Thanks for posting this useful information. But could you please tell me what you mean by the term “brick?” I have a 1T MBL that no longer appears on my network, and the front LED does not illuminate. HOWEVER, I can hear the disks spinning when plugged in. Would you consider my MBL to be “bricked?” And could you suggest a remedy?

Hi ,

if LED does not illuminate at all, either power adopter is broken , or LED broken or PCB broken

first try to get power supply check  , rest if you are newbie with linux sh*t , and can manage to buy new one then go to buy instead of wasting time on this de-bricking.

(if device is under warranty best to claim that)

A liitle help, please.

First, I tried to install some server s/w on my MyBook Live 2 TB. Long story, short, it is now a brick. (I’m pretty sure where I went wrong – a little bit more about that below).

I say it is a brick b/c (1) the front panel light is a solid yellow, and (2) any attempt to access the server functions fail.

I want to use the guide to try to back up the contents of the drive which is my digital music library (iTunes) and the Mac OS X Time Machine share contents.

However, there’s a bit of confusion about the necessary platforms needed to perform all of the steps in the guide. Is it all Windows based, or, Windows and *NIX? And, if I need a LINUX system, will FreeBSD suffice?

OK, now to explore some options.

If I were to acquire a new WD Cloud device, configure it and put it up onto my LAN, is there a way to take the MBL drive (from the server now a brick) and to mount it on a Windows system then copy across the net the contents of the iTunes directories?

Next question, same as the one immediately above but for the Mac OS X TM files?

Finally, the task I was attempting was to install the Mozilla FireFox Sync server software. This would allow for using the FireFox Sync service but using a local server and not the service provided by Mozilla. My initial attempt failed when the sudo apt-get install command gave me an error for one of the 3 packages not found. The suggested fix was to update aptitude. I believe this is where it went south. What is the correct command for updating the Debian flavor aptitude?

TIA

DJ

i ran the script in this was my output :-( 

i cant access the storage via HTTP nor ssh (cant ping it or sniff it)

what am i doing wrong?

root@sysresccd root % mkdir mntusb
root@sysresccd root % mount -t vfat devsdb1 mntusb
root@sysresccd root % cd mntusb
root@sysresccd mntusb % mdadm -S devmd0
mdadm stopped devmd0
root@sysresccd mntusb % .debrick.sh rootfs.img devsda destroy

DISK

script will use the following disk

Model ATA VMware Virtual I (scsi)
Disk devsda 1000GB
Sector size (logicalphysical) 512B512B
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 devsda
image_img rootfs.img
destroy true

this is the point of no return, continue [y] y

dd error writing ‘devsda1’ No space left on device
10+0 records in
9+0 records out
10416128 bytes (10 MB) copied, 0.0194167 s, 536 MBs
dd error writing ‘devsda2’ No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00179725 s, 0.0 kBs
dd error writing ‘devsda3’ No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00117259 s, 0.0 kBs
dd error writing ‘devsda4’ No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00121096 s, 0.0 kBs
Testing with pattern 0x00 done
Reading and comparing done
GNU Parted 3.2
Using devsda
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 etcfstab.

Warning blocksize 65536 not usable on most systems.
mke2fs 1.42.12 (29-Aug-2014)
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 devsda1 is not a block device
mdadm Cannot find devmd0 No such file or directory
mke2fs 1.42.12 (29-Aug-2014)
The file devmd0 does not exist and no size was specified.
mdadm error opening devmd0 No such file or directory

synchronize raid… mdadm Cannot find devmd0 No such file or directory
done

copying image to disk…
dd writing to ‘devmd0’ No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.0235572 s, 0.0 kBs
mount devmd0 is not a block device (maybe try `-o loop’)
cp cannot stat ‘mntmd0usrlocalsharebootmd0.scr’ No such file or directory
.debrick.sh line 359 mntmd0etcnasservice_startupssh No such file or directory
umount mntmd0 not mounted
mdadm devmd0 does not appear to be an md device
BLKGETSIZE Inappropriate ioctl for device
BLKGETSIZE Inappropriate ioctl for device

all done! device should be debricked!