Recent Forum Posts
From categories:
page 1123...next »

Soft and hard batter resets didn't work! Looks like the HW unit is bork'd. Good news is that the disks are fine and work in my other NAS. Time for a Synology I guess.

Re: Case failure? by aaghaaagha, 24 Oct 2022 16:17

From the documentation, looks like unit failure — See the image about what the lights mean:

community dot wd dot com/t/my-book-world-edition-ii-white-light-undeined-led-patterns/215722/4

I'll try a factory reset tomorrow.

Re: Case failure? by aaghaaagha, 22 Oct 2022 06:36

I have two, My Book World 2's—one is working fine and the other is not. I swapped the drives in them and it seems the casing for one of the units has gone back.

When I power it up, I see just the bottom segment of the lights light up; occasionally the just the top segment lights up (while the bottom segment stays on). I can't mount the unit/drives or access it from the browser (as stated above, putting the drives in the other unit works fines—moving the drives from the good unit to this one doesn't work).

Is there a way to diagnose what's happening?

Case failure? by aaghaaagha, 22 Oct 2022 06:33

Update 2022.10.07: Never mind, after extensive testing of the disk with smartctl and badblocks with no errors found, I am now fairly confident that the errors originated from failing electronics or SATA contacts issues in the WD case. Discarding and replacing with a new NAS.

Hi, and thanks for all the great help and knowledge about the WD My Book Live here that has helped me a lot over the years!!

The last couple of days my aging WBL(10+ years) has started eliciting new and odd behavior. Almost every night it ends up not being reachable anymore either by ssh, the web admin interface or any of the shares. It only responds to pings, and I have to cut and reenable power to get it back online again.

The actual hard drive inside my MBL is pretty new, around 6 months old, and the combination has been working well until the last couple of days.

The last messages from the logs before a new reboot typically are, maybe indicating something with the sata connection, which I am unable to interpret, find any information about or fix:

Sep 21 23:17:13 SviskeNAS logger: exit standby after 365 (since 2022-09-21 23:11:08.860949593 +0200)
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect errors: DIAGN DIAGW DIAGX
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:16:47 SviskeNAS kernel: ata2: Freeze port with 1 QCs aborted
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect errors: ERRM DIAGN DIAGW DIAGX
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:16:47 SviskeNAS kernel: sata-dwc 4bffd1800.sata: Detect recovered communication error
Sep 22 00:16:47 SviskeNAS kernel: ata2: Freeze port with 0 QCs aborted
Sep 22 00:16:47 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:16:53 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:16:56 SviskeNAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
Sep 22 00:16:56 SviskeNAS kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x40)
Sep 22 00:17:01 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:05 SviskeNAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
Sep 22 00:17:05 SviskeNAS kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x40)
Sep 22 00:17:05 SviskeNAS kernel: ata2.00: limiting speed to UDMA/133:PIO2
Sep 22 00:17:10 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:16 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:17:20 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:26 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect errors: DIAGN DIAGW DIAGX
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:17:27 SviskeNAS kernel: ata2: Freeze port with 0 QCs aborted
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect errors: ERRM DIAGN DIAGW DIAGX
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:17:27 SviskeNAS kernel: sata-dwc 4bffd1800.sata: Detect recovered communication error
Sep 22 00:17:27 SviskeNAS kernel: ata2: Freeze port with 0 QCs aborted
Sep 22 00:17:30 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:36 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:17:48 SviskeNAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
Sep 22 00:17:49 SviskeNAS kernel: ata2.00: configured for UDMA/133
Sep 22 00:17:49 SviskeNAS kernel: ata2: EH complete
Sep 22 00:17:49 SviskeNAS logger: exit standby after 3032 (since 2022-09-21 23:27:17.132949579 +0200)
Sep 22 03:00:16 SviskeNAS logger: exit standby after 9083 (since 2022-09-22 00:28:52.992950114 +0200)

I also noticed for the first time this message, where I was able to unmount and fix the data partition with fsck, but I am unable to forcfsck on boot the /dev/md0 raid partition:

Sep 21 16:02:23 SviskeNAS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended

Just wondering if anyone here has experience with something similar, and whether it is fixable, something wrong with my hard drive, or if it is finally the end of the line for my WD MBL case this time?

Hi,

maybe try the instructions from this site (remove the blanks) h t p s://github . com / themaddoctor/linux-mybook-tools

Regards,
Jan

Hi,
I do not look often to this site even if I am seeking for information.

Have you try the following command on unbuntu "lsblk -fe7" it shall give you something like this for a WD worldedition disk

My WD disk is sdc

sdc
├─sdc1 linux_raid_member a1bfd51f-fe0f-a06c-3b6d-8c490838e6b9
│ └─md127 ext3 f6b302d9-cae8-46a7-8ddd-e86983e49d38
├─sdc2 linux_raid_member 5b94085a-e082-a29d-3b6d-8c490838e6b9
│ └─md126 swap c3f80e75-883d-46c2-9c6c-0f293bf775d8
├─sdc3 linux_raid_member eacc7784-59b6-7608-3b6d-8c490838e6b9
│ └─md125 ext3 72cc3da0-7abf-48e5-aead-7eba928354d2
└─sdc4 linux_raid_member MyBookWorld:2 1e358eef-4a00-889b-293b-d10c0e2c416f
└─md124 xfs ddc2d76a-0a34-40c5-b8c0-3db74e17495f
sr0

Regards,
Guy.

Hi My Book World Edition is not turning on so decided to remove it from the existing case and plug it in as an ext HDD to my computer running Ubuntu.

I tried to mnt the drive but I am getting this error mount: /mnt: can't read superblock on /dev/sdb

I guess this is could be because the drive is encrypted but im not sure.

Serial number of my Western Digital MyBook is WD7500G032

The drive contains photos of my kids which i am hoping to recover. Can someone please help and give direction as to how i can recover the files.

Thanks so much!

Hi,
if any body still reading this site.
I am looking for the binaries of blue light one drive (1TB would be beter).
Regards,
Guy.

Thank you Macindoe for your thrilling update.
I appreciate this is a pretty old project, but I like to save money and avoid wasting things that could be still useful.
I hate WD firmare and that's the reason why I installed your firmware.
Just two issue, hopefully this will help other people playing with their MBWE:
1. The box (1 slot, white light) was already tweaked with a 4TB disk. No dev/md2 is present though. Any ideas on how can I get my data back?
2. apt-get update says some keys are expired but I had no success in updating them. I think this would be nice to have a up-to-speed system.

Thank you in advance for your time.
Paolo

hi i found a way to upgrade to last version 8.5.2
1. download from here https: //download. twonky. com/8.5.2/ zip named Maxtor Shared Storage 2
2. upload the zip file to file .io
3. fallow all the step on first page
4. wget —no-check-certificate (and link gived from file .io)
5.unzip (copy the name of zip given on putty after download its complet)
6. continue whit the step on first page

Have a happy christmas and happy new year

I know it's been a while but… Now you can try a new kernel with working SATA for MBWE II (delete spaces): 4pda.to / forum / index.php?s=&showtopic=467828&view=findpost&p=110236729. For now the version 4.4.294 of Linux kernel is used, LEON acceleration and HW RAID (not fully) was dropped. No WixEvents and Trustees. Kernel reports that its version is 4.4.254.294 - this is for normal work of libc/glibc upgrading scripts in Debian Squeeze. Hot plug/unplug works but sometimes may totally freeze the system. Also sometimes it can fully ignore hotplug, then use following command to detect hotplugged drive: for host in /sys/class/scsi_host/*; do echo "- - -" | tee $host/scan; ls /dev/sd* ; done

I have joined the WikiDot site specifically to reply to this post.

After spending almost two full days trying to fix the "Warning: is_dir(): Stat failed for /DataVolume/_torrent_ (errno=5 - Input/output error) in /proto/SxM_webui/ctcs/ctcsconfig.inc on line 24 " problem with no success I was ready to get the HDD out of the enclosure and go "Linux" way as suggested by jimboh when I suddenly read this post.
I gave it a try and it worked for me!
I have almost talked myself into buying DiskInternals Raid Recovery for $250 if nothing else would have worked.
So glad Zeppe found the time to share his experience!

