Jump to content
XPEnology Community

djvas335

Member
  • Posts

    161
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by djvas335

  1. 7 hours ago, Red100 said:

    ok her is my situation:

     

    i got a dell optiplex 7010 with intel !5 processor 

     

    i prepared all what i need for install .i guess if not am mistaken i have to install this version DS3615xs 6.1.2 Jun's Mod V1.02b .so when i boot from usb all goes ok till i browse  to the server ip and get connected  all ok i tried two ways first manual installation with DSM_DS3615xs_15152 the process goes till 56% and stops with error: (13) invalide DSM .

    Remember when  tried aut install and download from server of synology gives also the same error and somtimes gives cant download the files due to connection problems.

    So im stuck in this situation ,what am doing wrong ? tried for the second time the higher version >>> jun's_mod_v1.03b_ds3615xs without any succes 

    Note: the first time connect gives install the server and now after all what i try when i try to install get in place of install>>>Migrate 

     

    Some on ecan please help me go through this 

     

    Apreciate all your work guys

     

  2. It depends if you are using native networking and extra.lzma for dsm 6.2.2, to upgrade successfully you will need to replace custom extra.lzma with old extra.lzma from jun 1.03 loader, if not using extra.lzma, and using intel card, you can just upgrade without any loader manipulation 

  3. 1. Yes

    2. Maybe corrupt image ? No need to replace anything except extra.lzma

     

    2 minutes ago, Decebalus said:

    I am sure I am doing something wrong. I have mounted the USB stick and replaced the extra.lzma file, however, when I am trying to load the 6.2.3 pat file from control panel, I am getting an unknown error. Now, 2 things I think it is worth mentioning:

     

    1. 6.2.3 does not show up under Update/Restore in control panel - hence trying to install it manually. Is it expected for 6.2.3 not to show up as an available update?

    2. I have not replaced zImage and rd.gz files on the stick with the ones from June's loader. Those files are from 6.2.2. Do those need to be replaced as well?

     

    Thanks in advance.

     

  4. 1) Enable SSH and ssh into your DiskStation

    2) Become root ( sudo -i )

    3) Make a mount point ( mkdir -p /tmp/mountMe )

    4) cd into /dev ( cd /dev )

    5) mount synoboot2 to your mount point ( mount -t vfat synoboot2 /tmp/mountMe )

    6) Profit!

     

     

    1 hour ago, Decebalus said:

    That's perfect. Is there a link or a thread that contains those details? What commands to use in terminal? Any help is definitely appreciated.

     

  5. I just mount it inside DSM, replace extra.lzma with old one and upgrade.

     

    7 hours ago, Decebalus said:

    Since I have installed from scratch 6.2.3 using June's loader 1.03b for 3615xs on one of my old machines, I was wondering what would be the best approach to upgrade to 6.2.3 for those of us who have custom extra.lzma. Would it make sense to boot up with the current USB stick containing custom extra.lzma and after booting up, taking out the stick, reimage it with original June's 1.03b loader (and modifying grub.cfg accordingly, of course), plugging it back in the USB port, install manually 6.2.3 from Control Panel and reboot?

     

    Sorry, it may be a stupid question but I have never went through a similar process before.

     

    Any suggestions are definitely appreciated and I hope this will help others in similar situation.

     

    Thanks in advance!

     

  6. You probably are using modified loader 1.03 with updated extra.lzma, check the extra.lzma on partition 2 of flash drive, it needs to be about 2mb in size, if its 4.5mb you are using modified loader

     

    1 hour ago, alirz1 said:

    I dont know whats going on. But i burnt stock 1.03b loader on a new USB. Updated the grub config. yet, it looks like the box still kernel panics within seconds after booting from the loader.

    no network, no keyboard lights etc....again, everything works fine with 1.02 loader.

     

  7. Use 1.03b loader and upgrade directly to DSM 6.2.3, do not use extra.lzma, it's no longer compatible with newer DSM, they reverted their driver support to old version of drivers, so old drivers from original loader work.

     

    14 hours ago, alirz1 said:

    - Outcome of the update: FAILED

    - DSM version prior update: DSM 6.1.7 UPDATE 2

    - CURRENT Loader version and model: JUN'S LOADER v1.02b - DS3617xs..... Trying upgrade using 1.03b with new dsm kernel file

    - Using custom extra.lzma: YES

    - Installation type: BAREMETAL - Asrock H370m - NIC: 1 x Giga PHY Intel® I219V, 1 x GigaLAN Intel® I211AT

    - Additional comments: HANGS SHORTLY AFTER BOOTING. NO NETWORK ON ANY NIC, NO KEYBOARD LIGHTS

     

     

    Hi All,

     

    So i currently have a intel i3-8100 processor, Asrock H370m motherboard based DS3617xs xpenology system running Junls 1.02b loader with DSM 6.1.7-15284 Update 2 and the extra ramdisk(some version from 2018)

    Trying to get it to upgrade to 6.2.2 using the 1.0.3b loader and the extra kernel for 6.2.x. However looks like that even without the disks connected, the system is kernel panicing shortly after the 1.03b loader boot. While i havent checked via serial console, if its indeed a kernel panic. But looks like that is the case, as shortly after the boot the keyboard lights go off. I get no network connection etc....

    NOTE: i have already upgraded my second xpenology box that has an older/different hardware successfully to 6.2.2 using the steps on page 1 of this thread, So im famialir with the requirements.

     

    This is the Asrock board and its specs.. No extra add on adapters/controllers etc... Any ideas? Is it known to be not compatible. 

    https://www.asrock.com/MB/Intel/H370M-ITXac/index.asp#Specification

     

     

     

     

  8. Можете заново переписать оригинальный loader и установить напрямую, мне просто так быстрее

     

    6 hours ago, i926 said:

    О..... оооо как то слишком мудрено.... И не совсем применимо.. 

    Если только обновиться ради самого обновления, для галочки, для зарубке на прикладе....

     

  9. Actually I got the ideia to try this from a post by alexku44, when he confirmed that older driver works in his setup, so credit for discovering this goes to him.

     

    I confirm upgrade success dsm3615xs to 6.2.3 on Microserver GEN 7, GEN8 and GEN10, this is only hardware I have running DSM

     

     

     

    4 minutes ago, IG-88 said:

    yes i don't doubt that but it will not work for everyone (every hardware) and on 918+ there are three types of extra/extra2.lzma and depending on what type used it will it will "influence" the result (3615/17 does not have i915 hardware transcoding and does not rely on i915 firmware)

    i guess it wont make things worse to try jun's original files - but don't blame me or djvas335 if it does not ;-) and i guess it will be back to what you had before when using the extra/extra2 you used before you tried jun's originals (also no guarantees - as usual)

    one thing is sure, your data are still there, you just cant use them because you might have lost network access or the storage does not work to get all disks into the raid

    one "safe" solution might be to boot up open media vault from a external (additional) source/disk, that will give you network access to your raid (data) volume - if you need files from there - thats my personal plan "f" if i loose access when dsm does not boot (if your raid is damaged then you are beyond "f")

     

     

     

     

    • Like 1
  10. I confirm upgrade to 6.2.3 using original jun's extra lzma on Microserver gen7 Microserver gen8 and Microserver gen10

     

    I see I was not clear in my last post, no extra.lzma I mean I used original extra.lzma from jun's bootloader

     

     

    2 minutes ago, IG-88 said:

    just be patient until romorrow, i'm working on it

    i could send you a link for a test i did that will work for systems using realtek nic and ahci for storage (like most mITX boards with apollo or gemini lake)

     

    i guess that can be misleading, for hp microserver you will need broadcom driver (onboard) and "no extra.lzma" can mean you used jun's default extra.lzma (part of the loader) or you deleted the extra.lzma completely from the loader

    the driver inside jun's default extra.lzma might work with 6.2.3 in some (lot's) cases but its not that universal to copy back jun's extra.lzma, depending on the hardware it might end in success but can also fail

    there will be cases where storage is not working or where network does not work (i've seen problems here with a igb.ko based network adapter, e1000e and realtek did work)

     

     

    • Like 1
  11. Как у меня обновилась первая система, вы обновляете сначала на 6.2.3, потом вытаскиваете флешку е меняете extra.lzma на оригинальный от лоадера, или монтируете флешку напрямую в ДСМ, заменяете extra.lzma  и устанавливаете 6.2.3, смотрите только не перезагружаете систему до установки 6.2.3, иначе придется опять менять extra.lzma

×
×
  • Create New...