I am trying to revive my old MBWE white lights with this script but having no joy. Script runs it course with these 3 identical warnings:

Warning: The resulting partition is not properly aligned for best performance:

When I place the drive back in the housing the bottom LED comes on and stays on.

Anyone else encountered this, have you found a solution?

Cheers!

Installed Ubuntu 20.04.2 LTS, original WD 1TB Caviar Green HDD connected to a USB IDE & SATA cable and attempting to install FW version 01.02.12

Thanks in advance!

You mean that you installed ubuntu12.04 on MBWE I white light? How ? Do you succeeded to have a full working system?

He means that the desktop PC he used had Ubuntu 12.04 installed as Operating System. It is more than impossible to install Ubuntu on MBWE.

Worked perfectly with Ubuntu 12.04 firmware 01.02.06 on a desktop with direct connection to the drive.

You mean that you installed ubuntu12.04 on MBWE I white light?
How ? Do you succeeded to have a full working system?

Thanks

Could not get it to work with USB - SATA with Ubuntu 15.10. Might be Ubuntu, might be the converter. Worked perfectly with Ubuntu 12.04 firmware 01.02.06 on a desktop with direct connection to the drive.

Yes I know its old and performance is not wonderful but it works and a backup is better than none.

Thanks for putting the work into this project Krzysztof and others. …. Now to hack it some more…. :-)

So he kept the disk and gave me the rest. Works like a charm!

It is not true that you can do it only when using WD Green disk. I believe that you can safely use anything of WD disks. I didn't touch the firmware nor tweak anything.

My World Book Edition I (White Light) has now gone down. I completed the instructions from the iknowsomething website (which were great) but the disk itself is badly damaged so I can't use it.
I want to replace it with a non-WD drive like you did.
I know that I need to edit the factoryDefault file but can't seem to do this bit.
My knowledge of Linux is very limited. Basically, I've followed the instructions and have ended up with a 200GB hard drive with 4 RAID components. How do I get to the factoryDefault file?

Any help would be great thanks.

David

That's long ago understood…

Btw, I think the word "green" above could be removed!
_

DISK_COUNT=0
WD_DISK_COUNT=0

let DISK_COUNT=DISK_COUNT+1
cat /sys/block/sda/device/model | grep WDC >/dev/null 2>&1
#if [ "$?" -eq "0" ]; then
let WD_DISK_COUNT=WD_DISK_COUNT+1
DISK1=sda
DISK_LIST=sda
#fi

New AF disks cost the same or sometimes even less than old models, so… All I want is to make sure that the disk is compatible (or backwards compatible if need be): SATA III is not an issue, but wasn't sure about the new AF…

In any case, I just realized that the MBWE originally shipped with a WD20EARS which is an AF drive itself, so… :)

Btw, these new drives bear less platters, therefore, they shall have a lower heat profile… the specs also claim so.

Cheers! ;)

Just curious, but what do you expect with this type of format ?

Remember the WD MBWE is 'old', you will be very limited by hardware enclosure and I think you will not be able to see performance difference with this kind of 'optimisation'.

Remember too, MBWE is fanless, if you put a 'normal' disk you can have problem with heat…

I was wondering if anybody could report any experience with non-WD advanced-format (4K/sector) drives with this tool?

@Krisp PL: does support for a 4K/sector drive depend entirely on the WD fw supporting / formatting it properly or would you also have to tune your code in any way?

I want to put a 2TB Toshiba DT01ACA200 (google for DT01ACA200 to see its datasheet on the Toshiba web site) in a 2TB MBWE I (WDH1NC20000E) using the latest WD fw (01.02.14), but I'm hesitating to buy it because I'm not sure the tool will work… and if it does work, if the drive will be formated / partitioned properly given its 4K/sector geometry or if it will just be underperforming…

Thanks a bunch in advance for any feedback! :)

do you happen to know, if I used the instructions for "non WD disks user" for a 2x1TB Caviar Blacks, would it work?

