So… I logged into my Web UI and blam red error telling me my data volumes have failed to mount? I have ssh enabled but im unsure on how to proceed. I would like to keep my data as it contains important pictures ie. Wedding and my sons birth and baby pictures. Im aware others have gotten this but I havent seen a solution yet. Thanks in advance. Fyi I already tried WD support and you know what they sent me here … -_^?
See my updated Guide below… Hopefully, I made it easier to follow
3 Likes
NAS:~# parted
GNU Parted 2.2
Using /dev/sda
Welcome to GNU Parted!Type ‘help’ to view a list of commands.
(parted) p
Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 15.7MB 2064MB 2048MB ext3 primary raid
2 2064MB 4113MB 2049MB ext3 primary raid
3 4113MB 4624MB 512MB linux-swap(v1) primary
4 4624MB 2000GB 1996GB ext4 primary
(parted)
partition table looks good, please continue on to step 2
1 Like
hello,
i am having the same issue as above can anyone help?
Step 1 ) First you need to turn on SSH in the MyBookLive dashboard. To do this go to your dashboard and in your address bar change the URL from
your mybooklive ip or name /UI/
to
your mybooklive ip or name /UI/ssh
Tick the enable SSH box
Step 2) If you are on a MAC login using Terminal app included with OSX
Open Terminal and type
ssh root@mybooklive.local
OR
ssh root@youmybooklive’s ip address
OR
ssh root@your mybooklive’s network name.local
and then hit enter and when asked, enter welc0me for the password
If you are a Windows user, download PuTTY from http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe
Enter the MyBookLive IP or Network device name in the window, port 22, tick SSH and click open
Now we need to enter the login information
type root for the username and hit enter
type welc0me for the password and hit enter
(The password text won’t show up in the PuTTY window)
Step 3) Now type the following at the command prompt
fsck /dev/sda4
The process should go through 5 passes and you will be prompted to fix things with a simple y or n
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
This should fix your filesystem on the datavolume. If it repairs everything successfully, type this at the command prompt
reboot
Your MyBookLive should reboot and mount the datavolume
DONE!
Following the guide linked below could lead to complete data loss. If the data is irreplaceable, I would recommend trying a data recovery service instead.
If you get an error that the superblock is invalid and has a bad magic number when you run the fsck /dev/sda4 command reference this guide
http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/
4 Likes
Same problem here…
Shramba:~# parted
GNU Parted 2.2
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) p
Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
3 15.7MB 528MB 513MB linux-swap(v1) primary raid
1 528MB 2576MB 2048MB ext3 primary raid
2 2576MB 4624MB 2048MB ext3 primary raid
4 4624MB 2000GB 1996GB ext4 primary raid
After command … Shramba:~# fsck /dev/sda4
I get the following:
fsck from util-linux-ng 2.17.2
fsck: fsck.linux_raid_member: not found
fsck: Error 2 while executing fsck.linux_raid_member for /dev/sda4
Shramba:~#
@aleksanderturk Your data partition 4 is marked as raid as well as your swap partition 3 which is not normal and is probably causing your issues.
This is normal for a MBLDUO but NOT for the single drive MBL.
Off the top of my head, I’m not sure how to fix it.
@ nfodiz … My device is DUO …Mybook Live DUO.
Ah that makes sense then 
Try posting your question in the MBLDUO thread
http://community.wdc.com/t5/My-Book-Live-Duo/bd-p/mbl_duo
I would try to help you in here but I don’t own the DUO and I don’t want to mess your drive up anymore than it already is.
The MBLDUO DataVolume is raid which is a whole different beast for me to learn.
You may also wanna try WD support
http://support.wdc.com/contact/index.asp?lang=en
You will probably get a quicker answer by phone
Good luck
Hi: yet another eager user who has lost access to mybook files.
I’ve been working through your instructions and after fsck/dev/sda4 my checksums were invalid so I clicked y to fix and now it comes up with a specific reference error. Is there any risk in fixing this: --see below
MyBookLive:~# fsck /dev/sda4
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
One or more block group descriptor checksums are invalid. Fix? yes
Group descriptor 0 checksum is invalid. FIXED.
/dev/sda4 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry ‘iTunes Library.itl’ in /shares/SmartWare/WD SmartWare.swstor/DAVID-PC/Volume.b0883aaf.4435.11e0.8530.806e6f6e6963/Users/David/Music/iTunes (13581410) references inode 13653406 found in group 209’s unused inodes area.
Fix?
Thanks for your help: kudos definitely on its way.
Do you have a backup of all fles in your Smartware backup folder? If you do I would say go for it
1 Like
Actually - no, except that the original files are nearly all on the host computer.
Anyway, I’ve gone for it and the Public share has mounted!!
Yet to test the rest - can I get into the UI etc. but looking good and feeling much better than I have for the last two weeks.
Thanks
Wooohooo! Please keep us updated
Hi,
It seems that I have got a slight problem. I do not have the fsck command on my WD box ?!?!?!
After the command p, I have got the following:
(parted) p
p
Model: WDC WDC WD20EARS-00M (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 32.9MB 2040MB 2007MB ext3 primary raid
2 2040MB 2303MB 263MB linux-swap primary raid
3 2303MB 3315MB 1012MB ext3 primary raid
4 3315MB 2000GB 1997GB primary raid
Could someone help please?
I am not LINUX savy at all. I thought about using mkfs to set 4 up to ext4, but …
I have done some further investigation, and I have got the following:
/ # e2fsck /dev/sda1
e2fsck 1.38 (30-Jun-2005)
/dev/sda1: recovering journal
/dev/sda1 has gone 1297 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 2683/122640 files (1.8% non-contiguous), 43929/489968 blocks
/ # e2fsck /dev/sda2
e2fsck 1.38 (30-Jun-2005)
Couldn’t find ext2 superblock, trying backup blocks…
e2fsck: while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
/ # e2fsck /dev/sda3
e2fsck 1.38 (30-Jun-2005)
/dev/sda3: clean, 108/61824 files, 8862/246976 blocks
/ # e2fsck /dev/sda4
e2fsck 1.38 (30-Jun-2005)
Couldn’t find ext2 superblock, trying backup blocks…
e2fsck: while trying to open /dev/sda4
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
Not sure if this could help…
Regards.
l_ingenu
Hi
I am having a very similar problem. A few weeks ago my MBL began to restart every now and then with no reason at all. Finally yesterday I was unable to access my data and the device seems to be intermitent. A couple of times I have seen the message that the drive was not accesible and unable to mount.
I managed to update to the latest firmware from the dashboard but it seems things are even worse. I tried to execute the procedure described here but it requires the drive to be unmounted, and when the drive is unmounted I cannot access anything not by ssh or web interface.
I will appreciate any insight
Regards
Alberto
