I've installed it and got it all running, but there's a few things that I can no longer do from the web interface.

1) In the drive management tab, I cannot change the drive type from Secure Volume (Mirrored) to Single Large Volume. I get the error "The drive is currently busy. Please stop using all shares and try again." even though there are no shares active. I've changed the drives IP Address, rebooted and shut down Samba, and still I still get this error.

2) I cannot update firmware from the web interface. The Get In Test fails and I can't install the feature packs, for example. I get the error “It appears that one of your drives is faulty or in an inconsistent state. Please make sure your drives are OK before retrying.” when I try. To fix this I was going to reformat the drives, by changing the raid type and changing it back again, but as above, this isn't possible. I'm pretty certain that there is nothing wrong with the drives. This is a new drive and the status says that both drives are healthy.

I'd go back to the original software if I could, but alas, the drive won't let me update the firmware.

I'm going to give the manual firmware update a go tomorrow unless anyone has any ideas how I can fix this.

unfortunately, the File Sharing tab of the web interface just throws up an error:
Error Code:: f00020

Failed to change file permissions

Please try again

so, I was wondering if there's anything special I need to do to set up my shares, permission wise, and such. I'll just dig into my memories for samba configuration

But I realized that I am using the customer firmware here along with the bluering feed. Wouldnt I need to build things with a tool set that was used for this and not the gumstix toolset?

On a sidenote while trying to follow the gumstix toolchain setup, I am running into an issue. It looks like a file it wants is not longer offered.

 Retrying from gumstix alternate site... --2009-09-02 22:07:26-- http://files.gumstix.com/binutils-2.17.tar.bz2 Resolving files.gumstix.com... 66.33.219.249 Connecting to files.gumstix.com|66.33.219.249|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2009-09-02 22:07:26 ERROR 404: Not Found. 

IMHO isn't WOL just a parameter compiling the Network interface into the kernel ?
i think i read that in another forum…

are you able to check that ?
it would be a great benfit for a lot, i suggest

thx
Big11

The backup I did of my system config didn't contain one originally, so I have nothing to restore, hower I'm still getting the "sudo: must be setuid root" error. Also visudo does not work. Is it OK to edit this file with nano?

I tried to install the alternative FW v.3.0 to my MyBookWE. (v.2.00.18)

after end of the install prcess (MBWE rebooted) i couldn't have access to the WebIF, but i had acess via SSH (root/welc0me)

As i found by starting lighthttpd manually ther was no lighthttpd.conf file available (!?)

Any suggestions what was wrong ? Can anyone explain my (probably by a list) what the Advantages of this FW are ?

thanks
Big11

Just wondering, is anyone interested in moving twonkymedia server to mbwe blue ring?
I know the "white light" edition has twonky installed, but not "blue ring".
Can twonky be integrated in the firmware for "blue ring"?

