After running the command
./debrick.sh rootfs.img /dev/sd
Should I get any kind of comfirmation? I received a reply about an unknown argument and that was it.
have you correctly entered the drive letter. You show ‘sd’ in your post. Shouldn’t it be something like ‘sdfc’ or ‘sdfa’ - whatever was listed in gpared?
@sndflea Sorry that was just a typo on my part.
I followed the guide here http://mybookworld.wikidot.com/forum/t-607715/debricking-script-for-my-book-live-duo
which uses the same script from here.
Now when I reassemble my MBLD will not power on at all (No LED, No Hard Drive noise etc. )
I am curious what should my next step be?
Also I want to back up my data before doing anything else and I have a USB to SATA dock but for the Duo would I need a dual dock or just use drive A. I had a spanning disk with a few shares created on it.
I am far from an expert on any of this but did get great help from this forum. As respects the MBLD, if it will not even power on I would suspect either a problem with the case or the power supply. Do you have another power supply you can try.
As respects the data, I believe Guide 1 - post # 1 of this thread, provides info on how to pull the data off of the drive. I followed guide 2 as I was merely installing 2 new drives.
Hi
I follow your guide 1 and I ran problem about run script (.debrick.sh rootfs.img /dev/sda) it’s return “zsh: exec format error: ./debrick.sh”, Please help me for fix
the error. I’m a new bie in Linux
WD_Newbie2015 wrote:
Hi
I follow your guide 1 and I ran problem about run script (.debrick.sh rootfs.img /dev/sda) it’s return “zsh: exec format error: ./debrick.sh”, Please help me for fix
the error. I’m a new bie in Linux
I ran into a similar problem when I ran the script. You need to be be careful on where you put spaces in the script. In my case the USB drive containing the debrick script was not being properly mounted. Check the message thread - a couple of pages back.
my notes on the script are as follows:
mkdir /mnt/usb
mount**[space]-t[space]vfat[space]**/dev/sdb1[space]/mnt/usb
Note Above: put space before and after ‘-t’, before and after after ‘vfat’ and after ‘sdb1’
cd /mnt/usb
mdadm -S /dev/md0
note below – will get an error message after it runs
mdadm -S /dev/md2
mdadm -S /dev/md3
./debrick.sh**[space]rootfs.img[space]**/dev/ sda
Note above: space after ‘.sh’ and after ‘.img’
sndflea wrote:
WD_Newbie2015 wrote:
Hi
I follow your guide 1 and I ran problem about run script (.debrick.sh rootfs.img /dev/sda) it’s return “zsh: exec format error: ./debrick.sh”, Please help me for fix
the error. I’m a new bie in Linux
I ran into a similar problem when I ran the script. You need to be be careful on where you put spaces in the script. In my case the USB drive containing the debrick script was not being properly mounted. Check the message thread - a couple of pages back.
my notes on the script are as follows:
mkdir /mnt/usb
mount**[space]-t[space]vfat[space]**/dev/sdb1[space]/mnt/usb
Note Above: put space before and after ‘-t’, before and after after ‘vfat’ and after ‘sdb1’
cd /mnt/usb
mdadm -S /dev/md0
note below – will get an error message after it runs
mdadm -S /dev/md2
mdadm -S /dev/md3
./debrick.sh**[space]rootfs.img[space]**/dev/ sda
Note above: space after ‘.sh’ and after ‘.img’
It’s been a while since I debricked my drive so I’ve forgotten a couple of things. Seems like I also ran into a format error. Try running the script a second time - seems like I had to run it twice to get it to properly format the drive. I don’t recall if I exited and rebooted linux and ran the script a second time or if i ran it twice in succession.
is there anyone on here in the Atlanta, GA area that would be willing to meet up and assist me with performing the guide steps? I have attempted them myself and am getting results/prompts that either do not match up and/or are not mentioned anywhere in all the discussions.
Please PM me if you are interested in helping me out.
Thanks
anyone know how to get a message to nfodiz?!?!?!
i’ve sent him a couple PMs over the last couple weeks and he’s not read them even though he’s been active on here.
i’m getting desparate with this process.
i have Drive A attached to an Unbuntu 14 laptop with a eSata to Sata cable
Gparted is see the Ext3 partitions and the larger partition
i run Terminal and do a sudo -i
then i did the following commands
mkdir /mnt/usb
***ever since my first time doing this i now get a directory already exists***
mount -t vfat /dev/sdd1 /mnt/usb
cd /mnt/usb
mdadm -S /dev/md0
****and this is where my problem begins****
after entering the md0 command i get “No Such file or directory”
even if i continue with the instructions i get the same response for md2 and md3
the when i do this command…
./debrick.sh rootfs.img /dev/sdb
i get this
-bash: ./debrick.sh: Permission denied
i have no clue what i’m doing wrong.
someone please help since i can’t get nfodiz to respond to my PMs!!!
I never had a proble with system-rescue-cd…
I use this debrick method more than 10 times!
Download the files again and try System-Rescue-CD, it should to work!
if i get what your saying. you’re suggesting that using the System Rescue CD may have better results than do this procedure directly from a Linux (Ubuntu) desktop?
not arguing against that suggest in the least, but i do find it curious as to why it would behave differently.
i’ll try that this evening, and see if it works.
thanks
In teory wee just need to use a linux distro to do the job right?
But i try on ubuntu also, install the related programs that wee need to use on the debrick process
but for same how that i dont know why i dont get it to work.
As i say before, i use S.C. CD and it may work.
My live book duo was displaying a constant yellow light which I learned indicated the internal OS was not loading. I could not see it on the network; it was basically a brick! I followed the instructions for guide 1 in this post and the process worked perfectly. I was able to recover all the data after recreating the users and the drive works as designed. Thank you for sharing this fix.
A big THANK YOU to those that developed this fix. I called WD Tech support two days ago with a solid yellow light and all they could tell me was try a reboot of the unit and also a reset. If that did not fix the problem to unit was toast…Ran the first guide and it corrected the issue promptly. Used this unit to store all of my photos and videos. I do have a backup system as well but it was not updated to the latest so I was able to salvage my most recent shots. Again, THANKS!
Also forgot to post the issues I had with Guida 1. When trying to enter the command “mdadm -s /dev/md0,2 or 3” i got an error indicating it could not be the first command. After looking through the help file I determined the correct command should be “mdadm --manage --stop /dev/md0, 2 or 3”. After ruiing those three commands I could then enter the final command to debrick the unit.
Thanks nfodiz for your great work!
Is this procedure expected to work on a duo with 2x4TB drives? I am having no luck and no one here seems to have got it working in this configuration.
I took the 2 drives out and used them for other storage, now I am trying to get the duo working again with the original 4TB WD Green drives. The procedure seems to work but I still get the same old yellow LED.
The only thing that looks funky is this output:
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
Maybe I just need firmware newer than 2012-12-06 but I can’t seem to find any.
Best Guide!!! Thanks NfoDiz!
I wanted to let anyone curious know that you can use a portable hard disk or any other hdd to store the files in the case you don’t have a thumb drive or its not big enough. You would change the mount command to match whatever format the drive is.
mount -t ntfs /dev/sdb1 /mnt/usb
1 Like
I’ve just swapped the stock 2x TB drives for 2x 4TB drives (WD)
RAID1 previously, RAID1 now. The RAID and data all work but it’s still reporting that the drives are 2TB total (should be 4TB total in RAID1)
I’m being told by some that I have to run this debrick guide - really?
Everything works perfectly apart from the fact it’s not reporting the correct disk sizes. This seems way over the top for a simple capacity upgrade
Can I get some help please. I’ve run the debrick Guide 2 but it isn’t working. When I put the 2 drives into the enclosure, the red light stays solid.With old/other drives it does work.
I have dashboard and ssh access.
This is the result of the guide, as you can see there are some errors here and you’re going to know a lot more than me about what/why it’s doing what it’s doing.
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sdb destroy
********************** DISK **********************
script will use the following disk:
Model: ATA WDC WD40EFRX-68W (scsi)
Disk /dev/sdb: 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 2000GB 1996GB ext4 primary raid
is this REALLY the disk you want? [y] y
********************** IMAGE **********************
********************** IMPLEMENTATION **********************
everything is now prepared!
device: /dev/sdb
image_img: rootfs.img
destroy: true
this is the point of no return, continue? [y] y
dd: error writing ‘/dev/sdb1’: No space left on device
10+0 records in
9+0 records out
10371072 bytes (10 MB) copied, 0.00516922 s, 2.0 GB/s
dd: error writing ‘/dev/sdb2’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000549151 s, 0.0 kB/s
dd: error writing ‘/dev/sdb3’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000553634 s, 0.0 kB/s
dd: error writing ‘/dev/sdb4’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000543612 s, 0.0 kB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.2
Using /dev/sdb
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.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/sdb1 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.00186105 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 361: /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 %
Both drives detected in the dashboard and reported as passing the test. However, the left coloumn says “failed”. I also get alerts, “Drive B Failed” and “DataVolume failed to mount”.
I’ve created the swap as instructed and using parted the partition table looks correct.
Factory reset quick and full. No luck.
Removed drive B, it’s gone from the details list but the dashboard shows A and B failed
The option to edit mode is greyed out.
Any ideas?
This is the structure of Drive A and B, they are identical
https://dumpyourphoto.com/photo/jOkahyi3rT
My old drives still work although if I put them in, it rebuilds the entire array again every time (apx 8 hours). Even though nothing has changed.
So it must be something in the debrick script that’s not preparing the new drives right?
