Jump to content
XPEnology Community

gnoboot

Member
 View Profile  See their activity

  • Posts

    278

  • Joined

  • Last visited

 Content Type 

Posts posted by gnoboot

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Sweet, thanks !

     

    Will it be possible to do "clean" update in the future? I can make 5 beta update with telnet command but it doesn't work with 4.3 (3810 -> 3827)

     

    No, update feature is DSM's job which isn't opensource. You can update to 3827 using gnoboot-me grub option, but have a backup before doing it.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    is there a method to install this directly to hardware without vm?

     

    thanks

     

    It's the same process for installing to physical hardware. You just need to write the image to your USB disk.

     

    • Attach your USB disk (PATA/SATA disk disconnected) and boot to your physical hardware using a LInux livecd.
    • Get the USB disk path.
      # dmesg | egrep '^(sd|hd).*[1-9]''


    • Let assume your USB disk is /dev/sda (step 2 result), write the image to your USB disk.
      # dd if=gnoboot-alpha7 of=/dev/sda


    • Open Synology Assistant to begin DSM installation.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    is there a method to install this directly to hardware without vm?

     

    thanks

     

    It's the same process for installing to physical hardware. You just need to write the image to your USB disk.

     

    • Attach your USB disk (PATA/SATA disk disconnected) and boot to your physical hardware using a LInux livecd.
    • Get the USB disk path.
      # dmesg | egrep '^(sd|hd).*[1-9]''


    • Let assume your USB disk is /dev/sda (step 2 result), write the image to your USB disk.
      # dd if=gnoboot-alpha7 of=/dev/sda


    • Open Synology Assistant to begin DSM installation.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    hi !

     

    Could it be use in virtual box ?

    I install it , it work on the first time and let me apply the DSM_DS3612xs_4418.pat(org. pat file from syno-logy) files.

    Other then that, it boot and then shuntdown ...

    Cannot go into the DSM system page ...

     

    I also rewrite the alpha7.img, but still fail to boot ...

     

     

    Thanks...

     

    hmmmm, it's known issue in virtual machines. Are you using AMD cpu?

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    hi !

     

    Could it be use in virtual box ?

    I install it , it work on the first time and let me apply the DSM_DS3612xs_4418.pat(org. pat file from syno-logy) files.

    Other then that, it boot and then shuntdown ...

    Cannot go into the DSM system page ...

     

    I also rewrite the alpha7.img, but still fail to boot ...

     

     

    Thanks...

     

    hmmmm, it's known issue in virtual machines. Are you using AMD cpu?

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Upgraded from gnuboot alpha 6 in VMware with DSM 5.0-4418 Update 1

     

    Made a 32MB boot disk in VMware to replace the standard 1GB boot device.

    D:\Virtual Machines\XPEnology gnoBoot>c:vmware-vdiskmanager -c -s 32MB -a ide -t 0 "XPEnology_gnoBoot_boot.vmdk"

     

    replaced the old sata:0:2 line XPEnology_gnoBoot.vmdk with the new 32MB XPEnology_gnoBoot_boot.vmdk in the corresponding .vmx

    booted with live iso (parted magic) and dd't the new alpha 7 to de /dev/sda

    reboot without live iso

     

    gnuboot alpha 7 booted..

    data disks are recognised and used, no data loss.

    no boot error's

     

    the only thing is I still have dsmnotify.cgi[20883]: segfault at 0 ip 000000000804c3c6 errors <- nothing I can do about it, maybe DSM security check or bug.

     

    XPenology> dmesg | grep error
