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

I have the same problems.
Has anyone found a solution?

lp Sax

Many years later, used this post as a springboard to upgrade my WD MyCloud from 2TB RAID1 drives to new 10TB drives while online and without losing any data. Including my steps here for posterity.

Complete full backup to external drive - not a member of the RAID array.
Remove #2 drive
Install new #2 drive
Boot up, perform recovery to build out partition table

#remove new #2 drive from raid group
mdadm /dev/md1 —fail /dev/sdb2 —remove /dev/sdb2

#use gdisk to resize partitions - data partition should contain all of the free space.
#use blkid to collect current partition guids - after creating new partitions, set GUID to old guid to keep alignment
gdisk /dev/sdb

Disk /dev/sdb: 19532873728 sectors, 9.1 TiB
Model: WDC WD101EFBX-68
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): A226A521-E027-4398-84CC-028A914481C4
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 19532873694
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 4196351 2.0 GiB 8200 Linux swap
2 6293504 3904931839 1.8 TiB 0700 Microsoft basic data
3 3904931840 19532873694 7.3 TiB 0700 Microsoft basic data
4 4196352 6293503 1024.0 MiB 0700 Microsoft basic data

/dev/sdb3: PARTLABEL="Microsoft basic data" PARTUUID="0cf82435-1432-400c-83df-3a84f9c0536a"
/dev/sdb2: UUID="f4e48f8e-e3c2-9419-d836-30a7bd1c092d" UUID_SUB="a2314c53-f14e-d48e-51c6-8c5a0b0e13c8" LABEL="1" TYPE="linux_raid_member" PARTLABEL="Microsoft basic data" PARTUUID="0b9b4fe0-e36b-40cc-ab68-c96a821fe8de"

#Delete partition #3, create new partition with new start/end values
#Set partition guid to same as collected from blkid earlier

19532873694 - 2097151 = 19530776543

sdb3
Start: 19530776543
End: 19532873694

#Delete partition #2, create new partition with new start/end values
#Set partition guid to same as collected from blkid earlier

sdb2
Start: 6293504
End: 19530774527

reboot

#recreate the md1 array
mdadm —add /dev/md1 /dev/sdb2

#Replace #1 drive, wait for rebuild to complete

#grow array - disable bitmap first, update size, then re-enable bitmap
mdadm —grow /dev/md1 —bitmap none
mdadm —grow /dev/md1 —size max
mdadm —wait /dev/md1
mdadm —grow /dev/md1 —bitmap internal

#kill processes using md1 (disconnect from web console first)

  1. use kill and the pid reported by fuser to kill all the processes

fuser -vm /dev/md1

#unmount md1 (try a couple times after killing as it will report busy)
umount /dev/md1

#filesystem check
e2fsck -f /dev/md1

#resize filesystem
resize2fs /dev/md1

#remount, check and see if expected files are still there :)
mount /dev/md1 /mnt/HD/HD_a2

#reboot
reboot

Re: Resize md4 by gutsnstuffgutsnstuff, 02 Jun 2023 22:12
Andy_DAndy_D 25 Apr 2023 17:39
in discussion Forum / Per page discussions » Samba Update

OK this is old but: I followed the update instructions OK and S90smbd_new runs fine BUT Windows (win10) still refused to map a network drive ( to \\MyBookWorld\Private ) because it is asking for the insecure smbv1

Any suggestions? AndyD

by Andy_DAndy_D, 25 Apr 2023 17:39

Hello,
I have a Mybook World Edition II (blue ring).
Now it does not start, the blue ring stay off.
Do you think it's worth replacing the mainboard ?
It'is in use use since 12 years.
Can I find a mainboard in Europ ?
Thank you for help.

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
page 1123...next »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License