[Announce] UFS200 v1.0 - Alternative USB filesystem for NAS200 running jac4 or higher

Announcing UFS200 v1.0

About

UFS200 a is full writable USB filesystem for your NAS200 running jac4 or higher.
It provides the same features as jac4 firmware, plus all this new:

• New shell with Busybox 1.15.3 with a lot more and updated applets than the original one
• Rsync support
• Bittorrent support (dctcs + ctorrent)
• aMule 2.2.4
• iSCSI Enterprise Target 1.4.19 (iSCSI support - turn your NAS200 into a SAN)
• VBlade (AoE support - turn your NAS200 into a SAN)
• Midnight Commander 4.6.1
• UnRAR
• Shoutcast support (listen to your music anywhere)
• lighttpd/1.4.23 (ssl)
• PHP 5.2.10 (fastcgi + cli) + extensions (mysql + mssql + gd + etc)
• MySQL 5.0.85
• SQLite 3.6.17
• No-IP DynDns client
• nfs-utils 1.0.10
• Vim 7.2 (with sintax support)
• Terminfo support
• OpenVPN 2.1.1 (routed mode and bridged mode now supported!)
• kexec (load your own custom Linux kernel anytime!)
• OpenSSL 0.9.7e
• Maintenance mode (similiar to "single" user mode)

As jac4, by default, UFS200 will not interfere with the standard NAS200 features provided by Linksys standard firmware.
Almost all the new features comes unconfigured and disabled by default (specially the network services). So you can enable them as needed and also configure them to run at startup by editing a simple file.
If after trying UFS200 you decide not to use it, rolling back is as simple as turning off the NAS200, removing the USB drive and turning NAS200 on again.
UFS200 is not a firmware, it requires jac4 or higher in order to run.


Where to get it

You can download UFS200 v1.0 from here.
MD5: DE6A87733B3078F63C4C65DD4CE70BD4

Running UFS200

To run UFS200 first of all you need:

• One USB flash drive formated with FAT32 and at least 1GB of free space
• Jac4 already installed and running. You can get it from here.
• Some GNU/Linux knowledge (file copying, editing, at least).

Installation steps

1. Download UFS200 from the link above.
2. Unpack the RAR file into a USB drive formatted with FAT32 and at least 1GB of free space.
3. Login as root to your NAS200 already running Jac4 through SSH and execute the following:
   
   
   Code:

   # cd /harddisk/volume_X/conf/
   # cp passwd passwd.ufs200
   # vi passwd.ufs200

   Note: X is a number between 1 and 6 and it depends of your harddisk configuration. For example for RAID1 configuration X=3.
   
4. Edit the passwd.ufs200 file and add this lines:
   
   
   Code:

   mysql:x:15:77:MySQL server:/var/lib/mysql:/bin.newbusybox/sh
   lighttpd:x:16:78:Lighttpd server:/home/lighttpd:
   amuled:x:17:79:aMuled user:/home/amuled:

5. Also modify the line for root user to look like this (except for "WhatEverHashForYourRealPasswordIs"):
   
   
   Code:

   root:WhatEverHashForYourRealPasswordIs:0:0:root:/root:/bin.newbusybox/sh

6. Save and close the passwd.ufs200 file.
7. Back to the prompt, execute the following:
   
   
   Code:

   # vi groups

8. Edit the "groups" file and add the follwing lines:
   
   
   Code:

   mysql:x:77:mysql
   lighttpd:x:78:lighttpd
   amuled:x:79:amuled

9. Save and close the groups file.
10. Upload the file rc.ufs200_boot that comes in the RAR file to your NAS200.
11. Make sure that you put the rc.ufs200_boot file in /harddisk/volume_X/data/rc.d/ directory.
    Note: X is a number between 1 and 6 and it depends of your harddisk configuration. For example for RAID1 configuration X=3.
12. Also make sure that you don´t have more files starting their filename with "rc.". If so, it´s really recommended that you move them somewhere else at least for the first run of UFS200 and until you verify that everything is working as expected with UFS200. Just for the record, the rc.ufs200_boot script is in charge of booting a custom kernel if the user decides to do and also to launch the normal UFS200 startup process. If you don´t need your scripts to run at this precise moment of the booting process it would be better to run them from the /etc/rc.d/rc.local file right after the system finishes the starup process.
13. Shutdown the NAS200.
14. Plug the USB drive to the NAS200 USB port 1 (and ONLY to that port, since it will not boot from the other port).
15. Turn on the NAS200.
16. Enjoy playing with UFS200 and its features.

Enabling and disabling features at startup

You can enable and disable features at startup, easily, by commenting or uncommenting them in: /etc/rc.d/rc.ufs200_services_startup.

Please keep in mind that if you enable or disable a feature at startup, you also need to do it for shutdown and reflect it by commenting or uncommenting the corresponding line in: /etc/rc.d/rc.ufs200_services_shutdown

Notes about some features

Running a custom kernel

With UFS200 you will be able to run a custom kernel image after the normal startup or even on every startup.
UFS200 already provides a custom Linux kernel that you will need to run in order for OpenVPN feature to run in bridged mode. But of course this is also usefull if you need to run a custom kernel image for anything else you can think of right know.
To run your custom kernel:

1. Compile your custom kernel BzImage in another computer and copy it to /boot/ in the NAS200 running UFS200.
2. Make sure that the symlink /boot/vmlinuz point to the kernel image that you want to use.
3. Run /etc/rc.d/rc.kexec_reboot

If you want to make this the default kernel for all your future startups you just need to execute:

Code:

# touch /boot/boot_my_custom_kernel

If you want to go back to the stock kernel, then just:

Code:

# rm /boot/boot_my_custom_kernel

And after the next reboot, the NAS200 will be running the stock kernel.

MySQL Server

UFS200 MySQL server data dir is: /var/lib/mysql .
By default this is symlink to a directory in the same path named mysql.data. It's highly recommended that you move this directory and its content to a harddisk in the NAS200 and then point the /var/lib/mysql symlink to the new path.

Default password for MySQL server (change it ASAP): "admin" (without quotes).

OpenVPN Server

You can run OpenVPN server in two modes:

• Routed mode (default)
• Bridged mode

For further details of each mode please consult OpenVPN documentation.
Regarding UFS200 to run OpenVPN server in bridged mode you need to boot the system with the included custom kernel.
You can do this by executing:

Code:

# touch /boot/boot_my_custom_kernel
# /etc/rc.d/rc.reboot

After the NAS200 reboot you will be able to run OpenVPN server in bridged mode.

To run OpenVPN server in routed mode (default) use: /etc/rc.d/rc.openvpn script.
To run OpenVPN server in bridged mode you should use: /etc/rc.d/rc.openvpn_bridged script.

Midnight Commander

To launch Midnight Commander run: mc200.
Don´t call it directly by running: mc.

Maintenance Mode

Maintenance mode is very similar to "single" user mode in every other GNU/Linux distribution. When you go into "Maintenance Mode" the system will stop almost all running processes, umount the harddisks and remount the root filesystem as readonly.
This can be usefull if for example you want to run e2fsck on a harddisk.

To go into "Maintenance Mode" run: /etc/rc.d/rc.maintenance_mode
To reboot the NAS200 while in "Maintenance Mode" run: /etc/rc.d/rc.maintenance_mode_reboot
To shutdown the NAS200 while in "Maintenance Mode" run: /etc/rc.d/rc.maintenance_mode_halt

What you are not getting with UFS200

I will not support or answer any questions regarding specific configuration of UFS200 features like:

• How can I configure MySQL replication?
• How should I configure NFS server?
• How can I configure virtual hosts in lighttpd?
• And so on