[  163.110827] dsmnotify.cgi[26487]: segfault at 0 ip 000000000804c3c6 sp 00000000ff802960 error 6
[  163.580603] storagehandler.[26490]: segfault at 0 ip 000000000809ce56 sp 00000000ff947850 error 6
[  200.356051] dsmnotify.cgi[29050]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb23e30 error 6
[  232.358461] dsmnotify.cgi[31110]: segfault at 0 ip 000000000804c3c6 sp 00000000ffc3eca0 error 6
[  264.110973] dsmnotify.cgi[711]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb05aa0 error 6
[  299.136910] dsmnotify.cgi[2968]: segfault at 0 ip 000000000804c3c6 sp 00000000ffe1c9a0 error 6
[  334.011865] dsmnotify.cgi[5289]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb4bd40 error 6
[  368.881965] dsmnotify.cgi[7559]: segfault at 0 ip 000000000804c3c6 sp 00000000fffd1cf0 error 6
[  400.818059] dsmnotify.cgi[9621]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa23370 error 6
[  435.845270] dsmnotify.cgi[11888]: segfault at 0 ip 000000000804c3c6 sp 00000000ff8fc4c0 error 6
[  470.770901] dsmnotify.cgi[14147]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa67b00 error 6
[  506.588812] dsmnotify.cgi[16485]: segfault at 0 ip 000000000804c3c6 sp 00000000ff824f80 error 6
[  537.517196] dsmnotify.cgi[18493]: segfault at 0 ip 000000000804c3c6 sp 00000000ffc02080 error 6
[  573.439082] dsmnotify.cgi[20883]: segfault at 0 ip 000000000804c3c6 sp 00000000ffe58b10 error 6
[  609.363999] dsmnotify.cgi[23230]: segfault at 0 ip 000000000804c3c6 sp 00000000ffe260d0 error 6
[  645.315920] dsmnotify.cgi[25613]: segfault at 0 ip 000000000804c3c6 sp 00000000fff84930 error 6
[  680.234725] dsmnotify.cgi[27870]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa6a0d0 error 6
[  715.134369] dsmnotify.cgi[30128]: segfault at 0 ip 000000000804c3c6 sp 00000000ff973e40 error 6
[  747.071405] dsmnotify.cgi[32190]: segfault at 0 ip 000000000804c3c6 sp 00000000fff39d20 error 6
[  779.049051] dsmnotify.cgi[1791]: segfault at 0 ip 000000000804c3c6 sp 00000000ffdd3d80 error 6
[  809.924793] dsmnotify.cgi[3791]: segfault at 0 ip 000000000804c3c6 sp 00000000fff3be20 error 6
[  840.957927] dsmnotify.cgi[5824]: segfault at 0 ip 000000000804c3c6 sp 00000000ffca8a40 error 6
[  872.870089] dsmnotify.cgi[7897]: segfault at 0 ip 000000000804c3c6 sp 00000000ff9a71f0 error 6
[  907.731003] dsmnotify.cgi[10154]: segfault at 0 ip 000000000804c3c6 sp 00000000ff8787c0 error 6
[  938.885874] dsmnotify.cgi[12152]: segfault at 0 ip 000000000804c3c6 sp 00000000ff995a50 error 6
[  970.575562] dsmnotify.cgi[14214]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa40510 error 6
[ 1006.491741] dsmnotify.cgi[16554]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa7e6f0 error 6
[ 1041.421149] dsmnotify.cgi[18818]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa23db0 error 6
[ 1076.341800] dsmnotify.cgi[21145]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb4e390 error 6
[ 1111.320164] dsmnotify.cgi[23489]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa0a000 error 6
[ 1146.289071] dsmnotify.cgi[25748]: segfault at 0 ip 000000000804c3c6 sp 00000000fff51a50 error 6

     

    gnoboot., what to test? <- please test everything that is kernel related issues, boot up issues, upgrade issues, and services (i.e. nfs, cifs, iscsi, etc).

    what are the benefits of adding open-vmdk-tools ? <- shutdown/reboot (auto) from host and VMware console, drivers are already available in the kernel.

    how to check that running alpha 7? <- Build date

    XPenology> uname -a 
Linux XPenology 3.2.40 #1 SMP Sun Feb 16 08:36:32 CST 2014 x86_64 GNU/Linux synology_bromolow_3612xs

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Upgraded from gnuboot alpha 6 in VMware with DSM 5.0-4418 Update 1

     

    Made a 32MB boot disk in VMware to replace the standard 1GB boot device.

    D:\Virtual Machines\XPEnology gnoBoot>c:vmware-vdiskmanager -c -s 32MB -a ide -t 0 "XPEnology_gnoBoot_boot.vmdk"

     

    replaced the old sata:0:2 line XPEnology_gnoBoot.vmdk with the new 32MB XPEnology_gnoBoot_boot.vmdk in the corresponding .vmx

    booted with live iso (parted magic) and dd't the new alpha 7 to de /dev/sda

    reboot without live iso

     

    gnuboot alpha 7 booted..

    data disks are recognised and used, no data loss.

    no boot error's

     

    the only thing is I still have dsmnotify.cgi[20883]: segfault at 0 ip 000000000804c3c6 errors <- nothing I can do about it, maybe DSM security check or bug.

     

    XPenology> dmesg | grep error
