Jump to content
XPEnology Community

wenlez

Member
 View Profile  See their activity

  • Posts

    191

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by wenlez

    [SOLVED] DSM5 update 2 with gnoboot 10.5 success

    in General Post-Installation Questions/Discussions (non-hardware specific)

    Posted

    Is anyone else having issues with ffmpeg/transcoding using ds video mobile app? I am using gnoboot 10.5 alpha and dsm 5 update 2. I can log in via ds video on android but, it won't transcode/play anything on the mobile device. Trantor 4.3 worked great with the same video files and mobile device.

     

     

     

    I have the same problem as well, I wonder if it has anything to do with the Serial number

     

    May  4 10:49:42 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:43 MasterWaiter synocodectool: G1Licence.cpp:81 Licence not Success,error msg "SN format is wrong."
May  4 10:49:43 MasterWaiter synocodectool: SYNOCodecPatentG1.cpp:240 ValidateG1Licence failed
May  4 10:49:43 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:44 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:46 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:47 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:48 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:49 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:50 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:51 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:52 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:53 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:54 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:49:55 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: pkgcurltool.cpp:350 http://packages.synology.me/spkrepo/spkrepo/packages, Failed to request packages, httpResponseCode=500
May  4 10:49:55 MasterWaiter entry.cgi_SYNO.Core.Package.Server[1].check[3253]: myds_token_generation.c:105 Serial number is invalid: [][0x2000]
May  4 10:50:36 MasterWaiter synocodectool: G1Licence.cpp:81 Licence not Success,error msg "SN format is wrong."
May  4 10:50:36 MasterWaiter synocodectool: SYNOCodecPatentG1.cpp:187 ValidateG1Licence failed
May  4 10:50:37 MasterWaiter synocodectool: G1Licence.cpp:81 Licence not Success,error msg "SN format is wrong."
May  4 10:50:37 MasterWaiter synocodectool: SYNOCodecPatentG1.cpp:240 ValidateG1Licence failed
May  4 10:53:27 MasterWaiter synocodectool: G1Licence.cpp:81 Licence not Success,error msg "SN format is wrong."
May  4 10:53:27 MasterWaiter synocodectool: SYNOCodecPatentG1.cpp:187 ValidateG1Licence failed
May  4 10:53:28 MasterWaiter synocodectool: G1Licence.cpp:81 Licence not Success,error msg "SN format is wrong."
May  4 10:53:28 MasterWaiter synocodectool: SYNOCodecPatentG1.cpp:240 ValidateG1Licence failed

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    That method is only for small updates, not new builds (4458 vs 4482).

     

    edit: I think gnoboot just needs to and the new build version to the version file buried in rd.gz, which is buried in the zImage now. Lets hope he finds some time to update it :smile:

     

    edit2: looks like I was wrong. It's much easier :smile: Just need to edit grub menu_me

     

    kernel /zImage gnoboot_me=5.0-4482

     

    But looks like they added new secruity meaursures :cry:

     

     

     

     

    So, you made the change to the grub first, then update? o

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi,

     

    I get 110 MB/s when copying files via GBit LAN. I'm using a LSI 9240-8i controller with stock-firmware w/o any Raid-Volumes defined. 6 WD-RED 4TB Disks are mapped via RDM (physical) into the Syno VM. The disks are attached as SCSI 0:1 thru 0:5. The Virtual Controller is LSI SAS. SMART is working except for the temp which displays 0°C

     

    Intel e1000 as virtual NIC.

     

    Mainborad is the A1SAM-2750F from Supermicro (Intel Avoton).

     

    bye,

    Darky

     

     

    Are you using ESXi5? are you able to see SMART status in your DSM?

    TWO DSM 5.0 Update 2 but only later one fix heartbleed

    in Archives

    Posted

    How do you update from Update 1 to Update 2? i get the following error:

     

    Apr 12 22:11:10 MasterWaiter updater: updater.c:4890 Start of the updater...