To configure any feature in particular please go to the application website and review it's documentation. And at the end you will always have www.google.com.

I will only answer questions regarding this apps and running them in UFS200, or problems itself.

Known Bugs (you need to read this!)

• The fan control script (rc.ufs200_fan_control) is not working with some HDDs brands. It has problems with: Seagate at least. It can be fixed by changing a regexp in the script or moving from sed to awk. This bug will be fixed in the next release (v1.0.1).
• The fan control script is not working when only one HDD is installed in NAS200. The script needs to be fixed. This bug will be fixed in the next release (v1.0.1).
• When booting to a new kernel UFS200 is not cleanly unmounting the data partition which can lead to a filesystem corruption problem. This bug will be fixed in the next release (v1.0.1).
• If dctcs is stopped with running torrents, the torrents will not be killed. In a reboot process this may prevent the conf or data partition to be cleanly unmounted which can lead to a filesystem corruption problem. This bug will be fixed in the next release (v1.0.1).
• New torrents download added through dctcs will not be reniced. After adding new downloads to dctcs they are not going to be reniced to low the priority of the process on CPU usage. This bug will be fixed in the next release (v1.0.1).
• When connecting a USB flash drive to NAS200 it will not be automatically mounted and shared as expected. This bug is still under investigation.
• The download manager included with NAS200 in some cases is not working. When you add a download to the download manager, it will not start and it will be showed in the list as "Unknown". This bug is still under investigation.

DISCLAIMER
NO WARRANTY OF ANY KIND! Regardless of the contents of this article or any other statements and posts in this forum or elsewhere (or interpretation thereof), I will not take responsibility for anything that happens to your NAS200 or any other hardware, to your software or to your data as a result of your use (or inability to use) this USB filesystem. By initiating a download of any part of my USB filesystem in any form, you acknowledge that you understand that this USB filesystem was developed for my own use, that any support is based on "best effort" (which may vary depending on how busy I am in real life) and that there is no warranty of any kind, not even the warranty that your NAS200 or any other system on your network will keep working or can be restored to working order. If you disagree with this, or if it's illegal to limit my responsibility this way in your area, then you are hereby forbidden to download or use any of the files that I make available.

OPEN SOURCE AND FAIR USE CLOSED SOURCE. The open-source parts of the USB filesystem are licensed under the Gnu Public License (GPL) version 2. The closed-source parts of the software (including the Twonky media server) were copied from the Linksys source distribution tarball, and are redistributed under the assumption that this is a tolerated use of these files. I have no intention of infringing on any rights that belong to Cisco, Linksys, Sercomm, PacketVideo or any other company involved in firmware development for the NAS200. I don't expect to gain any money from this project, actually it has cost me money for hosting and bandwidth. If you are the owner of any of the non-GPL works and you have a problem with me redistributing these files (which are freely available from the Linksys FTP site anyway), please contact me and I will take the offending files off-line immediately.

IF YOU UPDATE THE TWONKY SERVER, YOU MUST BUY A LICENSE. This article provides instructions on how to download and install an updated Twonky server. I do not distribute files for the Twonky server except the redistributed files that are also available as part of the Linksys binary distribution, as well as the Linksys source tarball. I will not take responsibility for any legal problems that you run into with TwonkyVision/PacketVideo because of licensing problems. You are responsible for abiding by the license that accompanies the download. As far as I'm aware of, the Twonky server that you can download from the TwonkyVision/PacketVideo website is not covered by the license agreement that covers the one that was included with your NAS200. In other words, you will have to pay PacketVideo after 30 days (or whenever the trial expires, if applicable) for a full license to the program. I am not aware of, nor have I made any attempts to find, any way to extract and/or reuse any license key or other information that might be stored on-board the Linksys-distributed firmware (neither in the binary distribution nor in the source tarball) to circumvent the need for a license key for the Twonky software that can be downloaded from the Twonky website. I purchased a license key for my own use, and I urge everyone else to do so too.

Hi, I have installed USF200 and I have found some problems:

1) the samba sharing sow only the "public" folder when I try to access as authenitcated user (admin), while in the original firmware it show the "data" folder too

2) I have enabled the fan control at startup but the fan of my nas is always ON

3) I can't start amuled services; if i start from rc.amuled it start but I can find the web interface, if I start from amuled command line it use the configuration in "/root/.amule" and not "/home/.amule" and give me an error. What I can do to configure amule? Where I put the command line to start It when nas boot?

4) I haven't try the torrent application, where is it? Where I put the command to start at boot? How I configure it to download torrent?

Sorry for my english, and thank's for answare!!!!!!!

Hi,

Please check in NAS200 web admin the configuration of your shares. UFS200 shouldn´t have nothing to do with this since in not touching the samba shares configuration of the NAS200 at all.

Please check if this works:

1. Login to your NAS200 through SSH
2. Execute: /usr/bin/Set_Led fan_off
3. Check if the FAN is stopping right after executing this

If YES, then the fan control should work, if NO, then check this thread.

Please remember that almost all features (specially the ones that listen for network connection) are UNCONFIGURED AND DISABLED BY DEFAULT so before enabling them you will need to configure them.

To configure aMule you should edit: /home/amuled/.aMule/amule.conf.
aMule web interface is accessible on port 4711. So once it´s configured and running you can point your favourite browser to: http://NAS200IP:4711/ and login.
Please refer to aMule website and documentation in order to configure it.

Also always use /etc/rc.d/rc.amuled to start aMule because it´s running as a different user (amuled) instead of root.

If you want to start it at startup (which I don´t recommend since aMule takes a lot of resources, specially memory) you can add a line with /etc/rc.d/rc.amule start at the end of /etc/rc.d/rc.local.

The "torrent app" is actually composed by ctorrent and DCTCS. ctorrent is actually doing the "download" job while DCTCS serves as a web interface to control it.
So you need to enable the DCTCS feature.
The startup script is: /etc/rc.d/rc.dctcs.
About how to configure it, you should edit /etc/dctcs.conf, please refer to DCTCS webpage and documentation.

To start it at startup, uncomment the relevant line in: rc.ufs200_services_startup and rc.ufs200_services_shutdown.

Again remember that almost all features (specially the ones that listen for network connection) are UNCONFIGURED AND DISABLED BY DEFAULT so before enabling them you will need to configure them. Also I will not answer questions regarding the specific configuration of the features provided. You should refer to the app documentation at the app website.

About your english, don´t worry is not my first language either.

Thank's jackito,

Why about you I can access the other samba shared folder when i login with admin account? All my subfolder are created with MC unser ssh probably I haven't some permission????

Sorry but I don´t understand the question. Is spanish your first language?
If so, feel free to ask in spanish and I will answer.

No sorry my first language is italian.

I mean that is possible that if i create a folder using mc in ssh shell, I can't see it when i connect with samba because the permission to access at this folder is only for the root user?

For sure it´s possible. Check the permissions of the files and directories that you can´t access through samba.

I completelly agree with Jac. In my case the option is OFF.
And I suggest to everyone else to also turn it off with or without UFS200.

Hi, I have only problem with amule.

When I Start with rc.amule the client seem to be ok but the web interface isn't show.
when I sto pthe service it give me an error that say "killall: amuleweb: no process killed"

Seem that amuleweb is not running, is possible?

Please review the configuration of aMule. Did you configure a password for the web interface? Did you set up the correct path for the incoming and temp dirs? Did you try to connect with your web browser to the right IP and port?

Please search in Google or in aMule´s website I can´t support specific app configuration if I don´t want to go crazy in the way and if I support you on this then everyone else should get the same treatment. Sorry.

