btomi9
-
Posts
7 -
Joined
-
Last visited
Posts posted by btomi9
-
-
2 hours ago, btomi9 said:
Update, I finally restarted the whole process from scratch, and synology assistant still hadn't found it. Until I disabled windows firewall and avast anti-virus, (maybe it was just the firewall). And it found it finally. I made the migration with manual install and chose the DSM_DS3615xs_24922.pat file, and I chose the option to keep most of the settings as well if possible. The migration has succeeded, but many of my packages are now in "starting" state, e.g. photo station cannot be updated because it says run php 7.0 before, but php 7.0 is just starting. Just like many other previously used packages.
Do you think I can redo the migration but now choosing the option to keep all my data but discard all the previous settings? I haven't restored the previously backed up configuration settings yet, now I will do that and see.
Update, I think it was Avast who prevented me to find the NAS via Synology Assistant. Now I chose the 2nd option from Jun's menu (Reinstall) and it put the NAS again into migratable in Syno assistant and successfully made the "update" again. Had to recreate my admin user etc. but my data on the HDD -s kept intact.
Thank you so much for all your help guys!
-
On 5/14/2020 at 4:18 AM, Decebalus said:
It sounds like you have the right steps. To answer your question, yes, you should see the HP microserver with the factory broadcom NIC on the network if you have used the proper extra.lzma v0.5 modified by IG88. That file, plus the rd.gz and zImage files from the 24922 DSM 6.2.2 for 3615xs should be copied to the 2nd partition of 30MB on Jun's 1.03b bootloader for 3615xs. I recommend to redo the steps carefully since it's possible you missed a step in the execution. Always use an extra empty HDD. If you have used the HDD previously, I recommend to erase it, just I to be safe there are no DSM leftovers on it.
Update, I finally restarted the whole process from scratch, and synology assistant still hadn't found it. Until I disabled windows firewall and avast anti-virus, (maybe it was just the firewall). And it found it finally. I made the migration with manual install and chose the DSM_DS3615xs_24922.pat file, and I chose the option to keep most of the settings as well if possible. The migration has succeeded, but many of my packages are now in "starting" state, e.g. photo station cannot be updated because it says run php 7.0 before, but php 7.0 is just starting. Just like many other previously used packages.
Do you think I can redo the migration but now choosing the option to keep all my data but discard all the previous settings? I haven't restored the previously backed up configuration settings yet, now I will do that and see.
-
11 hours ago, IG-88 said:
i don't know where you get or read this, the 1st post is very specific about what files to use, i even link the *.pat files to use
when installing 6.2.2 you use the kernel files from the inside the pat file (zImgage and rd.gz) and the extra.lzma from the link matching the type like 3615
the drivers in the extra.lzma are specifically made for 6.2.2 and will only work when you replace the kernel files on the loader too
no works also with winrar (at least it did when i tried it a few minutes ago)
you can't just use any *pat file, things are specific for every type and version
23739 is 6.2.(0) thats the files already on the loader as it comes from jun
and DDSM is a docker DSM - do you use it with a loader for docker?
when using loader for 3615 you also need to use files and driver (extra.lzma) for 3615
Thanks IG-88, I'm sorry I think my reply was misunderstandable. As I mentioned in my first post, I used the correct .pat version from which I extracted and copied the rd.gz and zImage files onto the pendrive's 2nd partition (partition 1 in OSFMount) overwriting the 2 files there coming from Jun's original v0.3b loader.
The .pat version came from here:
https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.patRegarding the 6.0 .pat file I meant I just wanted to try what Big_11 suggested, but after seeing that in that .pat file the rd.gz and zImage is not there (at least it might be inside the tar but I didn't extract that), I just stopped here.
So summarizing. Do you guys say that Jun's original v0.3b loader from here:
https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b
Extracting rd.gz and zImage from the .pat version from here:
https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.patThe extra.lmza from here:
DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test
http://s000.tinyupload.com/?file_id=87576629927396429210should work and see the HP microserver Gen8 's factory Broadcom NIC?
Once again, I don't have boot problem, I get to grub menu, and then I get to the final screen mentioning I should start looking for the NAS via find.synology.com etc. So seems like the loader has booted. Here can you confirm I don't have to see something like a normal linux booting process where it tests all parts of the operating systems and say OK or Warning or Faliure on multiple pages, so I should be just fine seeing Jun's page etc?
-
3 hours ago, Big_11 said:
I'm Not Sure, but you should use pat file from 6.2 Not 6.2.2....
the correct Version is shown at Synology Assistant and lower than 24922...
good luck..
Thank you, but in the base version 6.2 .pat file I haven't found the aforementioned 2 kernel files. Let me check the link where I downloaded it from. Here:
https://archive.synology.com/download/DSM/release/6.2/23739/
I chose the topmost file, DSM_DDSM_23739.pat
Okay, inside this file there is a hda1.tgz I assume it't a tar.gz archive, which I was able to extract with WinRAR, but after the extraction it's just a hda1 file without extension. So no rd.gz or zImage here. Shall I untar this file somehow to find those two files?
The detailed instructions in the opening post should work, I don't quite understand where I am mistaken here. dasupergrover could also make it work. I used a transcend jetflash 32G pendrive, not sure if it matters. I also have a Kingston 8G maybe I'll try that one as well. It shouldn't be a problem though, I think. Or maybe it's winRAR, and I should use 7zip. So far I had no problems using winRAR, everything worked. -
Actually I used WinRAR to extract rd.gz and zImage files and I copied it to the 2nd partition of the pendrive. In OSFMount partition 0 is the one where there is the /grub/grub.conf to be edited, and partition 1 is where I overwrote extra.lzma, rd.gz and zImage
These 3 files has the size in Total commander 7.55a shown as:
extra.lzma - 4 541 498
rd.gz - 6 284 912
zImage - 3 057 264
Now as I reply extracted it again from the 3rd downloaded version of the same file to a completely new folder, and the size and date is the same as previously.
BTW from windows 10 even with OSFMount I cannot access the 3rd partition (partition 2) (but the tutorial never told there is anything to do with that, so should cause no problems) -
Hi all,
I'm new to this forum and would like to ask your help to update my Xpenology to DSM 6.2.2 V24922
I summarize my configuration in the clear manner I found on this forum in other topics:
- Outcome of the update: UNSUCCESSFUL
- DSM version prior update: DSM 6.1.7-15284 Update 2
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: YES, also the 2 kernel files needed, see below
- Installation type: BAREMETAL - HP Microserver Gen8 / G1610T Celeron
- Additional comments: NIC factory Broadcom BCM5720
I followed the instructions described in the first post of this topic. Downloaded Jun's v1.03b loader from here:
https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b
The .pat version from here:
https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.patThe extra.lmza from here:
DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test
http://s000.tinyupload.com/?file_id=87576629927396429210
In the description I found that this extra.lzma is for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test, but I haven't found a link to this specific, modded 1.03b loader. Did I miss something? Maybe this is the only reason that the update is unsuccessful.
Actually, before commiting myself for the update, I plugged out the HDD -s from the server, put in a new one, created a new pendrive following the description in this tutorial:https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/
I prepared the pendrive on a Windows 10 laptop, used OSFMount and Win32 Disk Imager. Of course I edited the grub.conf with VID, PID, SN, MAC, and also copied (with overwriting) the extra.lzma and the extracted the zImage and rd.gz from the .pat file and copied to the second partition, just as I found in the first post.
The grub menu works and if I either let the timer run out or press enter to choose the first option from Jun 's menu, it seemingly works, there comes the screen ending with:
"Happy hacking.
Screen will stop updating shortly, please open http://find.synology.com to continue."
but I'm unable to find it either with find.synology.com or the downloaded Synology assistant.
So now I put back my "production" HDD -s and pendrive and reverted back to DSM version 6.1.7 but I wonder if there is a solution to make it work with the original NIC, or I'm forced to buy an Intel one.
Thank you.
Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+
in Additional Compiled Modules
Posted
Now I would like to get my pendrive back from the boot purpose, I left my original pendrive intact til the upgrade is successful. Now I would like to clone my actually working pendrive, I created a new .bin image from the 6.2.2 working pendrive with imageusb, edited the grub.cfg with the old pendrive's VID, PID with OSFMount, and then wrote the modified .bin to my old pendrive. But on partition 1 I could see that a checksum.syno and a grub_cksum.syno file appeared, I guess the DSM migration process somehow generated these two checksum files on the new boot pendrive. Now of course as I modified the VID, PID in grub.cfg, the grub.cfg doesn't match the grub_cksum.syno and of course it's not booting from my old pendrive. From the new one it's booting fine.
Do you know how to make DSM recreate that grub_cksum.syno file to be able to use my old pendrive as a boot stick with the new DSM 6.2.2? Or can I just delete it and it recreates automatically?