chipped
-
Posts
27 -
Joined
-
Last visited
-
Days Won
1
Posts posted by chipped
-
-
On 1/27/2019 at 4:44 AM, rony said:
Hello, what are the DS3617 users doing about updates?
Should we wait for a new loader until we can update to 6.2.1?
6.2 has very serious security flaws that have led me to deny my NAS access to the Internet.
If you have 4th Gen CPU or newer then you can upgrade using 1.04 loader.
The loader is customised to set 16 drives visible on the system on every boot. So it’s all good if you have up to 16 drives.
See compatible hardware here
-
On 1/24/2019 at 6:21 AM, dirkme said:
I have xpenology 6.1 running just fine, with the new bootloader, I can not create a bootable USB stick, not with rufus, Etcher or dd command in Linux. anybody else having that struggle or a solution??
Thanks for any help
Dirk
Sometimes I had problems too.
Run command prompt as Admin > diskpart > list disk > select disk 2 (number is your USB, whatever it is in the list) > clean > exit
This will clean the disk quickly, it basically gives you a raw disk like they come out of the box.
For some reason Rufus doesn’t like my usb unless I do this first.
-
1
-
-
@flyride Thanks i will go found one. Any card will do correct that has an Intel ChipSet. Also i need to stay on v1.03b DS3615xs due to the CPU Limitations.
What Card do you recommend
Not any Intel Ethernet cars, one that is supported by the e1000e driver. You see which chipsets are supported here
https://www.intel.com.au/content/www/au/en/support/articles/000005480/network-and-i-o/ethernet-products.html
“The Linux* e1000e driver supports PCI Express* Gigabit Network Connections except the 82575, 82576, 82580, I350, I354, and I210/I211.”-
1
-
-
17 hours ago, Bamle said:
Unfortunatly, it will not install a lower dsm version. Even though its a migrate from 3617 to 3615.
I think ill have to make an edit on the system partitions on the drives to make it work?
You need to follow the instructions in this topic, a few of us had the same issue. You can do it, the instructions can be a bit confusing to follow. Just let us know if you get stuck.
-
1
-
-
Loader version and type: 1.04b DS918+
DSM version in use (including critical update): DSM 6.2.1-23824 Update 4
Using custom modules/ramdisk? If yes which one?: no
Hardware details: Intel i5-4670, Gigabyte Z87X-UD5H, SATA PCIe card 4 ports (chipset Marvell 88SE9235, Model SI-PEX40062)
NOTE - I have 8 hard drives, I usually use the Intel SATA ports on the motherboard and if the others are not compatible then I disable them in BIOS/UEFI and use the above PCIe card which is cheap and never had problems with in all my Xpenology builds.
-
10 hours ago, wingspinner said:
That and the same hardware as Synology includes drivers for in their .pat file. As of update 6.2.1-23824 it appears that Synology has turned on module signing and security software that prevents anything but a Synology generated module from loading. So, I ntil someone puts a lot more effort in to find a way to bypass this you’ll need to have hardware that has uses the same chips for disk and networking as Synology uses. It also appears that they are taking drivers out that aren’t specific to the model it’s running on.
Ok, so try keep it as close to native as possible.
Does it work on Intel 8th Gen CPU's?
What SATA chipsets and LAN chipsets are safe?
-
Hey guys, So what is the deal now?
One loader maintained for DS918 with 16 drives?
So if I want to use the latest DSM I should make sure I have 4th Generation or newer?
I have two systems with 1st Gen i7 and 3rd Gen i5. I will upgrade these.
Can I go for a 8th Gen i3/i5/i7? And for motherboard do we just make sure it has Intel SATA, Intel LAN etc?
Thanks
-
Let me know if you have trouble and don't understand the instructions. I was a bit vague, they're personal notes I made for myself.
-
14 hours ago, Lillzo said:
it is not clear to me what the process is:
-change the above mentioned 3 files on the already prepared USB stick? What pat file do you use then?
-or you change them in the PAT file?
Thanks.
How to downgrade:
Replace zImage, extra.gz and rd.gz (open synology.img -> image.img with 7Zip) with the one from DS3615xs (use the opposite of what you have installed currently) so you will force a reinstall of DSM.
You cannot migrate the settings, so you have to do a clean install (keeps your data). Afterwards replace the above files again with your original bootloader, for me its DS3617xs and do a fresh install again.
What this means is, if you have 3617, then download the 3615 loader. Extract the files above using 7zip from the 3615 loader, use OSFMount to modify the 3617 with those files (by replacing them) and then make a USB with this modified 3617 loader.
-
Thanks for the tip guys. Saved my bacon today too
-
On 8/7/2018 at 7:54 PM, chipped said:
Had some issues, booted up and I started up the migration using 1.03b and 3617, however after it says Installation Completing it will reboot and I can’t get back into it.
I can see it’s boots up and there is HDD activity, I can ping it however I can’t login with SSH or to the web browser.
Any ideas?
Specs are:
Motherboard - H77-D3H-MVP
CPU - i5 3450
Loader - 1.03b DS3617xs
Baremetal - Yes
SATA - Onboard Intel and a Marvell based 4 port SATA card.The above system is now working.
Previously on DSM 6.1 my network settings were set to MTU 9k (9000) on a PCIe network adaptor, when I migrated the system it must have been applying these settings to my onboard network card which doesn't support them.
After I disabled it the system came up perfectly.
Probably not going to happen to anyone else but just something to look out for.
-
1 hour ago, kpas said:
maybe you reboot to UEFI mode
I tried in BIOS mode and UEFI mode, same results.
1 hour ago, mmkt said:I guess the CPU is actually to old, its an Ivy Bridge and its needed Haswell and newer....
It worked fine on the DS3617xs and DSM 6.1
Nobody seems to know for sure what the oldest supported version is.
Plus, if I can get the initial stage where we migrate the previous install then doesn't that mean it's compatible?
-
Had some issues, booted up and I started up the migration using 1.03b and 3617, however after it says Installation Completing it will reboot and I can’t get back into it.
I can see it’s boots up and there is HDD activity, I can ping it however I can’t login with SSH or to the web browser.
Any ideas?
Specs are:
Motherboard - H77-D3H-MVP
CPU - i5 3450
Loader - 1.03b DS3617xs
Baremetal - Yes
SATA - Onboard Intel and a Marvell based 4 port SATA card. -
Had some issues, booted up and I started up the migration using 1.03b and 3617, however after it says Installation Completing it will reboot and I can’t get back into it.
I can see it’s boots up and there is HDD activity, I can ping it however I can’t login with SSH or to the web browser.
Any ideas?
Specs are:
Motherboard - H77-D3H-MVP
CPU - i5 3450
Loader - 1.03b DS3617xs
Baremetal - Yes
SATA - Onboard Intel and a Marvell based 4 port SATA card. -
20 hours ago, Looky said:
I know IP of my nas and I was trying as you said, but without succes. When I will come back home I will try to check log. "Error" could you make some small tutorial, how to do it?
Did you get a chance to try again? Do you have any extra info?
Give some more info about your system.
-
Successfully upgraded.
Motherboard - Z87X-UD5H
CPU - i5 4670
Loader - 1.03b DS3617xs
Baremetal - Yes
SATA - Onboard Intel and a Marvell based 4 port SATA card.
Additional Comments - find.synology.com or Synology Assitant couldn't find my NAS, I used a network scanning tool to find the IP address and browse to it manually to do the update. Otherwise all smooth.
-
Just want to confirm the upgrade path. My understanding is basically:
1. Shutdown my current DSM 6.1 server
2. Make a fresh USB boot loader with the 1.03b loader
3. Boot up and find the synology server
4. Specify the PAT file 6.2 manually
5. DSM will find my previous 6.1 install and migrate it
Does this sound right?
I've been using it for about a year now but this is the first time I actually have two change the boot loader.
Thanks
-
5 hours ago, Flotho said:
I have testet it with my HP Microserver Gen8 and ESXi 6.7!
Coming from the older Loader 1.02b for DS3617xs. Boot up with the new Loader hangs within "Screen will stop updating shortly....".
But after that i can find the DS3617xs under find.synology.com for migration!
Started the manually update with the newest pat but ended in error 13!
Have a IBM1015 in IT Mode (LSI9211-8i) and with PCIe Passtrough.
Error 13 means PID and VID are incorrect.
When you download the image, you need to edit grub.cfg to have the correct VID and PID values before you make the USB using Rufus.
Obtain values as show here http://xpenology.me/how-to-see-the-value-of-my-vid-pid-stick/
Edit them as shown here on Point 5 https://xpenology.club/installmigrate-dsm-5-2-to-6-0-juns-loader/ Good luck, let me know how it goes.
-
All hail Jun 🙏
So tempted to try the ds3617 now but it's 10:42 PM and I have to wake up at 5:30 AM haha
Everyone please report what systems you used and if you were successful.
I have three systems, 1st Gen i7, 3rd Gen i5 and 4th Gen i5.
Good night and good luck.
P.S - Thank you again Jun!! 😁
-
I am testing ds3517 with 6.17. In my case I found the 918 is not stable enough to boot with 6.17 DSM and my j4105 motherboard, however ds3517 seems to do pretty good jobs.
Ok, thanks mate. -
44 minutes ago, Olegin said:
Wait for 3617 6.2 loader, may be Jun do it.
Hi mate, I think you misunderstood. He said he was testing ds3517 with 6.2.
I was asking how he was doing this.
-
On 03/07/2018 at 9:12 AM, BigBro said:
Can you try the ds3517xs firmware? I am using the j4105 cpu and the ds3517 seems to be more reliable than the 918 for this cpu.
I'm confused, I thought the current 1.03a2 bootloader is exclusively for the 918+
How are you using ds3517 with 6.2 firmware?
-
1
-
-
Thank you so much for your time Jun, I wasn't sure if you would return. You have your own life and are not obligated to help us.
Do you accept donations?
Again, Thanks!
-
1
-
-
Hi, I’m sorry I know this question has probably been asked a hundred times.
How do I upgrade my boot stick to the newest boot loader properly?
last time I just wrote over it directly and had to put my pid and vid back in the configuration file and also had to recover the Synology.
Is there a proper way to update without losing these settings?
cheers
The New Active Backup
in Synology Packages
Posted
THANK YOU VERY MUCH!!