I found some help about how to do this but (a) it was spread across many different sources and (b) wasn't always accurate, so I decided to post my own HowTo (and How Not To) for the
MBWEII.
- Getting started:
- Connect up the LAN and power cables, and automagically it will turn on
- Quickest way (I found) to get the IP address for your MBWEII is to look at your router's DHCP table (for the sake of this How To let's assume the IP address is 192.168.1.2 but remember to substitute your IP address)
- Point your browser at the Shared Storage Manager admin site @ http://192.168.1.2/
- Do not change the username/password or network settings at this point - it's a waste of time and can in fact cause problems!
- You could, if you want, set up the date/time and location info (General Setup -> Change Current Date and Time)
- I recommend you check firmware updates (General Setup -> Upgrade the System Firmware); mine was up to date (01.01.18)
- Set up RAID 1 on MBWEII: (This isn't required in order to mount it on a Linux box but I recommend it as a way to protect your data)
Note: changing to RAID 1 will format your drives - make sure you backup all your data before starting this process
I also jotted down the Total Space info (from the System Summary box on every page) before I started (953,454,724K) - expect this number to be halved because that's a consequence of going to RAID 1
- Drive Management -> Change Drive Type -> Secure volume (RAID-1) -> Change Drive Type button
It'll check that's you're sure, because it will format the drives and you will lose all your data
- Once it's underway you'll see
Formatting in progress
Please wait while this process completes. If this page does not refresh, please navigate back to the home page...
and then Formatting Complete. Please wait while this process completes. If this page does not refresh, please navigate back to the home page...
In the top right corner you'll also see "Drive Status: Synchronizing"
From the MBWEII User Manual (pg44): Note: Rebuilding the RAID 1 configuration may take up to several hours, but you can begin using the device as soon as the interface is enabled and allows you to start using it (approximately 30 minutes).
Personally I wouldn't start trying to write to the drive until this is done
I don't know how long my 1Tb system took to format - I ignored it for a few hours and it was done by the time I checked back
- The total space should be approximately half (mine says 476,726,416K)
- Remote access via
ssh:
As with everyone else I've seen do this, I used Martin Hinner's hack
- Don't skip Step 1 like I did!
First of all you have to create a new user using standard web interface. SSH will not allow you to log-in as root without password.
To do this, go to File Sharing -> User Management and create a new user - for the sake of this HowTo, I'm going to call the user "newuser"
- Modify the link to your MBWEII admin page by telling it to upgrade from Martin's site, i.e. http://192.168.1.2/auth/firmware_upgrade.pl?fwserver=martin.hinner.info/mybook/firmware.php
(Remember to replace 192.168.1.2 with your box's IP address)
- The first time I tried this I got an error saying the download failed, but I simply restarted the update (i.e. refreshed the page to retry the firmware upgrade)
- This time I saw "Applying new firmware" followed fairly quickly by "Firmware downloaded and applied"
- The upgrade process takes approximately 30minutes depending on internet connection speed and general network activity.
- THE USER SHOULD NOT ACCESS THE DEVICE UNTIL THE UPGRADE IS COMPLETE
- The user must NOT power off the device during the upgrade process.
- The user should NOTE, the front panel lights will
- flicker during firmware download
- extinguish for approximately 15 minutes, whilst applying the firmware
- illuminate when firmware upgrade is complete
As that note says, the status doesn't appear to change even though the page was refreshed every couple of minutes
- To check if
ssh is ready, from a Linux machine's command line:
$ ssh 192.168.1.2 -l newuser
newuser@192.168.1.2's password:
- Make sure the
sshd service will run every time you reboot: add the following line to /etc/inittab:
::sysinit:/usr/sbin/sshd
I also took this opportunity to check the disk space/layout
- While you're still logged in to the MBWEII, reboot to check
sshd is setup correctly:
# sync && sync && reboot
(I found I had to disconnect from the remote session quickly or my local telnet session hung, waiting for a response from the MBWEII.)
- Some people recommend disabling Mionet but I left it enabled - I haven't had a chance to see how our Windows machines would be affected by removing it
- File transfer (FTP) configuration:
- Set up
vsftpd as per Edouard Brière's notes but the filename is wrong - the command should be wget ftp://ftp.penguin.cz/pub/users/mhi/mybook/vsftpd.tar.gz -q -O - | tar xzvf - -C /
- I also personalised "ftpd_banner" (in the config file) and then connected via gFTP to check it's OK
- Setup an "Alternative Web Interface":
- Again I followed Martin Hinner's instructions
He warns not to interrupt the first step but I found they all completed very quickly
- Remember to change the password in /etc/httpd.conf
-
sync && sync && reboot
- Check that both the standard WD admin page (http://192.168.1.2/ or http://192.168.1.2:80/ if you want to be explicit) and the "MyBook webif management interface" (http://192.168.1.2:8080/) are both available
- Mount the MBWEII share on a Linux server:
I saved the hardest step for last!
For this step I'm assuming the hostname for the MBWEII is "mybook" and that you want to mount it as a local directory called /mnt/mbwe2 - you can of course change these as you want but be sure to change it consistently in the steps below
- On the MBWEII:
# echo /shares/internal/PUBLIC 192.168.1.0/255.255.255.0(rw,no_root_squash,sync) >> /etc/exports
[Note: adjust the IP address accordingly - this allows any machine on my LAN to connect but you can specify individual IP addresses or host names]
# modprobe nfsd
# portmap
# rpc.mountd
# rpc.nfsd
# rpc.statd
# rpc.lockd
# exportfs -ra
# exportfs
/shares/internal/PUBLIC 192.168.1.0/255.255.255.0 - On the Linux serer:
# mkdir /mnt/mbwe2
# mount -t nfs mybook:/shares/internal/PUBLIC /mnt/mbwe2
# df -h /mnt/mbwe2
Filesystem Size Used Avail Use% Mounted on
mybook:/shares/internal/PUBLIC
455G 2.2G 453G 1% /mnt/mbwe2 So now that info can go in /etc/fstab: mybook:/shares/internal/PUBLIC /mnt/mbwe2 nfs rw,noauto,user 0 0
- check it's OK:
# umount /mnt/mbwe2
# mount /mnt/mbwe2
(to use the info from /etc/fstab rather than the command line))
# touch /mnt/mbwe2/x
# ls -al /mnt/mbwe2
(you should see an empty file called "x") - setup backups from the Linux box:
$ rsync -aq ~ /mnt/mbwe2 &
(Once I checked it was backing up OK I copied that command to my crontab file.)
Easy! :)
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
henman's journal
- How To Create and Restrict Access To Sub-Folders?
# cd /etc/init.d# ./mionet.sh stop
Stoping mionet
Shutting down monitorCVM:
Shutting down changeNotifySocket:
iNotify is not running...
Shutting down MioNet:
MioNet is not running...
Verify: Now monitorCVM is Not running
Verify: Now changeNotify is Not running
Verify: Now Mionet is Not running
#
To stop it permanently:
# cd /etc/init.d# mv mionet.sh mionet.sh.disabled
#