Jump to content
XPEnology Community

freud

Transition Member
  • Posts

    6
  • Joined

  • Last visited

Posts posted by freud

  1. Hi,

     

    Of course this procedure was for DSM 4.3.

    For the 5.x release we need to use different release as Trantor said:

     

    4458 and 4482 builds use same source files.

    I don't know what kernel and/or toolchain gnoBoot use, but:

     

    DSM 5.0 and 4.3 use the same kernel 3.2.40.

     

    But toolchains are different:

    4.3 use gcc420 and glibc2.3.6

    5.0 use gcc473 and glibc2.17

     

    You will find some good documentation from Andy here: https://github.com/andy928/xpenology/tr ... umentation

     

    Regards,

  2. Hi,

     

    I'm shocked, did you loose the fact that it's just a challenge and not really legal ?

    How could you criticize the forum or trantor, gnobot, guys that permit to everyone to have access to an excelllent toy (Xpenology) ?

     

    Ok now they don't have really time to work on the new build, that's the life. You are frustated because you have your own data on a dev/hack release of DSM, don't you think it could be more comfortable for you to buy a real syno ? and keep your Xpenology just for backup or to play.

     

    If you want to work for build 4482, you have some good information here: http://xpenology.com/wiki/en/building_xpenology

     

    I not skill in Linux kernel compile but i thing if we are some of this forum to test and work together we could arrive to do a functionnal build.

     

    And once again many thanks to Trantor and Gnoboot for their excellent job :wink:

  3. Trantor wrote:

     

    john_matrix wrote:It should be a good beginning to see what's happening when DSM create the dsm.dat and what are error messages.

    But how to start? somebody can send logs from an impacted DSM for analysis?

     

     

     

    I think the easiest way to do is like we did with 4.3, I repack a minimal 5.0-4482 build with only sata/network drivers so everyone can test/debug.

     

     

     

    Hi Trantor, happy to test on an HP N54L.

     

    Hi,

     

    I will be happy to help too :grin: .

    I have a N54L and could put in place an ESXi if needed.

  4. Hi,

     

    Just update mine, i was in DSM 4.3 update 3 then move to update 4 using this method: http://xpenology.com/forum/viewtopic.php?f=2&t=2049

     

    4.3 build 3810 v4

    ===============

    1. First check if you're able to download update 4 from the GUI (Control Panel, DSM Update) - Download the update.

    - 1a. If not able to download, connect/login with putty/telnet (user: root)

    - 1b. Remove /autoupd@te.info (rm /autoupd@te.info)

    - 1c. Now try to donwload update 4 from GUI again (Control Panel, DSM Update)

    2. Connect/login with putty/telnet and execute these 2 commands:

    Code:

    Select allsed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1

    mv /autoupd@te.info1 /autoupd@te.info

    3. Install the update from GUI (Control Panel, DSM Update)

    =============

     

    Update

    A second option is as follows from user costib who kindy grabbed the update package before it was deleted

     

    His instructions are

     

    To Manually Update to 4.3 build 3810 v4:

    1. Transfer via ftp "autoupd@te.info" and "@smallupd@te_deb" to /volume1/public

    2. Connect/login with putty/telnet and execute these 2 commands:

    cp /volume1/public/autoupd@te.info /

    cp -a /volume1/public/@smallupd@te_deb/ /volume1/

    3. Go to Control Pannel - DSM Update and press the Update Now button

     

    Once done, to update to DSM 5.0 Beta i used method in thread http://xpenology.com/forum/viewtopic.php?f=2&t=2242&start=0

     

    01. Download DSM 5.0-4418 from http://xpenology.trantor.be/xpenology.com/417d8593b25892172333cbd43a428d6a/52e78fb7/XPEnology_DS3612xs_5.0_BETA.7z

    02. Extract files

    03. Burn *.img file with this program https://dl.dropbox.com/u/8476146/qnology/win32diskimager-binary06.rar

    04. Eject the USB

     

    05. Shutdown Synology

    06. Exchange USB Flash drive with new one ( 5.0-4418 )

    07. Power on Synology & DSM will boot normally

    08. Launch Synology Assistant on your second PC

    09. Click 'Search'

    10. If you've done everything correctly you'll see a new 'DiskStation' has been found.

    11. Disconnect the USB flash drive from the Synology for this next step

    12. Right-click on new 'DiskStation' and choose 'Install'

    13. Browse and select the new downloaded version (5.0-4418.pat)

    14. Choose a Name for the DiskStation, a new default admin password and IP configuration

    15. After installation is complete the DiskStation will reboot automatically.

    16. Turn OFF Synology manually now

    17. Isert the same USB Flash drive ( 5.0-4418) back into Synology

    18. Power on Synology & DSM will boot normally

    19. In Synology Assistant click 'Search' again

    20. Depending on the name and network config you chose during installation you will see now a DiskStation has been found with the NAME you chose

     

    Thanks to "interested" to share his experience :smile:

     

    To applied DSM 5.0 Update1 i do same method as for DSM 4.3 U3 to U4.

     

    Enjoy :grin:

×
×
  • Create New...