Now if only transmission would stop crashing on me :(

It's some sort of a libevent-related bug: http://trac.transmissionbt.com/ticket/2078

Not necessary, but would be good for future upgrades.

Now if only transmission would stop crashing on me :(

Regards,
Alex

Thanks for noticing this issue,
Alex

Gameboyy

Alex

Any idea? thanks again

 /shares/internal/PUBLIC/WWW/Admin/SetWebUser.sh,\ 

Regards,

I'm just clueless, any help would be great, thank you.

 # Write a new mDNS responder config file echo "\"$current_hostname user if\"" > $mDNSconfig echo "_http._tcp. local" >> $mDNSconfig echo "80" >> $mDNSconfig echo "$current_hostname file server user interface" >> $mDNSconfig for FILE in `ls ${mDNSconfig}.d 2>/dev/null` do if [ -f ${mDNSconfig}.d/${FILE} ] ; then cat ${mDNSconfig}.d/${FILE} >> ${mDNSconfig} fi done 

 MyBookWorld AFP _afpovertcp._tcp. local 548 MyBookWorld AFP server 

And I'll just tune upgrade script to preserve /etc/mDNSResponderPosix.d folder at upgrade time

P.S. Sorry for double-posting - it was an accident…

 # Write a new mDNS responder config file echo "\"$current_hostname user if\"" > $mDNSconfig echo "_http._tcp. local" >> $mDNSconfig echo "80" >> $mDNSconfig echo "$current_hostname file server user interface" >> $mDNSconfig for FILE in `ls ${mDNSconfig}.d 2>/dev/null` do if [ -f ${mDNSconfig}.d/${FILE} ] ; then cat ${mDNSconfig}.d/${FILE} >> ${mDNSconfig} fi done 

 MyBookWorld AFP _afpovertcp._tcp. local 548 MyBookWorld AFP server 

And I'll just tune upgrade script to preserve /etc/mDNSResponderPosix.d folder at upgrade time

It is good just having the ability to write to ntfs if necessary. Most of my drives are ext/hfs so ntfs support is just a nice-to-have.

For future versions can you retain settings in mDNSResponderPosix or comment out the necessary lines in update_network_config.sh as described here: http://mybookworld.wikidot.com/forum/t-106007/netatalk-tutorial .

Thanks for you hard work, will report back any issues that I notice.

Alex

 # ipkg install util-linux-ng # rm /bin/mount /bin/umount # cp /opt/bin/util-linux-ng-mount /bin/mount # cp /opt/bin/util-linux-ng-umount /bin/umount # ln -s /opt/bin/ntfs-3g /sbin/mount.ntfs-3g 

 # ln -s /sbin/mount.ntfs-3g /sbin/mount.ntfs 

P.S. Unfortunately, the speed is really low, less then 1 mb/sec, due to weak CPU :(

Upgrade worked without issue.

ntfs write support seems to work fine. Mounted the disk manually using fuse, but how do I get it to mount using fuse automagically when it gets plugged in. I assume it involves playing with fstab. But does anyone want to hold my hand so I don't brick something?

Cheers!

Regarding WOL support, it's not enabled by default and I haven't got the slightest idea how to enable it (or if it's possible at all) - there's no BIOS in MBWE for you…

Cheers,
Alex

Thx for your information. Question: where can i find the "new" firmware V2 and some more informations about.

Any chance to get also WOL (WakeOnLan) in the new "Firmware" V3 ?

should i wait a couple of days till release of V3 ? or would it takes longer ??

Big11

UPD: I also enabled writing support in the ntfs module - we'll see whether it works or not

Thanks for your interest,
Alex

 # wget http://mybookworld.wikidot.com/local--files/optware/setup-optware.sh # sh setup-optware.sh # sed -i -e s/gumstix1151/mbwe-bluering/ /opt/etc/ipkg.conf 

The feed is more or less tested now, but before updating the howto it would be nice to have more people test the ldso-enabled firmware to mention it there too.

Cheers,
Alex

First: Sorry for my english but it is not my native language.

Second:
How can i install optware with the new feeds as decribed, on my MBWE-blueRings ?

can i do that is in the installation Guide - second option: "Alternatively, run following commands one by one:"
replacing the Path of the "gumstick" packages with the new "mbwe-bluering" ?

thanks a lot for your support

Big11

UPD: On the other hand, feel free to use this howto to fix this yourself after installing the FW

Cheers,
Alex

If I have a two 2 mbw, do I need to do this on both disks?

Regarding cyrus-sasl, this is not an LDSO_RUNPATH issue. This should fix the problem:

 # killall saslauthd # ipkg install cyrus-sasl -force-reinstall 

I've tried adding /opt/lib/sasl2 to /etc/ld.so.conf and running ldconfig, but I still get the cyrus-sasl errors every time i install a package.

@alllexx: what do you mean by " replace conflicting stock libs (like ncurses with dialog) with optware ones"?

As you can probably tell, I'm a newbie in the linux space.

Thanks!!!!

What other packages were not previously working? Happy to test, but honestly I only ever use transmission and mt-daapd.

but for no apparent nfs is acting weird, gonna look into that later. (might not be related to all this) using fw 2.18. seems like some dns issues. hah, i got it, there was no hostname assigned in my router for mbwe so it got stuck when looking for it's name although i have it in /etc/hosts …. go figure ..

I am also not looking to to update my uclib, mainly cause I don't have the spare sata ports.

Each time I install a new package the cyrus-sasl post install script tries to run:

 Configuring cyrus-sasl Please read the man page of saslauthd and check settings in /opt/etc/init.d/S52saslauthd If you dislike the link /usr/lib/sasl2 -> /opt/lib/sasl2 then you may want to set SASL_PATH instead (re)starting service saslauthd postinst script returned status 2 ERROR: cyrus-sasl.postinst returned 2 Configuring libjpeg Configuring libpng Configuring libtiff Configuring openldap Starting OpenLDAP postinst script returned status 1 ERROR: openldap.postinst returned 1 Successfully terminated. [root@MyBookWorld2TB ~]# 

I'd like to announce that since recently we have mbwe-bluering-specific feed on nslu2-linux: http://ipkg.nslu2-linux.org/feeds/optware/mbwe-bluering/cross/unstable/
The toolchain was built from WD GPL sourcecode using WD .defconfig with additionally enabled LDSO_RUNPATH support in uclibc and should be fully compatible with MBWE bluering.

Why do we need this? Well, did you ever get 'Segmentation fault' errors or had 'ENOTTY (Inappropriate ioctl for device)' for no apparent reason while using optware packages?..

Ok, before updating the wiki howto this feed should be tested. This is one way to do so:
1. Stop any running optware processes
2. Backup your /opt dir

 # tar -czf opt.bak.tar.gz /opt 

 # sed -i -e s/gumstix1151/mbwe-bluering/ /opt/etc/ipkg.conf 

 # ipkg update # ipkg remove libstdc++ -force-depends # ipkg install libstdc++ # ipkg -force-reinstall install `ipkg list_installed | awk '{print $1}'` 

That's it for testing. You can always restore your backup if anything goes wrong:

 # rm -rf /opt # tar -C / -xzvf opt.bak.tar.gz 

The firmware

bzhou:

For optware, the big obstacle on MBWE is the lack of LDSO_RUNPATH in stock /lib/libuClibc-0.9.28.so
This is becoming more and more annoying as you often need to adjust /etc/ld.so.conf

Here's the custom firmware I made for best optware experience on mbwe-bluering:
ldso-runpath-enabled-firmware

An alternative way to enable LDSO_RUNPATH support:

(This is not recommended for unexpirienced/unskilled people as you can easily brick your MBWE if you mess anything up. And don't forget to make backups! It's been tested to work perfectly on my box, but no guarantee of any kind, though)
1. Shot down your mbwe
2. Remove the HDD(s) from MyBook World Edition (PDF Link) and connect to your linux machine
3. Mount first partition (e.g. /mnt/mbwe1)
4. If you haven't made backups - make them now

 # tar -czf /backups/mbwe.lib.bak.tar.gz /mnt/mbwe1/lib 

 # cd /tmp # wget http://ipkg.nslu2-linux.org/feeds/optware/mbwe-bluering/cross/unstable/uclibc-opt_0.9.28-1_arm.ipk # tar -xvf uclibc-opt_0.9.28-1_arm.ipk ./data.tar.gz # rm -rf opt # tar -xvzf data.tar.gz # cp -f opt/lib/* /mnt/mbwe1/lib # umount /mnt/mbwe1