/usr/sbin/smartctl -d ata -A %s | grep Temperature_Celsius

If the result is null i.e no match then that is the issue, the Smart attribute list reported back has no parameter matching "Temperature_Celsius" and you will get an alarm reporting 0degC,

These are the Smart values from an original MBWE 1TB disk …

/etc/init.d # /usr/sbin/smartctl -d ata -A /dev/sda smartctl version 5.38 [arm-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 165 163 021 Pre-fail Always - 6750 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 29 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 17 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 26 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 391 194 Temperature_Celsius 0x0022 118 099 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 /etc/init.d #

These are the Smart values from my currently installed 16GB SSD disk …

/sbin # /usr/sbin/smartctl -d ata -A /dev/sda smartctl version 5.38 [arm-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 154 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 303 175 Unknown_Attribute 0x0032 100 100 012 Old_age Always - 0 176 Unknown_Attribute 0x0032 100 100 012 Old_age Always - 0 177 Unknown_Attribute 0x0013 092 092 017 Pre-fail Always - 431 178 Unknown_Attribute 0x0013 085 085 012 Pre-fail Always - 9 179 Unknown_Attribute 0x0013 099 099 010 Pre-fail Always - 13 180 Unknown_Attribute 0x0013 012 012 010 Pre-fail Always - 467 181 Unknown_Attribute 0x0032 100 100 010 Old_age Always - 0 182 Unknown_Attribute 0x0032 100 100 010 Old_age Always - 0 183 Unknown_Attribute 0x0013 100 100 010 Pre-fail Always - 0 187 Reported_Uncorrect 0x0033 100 100 000 Pre-fail Always - 0 195 Hardware_ECC_Recovered 0x001a 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 253 253 000 Old_age Always - 1 232 Unknown_Attribute 0x0013 083 083 012 Pre-fail Always - 51 233 Unknown_Attribute 0x0032 093 093 000 Old_age Always - 269232885 /sbin #

Spot the difference !

To stop my alarms, I edited the line in script /etc/init.d/S96wixalarm

WIX_APP="wixalarmdaemon wixhwmonitor"

to

WIX_APP="wixalarmdaemon"

This brute force method remove ALL hardware monitoring! but I only have an SSD and usb stick in my MBWE - so I'm not too worried. Hopefully someone will work out a more elegant solution to this little issue.

Same problem with 2TB WD Green edition ??

I've switched the disk in my My Book World Single Disk (White Light) running FW 01-02-12, from the original 1TB to a 160GB laptop drive, and loaded Squeezcenter Version: 7-3-3 via Optware using the FeaturePack Mgr program and System tools v1-57 Everything worked fine.

Now I have switched to a 16GB SAMSUNG UM410 SSD for the OS, it's again running Squeezcenter Version: 7-3-3 with music files on a 64GB USB drive - running OK except for occasional Thermal Alerts ( 0degC) blinking my LEDS.

I've tried to look for the thermal monitoring script but cannot find it, where's the S15wdc-heat-monitor script that everyone references ? It is not listed in directory /etc/init.d which only contains …

