Jump to content
XPEnology Community

squallelf

Member
 View Profile  See their activity

  • Posts

    18

  • Joined

  • Last visited

 Content Type 

Posts posted by squallelf

    DSM 5.0-4493 Update 7

    in DSM Updates Reporting

    Posted

    Nick,

    I don't see any issue with going straight from U1 to U7 although you might need to make sure your boot .iso/usb is 4493 _U7 (not too sure if this is a show stopper or not).

     

    Regarding the magical commands, here is how the update procedure works, as I understand it:

    Downloading (either straight from synology, or manual from a .pat file) creates two files, one is the .pat file, the other is an "Update info" file.

    The .pat file is just a compressed archive, ins some cases the synology will uncompress it to /volume1/@tmp/some directory, in some cases it just downloads the .pat to /volume1/@temp/some_number.pat. Whether the .pat file is uncompressed or not seems to be dependant on how major the update is, but is anyways uninmportant with respect to the "magical Command"

     

    The "update info" file will either just have a string indicating where the uncompressed.pat file is, or a list of each individual update and where they are if the update is uncompressed by the download mechanism.

     

    On a real synology there is a flash memory device, which contains the boot code for the box. This device is updated by a patch called "flashupdatedeb". Since our xpenology boxes don't have a real flash device (this is why we boot from a usb or .iso image), we can't update that device. Presumably the synology update procedure will fail if it cannot update the boot device (obviously the first test for the update procedure is "Where did I boot from?, can I update it? If No, exit".

     

    What the magical commant does is modify the "update info" file named "autoupd@te.info" , changing every instance of "flashupdatedeb" to "flashupdatedeb1" i.e. to an update that does not exist in the extracted directory structure. The sed command makes a 2nd copy of the "update Info" called "autoupd@te.info1, which we overwrite the orginal autoupd@te.info with via the "mv" command.

     

    Fortunately the synology update procedure doesn't do any testing to see if every update listed in the .info file is actually there, so that when you then click on "update" in the GUI, the software then just steps through the updates listed in the info file, ignoring the flashupdatedeb (because it isn't listed) and wordlessly skipping the updateinfodeb1 (because it doesn't exist), but it updates everything else.

     

    On updates that don't include changes to the flashdevice the magical command isn't needed.

     

    The update info file is just a text file, you can look at it with any editor/viewer. The .pat file is just an archive, you can expand it with tar -xvf or 7zip in windows and see what is inside.

     

    Andrew

     

    nice explaination.

    gnoBoot 4458-Update 1

    in General Questions

    Posted

    i tried to download the update

    the @smallupd@te_deb folder contain the following file

    apache-2.2.x-bromolow-bin_2.2.26-4458-s1_all.deb

    dsm-AdminCenter-bromolow-bin_5.0-4458-s1_all.deb

    dsm-bromolow-bin_5.0-4458-s1_all.deb

    flashupdate_5.0-4458-s1_all.deb

    libsynobackup-bromolow-bin_5.0-4458-s1_all.deb

    libsynocgi-bromolow-bin_5.0-4458-s1_all.deb

    libsynosdk-bromolow-bin_5.0-4458-s1_all.deb

    libsynoshare-bromolow-bin_5.0-4458-s1_all.deb

    libsynowireless-bromolow-bin_5.0-4458-s1_all.deb

    lnxessential-bromolow-bin_5.0-4458-s1_all.deb

    lnxscemd-2.0-bromolow-bin_5.0-4458-s1_all.deb

    lnxsdk-bromolow-bin_5.0-4458-s1_all.deb

    php-5.5.x-bromolow-bin_5.5.9-4458-s1_all.deb

    smallupdate_5.0-4458-s1_all.deb

    synocredential-bromolow-bin_5.0-4458-s1_all.deb

    webapi-Upgrade-bromolow-bin_5.0-4458-s1_all.deb

     

    and during update, the following message found in messages log

    Mar 26 16:00:09 NAS updater: updater.c:4890 Start of the updater...

    Mar 26 16:00:09 NAS updater: updater.c:4994 This is X86 platform

    Mar 26 16:00:09 NAS updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:6)

    Mar 26 16:00:09 NAS updater: updater.c:4833 Failed to mount boot partition

    Mar 26 16:00:09 NAS updater: updater.c:5490 Failed to accomplish the update! (errno = 2)

    Mar 26 16:00:09 NAS entry.cgi_SYNO.Core.Upgrade[1].start[30465]: smallupdate.cpp:1017 failed to exec updater -r

    Mar 26 16:00:09 NAS entry.cgi_SYNO.Core.Upgrade[1].start[30465]: smallupdate.cpp:1206 failed to update flash

    Mar 26 16:00:09 NAS entry.cgi_SYNO.Core.Upgrade[1].start[30465]: Upgrade.cpp:202 Fail to apply small update

    Mar 26 16:00:09 NAS cupsd[31198]: [conf.c:1893] Filter "pstoraster" not found.

    Mar 26 16:00:10 NAS synorelayd[31252]: synorelayd.cpp:1221 stoped

    Mar 26 16:00:10 NAS isccore: synocomm_types.c:268 szName eth0 192.168.1.100 is Active

    Mar 26 16:00:10 NAS isccore: synocomm_types.c:268 szName eth0 192.168.1.100 is Active

    Mar 26 16:00:11 NAS iss: synocomm_types.c:268 szName eth0 192.168.1.100 is Active

    Mar 26 16:00:11 NAS iss: synocomm_types.c:268 szName eth0 192.168.1.100 is Active

    Mar 26 16:00:15 NAS avahi-daemon[30909]: Failed to add service 'NAS' of type '_http._tcp', ignoring service group (/usr/syno/avahi/services/http.service): Invalid record

    Mar 26 16:00:16 NAS avahi-daemon[31653]: Failed to add service 'NAS' of type '_http._tcp', ignoring service group (/usr/syno/avahi/services/http.service): Invalid record

    unable to install DSM4.3-3827 update 1

    in Archives

    Posted

    I set the DSM only shows the major update. Yesterday the update apps shows a major update of DSM4.3-3827 update 1

    however, with gnoboot 10.3, i failed to update this with build-in update apps.

    Such update seems unavailable from synology website.

     

    Here is the cat messages about the update failure

     

    Mar 20 10:27:44 NAS updater: updater.c:4405 Start of the updater...

    Mar 20 10:27:45 NAS updater: updater.c:4503 This is X86 platform

    Mar 20 10:27:45 NAS updater: updater.c:4509 The SynoBoot partitions exist.

    Mar 20 10:27:45 NAS updater: updater.c:2744 SYNORedBootUpdCheckAndApply(2744): Skip bootloader update, no uboot_do_upd.sh exists

    Mar 20 10:27:45 NAS updater: boot_lock.c(224): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:6)

    Mar 20 10:27:45 NAS updater: updater.c:4605 fail to unlock boot partition

    Mar 20 10:27:45 NAS updater: updater.c:4915 Failed to accomplish the update! (errno = 21)

    Mar 20 10:27:45 NAS upgrade.cgi: smallupdate.cpp:931 failed to exec updater -r

    Mar 20 10:27:45 NAS upgrade.cgi: smallupdate.cpp:1125 failed to update flash

    Mar 20 10:27:45 NAS upgrade.cgi: upgrade.cpp:1295 Fail to apply small update

     

     

    any way to install the update?

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi newbi,

     

    I have a HP N54L with Trantor's v5.4418 (installed locally without any virtualization).

    After having downloaded the correct .pat image on Synology web site,

    I have just downloaded the image here : http://www.firedrive.com/file/52CCF5D28D3EFDAD (link found in this forum as Google drive is saturated)

    and follow the tutorial :

    viewtopic.php?f=2&t=2545

     

    Everything works for me.

    Do not hesitate if you need any precision.

     

     

    Great :smile: have you got a link to the correct pat file please :smile:

     

    thanks for your help dude...

    pat file can be found from the official synology website

    you may use DS3612xs as your syno model (which is most commonly used model in xpenology)

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi everyone!

    Once again, many thanks Gnoboot for your work!

    I managed to upgrade to the DSM 5.0 4458 with the gnoboot 10.3vfat image on a HP N54L. Before, I had a native install with DSM 4.3 3827.

    So far it works pretty well. No loss of data. The only things is that i don't see my shared folders in the File station, eventhough settings are still the same as i had on the previous DSM and i can access my shared files... I guess i'll have to go through the settings again.

     

    As soon as i find time, i'll try an install with esxi 5.1. Will let you know how it goes.

     

    Once again thank you very much for your work all of you :smile:

     

    Edit: problem solved. It was a user right issue.

     

    hello, can you talk more about your upgrade step?

    which boot option do you choose when boot with 10.3 gnoboot-alpha or gnoboot-me ?

    and did you upgrade via DSM or syno assistant?

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    i don't have time recently to test it on the real machine yet.

     

    Just ask for safety.

     

    I'm currently running DSM4.3, when i decided to upgrade to 5.0, should i boot from gnoboot-alpha and upgrade online,

    or boot from gnoboot.me and upgrade from syno assistant??

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    actually it is not necessary to make mirror.

    although you may not be able to down it, you can make a copy to your google drive

    then download it from your own google drive.

     

    I just made a copy to my own google drive and it immediately synced to my computer in a second.

    DSM 5.0 - 4458 is released today

    in Readers News & Rumours

    Posted

    wow this is a big slap in the face for all those still on 4.3! means our shit is outdated!!!!!!!! and continues to be outdated. Gives the malware writers a one up to come rape our shit. wonder when trantor will come out with a release.. never heard back from him when it came to the 4.3 update back in feb now its march!!!!!!!!!

     

    I keep hearing this ginoboot ginoboot thing, not sure how well it gells with trantors build especially if you have data, that means you gotta scrap it and start from 0. Not a viable option for anyone out there who has terabytes of data. with that being said i hope to see the ginoboot being a easier step but what worries me is its skimming out what is originally synology. this reminds me of osx and those who would come up with amd builds was so ass backwards that it wasnt even a true genuine osx install. i like trantors method because its still within the realm of synology but just modding so it bypasses the boot rom found in synology boxes and still can be updated within the synology updater. i hope im wrong about the ginoboot,

     

    did u pay trantor or gnoboot to work for you?

    if no. u better shutup, he didnt own u anything

    if u want an update, u can programme a kernel yrself or buy a real synology

    if u are not knowledgeable enough to do it yrself, then shutup

    Power off from the buttom

    in Software Modding

    Posted

    actually, i think the physical button should use "poweroff" or "shutdown -h now"

    normally we can shutdown in the web interface, which regard as the safest shutdown

    however when something happen and the web service and ssh/telnet service is closed, you 'll finded no way to shutdown properly (unless you plug a keyboard and blindtype your login password poweroff

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    i have a new idea

    according to this post

    http://xpenology.com/forum/viewtopic.php?f=2&t=889

     

    it is possible to incorporate the ACPI support so that we can power off by physical power button.

    using the power button to call "shutdown -h now" or the syno_poweroff_feasible_check + syno_poweroff_task script

    it would be convenience when testing the machine. (although it may not be necessary when the machine started in use for 24/7 )

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Something big is coming in the next few days...

    [spoiler=]Click the ADs on my blog or email me for donation. Enjoy!

     

    that's great~ is the big things shift from alpha version to beta version??

     

    i have a question would like to ask.

     

    is there any different for tigon3 driver between 10.0 and 10.1/10.2 ??

    according to your change log, 10.0 is already used tg3_new and my broadcom Lan card can use it without any problems,

    however in 10.1 and 10.2, no lan card driver is available for the same hardware. it work again having kernel parameter rmmod=tg3_new insmod=tg3

    but i suppose my lan card can use tg3_new (according to 10.0 experience) , so i just curious ... is the tg3_new missed in 10.1 or 10.2 ?

×
×
  • Create New...