NAS-BASIC45 LANDISK RDC2882

Today released ‘ALPHA, BETA, GAMMA’  download the nasbasic45-69.rar file from the landisk folder.

NAS-BASIC45 firmware with loader 69 

  • BugFixes as released by RDC
    1. Failing renaming file names (CONCEPTRONIC to Conceptronic): solved
    2. Files >4GB could not be deleted: solved
     note: through some tricks the FAT32 formatted HD can support >4GB files !
     (only through LAN)
    3. Problem with writing samba config policy: solved
    4. Problem with writing DHCP client policy: solved
    5. Problem with allowing seek over file size with RAM/FLASH file system: solved
    6. Problem with Disk/Format disk policy: solved
  • Own Bugfixes:
    1. Changed status page html internal code !# became !-#, status page now working again with NAS-BASIC45
    2. Changed html problem with SNTP daylight time saving issue

Known bug:
The internal webserver seems to crash when using multiple times F5 (refresh). (Call it abusing the LANDISK) turn off/on will bring the device back to live. This behaviour I have with the standard generic firmware of RDC as well, so I think it is introduced during BASIC45 and LOADER69.

Together with the firmware RDC released tools for better maintenance of the device

  1. Quick Update Utility
    this utility will search for LANDISKS in your network and you can upgrade them easily.  

Note: this utility allows you to update: LOADER+KERNEL+WEB !

Note: I believe this only works if you have loader 67 or higher cause loader 66 was failing by me.

  1. Configuration Utility
    As F5 can crash the internal webserver (not confirmed by RDC) you can use the 1.1 RDC configtool Note: No Support for Daylight time saving.

please read the whole readmefirst.txt

Comments are welcome