/etc/init.d # ls -l -rwxr-xr-x 1 root root 2106 Feb 5 2009 S01auto_mountd -rwxr-xr-x 1 root root 533 Sep 29 04:04 S10portmap -rwxr-xr-x 1 root root 847 Aug 8 2008 S40network lrwxrwxrwx 1 root root 9 Mar 23 18:02 S50sshd -> _SK50sshd -rwxrwxr-x 1 root root 1418 Jul 15 2008 S55mini_httpd -rwxrwxr-x 1 root root 395 Apr 29 2008 S60inetd lrwxrwxrwx 1 root root 25 Sep 29 04:06 S85ntpdated -> /etc/init.d/_SK85ntpdated -rwxr-xr-x 1 root root 3316 Apr 30 2009 S90smbd lrwxrwxrwx 1 root root 22 Sep 29 04:06 S91atalk -> /etc/init.d/_SK91atalk -rwxr-xr-x 1 root root 1860 Sep 29 04:03 S94fuse -rwxr-xr-x 1 root root 2438 Feb 9 2010 S95windbindd -rwxr-x--- 1 root root 1984 Sep 29 04:06 S96wixalarm -rwx--x--x 1 root root 0 Mar 23 18:05 S97twonkyserver -rwxr-xr-x 1 root root 686 Sep 29 04:03 S98logrotate -rwxr-xr-x 1 root root 4795 Sep 30 2009 S99sxminit -rwx------ 1 root root 98 Mar 23 18:05 S99toptware -rwxr-xr-x 1 root root 682 Sep 29 04:04 S9M_mionet -rwxrwxr-x 1 root root 205 Nov 20 2008 S9WiAutoConfig lrwxrwxrwx 1 root root 21 Sep 29 04:06 S9iTune -> /etc/init.d/_SK9iTune -rwxr-xr-x 1 root root 804 Sep 29 04:03 S9lltd -rwxr-xr-x 1 root root 1300 Sep 29 04:03 S9mDNSResponder -rwxrwxr-x 1 root root 1636 Aug 8 2011 SxxAddBackupToPasswd-php-bak *** -rwxrwxr-x 1 root root 1302 Jan 5 2010 _SK01controlled_power_down -rwxr--r-- 1 root root 1136 Sep 9 2008 _SK02upgrade -rwxr-xr-x 1 root root 0 Mar 24 13:25 _SK50sshd -rwxr-xr-x 1 root root 898 Sep 29 04:04 _SK80nfsd -rwxr-xr-x 1 root root 0 Mar 24 13:25 _SK85ntpdated -rwxr-xr-x 1 root root 0 Mar 24 13:25 _SK91atalk -rwxrwxr-x 1 root root 1814 Jun 23 2008 _SK9C_cds -rwxr-xr-x 1 root root 0 Mar 24 13:25 _SK9iTune -rwxr-xr-x 1 root root 2827 Oct 8 2009 rcH -rwxr-xr-x 1 root root 10273 Mar 9 2010 rcS

these are my startup scripts as reported by the FeaturePacks Manager

List of startup Scripts in /etc/init.d : -rwxr-xr-x 1 root root 2106 Feb 5 2009 /etc/init.d/S01auto_mountd -rwxr-xr-x 1 root root 533 Sep 29 04:04 /etc/init.d/S10portmap -rwxr-xr-x 1 root root 847 Aug 8 2008 /etc/init.d/S40network lrwxrwxrwx 1 root root 9 Mar 23 18:02 /etc/init.d/S50sshd -> _SK50sshd -rwxrwxr-x 1 root root 1418 Jul 15 2008 /etc/init.d/S55mini_httpd -rwxrwxr-x 1 root root 395 Apr 29 2008 /etc/init.d/S60inetd lrwxrwxrwx 1 root root 25 Sep 29 04:06 /etc/init.d/S85ntpdated -> /etc/init.d/_SK85ntpdated -rwxr-xr-x 1 root root 3316 Apr 30 2009 /etc/init.d/S90smbd lrwxrwxrwx 1 root root 22 Sep 29 04:06 /etc/init.d/S91atalk -> /etc/init.d/_SK91atalk -rwxr-xr-x 1 root root 1860 Sep 29 04:03 /etc/init.d/S94fuse -rwxr-xr-x 1 root root 2438 Feb 9 2010 /etc/init.d/S95windbindd -rwxr-x--- 1 root root 1984 Sep 29 04:06 /etc/init.d/S96wixalarm -rwx--x--x 1 root root 0 Mar 23 18:05 /etc/init.d/S97twonkyserver -rwxr-xr-x 1 root root 686 Sep 29 04:03 /etc/init.d/S98logrotate -rwxr-xr-x 1 root root 4795 Sep 30 2009 /etc/init.d/S99sxminit -rwx------ 1 root root 98 Mar 23 18:05 /etc/init.d/S99toptware -rwxr-xr-x 1 root root 682 Sep 29 04:04 /etc/init.d/S9M_mionet -rwxrwxr-x 1 root root 205 Nov 20 2008 /etc/init.d/S9WiAutoConfig lrwxrwxrwx 1 root root 21 Sep 29 04:06 /etc/init.d/S9iTune -> /etc/init.d/_SK9iTune -rwxr-xr-x 1 root root 804 Sep 29 04:03 /etc/init.d/S9lltd -rwxr-xr-x 1 root root 1300 Sep 29 04:03 /etc/init.d/S9mDNSResponder -rwxrwxr-x 1 root root 1636 Aug 8 2011 /etc/init.d/SxxAddBackupToPasswd-php-bak *** List of startup Scripts in /opt/etc/init.d : -rwxr-xr-x 1 root root 106 Feb 16 11:55 /opt/etc/init.d/S05gconv-modules -rwxr-xr-x 1 root root 153 Feb 16 08:15 /opt/etc/init.d/S10cron lrwxrwxrwx 1 root root 30 Mar 23 18:22 /opt/etc/init-d/S70mysqld -> --/--/share/mysql/mysql-server *** -rwxr-xr-x 1 root root 3537 Feb 17 10:06 /opt/etc/init.d/S99squeezecenter