With many, MANY thanks!
GYakushkin

Hi from France,

Just unburrying this thread from 1 year back to add somewhat usefull details^^

I rebuilt my WBL (1 disk) from a dead HD with debrick.sh . Upgraded Twonky to 8.3 following your guide, Twonky works fine, thank you !

However, GUI from WBL UI was broken and i made changes to many scripts DLNA files in /usr/local/sbin (basically, because i cant' find out why twonky doesn't create /tmp/twonky_server with IP:PORT inside)

# TWONKY_IP="`cat /tmp/twonky_server`"
TWONKY_IP="127.0.0.1:9000"

also made some changes in share-param.sh (same location) for twonky_dir and in awk line of getDlnaServerConnectedList.sh for new lines in TwonkyIP:9000/rpc/info_connected_clients answer

# JUST THE AWK COMMAND HERE vvvv

awk '
BEGIN { 
    FS = "\n"; RS = "##########\n";
    getline info < "/tmp/info_clients"
    split(info, info_arr, ",")
    for ( item in info_arr ) info_count++;
}
{
    id = $2;
    mac = $3;
    ip = $4;
    if ( $6 == 1 )
        enable = "enable";
    else
        enable = "disable";

    friendly_name = $7;
    for (i = 1; i <= info_count; i=i+2) {
        if (info_arr[i] == id) {
            desc = info_arr[i+1];
            break;
        }
    }
    printf("\"%s\" \"%s\" \"%s\" \"%s\" \"%s\"\n", mac, ip, friendly_name, desc, enable);
}

' /tmp/info_connected_clients

It was just some garbage tech infos, if someone can find why twonky doesn't create /tmp/twonky_server, this can help.

Thanks !

Hi all!

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

Hi all!

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

by QuintaHomemQuintaHomem, 09 Apr 2021 17:16

A little background:

I bought this WD NAS over ten years ago and it has ran fine up until about six weeks ago
when it died. Windows 7 just no longer sees the mapped out drives in My Computer. There
were no sounds coming from the spinning drives just nothing. So I decided it was a WD
enclosure problem and not a hard drive problem. So I pulled the hard drives from their
enclosure and connected one of them to a “USB to SATA Adapter”, then plugged it into my
computer. The computer made a sound of a USB device being plugged in, but nothing
showed up in My Computer window. My conclusion is that I would have to look elsewhere
for my answer if I wanted my data back.

So I started my research on the internet, and found there are a lot of people with the
same problem and no support or fix from WD to correct it. I found that some people had
success with Linux. I have an older DELL laptop laying around so I loaded Linux Mint 20
“Ulyana” – Cinnamon (64-bit) on to this older DELL. I can at least see the drive now in
the My Computer window but can’t get into it. When I try, I get the error message “Unable
to mount location”.

In the past six weeks I have read and tried countless internet posts, most of them have
been Terminal Window stuff without any success. I know there is a solution out there, I
just need someone’s help to find it.

If you are willing to take on this challenge, you will find that I’m highly motivated to
retrieve my data. I promise to check this forum every day and try your suggested key
strokes and post results.

Shown below are two looks at both drives “Disks” & "sudo fdisk -l". I’m hoping that if
someone is willing to help me this will be useful to you.

Thank You in Advance
TSQMAN-1


Information from Linux Mint Disks Command -Disk Number 1

Model: WDC WD20EADS-00R6B0 (01.00A01)
Size: 2.0 TB (2,000,398,934,016 bytes)
Partitioning: Master Boot Record
Serial Number: WD-WCAVY2497662
Assessment: Disk is OK, one bad sector

