Generic

How to fix you CHD3NET (RDC 2891 LANDISK)

This fix is for those who have a Conceptronic CHD3NET (or any device running RDC’s 2891 LANDISK chipset) and upgraded it to a new firmware but where it did not reboot properly: here’s the tip how-to restore the firmware especially when your firmware upgrade failed and you are only able to ping to the NAS.

Other features seem unusable to start: the web user interface at 169.254.0.1  cannot start and TFTP functions are also not functioning (RDC does not support Telnet) so it seems you are now the ‘proud’ owner of an USB storage device!

Here’s are the steps how you can try to fix your bricked LANDISK with RDC 2891 chipset:

1) Download the latest firmware
2) Download this file
3) unzip this file somewhere on you harddrive and browse to the ‘Utility Tool’  Directory. Execute Scan ip.exe and perform a scan, after a moment your NAS will be found by the program.

4) Select the NAS from the list and press the SETUP NAS button, you might get some error message but just ignore them. Now you’ll entered a menu where you’ll be able to download new firmware to the NAS.

5) Browse to the directory where you saved the .bin firmware and upload this to you NAS, afterwards you’ll need to reboot and back is you WebInterface

Thanks to Emiel Kosse

Uit de RSS feed

De redactie van NU.NL maakt er een potje van ..

Volgens mij zijn dozen van karton en is iets van hout een kist …….

Eerst schrijft NU.NL

Amerikanen sluiten Irakezen op in houten kisten
WASHINGTON – De Amerikaanse bezettingsmacht in Irak sluit recalcitrante Iraakse gevangenen staande op in houten kisten die amper groter zijn dan de Arabieren zelf en soms kleiner zijn dan een telefooncel.

Dan een wijziging door de redactie, een kist is nu ineens een doos geworden ..

Amerikanen sluiten Irakezen op in houten dozen
WASHINGTON – De Amerikaanse bezettingsmacht in Irak sluit recalcitrante Iraakse gevangenen staande op in houten dozen die amper groter zijn dan de Arabieren zelf en soms kleiner zijn dan een telefooncel

En dan het uiteindelijke bericht: waar we nog steeds een houten doos hebben maar waarin de telefooncel als voorbeeld weggehaald is.

Amerikanen sluiten Irakezen op in houten dozen
WASHINGTON – De Amerikaanse bezettingsmacht in Irak sluit recalcitrante Iraakse gevangenen staande op in houten dozen die amper groter zijn dan de Arabieren zelf.

Leuk, het neuken van mieren .. ;-)

CH3SNAS: Firmware 1.04RC3

After listening to users of CH3SNAS I finally present you the 1.04RC3 which will be released on the official webpage soon as 1.04-0627 version

Release notes:

In this release we have fixed a number of issues needed to be fixed for an official release:

(this release is about to be released through the official channel as wel as official supported download)

  1. http://ch3snas/server.pem & http://ch3snas/etc/shadow can reveal information: fixed
  2. Certain UPnP Devices (Like PlayStation 3) could only browse but not play content: fixed
  3. Files > 2GB could not be played entirely: should be fixed
  4. Issue with mt-daapd when using bonjour tool: Partly fix: we only support to see the status. New features needed can be proposed and if useful, we can try to add.

Please reset your device to factory defaults after upgrading to have certain scripts work properly. Without resetting to factory defaults I cannot guarantee any option to work properly.

Download the 1.04RC3 file here.

CFULLHDMA: Beta 1.09.14

Announcement:

v1.09.14

  • 1. Solving the artefact issue on MKV files caused some issues at the On Screen Display: fixed.
  • 2. CFULLHDMA could not work with Twonky Media Server on Music Level due to usage of M3U by Twonky. CFULLHDMA used it as PlayList, Twonky has other purpose for it, so things got messed up: fixed.
  • 3. Issues with playing DVD’s and subtitles. It could not switched correctly (manually) and when selected it did not start at the beginning of the video. Fixed.
  • 4. IMedia entries (like NFS) could not be edited after saving it. Fixed.
  • 5. In the background errors on NFS could be created. An error causes the device to crash: fixed.
  • 6. Files with for instance dvsd codec type crashed the codec engine: dvsd is not supported, crash fixed.
  • 7. Certain movie files could not played properly (freezing video): fixed.

only available for beta testers (Check your mail. gmail accounts: it can be in your spam mailbox, Hotmail accounts are totally unknown if they get it .. Unreliable email host.

Trying to understand: CH3SNAS & NFS = Help needed !

I’ve written earlier a simple howto for users with a CH3SNAS to work with NFS. UNFS is a user space implementation of the NFSv3 protocol. This is working flawlessly on the CH3SNAS with various Linux PC’s I am running (CentOS, Debian, Linux Embedded device etc.. )

but for a VMware implementation I need the READDIRPLUS procedure which is not available in UNFS. So I need to run Kernel-NFS on the CH3SNAS

Fonz fun_plug is providing Kernel NFS (enabled in the CH3SNAS) and UNFS. Installation is easy and almost fool proof.

The issue is following: on all my linux boxes (CentOS, Debian etc.. ) I get following message:

mount: mount to NFS server ‘192.168.1.60’ failed: timed out (retrying).

  • rcpinfo -p 192.168.1.60 gives all correct info
  • showmount -e 192.168.1.60 gives all correct exports
  • rpcinfo -u 192.168.1.60 gives:

program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting

  • Showmount -a 192.168.1.60 gives the mount points I ‘tried’ to use:

All mount points on 192.168.1.60:
192.168.1.100:/mnt/HD_a2

and even syslogd gives on the NFS server (CH3SNAS):

Jun 12 18:33:07 DEVELOPMENT daemon.notice mountd[1868]: authenticated mount request from 192.168.1.100:615 for /mnt/HD_a2 (/mnt/HD_a2)

  • Portmap is running at server and client!!

I am totally not understanding why I get time-outs. I do not have a firewall, I do not use iptables. Today I tried in another environment the same: always the error:

mount: mount to NFS server ‘192.168.1.60’ failed: timed out (retrying).

suddenly here at home after about 20 minutes trying to mount the NFS share, the NFS server has been mounted on my local system. But when umounting and mounting again I have again same situation. In my work environment it was totally not possible (standard Debian setup and a CentOS configuration) to have the NFS share mounted. Although it is similar setup ..

So although al tools tells me that everything is correct: I am not getting any mount :-(

Is there anyone with enough NFS knowledge who can tell me why the NFS share is not mounted?