It seems a side effect of not using WD disks is that the check temperature function shows 0degC and sets off an alert.

BTW I always try to post detailed info but whenever I try to include raw unix listing using the Code Block feature I always get …

The data you have submitted contains following errors:

* Guests and low-karma users are not allowed to publish links on this site.

I had to edit three lines marked *** replacing dots with dashes - to get rid of the error message - very frustrating !

I did not edit the factoryDefault file correctly. It should have been like this …

DISK_COUNT=0 WD_DISK_COUNT=0 let DISK_COUNT=DISK_COUNT+1 cat /sys/block/sda/device/model | grep WDC >/dev/null 2>&1 # if [ "$?" -eq "0" ]; then let WD_DISK_COUNT=WD_DISK_COUNT+1 DISK1=sda DISK_LIST=sda # fi if [ "$MODEL" != "WWLXN" ]; then let DISK_COUNT=DISK_COUNT+1 cat /sys/block/sdb/device/model | grep WDC >/dev/null 2>&1 # if [ "$?" -eq "0" ]; then let WD_DISK_COUNT=WD_DISK_COUNT+1 DISK2=sdb DISK_LIST="sda sdb" # fi fi

Thanks again for providing the means to do this at all - now I will install the Squeezbox server and hope to get that working.

I have a My Book World (White Light) single disk unit.

I wish to replace the WDC 1TB drive with a spare Samsung 2.5" 160GB drive and use it only as a music server.

I followed all the instructions and hacked the factoryDefault file BUT when I power up the unit - WD Link does not see it and the white LEDs do not blink correctly.

I've spent two days on this and I'm about to give up. The unit is operational because if I put the original untouched 1TB drive back it works fine! But put the little Samsung drive in and I cannot access the unit - no matter what I do.

Is there something I'm completely missing here ?

I used the latest current Ubuntu Live distribution on a USB stick and your script picked up the latest fw and loaded everything onto the Samsung disk. I then mounted the partition /dev/sdb1 to hack the factoryDefault file by commenting out the required lines. The Samsung drive was connected via a external SATA interface and seen as sdb

I also tried it without hacking the factoryDefault file - no difference - still no access to the unit and unrecognised LED patterns.

Currently with an unhacked factoryDefault file - the first four LEDs are on permanently - the lan leds show some activity.

Pressing the reset button makes the LEDS flash as expected and then after a few minutes the first four LEDs are on permanently - again the lan leds show some activity - but still no access to the unit.