[  163.110827] dsmnotify.cgi[26487]: segfault at 0 ip 000000000804c3c6 sp 00000000ff802960 error 6
[  163.580603] storagehandler.[26490]: segfault at 0 ip 000000000809ce56 sp 00000000ff947850 error 6
[  200.356051] dsmnotify.cgi[29050]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb23e30 error 6
[  232.358461] dsmnotify.cgi[31110]: segfault at 0 ip 000000000804c3c6 sp 00000000ffc3eca0 error 6
[  264.110973] dsmnotify.cgi[711]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb05aa0 error 6
[  299.136910] dsmnotify.cgi[2968]: segfault at 0 ip 000000000804c3c6 sp 00000000ffe1c9a0 error 6
[  334.011865] dsmnotify.cgi[5289]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb4bd40 error 6
[  368.881965] dsmnotify.cgi[7559]: segfault at 0 ip 000000000804c3c6 sp 00000000fffd1cf0 error 6
[  400.818059] dsmnotify.cgi[9621]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa23370 error 6
[  435.845270] dsmnotify.cgi[11888]: segfault at 0 ip 000000000804c3c6 sp 00000000ff8fc4c0 error 6
[  470.770901] dsmnotify.cgi[14147]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa67b00 error 6
[  506.588812] dsmnotify.cgi[16485]: segfault at 0 ip 000000000804c3c6 sp 00000000ff824f80 error 6
[  537.517196] dsmnotify.cgi[18493]: segfault at 0 ip 000000000804c3c6 sp 00000000ffc02080 error 6
[  573.439082] dsmnotify.cgi[20883]: segfault at 0 ip 000000000804c3c6 sp 00000000ffe58b10 error 6
[  609.363999] dsmnotify.cgi[23230]: segfault at 0 ip 000000000804c3c6 sp 00000000ffe260d0 error 6
[  645.315920] dsmnotify.cgi[25613]: segfault at 0 ip 000000000804c3c6 sp 00000000fff84930 error 6
[  680.234725] dsmnotify.cgi[27870]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa6a0d0 error 6
[  715.134369] dsmnotify.cgi[30128]: segfault at 0 ip 000000000804c3c6 sp 00000000ff973e40 error 6
[  747.071405] dsmnotify.cgi[32190]: segfault at 0 ip 000000000804c3c6 sp 00000000fff39d20 error 6
[  779.049051] dsmnotify.cgi[1791]: segfault at 0 ip 000000000804c3c6 sp 00000000ffdd3d80 error 6
[  809.924793] dsmnotify.cgi[3791]: segfault at 0 ip 000000000804c3c6 sp 00000000fff3be20 error 6
[  840.957927] dsmnotify.cgi[5824]: segfault at 0 ip 000000000804c3c6 sp 00000000ffca8a40 error 6
[  872.870089] dsmnotify.cgi[7897]: segfault at 0 ip 000000000804c3c6 sp 00000000ff9a71f0 error 6
[  907.731003] dsmnotify.cgi[10154]: segfault at 0 ip 000000000804c3c6 sp 00000000ff8787c0 error 6
[  938.885874] dsmnotify.cgi[12152]: segfault at 0 ip 000000000804c3c6 sp 00000000ff995a50 error 6
[  970.575562] dsmnotify.cgi[14214]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa40510 error 6
[ 1006.491741] dsmnotify.cgi[16554]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa7e6f0 error 6
[ 1041.421149] dsmnotify.cgi[18818]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa23db0 error 6
[ 1076.341800] dsmnotify.cgi[21145]: segfault at 0 ip 000000000804c3c6 sp 00000000ffb4e390 error 6
[ 1111.320164] dsmnotify.cgi[23489]: segfault at 0 ip 000000000804c3c6 sp 00000000ffa0a000 error 6
[ 1146.289071] dsmnotify.cgi[25748]: segfault at 0 ip 000000000804c3c6 sp 00000000fff51a50 error 6

     

    gnoboot., what to test? <- please test everything that is kernel related issues, boot up issues, upgrade issues, and services (i.e. nfs, cifs, iscsi, etc).

    what are the benefits of adding open-vmdk-tools ? <- shutdown/reboot (auto) from host and VMware console, drivers are already available in the kernel.

    how to check that running alpha 7? <- Build date

    XPenology> uname -a 
Linux XPenology 3.2.40 #1 SMP Sun Feb 16 08:36:32 CST 2014 x86_64 GNU/Linux synology_bromolow_3612xs

×
×
  • Create New...