there is another erro on the regular expression used for find tempreature in celsius, the new jac4 return:
"194 Temperature_Celsius 0x0022 052 054 000 Old_age Always - 52 (Lifetime Min/Max 0/16)" and the regular expression cautre only the last two char in this case "6)".

and this one is my amule.conf
can you post your without your passoword or with a "default" password.....

[eMule]
AppVersion=2.2.4
Nick=http://www.aMule.org
QueueSizePref=50
VerboseDebug=0
MaxUpload=40
MaxDownload=800
SlotAllocation=10
Port=4662
UDPPort=4672
UDPDisable=0
Address=
Autoconnect=1
MaxSourcesPerFile=300
MaxConnections=500
MaxConnectionsPerFiveSeconds=20
RemoveDeadServer=1
DeadServerRetry=3
ServerKeepAliveTimeout=0
Reconnect=1
Scoresystem=1
Serverlist=0
AddServerListFromServer=0
AddServerListFromClient=0
SafeServerConnect=0
AutoConnectStaticOnly=0
UPnPEnabled=1
UPnPTCPPort=50000
SmartIdCheck=1
ConnectToKad=1
ConnectToED2K=1
TempDir=/home/amuled/.aMule/Temp
IncomingDir=/home/amuled/.aMule/Incoming
ICH=1
AICHTrust=0
CheckDiskspace=1
MinFreeDiskSpace=100
AddNewFilesPaused=0
PreviewPrio=0
ManualHighPrio=0
FullChunkTransfers=1
StartNextFile=0
StartNextFileSameCat=0
FileBufferSizePref=16
DAPPref=1
UAPPref=1
AllocateFullFile=1
OSDirectory=/home/amuled/.aMule/
OnlineSignature=0
OnlineSignatureUpdate=5
EnableTrayIcon=0
MinToTray=0
ConfirmExit=1
StartupMinimized=0
3DDepth=10
ToolTipDelay=1
ShowOverhead=0
ShowInfoOnCatTabs=1
ShowRatesOnTitle=0
VerticalToolbar=0
ShowPartFileNumber=0
VideoPlayer=
VideoPreviewBackupped=1
StatGraphsInterval=3
statsInterval=30
DownloadCapacity=1100
UploadCapacity=80
StatsAverageMinutes=5
VariousStatisticsMaxValue=100
SeeShare=2
FilterLanIPs=1
ParanoidFiltering=1
IPFilterAutoLoad=1
IPFilterURL=
FilterLevel=127
IPFilterSystem=0
FilterMessages=1
FilterAllMessages=0
MessagesFromFriendsOnly=0
MessageFromValidSourcesOnly=1
FilterWordMessages=0
MessageFilter=
FilterComments=0
CommentFilter=
ShareHiddenFiles=0
AutoSortDownloads=0
NewVersionCheck=0
Language=
SplitterbarPosition=75
YourHostname=
DateTimeFormat=%A, %x, %X
AllcatType=0
ShowAllNotCats=0
SmartIdState=1
DropSlowSources=0
KadNodesUrl=http://emule-inside.net/nodes.dat
Ed2kServersUrl=http://gruk.org/server.met.gz
[Browser]
DefaultBrowser=0
OpenPageInTab=1
CustomBrowserString=
[Proxy]
ProxyEnableProxy=0
ProxyType=0
ProxyName=
ProxyPort=1080
ProxyEnablePassword=0
ProxyUser=
ProxyPassword=
[ExternalConnect]
UseSrcSeeds=0
AcceptExternalConnections=0
ECAddress=
ECPort=4712
ECPassword=
UPnPECEnabled=0
ShowProgressBar=1
ShowPercent=1
UseSecIdent=1
IpFilterClients=1
IpFilterServers=1
[WebServer]
Enabled=1
Password=MYPASSWORDMD5ENCODED
PasswordLow=MYPASSWORDMD5ENCODED
Port=4711
WebUPnPTCPPort=50001
UPnPWebServerEnabled=0
UseGzip=1
UseLowRightsUser=0
PageRefreshTime=30
Template=php-default
[Razor_Preferences]
FastED2KLinksHandler=1
[SkinGUIOptions]
UseSkinFiles=0
Skin=
[Statistics]
MaxClientVersions=0
TotalDownloadedBytes=10311102757
TotalUploadedBytes=16403686759
[Obfuscation]
IsClientCryptLayerSupported=1
IsCryptLayerRequested=1
IsClientCryptLayerRequired=0
CryptoPaddingLenght=254
CryptoKadUDPKey=-815723902
[UserEvents]
[UserEvents/DownloadCompleted]
CoreEnabled=0
CoreCommand=
GUIEnabled=0
GUICommand=
[UserEvents/NewChatSession]
CoreEnabled=0
CoreCommand=
GUIEnabled=0
GUICommand=
[UserEvents/OutOfDiskSpace]
CoreEnabled=0
CoreCommand=
GUIEnabled=0
GUICommand=
[UserEvents/ErrorOnCompletion]
CoreEnabled=0
CoreCommand=
GUIEnabled=0
GUICommand=
[Debug]
Cat_General=0
Cat_Hasher=0
Cat_ED2k\ Client=0
Cat_Local\ Client\ Protocol=0
Cat_Remote\ Client\ Protocol=0
Cat_Packet\ Parsing\ Errors=0
Cat_CFile=0
Cat_FileIO=0
Cat_ZLib=0
Cat_AICH-Hasher=0
Cat_AICH-Transfer=0
Cat_AICH-Recovery=0
Cat_ListenSocket=0
Cat_Credits=0
Cat_ClientUDPSocket=0
Cat_DownloadQueue=0
Cat_IPFilter=0
Cat_KnownFileList=0
Cat_PartFiles=0
Cat_SHAHashSet=0
Cat_Servers=0
Cat_Proxy=0
Cat_Searching=0
Cat_ServerUDP=0
Cat_Client\ Kademlia\ UDP=0
Cat_Kademlia\ Search=0
Cat_Kademlia\ Routing=0
Cat_Kademlia\ Indexing=0
Cat_Kademlia\ Main\ Thread=0
Cat_Kademlia\ Preferences=0
Cat_PartFileConvert=0
Cat_MuleUDPSocket=0
Cat_ThreadScheduler=0
Cat_Universal\ Plug\ and\ Play=0
Cat_Kademlia\ UDP\ Firewall\ Tester=0
Cat_Kademlia\ Packet\ Tracking=0
Cat_Kademlia\ Entry\ Tracking=0

Sorry the_goodman but I don´t think it´s fair for the rest if I help you to configure aMule itself. All I can tell you is that aMule is working on UFS200 when is configured the right way. And again I will not support app configuration itself but only problems related to UFS200, basically because UFS200 has a lot of features and for sure everybody can have configuration questions for any of them and I don´t have the time or knowledge about every app to keep answering them.

Fell free to open another thread (since has nothing to do with UFS200), and ask all the questions you have. Maybe somebody has the answer.

Hi,

Can you please run this commands and post the output please?

Code:

root@NAS200 ~# /usr/sbin/smartctl -A /dev/sda | grep 'Temperature_Celsius'

root@NAS200 ~# /usr/sbin/smartctl -A /dev/sdb | grep 'Temperature_Celsius'

Thanks.

Jackito

hi, the output is the one that I have posted up...

"194 Temperature_Celsius 0x0022 052 054 000 Old_age Always - 52 (Lifetime Min/Max 0/16)"

hi, the output is the one that I have posted up...

"194 Temperature_Celsius 0x0022 052 054 000 Old_age Always - 52 (Lifetime Min/Max 0/16)"

Jakito, Where you start the amuleweb command? in rc.amule? with command line?