I've checked the Samsung drive using HDDScan and it's OK.

Does anyone have any clues or hints?

Bye

first of all congratulations for the fantastic work!!! :-)

I want to buy two WD30EZRX, I saw in the guide that these HDs are perfectly compatible with the procedure. My idea is to use both 1TB HDs working on my MBWEII in my Desktop PC, using them in RAID. I have two questions:

1) Do you think that is possible to use both disks into my PC? If yes, how can I format/partition them?
2) In the future, will I have the possibility to use again your procedure to restore original 1TB disks on my MBWEII NAS?
3) Last question…in the MBWEII if one disk breaks, and both disks are RAID/mirror configured, does the NAS works with only a disk as I can backup my data and only after send It to WD for repairing or not? If not, It's absurd that I will send my data to them!!!

Thank you very much

tnx

Tried to clean my HDD it didn't boot up. when I connect my HDD only one light comes on and it stays on for ever… My HDD is WD10EADS 1 TB ; it came with NAS my book we 1 disk. Ubuntu used 10.10; Firmware applied : 01.02.12;

Following is fdisk -l output.

fdisk -l /dev/sdb Note: sector size is 4096 (not 512) Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 15200 cylinders Units = cylinders of 16065 * 4096 = 65802240 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000300 Device Boot Start End Blocks Id System /dev/sdb1 5 249 15679488 fd Linux raid autodetect Partition 1 does not end on cylinder boundary. /dev/sdb2 249 280 2055936 fd Linux raid autodetect Partition 2 does not end on cylinder boundary. /dev/sdb3 280 403 7904000 fd Linux raid autodetect Partition 3 does not end on cylinder boundary. /dev/sdb4 403 121602 3493236672 fd Linux raid autodetect

can't upload the script log. I will see how I can upload it.

Any idea how do I get the NAS up and running? Please help.

Thanks.

By now I suspect the reason is that my new WD-2TB-drive has different sector-size – 4096 instead of 512 which could make all of the pre-defined partitions useless.

1. fdisk -l /dev/sdb

Note: sector size is 4096 (not 512)

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 30400 cylinders
Units = cylinders of 16065 * 4096 = 65802240 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0×00000300

I actually tried to partition my harddisk manually (based on the real size of my current drive) and then run your script but skipping the part where it applies rootfs/etc/DSKPART. Looked promising but didnt work out either.

so my questions here:

• is my sector-size a problem or is it something completely else?
• anyone sucessfully put a 2TB-drive with 4096-sectors in a mbwe yet?
• is there a DSKPART-table for 4096B-sectors available somewhere?
• any other tips?

thnx,
p

mybookworld.wikidot.com/forum/t-90514/how-to-recover-data-from-wd-my-book-world-edition-nas-device

So I have tried doing this, and the reconstructing of my new 2tb drive worked well using ubuntu 11.04.

However, when i try to connect the old and the new onto the sata ports, i am not able to mount the new filesystem. It keeps saying unknown filesystem 'linux_raid_member', whereas my 1tb drive can be mounted easily (has xfs filesystem).

If anyone can assist, that would be great :)

Cheers,
Stuart

firmware version used: wdhxnc-01.02.06_273745.img
OS used: ubuntu 10.10

echo "y" | mdadm —create —metadata=0.9 /dev/${PART_OS_BOOT} -l 1 -n 2 /dev/${DISK_LABEL}1 missing
echo "y" | mdadm —create —metadata=0.9 /dev/${PART_SWAP} -l 1 -n 2 /dev/${DISK_LABEL}2 missing
echo "y" | mdadm —create —metadata=0.9 /dev/${PART_OS_VAR} -l 1 -n 2 /dev/${DISK_LABEL}3 missing
echo "y" | mdadm —create —metadata=0.9 /dev/${PART_DATA} -l 1 -n 2 /dev/${DISK_LABEL}4 missing

In my MBWE the lowest led is on and after about 10 sec the highest one illuminates for about 5 sec - that's all.

