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!
If you get an error that the superblock is invalid and has a bad magic number when you run the fsck /dev/sda4 command
Try this command to see if your superblock is corrupt
fsck.ext4 -v /dev/sda4
I believe backup superblocks for /dev/sda4 are stored at
65528, 196584, 327640, 458696, 589752, 1638200, 1769256, 3210872, 5307768, 8191000
Now to restore a backup superblock
e2fsck -b 65528 /dev/sda4reboot
Now try the command in step 3 again to fix the filesystem
If the command again complains about a bad superblock repeat the steps, but restore a different backup superblock
e2fsck -b 196584 /dev/sda4reboot
Now try the command in step 3 again to fix the filesystem
And on and on…
If you run into any errors, please post the exact errors here and I will try to help