In my case I have this output:

Code:

root@NAS200 ~# /usr/sbin/smartctl -A /dev/sda | grep 'Temperature_Celsius'
194 Temperature_Celsius     0x0022   104   080   000    Old_age   Always       -       43

Can anybody else confirm that is having the same or similar problem as the_goodman?
If so, please post the output of: /usr/sbin/smartctl -A /dev/sda | grep 'Temperature_Celsius' so I can correct the regexp.

Thanks,

Jackito

amuled is launching amuleweb by itself according to the configuration in amuled.conf.
AFAIK there is no need to start it separatelly.

Jackito

Hello,

I want to install SabNzb on my NAS, but I have a problem because SabNzb needs python.

Can you integrate python on UFS200 ? Or, can it be installed on the NAS and how ?

Thank you.
Djniklos

For sure it helps, I was suspecting that maybe different HDDs will provide a different output. And this seems to confirm it. I got the same output for my two WD drives.
I will change the regexp. In fact I already did it.
Now I must think about how to provide the updated script. Any suggestions?

Jackito

Please add the request to this thread that I specifically opened for new features request.
If more people ask for python probably I will integrate it, if possible.

Jackito

It's possible that any hard disk drive have a different output so we need to change the regular expression to find the real temperature.

I have now a strange problem, when I save with mc200 any changes to any files, It remanin only in ram. If I reboot the nas I lost any changes so I need to reconfigure all from ssh.

Why?
My pendrive is formatted in FAT32......

I know that´s why I asked users to provide outputs from different drives.
For now, Seagate and WD are working with the new script that will be part of UDS200 v1.1.

It´s not strange at all. From your post I guess that you are editing files in /etc.
If this is the case the problem is that you are actually editing files in RAM not in any disk.
This is the list of ramdisk created by NAS200 firmware:

none on /etc type ramfs (rw)
none on /harddisk type ramfs (rw)
none on /tmp type ramfs (rw)
none on /dev type ramfs (rw)
none on /mnt type ramfs (rw)

The content of /etc is more or less a copy of /etc.defaults that the firmware is doing on boot since in the original firmware the root fs is read-only.
Now, you will ask WHY UFS200 keeps behaving like this if now we have a read-write root fs.
The answer is short: because I wanted to modify as less as possible jac4 (and Linksys original firmware) default behavior. Another example of this policy is the fact that original busybox wasn´t replaced at all but instead the new one is used for default shell and some commands that the user can decide by creating a symlinks in the right directories and even doe, this will ONLY affect the user shell and not the system behavior itself.

If you need to do permanent changes to config files, for instance, do them on the "permanent files". They are in /etc.defaults and /etc.links.
This changes will be permanent also after reboot.

Jackito

I've changed to the fan control sed regular expression to s/.* \([0-9]\{2\}\).*/\1/ which should find the last 2 digit number on the line.

Another problem is that the fan control script fails if you don't have two drives installed. The temperature of the missing second drive is returned as an empty string which fails in the comparison later on.

With a bit of trickery pokery I was able to install UFS200 so that it resides on the internal hard disk.

Basically I reduced the size of the sda1 partition by 2Gb using sfdisk (WARNING:not for the faint hearted and this wipes the data directory). In the new free space I created and formatted a 2Gb partition on sda4. I then loopmounted the UFS200 root filesystem and copied the contents to the sda4 partition. A nas200.sh script in conf runs on bootup to mount the sda4 partition and pivot_root to it. UFS200 then boots up without needing an attached USB device.

Hi dsc, can you post your nas200.sh script?

Anyone have a problem with Amule and web interface?

Thanks for the inputs dsc68!
I will add the new bug to the list of known bugs and it will be fixed for the next release (v1.0.1).

BTW regarding the regexp issue, I fixed it by moving from sed to awk.

Code:

| awk '{print $10}'

Thanks,

Jackito

Nice mod!

Code:

#!/bin/sh
/bin/mount -t xfs /dev/sda4 /tmp && cd /tmp && /sbin/pivot_root . mnt && exec /sbin/init <dev/console >/dev/console 2>&1
/bin/echo "Error mounting image file, pivoting root or execing /sbin/init! Starting shell."
        while true; do /bin/sh; /bin/sleep 1; done

Pretty much a straight cut and paste from Jac's init script.

Hi all, I have reat the logfile of amule, and seem that when It can try to load amuleweb, the amuleweb binary canno't be loaded or found...... so amule startup, but can load the web interface....... someone can help me??

Please, someone can help me with regular expression
my string for stop hard disk fan is

"194 Temperature_Celsius 0x0022 052 054 000 Old_age Always - 52 (Lifetime Min/Max 0/16)", with the posted regular expression the string that is find was 16, but the real temperature is 52. How I can acqure the "52"?

Anyone have amule web interface problems? The amuled log tel me that can't find binary of amuleweb. but it is in the same folder of amule.......
Any idea?

I did test this with the Seagate drive I have. It relies on the fact that the temperature is the only 2 digit number in the string and that the first .* will be greedy.

I agree though, awk is the better solution.

Use either the sed expression I provided above or preferably replace the whole sed part with the awk expression jackito provided just afterwards.

However, if your fan is not turning off when the script reckons the temp is 16 then you have other problems. Do you have one or two drives installed? The script as is only works properly when two drives are installed.

To get it to work with one drive add the following between the "Let's get both hdd temps" and "Which on is running hotter?" sections

Code:

  
 if [ "x$SDB_TEMP" = "x" ]; then
          SDB_TEMP=0
 fi

I could have done that but I didn't feel like pulling the drive to put it in another PC. Besides it isn't possible to shrink an XFS file system. Ext3 is a different story as it is resizable and resize2fs is available on the box.

The goal was to be able to install the UFS200 file system on the internal drive so I needed at least 1Gb. Unfortunately jac4 will only mount loopmounted file systems from the conf partition which is too small for UFS200. I guess I could have pulled the same nas200.sh trick to loopmount the UFS200 file system from the data partition but that becomes messy as you have to mount the data partition somewhere and then loopmount the UFS200 file then pivot_root the whole lot.

As I said, sfdisk isn't for the faint hearted (best to use the -N option to change only one partition at a time). Don't know why fdisk isn't there?

One thing I did discover is that the NAS200 doesn't mind if you hotplug the SATA drives. They don't mount automatically but they are accessible. Handy when you screw up the nas200.sh boot script as it allows you to boot solely from the flash.

hi dsc, I have disabled the temp of second hard disk with DB_TEMP=10, so the vaule is < then 16, But If I use the nas 24H probably I need to read the real temperature so I can power on the fan when I really need.
The fan work in fact when I launch from command line "/usr/bin/Set_Led fan_off" the fan turn off, after some second, return On, so I need to relaunch the command.

I Have buy the nas 200 tu use as a small server for amule and torrent files, but I can't use it because amule can't start the web interface, so when I launc it from /etc/rc.d/rc.amuled I can see in "ps" the process amuled executing but I have no web interface for access, ad if I open the logfile in /home/amule/.aMule it thell me that is impossible to find bin of amuleweb.

I can't use ctorrent too because when I try to load a torrent in web interface, it remain as "stop" status, and if I select it and try to Start, It seem not reponding, and reamin in a Stop status.
I have locate the torrent file in my device and after upload the haven't the permission to 777. If with MC200 I set the permission to 777, the status not change and I can't Start the download of my torrent.

This is my status now, anyone have the same problems?

Thank's Giovanni.

hi dsc, I have disabled the temp of second hard disk with DB_TEMP=10, so the vaule is < then 16, But If I use the nas 24H probably I need to read the real temperature so I can power on the fan when I really need.
The fan work in fact when I launch from command line "/usr/bin/Set_Led fan_off" the fan turn off, after some second, return On, so I need to relaunch the command.