Will try the mdadm parameter and give feedback.

Everything look OK, but when boot from MBWE, it is not working. Only the lowest LED indicator is on, not blinking.

That's the same symptoms as my MBWE(White)1TB. I've come to the conclusion that that it's a board failure of some sort and have contacted WD to get an RMA for replacement.
Well, almost the same symptoms. The LED on mine goes out after several minutes, but the network connector's "cable connected" light remains on (indicating that the power supply is still good).

I try to unbrick my MBWE II 2TB.

I follow the procedure, I use Ubuntu 11.04 on a Pen drive, attach the WDC Green Hdd on SATA Port, detected as sda.
Everything look OK, but when boot from MBWE, it is not working. Only the lowest LED indicator is on, not blinking.

What should I do? Is it OK to attach the disk on SATA Port? Any clues?

Thanks.
Pujo

the temp is only 39 C and still got warning at the web interface:

05/08 09:07:11 [Thermal Alarm] System temperature exceeded threshold!(0 degrees)

0 degrees ???!?

the disk is new, and it is working fine when I watch videos. No spins down.
I have WDWE White, single disk without FAN

Why does it have to be a WD Caviar Green? I didn't look into your scripts yet, but I cannot imagine a reason why this shouldn't work with other drives as well. Or did WD a "I only run on WD" in their firmware?!

Tweaked my hard drive, in order to disable its spin-stop (see thread at http://mybookworld.wikidot.com/forum/t-258653/smart-load-cycle-count) and the temperature, as expected, rise a lot.

I attached an old power supply exhaust fan at the top of my mbwe and this is what I have:

Me, personally, would not be concerned if temperature runs below 55°C.

I have this script to monitory my MBWE, running at every 10 minutes. If temperature goes in a given threshold, front LEDs will flash:

#!/bin/sh -x HD=`/usr/sbin/smartctl -a -d ata /dev/sda | /usr/bin/awk '/Temperature/ {print $10}'` case $HD in 55|56 ) echo 3 > /sys/class/leds/oxnas-wd810-leds\:st/brightness ;; 57 ) echo 5 > /sys/class/leds/oxnas-wd810-leds\:st/brightness ;; 58|59|60|61) echo 6 > /sys/class/leds/oxnas-wd810-leds\:st/brightness ;; * ) echo 15 > /sys/class/leds/oxnas-wd810-leds\:st/brightness ;; esac

HTH,

- R

Do you have one or two drives ?
Does your drives pauses as they should ?
Is the pb linked to the rebuild of raid1 ?

Is the problem my new disk or… Doesn't want to lose my data…

tnx again for your job… it is much much easer then step by step :)

any chance how to low down temperature?

Here is: Ultra Fast Install for My Book World Edition I and II (White Light) of any disk size

• Works with both MBWE White Light (I and II) with any size of disk!!! but only WD Caviar Green!
• Full install takes 1 minute!!! excluding firmware download.
• Only 3 scripts!!! - no more heavy junk stuff like MBR, sda copies, MAC etc.
• Separate config file with only 3 lines to adjust: disk label, MBWE type and MBWE serial.
• 1 script to fire!!! and little wizard will guide you.

Updated and maintened version is here.

Release info:
2011-11-16: Changed mbwe-install.sh to address partitions bigger than 2TB (parted/GPT instead of sfdisk/MBR).
2011-10-25: Added MAC definition (in mbwe-config.sh and mbwe-install.sh). Improved FW autoload (in mbwe-getfw.sh).
2011-10-22: New FW 01.02.12 - changed FW URL (in mbwe-getfw.sh).
2011-10-17: wdc.com FW URL (in mbwe-getfw.sh) has changed.
2011-07-19: Added (in mbwe-install.sh) "mdadm -metadata=0.9" for linux distribution compatibility reasons.
2011-04-21: First version for firmware "wdhxnc-01.02.06_010411.img"