Apr 12 22:11:10 MasterWaiter updater: updater.c:4994 This is X86 platform
Apr 12 22:11:10 MasterWaiter updater: updater.c:5008 The SynoBoot partitions exist.
Apr 12 22:11:10 MasterWaiter updater: updater.c:3128 SYNORedBootUpdCheckAndApply(3128): Skip bootloader update, no uboot_do_upd.sh exists
Apr 12 22:11:10 MasterWaiter updater: updater.c:340 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup
Apr 12 22:11:10 MasterWaiter updater: updater.c:394 Failed to open /tmp/bootmnt/checksum.syno [No such file or directory]
Apr 12 22:11:10 MasterWaiter updater: updater.c:474 Fail to get update [/bin/rm -f /tmp/checksum.syno.tmp] to checksum.syno.
Apr 12 22:11:10 MasterWaiter updater: updater.c:5140 failed to install images
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [rd.gz] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [grub_cksum.syno] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [updater] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [VERSION] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [checksum.syno] fail, remove it from synoboot
Apr 12 22:11:11 MasterWaiter updater: updater.c:5490 Failed to accomplish the update! (errno = 16)
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: smallupdate.cpp:1017 failed to exec updater -r
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: smallupdate.cpp:1206 failed to update flash
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: Upgrade.cpp:202 Fail to apply small update
Apr 12 22:11:11 MasterWaiter cupsd[32672]: [conf.c:1893] Filter "pstoraster" not found.
Apr 12 22:11:11 MasterWaiter synorelayd: register_api_key.cpp:226 failed to send https request to [apiauth.synology.com], err=[0x2000]
Apr 12 22:11:11 MasterWaiter synorelayd[455]: synorelayd.cpp:1221 stoped

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hello,

     

    with 10.5 my PERC310 (8 SATA/SAS-Port Controller) doesnt work, the Volume is not showing up...with 10.4 it works great...PLS Help :smile:

    I´ve created the Volume in the BIOS settings (4 SAS Drives / 1 Volume) so i dont have to create an Software-Raid in the DSM.

    I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk?

     

     

    Have you been able to get disks conected to the 9211-8i to start from Disk1-Disk8?

    Do i need to blacklist any other drivers to make sure theres no unused slots before the disks on the raid card?

     

    Also , Will flashing IT firmware instead of IR benifit in any way?

     

     

    Someone here said you can't install DSM directly onto a disk over a passthroughed SATA controller.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Does anybody have a problem where a virtual machine with DSM5.0-4458 would shutdown every day a random time because of "disk overheating" ?

    Disks are virtual, how can they overheat ? :smile:

     

    Also from /var/log/messages i frequently have such errors :

     

    Mar 25 15:05:01 DSMesxi5 SystemInfo.cgi: disk_info_get.c:82 Failed to open /dev/sdc, errno=No such file or directory

     

     

    And this are always the last line before each forced shutdown. Any info on that?

     

     

    I have the same problem. I use ESXi5.0, with gnoBoot10.5. Using a 64GB virtual disk as the installation for DSM5, and passthrough a LSI 9122-8i to this VM. For the longest time, i kept thinking one of the disk on the LSI controller is overheating, but none of them go over 41C. Now reading your post, realizing it's the virtual disk. Also, in my ESXi, the VM controller is set to ParaVirtual.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    My set up is: one virtual disk to host the syno-boot-ext2 image. one 60GB virtual disk for initial installation; one LSI 9211-8i IT mode with one 160GB SSD, and two 4TB hard drives. Somehow the first disk starts with Disk 4. The 60GB is Disk 4; the 160GB SSD is Disk 5, and so on. Does anyone have similar issue? i saw someone posted here with first disk of Disk 3 (sdc) , and need to use the insmod during GRUB boot?

     

    For my motherboards, both Intel brand, I need to rmmod=ata_piix in grub. Or else DSM will start the array at slot 3 and onward (it seems to reserve the first 2 slots for that driver for some reason). You can try that in a test VM and see if your array starts at the correct slot. If not, then it's probably another driver.

     

    edit: I guess it happens for me because I install gnoboot to a IDE vdmk rather than ACHI. https://ata.wiki.kernel.org/index.php/Ata_piix

     

    On a side note, does anyone know if it's possible to run gnboot off a .flp (floppy image) rather than virtual hard drive? I tried to get it working, but got boot errors.

     

    Interestingly, setting rmmod=ata_piix moves my first drive to disk 2.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    My set up is: one virtual disk to host the syno-boot-ext2 image. one 60GB virtual disk for initial installation; one LSI 9211-8i IT mode with one 160GB SSD, and two 4TB hard drives. Somehow the first disk starts with Disk 4. The 60GB is Disk 4; the 160GB SSD is Disk 5, and so on. Does anyone have similar issue? i saw someone posted here with first disk of Disk 3 (sdc) , and need to use the insmod during GRUB boot?

    XPEnology DS3612xs DSM 4.3 build 3827 (ESXi v1.2)

    in DSM 5.2 and earlier (Legacy)

    Posted

    is it possible to convert a regular n54l xpenology 4.3 build into an ESXi build without losing data on the data drives?

     

    I currently have 4 drives: 2x3gig, 2x2gig in a SHR array. How would I go about changing converting to an ESXi build?

     

    Yes, you can. I've done it in the past, with a PC hardware. What you will need is another hard drive. Ideally, installing ESXi in the 5th hard drive ( best practice is remove your old 4 drives first ). THen, enable passthrough ( does your n54L even support hard drive passthrough ?) .

     

    Then install the Xpenology, and passthrough the hard drives.

×
×
  • Create New...