Information on Partition 4 (It's the Largest and I Believe the Data is Here)

Size: 2.0 TB (1,997,081,543,168 bytes)
Device: /dev/sdb4
UUID: 8f7e3052-dbae-d664-7273-ee3ce6483360
Partition Type: Linux RAID auto
ConTents: Linux RAID Member (version 0.90.0)


Information from Terminal Window Command "sudo fdisk -l" -Disk Number 1

Disk /dev/sdc: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: EADS-00R6B0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001cf00

Device Boot Start End Sectors Size Id Type
/dev/sdc1 64320 3984191 3919872 1.9G fd Linux raid autodetect
/dev/sdc2 3984192 4498175 513984 251M fd Linux raid autodetect
/dev/sdc3 4498176 6474175 1976000 964.9M fd Linux raid autodetect
/dev/sdc4 6474176 3907024064 3900549889 1.8T fd Linux raid autodetect


Information from Linux Mint Disks Command -Disk Number 2
Data is exactly the same as disk number 1 except what’s shown below.

Serial Number: WD-WCAVY2497155

Information on Partition 4 (It's the Largest and I Believe the Data is Here)

UUID: 3066fbfa-03fd-8233-4217-cbc4f1db6bbb


Information from Terminal Window Command "sudo fdisk -l" -Disk Number 2
Data is exactly the same as disk number 1 except what’s shown below.

Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors

Device Boot Start End Sectors Size Id Type
/dev/sdb1 64320 3984191 3919872 1.9G fd Linux raid autodetect
/dev/sdb2 3984192 4498175 513984 251M fd Linux raid autodetect
/dev/sdb3 4498176 6474175 1976000 964.9M fd Linux raid autodetect
/dev/sdb4 6474176 3907024064 3900549889 1.8T fd Linux raid autodetect


Hello: netvizier

If you would like to read more background of my problem I'm facing please look in section 3 for "TSQMAN-1" on this forum.

I have tested your posting and the results are shown below do you anymore suggestions?

QUESTION for you: It looks like it had a problem with STEP #5 & STEP #7, where does the "/dev/md4" come from?

Thank You in Advance
TSQMAN-1


TITLE: How to Recover Data From WD My Book World Edition NAS Device
POSTED BY: netvizier 19 Sep 2008

STEP 1:---------------
KEYED IN: sudo fdisk –l
REPLY MESSAGE:

Disk /dev/sdd: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: EADS-00R6B0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001cf00

Device Boot Start End Sectors Size Id Type
/dev/sdd1 64320 3984191 3919872 1.9G fd Linux raid autodetect
/dev/sdd2 3984192 4498175 513984 251M fd Linux raid autodetect
/dev/sdd3 4498176 6474175 1976000 964.9M fd Linux raid autodetect
/dev/sdd4 6474176 3907024064 3900549889 1.8T fd Linux raid autodetect

STEP 2:---------------
KEYED IN: sudo modprobe md
REPLY MESSAGE:

No Reply

STEP 3:---------------
KEYED IN: sudo mknod /dev/md4 b 9 4
REPLY MESSAGE:

No Reply

STEP 4:---------------
KEYED IN: sudo apt-get install mdadm
REPLY MESSAGE:

Reading package lists… Done
Building dependency tree
Reading state information… Done
mdadm is already the newest version (4.1-5ubuntu1.2).
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

STEP 5:---------------
KEYED IN: sudo mdadm —assemble /dev/md4 /dev/sdd4
REPLY MESSAGE:

mdadm: Found some drive for an array that is already active: /dev/md2
mdadm: giving up.

STEP 6:---------------
KEYED IN: sudo mkdir /media/abc
REPLY MESSAGE:

No Reply

STEP 7:---------------
KEYED IN: sudo mount /dev/md4 /media/abc
REPLY MESSAGE:

mount: /media/abc: can't read superblock on /dev/md4.

STEP 8:---------------
KEYED IN: sudo chmod -R 777 /media/abc
REPLY MESSAGE:

No Reply


Update: aMule2.3.3

ed2k://|file|aMule2.3.3-MyBookWorld-v1-Blue.tar.gz|7374903|e94657277f5697d5666e0021a7fd9451|/
Re: plea for amule binaries by CoronasCoronas, 05 Mar 2021 14:32

Hi all.
I am trying to swap my MBWE I hdd for a bigger one.
Following the steps in this guide i got stuck at downloading mbwe.tar.gz script, because the site iknowsomething.com is down (forwarding to random commercials)
Is there any place where I can find the same script ?

Thanks in advance!

page 1123...next »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License