80 thoughts on “NAS-BASIC45 LANDISK RDC2882”

  1. HoBRoB says:

    Hi,

    It seems that you do a lot of technical stuff with these drives, so thats why a drop this qeustion here.

    I have a LanDrive and tried to flash a new firmware into it (had some problems), but during the upload the drive had a hangup, so now I have a drive with a broken firmware. The drive is completly un-responcive. Do you know if there is a way to recover from this.

    Thanks,

    HoBRoB.

  3. RDC designed the LANDISK without any feedback from customers or experts like me (kuch kuch) .. So if you fail in upgrading the device with firmware the device is broken. You have to remove the EPROM and changed it for a new EPROM with correct data. There is no emergency mode or kernel mode.

    As long as the device responds to 169.254.0.1 or any other address you can use the MT.exe file for upgrading the loader again and use tftp for restoring the kernel, but when the device does not react the only possible option is a new EPROM.

  4. XBMC has not been tested by me. I do not have a XBOX
    (surely want one but do not want to spend money on it) but the XBOX media Center: no info about that. Sorry

  6. Hi Andrew

    Yes the firmware is interchangeable with different vendors.
    your vendor (I know where it’s manufactured) is using standard RDC firmware and can work with the firmware I use.

    The tool(s) for creating HTML files I do not send. I want to
    keep some control but if someone is building his own GUI: be my
    guest. I build the firmware for you and test. Why? I can break as many devices as I want cause I have many LAN devices as well as spare EPROM’s ;-)
    Also I do not want to fight with RDC about this ;-)

    Use my HTML, fix it, change it or use utility_use.htm for checking all options available Send me the HTML code and I will create a workable webinterface firmware for you. It’s not rocket science, but I messed up sometimes due to incorrect parameters.

  7. Andrew says:

    dennis,
    Thanks for your quick answer.
    Are you sure that all devices can share firmware versions?
    I’m asking you again because some devices have more leds, fans etc.
    Are you saying that I can use any vendor’s firmware or only yours?
    Is there anything i should watch out for when using other firmware? E.g.chip type?
    Also, do you know any pinouts on the board that can be used to flash it in an emergency situation? I’m experienced in electronics.

    Thanks, and sorry for bombarding you with my niewby questions.

  8. > Are you sure that all devices can share firmware versions?
    Yes, cause RDC does the firmware development themselves
    Prohubs in Taiwan does the distribution of that stuff to all their contacts. (they sell the chipset)

    > I’m asking you again because some devices have more leds, fans etc.

    Does not matter. when using NAS-BASICxx with Loaderxx you can use all kinds of firmware.

    > Are you saying that I can use any vendor’s firmware or only yours?

    Any firmware you want. If you do not like my HTML GUI, choose another one.

    >Is there anything i should watch out for when using other firmware? E.g.chip type?

    Nope. Not that I am aware of.

    > Also, do you know any pinouts on the board that can be used to > flash it in an emergency situation? I’m experienced in electronics.

    As explained before: there is no memory or space for Kernel Mode / Emergency situation. Means, if you break the device than the Flash EPROM is corrupted. Only a new flash chip with basic-firmware can help you.

    > Thanks, and sorry for bombarding you with my niewby questions.

    Finally someone is using the comment system ;-)

  9. michael says:

    Hi,

    I’ve a little problem using this version. Connected to LAN I try to rename a file like this: “test.jpg” to “Test.jpg” – but the drive did not recognize the big “T”. After renaming it was named as “test.jpg”…. ?? Now I’m a little confused – using the FirmwareBasicNAS-v45.bin the renaming works. What’s wrong?

  10. I do not follow Michael. I renamed an MP3 file from blablabla.mp3 to TEST.MP3 to test.mp3 no problem when accessing / renaming the device through \\disk1\PUBLIC\

  12. andrew says:

    One problem I have though, is that the hardware reset button is not working. I’m not sure if I had the problem before, but i’ve seen many people that have this problem. Do you have any ideas?
    Thanks

  13. Be happy about the F5 problem I had ;-) let me say that it CAN occur but when how why what is still unknown to me

    Please not that loader69 is needed for correct working! so if VGEAR is not releasing that one, than they are sutipid

    hardwar reset? mm Will check today.

  14. Dennis,
    Thanks for your work, I installed the latest firmware in my LanServer and its seems very stable now, nice GUI too.
    The only things I notice are that applying passwords to multiple folders seems to be a bit hit and miss & once a folder is created in SMB then it can’t be deleted except by formatting the drive.
    Also has any one managed to use patitioned hard drives as I heard you can only use less than 32.0 gig partitions but i haven’t managed to get that working.

    Regards

    Paul

  15. andrew says:

    Dennis,
    do you think it is possible to add cgi scripts in order to make a small download manager?
    What else can you configure that we can’t?
    Andrew

  17. Paul,

    you found an issue in my HTML GUI ;-)
    I see that the base firmware has the delete function on SMB
    Let me check to see if I can release a new web-firmware.

  19. Julien says:

    I can confirm that v45 does not work with XBMC over SMB. You can navigate certain folders and sub directories, but it will not open any folder that has files inside.

    Browsing by FTP work fine though, although fast forward and short/large skip doesn’t work too well (this is an XBMC issue, not LanDisk).

    v41 is the only firmware I’ve been able to get to work with SMB and the latest build of XBMC. I’ve seen reports that older XBMC builds from April 06 work fine with any firmware.

    I might have to turn on logging and submit a bug to the XBMC crew.

  22. HoBRoB says:

    It has the RDC R2882 and Actrans AC39LV040 chips on there, i think one of these holds the firmware and needs to be replaced.

    Thanks,

    HoBRoB.

  25. whilst looking through the RDC website that some where on was information for a simple JTAG like device and I suspect this could be used for recovery purposes.

  26. EN29LV040A
    -70JCP
    158A04B
    05400DA

    maybe I will brick one myself cause I think that no devices will be bricked when using 69 .. but than you need to be using 169.254.0.1 and use tftp. but that is something I will check when I have time

  28. Troy,

    the FAT32 trick is like this (I have no working sample now on hand) but see it as this:

    when a file is transferred through LAN the device detects the data >4GB.
    On the HDD there is made a Folder with the name of the file
    in that folder there is a filenam 001 and a filename 002
    than there is a reference file on the HDD placed (somewhere and readable by the LANDISK) where is stated what the start/end addresses are

    So than when retrieving that file again file 001 and 002 are put back together with the name of that folder ..

    It’s neat simple trick. So actually the file stored is never >4GB
    but cutted into 2 pieces

  29. HoBRoB says:

    Dennis,

    I cross reverenced both types and the should be interchangeble, but the chip you have, contains it already the firmware ???, if not changing it will not solve the problem, I think.

    HoBRoB.

  30. of course I have it with firmware ;-) Not the latest .. but I have them ;-)
    I see you are in the lowlands? Send me your mail addres and I sent you one ;-)

  31. troymclure says:

    Thanks for clearing the 4 gb stuff out for me.

    What’s the difference between loader 67 and 69?

    I have NAS-BASIC45, LOADER 67

  32. to be honest; I have no clue what is the difference between those loaders. But I think it has to do with the behaviour of the device ..
    it’s not stated in the manual or release notes what the loader does.

  34. Val3r10 says:

    Hello. I tried uploading rom100_2m.bin by quick_upgrade.exe tool.
    After shutting off and on, my landrive IS NOT SEEN any more on the network, and my router only sees a fake Mac address like this:
    06:07:08:09:0a:0b

    Is there any recovery procedure ?
    Nothing seemed wrong, but I can’t manage to upload anything else because the drive hasn’t an IP address any more.

    Neither the reset button does anything…

    PLEASE, HELP!

    Thanks anyone

  36. Clem says:

    Dennis, I have a LanServer that I purchased several months ago. It’s worked perfectly the entire time. However, being a PC Consultant and “tinkerer”, I always like to have the latest version of software and firmware for my hardware. I tried googling NAS-BASIC41 (current firmware on my LanServer) and LanServer and found several sites that list firmware for LanDisk with specific warnings about LanServer. My question is can I use your version of the firmware on my system or will it crash the LanServer making it no more than a paperweight? Also, you mention procedures on this site. Where are they and how can I find them?

    Thanks in advance…

    Clem

  37. The experience is, Clem, that you can use it, but always at your own risk. My landisks have had many ‘brandnames’ with various versions of firmware. the most important part is that you have the 2882 RDC chipset. If you have the older 2881 (ie. CompUSA has one) than do not even try it.

  38. Hello,

    I’m really grateful, I picked up a NAS enclosure yesterday and it was a bit of a pain. It kept dropping off the LAN when I put it under pressure (i.e. copied files to it!).

    Your work lead me to a solution – thank you, thank you, thank you.

    Martin

  39. daffyduck says:

    is it possible to change the eprom, because the device will not update anymore (tftp, mt.exe) are not responding.

  42. Gulli Baer says:

    Hi Dennis,

    first of all good work to get everything together, i think this should be done on some other pages as well.

    Now to my quick question:

    Is it not possible, that the smb share will be mounted for different users, so that you can specify that e.g. user1 has only read permission and user2 all permissions for the same folder ?

    Is there any instruction available, on how to change the webGUI or to modify the kernel ?

    Thanks for any answer

    Happy new year to everyone ;-)

    Gulli Baer

  43. Gulli, the kernel cannot be modified as it is closed source by RDC
    the GUI you can change if you want, but not in feature way.

    the features you want are impossible and may only be used with devices running Linux which is the RDC not having. So means that it is very limited in the usage of various settings

  44. Gulli Baer says:

    thanks for that answer.

    this is a shame, that this is not possible, so i think the only way i can do it, is to use an specified extra PC with linux.

    what a pity !

    But anyway, if you have smb support, it should be possible, maybe i need to try to contact the support of RDC ;-)

    have a nice evening

    Cu
    Gulli

  45. Mike says:

    I have the loader issue but have no webinterface and during the other update keep getting a bind:mbad file descriptor errono=9 message.

    Any Suggestions, (CHD3LAN)

  46. probably your system is on an incorrect IP address
    the device is running at 169.254.0.1 your system 169.254.0.2 than trying all tips what is here avail on the site.

  47. Hi Dennis,

    I’ve got this LAN Server, just got it last week. Problem is that I can see my HDD via the USB connector on XP but via the unit WebGUI, it’s says No Disk information. This is my first time trying this type of LAN Server, what could be the problem here.
    I used a 80GB WD HDD formatted to FAT32, 1 Partition.
    Here are the details of the unit.

    LAN Server Model DX-3535
    Firmware: NAS-BASIC41, LOADER 067
    Chipset: RDC R2882-G

    Would a firmware/loader upgrade solve this problem? Would you have any other suggestions?

  48. Hi Dennis,

    Sorry to bother you abt my previous question. I managed to solve the HDD unable to be detected problem. Anyway, perhaps you could let me know if there is a need for me to update the Firmware/Loader. Is it gonna improve anything at all?

    Thanks
    Cheers
    Tharma

  49. Stefan says:

    Hello!
    Great stuff, what you are doing! I just got a No-Name-NAS, and due to being a fan of modified firmware, i found your site! Nice!
    Unbelieveable what some guys are doing…:)

    Do you have an Idea, how to get “into” the box via Telnet? Is there a Linux running?

    Thanks an greetings from Nürnberg,Germany
    Stefan

  50. device is not running Linux but an RTOS alike OS
    there is 1 GPL part available in the Source and RDC has released the source for that, there is no room for Telnet.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.