I Have buy the nas 200 tu use as a small server for amule and torrent files, but I can't use it because amule can't start the web interface, so when I launc it from /etc/rc.d/rc.amuled I can see in "ps" the process amuled executing but I have no web interface for access, ad if I open the logfile in /home/amule/.aMule it thell me that is impossible to find bin of amuleweb.

I can't use ctorrent too because when I try to load a torrent in web interface, it remain as "stop" status, and if I select it and try to Start, It seem not reponding, and reamin in a Stop status.
I have locate the torrent file in my device and after upload the haven't the permission to 777. If with MC200 I set the permission to 777, the status not change and I can't Start the download of my torrent.

This is my status now, anyone have the same problems?

Thank's Giovanni.

That's what the XFS FAQ says.

Sorry, I stand corrected. NAS200 does have fdisk but it wouldn't work for me - maybe it didn't liked the 500Gb disk.

Yes, just to be clear I was talking about plugging a drive in after the NAS200 had booted. Pulling it out is fraught with danger.

However, I wonder how it would go with RAID 1 mode? In theory it should be ok to pull one of the disks from a running system but I don't know if it has the smarts to respond to a new drive being inserted and start remirroring.

I've just notice that USB drives no longer mount automatically under UFS200. For some reason the USB_Detect process, which is responsible for detecting and mounting USB drives, won't run. Trying to start it manually results in it crashing immediately. As it's a Linksys executable there is no indication of what's wrong.

Could someone else using UFS200 check if USB drives are working on their system?

Hi dsc68 I could reproduce it. :frown:
In my NAS200 I can see this in the GUI:

USB Port 2: Ejected

In the status web page and as soon as the page is loaded the LED for the USB port is turned off.
I didn't face this issue before since both of my USB ports are in use all the time. One for UFS200 and the other one for an external backup drive.
I´m running UFS200 custom kernel, maybe is related.
If you can, try to boot with the stock kernel and check if it is working then. Also if you don´t mind, please verify that this feature was working with standard jac4 firmware probably it will work, but it worth verifying.
I will try to do it also.
Thanks.

Jackito

Hi Giovanni, both features are working for me.
I can´t reproduce your issues.
On the other hand I must say that I found two problems with the dctcs, startup script that are now listed in the known bugs. But any of them are preventing dctcs or ctorrent to work.

Jackito

I found today that the download manager provided with Linksys web gui is not working anymore. The new downloads remain in the list as "Unkown" and they will not start. :frown:
Can somebody else try to reproduce this problem give some feedback.
Also can somebody try this running jac4.
Thanks,

Jackito

I have a second NAS200 running the standard jac4 firmware and the USB function works properly on it.

Thanks a lot for the input!
I think that maybe this is related in some way to the other problem of the download manager that I just reported. Is like some Linksys features just stopped to work.
But what is very strange is that none of UFS200 features are related to them at all.
Can you check one thing please?
Login to the second NAS200 (the one running jac4) and try to run this:

Code:

# /usr/sbin/wget --help

Do you get any output?
Thanks,

Jackito

Download manager is working OK for me under UFS200.

If new downloads show up as unknown then the down_manager process is not running. After a quick look at the internals I suspect there could be conditions where down_manager won't start immediately after a reboot when using a download schedule.

Someone can post the amule.conf and the rc.amule because I can start amuleweb? Seem that it start, bat after few second the process is killed.

Still not working for me. As you mentioned down_manager is not running (I already verified that it is enabled in the web gui).
If I try to run it from the ssh console, nothing happens, no error messages, nothing.
It´s the same behavior that I found when trying to run USB_Detect by hand.
I have no idea what is causing these since a just copied all this files from the original jac4 firmware and nothing was changed that can make them stop working. :frown:

Hi all,

Tonighjt I have resolved my problems with amule.
On My Nas200 the amuleweb won't worlking if is it launched from amuled, if I enable the webserver=1 in amule.conf
So I create the remote.conf in /home/amuled/.aMule, and i have modify the rc.amule to launch the amuleweb too.

Now amule Work!!!!!

I havo only a problem with the fan noise.

When I run the script to power off fan, the fan power off bu after few second the became active again.
There's some other script that is calld from jack4 firmare that re-active fan at specific interval???
Can I disable it?

Thank's!!!!!

I´m glad to hear!
Just one comment. I checked the conf file that you posted and I must say that I found more than one configuration mistake, that´s why I suggested you to check the configuration again at the moment. In my case amule web interface is working without remote.conf file and amuleweb is correctly started by amuled.
Just my two cents.

The fan is automatically turned on by a kernel mod done by Linksys after a few access to the HDDs. Nothing can be done about it, unless you want to mess with the kernel code and Linksys mods to it.

Jackito

Code:

$ wget --help
BusyBox v1.00-rc2 (2009.08.09-23:13+0000) multi-call binary

Usage: wget [-c|--continue] [-q|--quiet] [-O|--output-document file]
                [--header 'header: value'] [-Y|--proxy on/off] [-P DIR] url

wget retrieves files via HTTP or FTP

Options:
        -c      continue retrieval of aborted transfers
        -q      quiet mode - do not print
        -P      Set directory prefix to DIR
        -O      save to filename ('-' for stdout)
        -Y      use proxy ('on' or 'off')

Please verify that in jac4 there are also 2 wget files.
One is a symlink to busybox and it is located in /usr/bin.
But there is another one in /usr/sbin that its not a symlink that in UFS200 is not doing anything when you try to execute it, in my case.
Can you check in jac4 if /usr/sbin/wget is giving you any output and then check the same in your UFS200?
Thanks,

Jackito

jac4

Code:

BusyBox v1.00-rc2 (2009.08.09-23:13+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

$ which wget
/usr/bin/wget
$ ls -l /usr/bin/wget
lrwxrwxrwx    1 root     root           17 Aug 10 08:34 /usr/bin/wget -> ../../bin/busybox
$ /usr/bin/wget --help
BusyBox v1.00-rc2 (2009.08.09-23:13+0000) multi-call binary

Usage: wget [-c|--continue] [-q|--quiet] [-O|--output-document file]
                [--header 'header: value'] [-Y|--proxy on/off] [-P DIR] url

wget retrieves files via HTTP or FTP

Options:
        -c      continue retrieval of aborted transfers
        -q      quiet mode - do not print              
        -P      Set directory prefix to DIR            
        -O      save to filename ('-' for stdout)      
        -Y      use proxy ('on' or 'off')              
$ ls -l /usr/sbin/wget
-rwxr-xr-x    1 root     root       193116 Aug 10 09:21 /usr/sbin/wget
$ /usr/sbin/wget --help
$

UFS200

Code:

BusyBox v1.15.3 (2009-12-16 14:44:57 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.                 

~ # which wget
/usr/bin/wget
~ # ls -l /usr/bin/wget
lrwxrwxrwx    1 root     root           17 Jan 25 10:27 /usr/bin/wget -> ../../bin/busybox
~ # /usr/bin/wget --help
BusyBox v1.00-rc2 (2009.08.09-23:13+0000) multi-call binary

Usage: wget [-c|--continue] [-q|--quiet] [-O|--output-document file]
                [--header 'header: value'] [-Y|--proxy on/off] [-P DIR] url

wget retrieves files via HTTP or FTP

Options:
        -c      continue retrieval of aborted transfers
        -q      quiet mode - do not print
        -P      Set directory prefix to DIR
        -O      save to filename ('-' for stdout)
        -Y      use proxy ('on' or 'off')

~ # ls -l /usr/sbin/wget
-rwxr-xr-x    1 root     root       193116 Aug 10 09:21 /usr/sbin/wget
~ # /usr/sbin/wget --help
~ #

/usr/sbin/wget in neither jac4 or UFS200 appears to work.

Thanks a lot for your feedback.
So I guess my problem is related to down_manager not running.
I can see /usr/sbin/download process running but not down_manager.
And if I try to run it from the ssh console, it´s not doing anything (maybe it´s crashing?) just like USB_Detect.
I´m lost on this. :frown:
Any ideas? Somebody?
Thanks,

Jackito

Jac, as always, great explanation BUT I think that dsc68 has nothing connected to the USB ports on boot, since he already deploy UFS200 to the harddrive and is "pivot_rooting" there. dcs68 correct me if I'm wrong, please.
So in this case I guess USB_Detect should work since during boot the USB drives are all for him.
For me of course is a different story since I'm starting NAS200 with both USB ports in use, as you said.
What do you think jac?

Jackito

Jac, dsc68 already confirmed that this is working for him in UFS200. :frown:
I´m really lost on this. It´s crazy.

There are two wget files in NAS200. One is a simple symlink calling the included busybox binary. That´s working and is located in /usr/bin.
But there is also another one, a complete binary by itself in /usr/sbin. This one is the one that is not doing anything. Also weird...

USB_detect works as it should under jac4 as does down_manager.

The USB_detect problem isn't connected to the USB ports being in use because it fails for me and I am running UFS200 from a partition on the internal HDD - USB ports are all free.

Pivot_root could be an issue - my mount table is all screwy - but USB_detect shouldn't really care.

Code:

/dev/sda4 on /mnt/tmpmnt type squashfs (ro)
/dev/sda2 on /mnt/tmpmnt/mnt type xfs (rw)
/dev/sda4 on / type xfs (rw)
none on /proc type proc (rw)
none on /etc type ramfs (rw)
none on /harddisk type ramfs (rw)
none on /tmp type ramfs (rw)
none on /dev type ramfs (rw)
none on /mnt type ramfs (rw)
/dev/sda1 on /harddisk/volume_1/data type xfs (rw,noatime,nodiratime,usrquota)
/dev/sda2 on /harddisk/volume_1/conf type xfs (rw)

What makes this more weird is that in my case down_manager isn´t working either but it´s working for you both of us running UFS200.
Also I don´t think that pivot_root is the root of the problem.

Jackito

This is the output of mount in my NAS200 running UFS200 from a USB stick:

Code:

root@NAS200 ~# mount
/dev/loop7 on /mnt type squashfs (ro)
/dev/sdc1 on /mnt/mnt type vfat (rw,uid=501,gid=501,fmask=0022,dmask=0022,codepage=cp437,iocharset=ascii)
/dev/loop7 on / type ext3 (rw,data=ordered)
none on /proc type proc (rw)
none on /etc type ramfs (rw)
none on /harddisk type ramfs (rw)
none on /tmp type ramfs (rw)
none on /dev type ramfs (rw)
none on /mnt type ramfs (rw)
/dev/md1 on /harddisk/volume_3/conf type ext3 (rw,data=ordered)
/dev/md0 on /harddisk/volume_3/data type ext3 (rw,data=ordered,usrquota)
/dev/sdd1 on /harddisk/volume_5/data type ext3 (ro,data=ordered)
root@NAS200 ~# 

Jac I don´t think that it is possible to umount them because of pivot_root in place.
Just my two cents.

Jackito

Nope, I can't umount either of them because they don't exist in the current file system.

Unmounting the device unmounts the real mount and not the 'phantom' mounts.

Amule :-( ......

I have moved the Incoming folder and the Temp folder on my hard disk, under PUBLIC diretory.
I have set the chown of the two new folder to "amuled" and the chmod to "777".
When I put something to download the system became slow....
If I enter in ssh and stop amule, the system return fast.
If I restart amule, I can't see the file partially transferred, and If I try to put something other to download, the nas DISMOUNT the hard disk so I can' access to the public directory.

Someone have same problem???????

I have fond a partial solution.
Probably during some shutdown the nas have broken the filesystem on hard disk ,so it can rebuild the file name. I have stoppend any program at startup and I have run a scandisk, after I have restarted amule and is all ok.
Now I want run scandisk every time I boot nas, what I can do????

This is because of the pivot_root.

Jackito

I' having trouble installing UFS200 on my box. I followed the steps on page 1, but I don't seen any changes after reboot (yes with /etc/rc.d/rc.reboot). For example, I don't see /etc/rc.d/rc.ufs200_services_startup, no new processes, etc.

The only installation step I am not sure I did correctly is step 7/8, because in /harddisk/volume_1/conf I have a file named group and one named group.ttt, but no file named groups. I modified both group and group.ttt.

I put the files on a USB key (big enough 4Gb) and they show up on /harddisk/volume_6/data/FLASH_1_1. I also put rc.ufs200_boot in its place and it runs since it creates/updates the log file.

Can you guys help me? I just want to run rsync and I'll be :biggrin:!!

This is because the firmware is not "pivot_rooting" to the USB loop filesystem.
It happened to me several times and I don´t have an explanation for this phenomena. Maybe jac can put some light on it.
As a workaround, what I do (and works for me 95% of the times) is to shutdown the NAS. Unplug the USB flashdrive and unplug the power from the NAS200. Wait 10 seconds, plug the power back, plug the USB flashdrive back and turn the NAS200 on.

Jackito

Maybe adding a "sleep 5" at the beggining of the "/init" script of jac firmware can prevent this?

Jackito

Yeah, I tried and it didn't work. I'll see if I can get my hands on another USB key to try with.

Understood Jac. Maybe I can change ONLY THIS for the guys that wants to go with the USB fs. I mean, only to change this script and recompile your firmware. Then the people can choose if the want to install regular jac firmware or the "5_second_delay_boot_jac_firmware".
What do you think?

OMG This is complicated!! I'll write a script to mount the samba share and do the backup stuff on the other machine, or something.

I finally got around to try it with another USB drive and it works!! I used a 1GB drive instead of a 4GB drive. Must be that that made the difference. Thanks!!

You shouldn't need to use the linksys/sercomm libraries. The format of the flash configuration area is drop-dead simple. The body is an INI file with Unix-style EOL (bare LF), with the first 4 bytes of the file being a 32-bit integer representing the length of the INI file in bytes, and the rest of the config area is padded out with 0xFF bytes. So it literally looks like <32-bit length><INI File><0xFF pad bytes> (to 256K)

Writing it should be a matter of dd'ing it back to /dev/mtd2, but you said that didn't work for you.

configurations not being keeped

hi,

i've got my nas200 running ufs200 and everything is fine but everytime i restart it i've to configure the lighttpd and dcts.

Is there any replication of files that i need to do to keep it always configured (as in the password files for example)?

cumps

Linksys original firmware is making a copy of /etc.default to /etc on every boot. This behavior remains the same on jac4 and UFS200.
So to solve your problem, configure lighttpd and dctcs as needed (or any other app that saves it´s configuration in /etc) and then simply copy those files or directories to /etc.default.

Jackito

Jackito...
New torrents download added through dctcs will not be reniced. After adding new downloads to dctcs they are not going to be reniced to low the priority of the process on CPU usage. This bug will be fixed in the next release (v1.0.1).

How i can solve this Bug? i tried with renice or nice commands.. but nothing changes

thnks

Jackito...
New torrents download added through dctcs will not be reniced. After adding new downloads to dctcs they are not going to be reniced to low the priority of the process on CPU usage. This bug will be fixed in the next release (v1.0.1).

How i can solve this Bug? i tried with renice or nice commands.. but nothing changes
Edit/Delete Message
maybe i'm making some mistakes?

Hello,

After my install with jac4 i am trying to expand this equipment with UFS200.

I have done everything but i don't think UFS200 is starting
What i have done till now

1. Fixed a FAT32 2Gb drive with UFS200 files in it
2. Login as root with ssh in my jac4 ready NAS200
3. Change directory to harddisk volume 3 conf since i can see my files in there with this command "cd /harddisk/volume_3/conf/"
4. Copy the file passwd to a new file passwd.ufs200 with this command "cp passwd passwd.ufs200"
5. Edit passwd.ufs200 file with VI editor with this command "vi passwd.ufs200"
6. Change to insert mode of VI by pressing "i" and adding these lines to the end of it
"mysql:x:15:77:MySQL server:/var/lib/mysql:/bin.newbusybox/sh
lighttpd:x:16:78:Lighttpd server:/home/lighttpd:
amuled:x:17:79:aMuled user:/home/amuled:" and i also modified the first line in this file to this "root:I DIDNTTOUCHTHEHASH:0:0:root:/root:/bin.newbusybox/sh" then i press escape twice to go to command mode of VI and with "ZZ" to save and exit. I opened the file again in VI to be sure i saved it
7. Opened groups file with VI with this command "vi groups" pressed "i" to go into insert mode and added these lines (the file was empty before) "mysql:x:77:mysql
lighttpd:x:78:lighttpd
amuled:x:79:amuled" pressed escape twice to go back into command mode and with "ZZ" i saved it and closed VI
8. Created a folder named "rc.d" in /harddisk/volume_3/data with this command "mkdir /harddisk/volume_X/data/rc.d/"
9. I didn't have permissions to write a file in it so i changed the permissions of the folder to 777 with this command "chmod 777 -R /harddisk/volume_3/data/rc.d" then i did a copy of the rc.ufs200_boot to rc.d directory
10. Shutdown of the NAS200
11. Plug in the UFS200 ready flash drive to USB1
12. Turn on NAS200

Unfortunately i don't think it runs.
My busy box is still v1.00-rc2
in /etc/rc.d/ rc.ufs200_services_startup and rc.ufs200_services_shutdown does not exist will i have to manually create them?
Any ideas?

Thanks in advance

Hi GnFi,

After reading your description of the problem I can quickly think about to possible suspects.

Suspect no. 1 - USB port and device id assignment: Maybe you are connecting the USB drive to the "wrong" USB port? The NAS200 (with the stock kernel and also with the one used by jac´s firmware) is assigning fixed device ids according to the port where you plug the USB driver. So for instance if you plug it to, let´s say USB port 1, then this drive will always be attached to sdc device. If you plug it to USB port 2 it will always be attached to sdd device, even if there is nothing plugged to the other port. So, since jac´s init script is mounting as vfat only sdc1, try to boot the NAS200 with the USB drive plugged in the other USB port (I dont remember right now, which one is always associated to sdc and which to sdd). If changing the USB port doesn´t help, keep reading.

Suspect no. 2 - USB drive "readiness time" (I will bet on this one): USB drives need some time after powering up to be ready for use. Usually it´s a very short time but it can be different between different brands or models of drives. The problem that this "readiness time" generates is that sometimes the drive is not ready for use when jac´s firmware try to mount it so it´s continues with normal boot instead. Here you have two options. First try with another USB drive if you have one. Second do a normal boot, plug the USB drive to the correct USB port (I think port 1 is the right one), login through SSH and execute "/etc/rc.d/rc.reboot" (without the quotes of course). This script will make a proper reboot of the NAS200 and since when rebooting the USB drive will be ready in advance, jac´s firmware should boot from there this time.

Try this and let us know it the problem is solved.

jackito

I really think i have messed something up in the UFS200 installation sir. I am not sure tho what it is. Maybe i did something wrong at the autostart script location? Maybe i shouldn't put it in /harddisk/volume_3/data/rc.d folder? I can see the rc.d folder in my shared folders right now. Is that the right behavior?

This is the output of the "mount" command when the usb is connected at USB1

Code:

BusyBox v1.00-rc2 (2009.08.09-23:13+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

$ mount
/dev/rom1 on / type squashfs (ro)
none on /proc type proc (rw)
none on /etc type ramfs (rw)
none on /var type ramfs (rw)
none on /harddisk type ramfs (rw)
none on /tmp type ramfs (rw)
none on /dev type ramfs (rw)
none on /mnt type ramfs (rw)
/dev/md0 on /harddisk/volume_3/data type ext2 (rw,usrquota)
/dev/md1 on /harddisk/volume_3/conf type xfs (rw,sunit=128,swidth=256)
/dev/sdc on /harddisk/volume_6/data/FLASH_1_1 type vfat (rw,uid=501,gid=501,fmask=0113,dmask=0000,codepage=cp437,iocharset=utf8)

This is the output of the "mount" command when the usb is connected at USB2

Code:

BusyBox v1.00-rc2 (2009.08.09-23:13+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

$ mount
/dev/rom1 on / type squashfs (ro)
none on /proc type proc (rw)
none on /etc type ramfs (rw)
none on /var type ramfs (rw)
none on /harddisk type ramfs (rw)
none on /tmp type ramfs (rw)
none on /dev type ramfs (rw)
none on /mnt type ramfs (rw)
/dev/md0 on /harddisk/volume_3/data type ext2 (rw,usrquota)
/dev/md1 on /harddisk/volume_3/conf type xfs (rw,sunit=128,swidth=256)
/dev/sdd on /harddisk/volume_6/data/FLASH_2_1 type vfat (rw,uid=501,gid=501,fmask=0113,dmask=0000,codepage=cp437,iocharset=utf8)

Trying both ports after the reboot command "/etc/rc.d/rc.reboot" should load it. In my situation it didn't. I am posting the results of the mount command in case that is helpful somehow.
I will try later with a different usb flash disk sir.

Maybe because i am having the hard disks in RAID0 and they are mounted at volume3 is the problem? I am quite blind from this spot. Unfortunately my linux knowledge stops somewhere here.

Also according to your reply the right port to load UFS200 for me is USB1 since on that port it mounts the flash disk at sdc. But not sdc1? maybe force umount it and then mount it at sdc1 and then reboot fix it? I am not sure

First of all, please, don´t call me sir. I´m only 30 and since less than two months ago. :tongue:

After watching the output of mount (it was very helpful) I have two conclusions:

1- USB port 1 is the right port to use.

2- As you mention, now I think the problem is the partitioning of your USB drive that is not going to be solved by mount. Maybe you should try repartitioning it. If you have a computer running GNU/Linux that should be very easy, using fdisk. Just delete all the partitions in the USB drive and create a new FAT32 primary partition no. 1 (you can create only 4 primary partitions in one drive), format it in a Windows machine and copy the UFS200 data back to it. Then try to boot the NAS200 again with the USB drive connected to USB port 1 and let us know how did it go. Also, before doing all this maybe you want to post here the output of "fdisk -l" with the USB drive plugged in.

jackito

sir goes for my respect for all the work you two people have done till now.

We have the same age.

I will try what you have mentioned above and report back as soon as possible. Right now i am not at home.

Anyway for once more really thank for the reply

This is the command "fdisk -l" output

Code:

$ fdisk -l

Disk /dev/sda: 255 heads, 63 sectors, 60801 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1             1     60756 488022538+  fd  Linux raid autodetect
/dev/sda2         60757     60786    240975   fd  Linux raid autodetect
/dev/sda3         60787     60801    120487+  82  Linux swap

Disk /dev/sdb: 255 heads, 63 sectors, 60801 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sdb1             1     60756 488022538+  fd  Linux raid autodetect
/dev/sdb2         60757     60786    240975   fd  Linux raid autodetect
/dev/sdb3         60787     60801    120487+  82  Linux swap

Disk /dev/sdc: 64 heads, 62 sectors, 1011 cylinders
Units = cylinders of 3968 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sdc1   ?    196103    483782 570754815+  72  Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(357, 116, 40) logical=(196102, 51, 11)
Partition 1 has different physical/logical endings:
     phys=(357, 32, 45) logical=(483781, 40, 51)
Partition 1 does not end on cylinder boundary:
     phys=(357, 32, 45) should be (357, 63, 62)
/dev/sdc2   ?     42513    530423 968014120   65  Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(288, 115, 43) logical=(42512, 30, 47)
Partition 2 has different physical/logical endings:
     phys=(367, 114, 50) logical=(530422, 52, 42)
Partition 2 does not end on cylinder boundary:
     phys=(367, 114, 50) should be (367, 63, 62)
/dev/sdc3   ?    471241    959151 968014096   79  Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(366, 32, 33) logical=(471240, 18, 30)
Partition 3 has different physical/logical endings:
     phys=(357, 32, 43) logical=(959150, 39, 39)
Partition 3 does not end on cylinder boundary:
     phys=(357, 32, 43) should be (357, 63, 62)
/dev/sdc4   ?    727239    727253     27749+   d  Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(372, 97, 50) logical=(727238, 12, 25)
Partition 4 has different physical/logical endings:
     phys=(0, 10, 0) logical=(727252, 11, 33)
Partition 4 does not end on cylinder boundary:
     phys=(0, 10, 0) should be (0, 63, 62)

Partition table entries are not in disk order
$

Unfortunately i only have windows vista and windows 7 and they do not let me to delete the partition of any flash disk in disk management. I can only reformat them.
I did try to delete the partition in busybox but it seems that it misses some things and cannot do it. At least giving the command "fdisk /dev/sdc" does nothing.
I did try to format the flash disk in fat23 again in windows with no success. Now i will try another flash disk. The problem is that the new flash disk is 4Gb and i am not sure it will work as intended. Still i will give it a try.

I will also try to boot windows xp in virtual pc through windows 7 and mount the flash usb disk in there and see if i am able to delete the partition there.
Nope neither in windows xp via virtual pc i can delete the flash drive partition.
I really think i have a laptop with redhat & ubuntu in it around. I will try tommorow to find it and will report back using fdisk what it will do.



I think i have success with the 4Gb USB flash drive. It looks you where absolutely right about your thoughts. Now i can recall in my memory that some computers could not even load that particular 2Gb flash drive where others could easily load it. Maybe there is something wrong with it or i might have done something wrong with it.
Anyway i can now see at NAS200 boot that it heavily reads from the 4Gb flash drive. I cross my fingers and hope it will work. If it does i am gona get a new one for that job.

Ohhhhh yes it doeesssssssss. haha thanks a lot for the help mate

Really good news that is working with the other flash drive!!!

From fdisk´s output on sdc (2GB flash drive) IMHO your flash drive partition table is screw...
Just try to repartion it (delete all the partitions and create a new one for FAT32), format and give it another try. Maybe that´s all you need to do to recover it.
If you don´t have any computer with GNU/Linux around you can try with a live-cd with Ubuntu or any other distro. To run fdisk it will be more than enough.

About the fdisk included in the NAS200...nevermind it stinks, you also have sfdisk but is more difficult to use. Right now if I need to do some partition work, I´m always using GNU/Linux fdisk from a live cd.

Enjoy your new UFS200. :biggrin:

jackito

Mate i will try tomorrow to fix it via redhat. I did found the laptop with it.
Right now i am trying to properly configure amule. If i manage to run amule in a box that spends so much less power i will have a much cheaper power bill every month. This is really something i think. All i have to see is if it will run properly.

Next thing is to try and install zoomla in this damn box. After i manage to setup php and mysql. If everything goes well on that too i will build a simple page that will give me a much more nice start page for all the services this box has (ftp server link, amule web server link, and maybe shoutcast link imho??? who knows)
Since my network port 80 is completely free of use maybe this will be the best way for my girlfriend to find all the services she needs.

Right now possibilities seem to be endless or should i say the slow cpu in this box is the end of the road? amule will be quite heavy in the long run i think but all that is left for me is to check it out.
By the way is there any way to comment the amule for autostart but with a big time delay that will give the proper amount of time on NAS200 to start up?
Bah forget it my friend you have done more than enough for everybody following this thread. The 2 gold "jac" people

All i can say is really thanks. I will try to help others by trying to explain some of the configuration files for the services. That is something i can do at least if everything goes well

Damn new busybox has a lot more commands in it to play with. I also can see the directory i am in. That is a valuable information.
By the way is it just my idea or NAS200 running jac4 was more responsive and now with UFS200 it is much much more responsive? It really looks like a much faster equipment. Even NAS200 web interface loads faster.......weird

Well amule runs properly in my own experience. The only downside is that is taking to much memory in the long run that´s why I only start it up when a have a list of links to download. Then I let amule do his job and shut it down.

Well...CPU power as you probably already read it´s a very weak point in NAS200. But as far as you don´t expect too much from it, you will be happy.

Yeah sure. Just modify the init scripts by adding one sleep line to the amule startup script with the amount of seconds you want to wait before launching amule on startup and also modify the services startup script by adding a "&" at the end of the line that launchs amule startup script.

This will be very helpful! Since for now documentation is not a strong point of UFS200 we will be pleased.
For instance I now that some users are having problems with ctorrent+dctcs and I´m 90% sure that they are only configuration related issues. But as I stated in the announcement of UFS200, I can´t start suppporting application configurations, first because I don´t have a lot of knowledge about them (in some cases), second I don´t have the time and third but not less important, I will endup crazy!

I never benchmarked this but now that you mention I can only think about one reason althrough jac can come up with something different and probably more accurate.
Here it goes: the original filesystem of the firmware (and jac´s firmware also) is squashfs. Squashfs is a compressed filesystem and it seems that decompression is made on the fly (jac please correct me if I´m wrong). On the other hand UFS200 filesystem is ext3. So when the system needs to access a file for reading, it just do it, and in the case of jac´s and the original firmware it first must do some on the fly decompression. As far as I know the compressed filesystem use a little bit more than 30% of the same uncompressed filesystem space which is a nice compression ratio. As everybody already knows NAS200 CPU is not very strong so this decompression step can be noticeable and that´s why it seems that running UFS200 is more responsive and faster than the original or jac´s firmware.

jackito

I imagined that especially with mule users like me that likes to have 200+ files downloaded at the same time

I don't expect nothing more that i already have got. I bought it with the knowledge that it is slow. Right now i have already much more that i bought and on a long run of almost 2 years i had a trouble free service. So i expect nothing more than all i have got till now. The later is just extra gifts.

Really thanks for the info. According to these info and a search engine i found much much more. I will try to give a 10 minutes head start to NAS200 boot, before amule even starts.

I still do a little search on amule config file. I am a mule user and most of those lines do not see alien to me. It will not be that hard for me to spend a couple of hours and fix a thread with the config file and an explanation of what every line does. Maybe others supply explanation unknown lines to me too.

Those are valuable information indeed if it does work like that. I am now trying some file transfer and i think i got a minor boost there too. More testing will be needed for that of course, but as i said i know what i have bought from the start.

Right now i feel like a small kid playing with his new toy, i think thats all i can say.