chege
-
Posts
143 -
Joined
-
Last visited
Posts posted by chege
-
-
Take a look at this post.This is exactly how I was able to fix it without any personal data loss. However, apps and settings WILL go bye bye: viewtopic.php?f=2&t=20216&start=2770#p100378
Thank you for your prompt reply. I have read it. I've seen you have erased first 2 partitions of each drive? I've seen somewhere on the forum, that only first partition of each drive have to be erased and formatted as ext4.
As i mentioned some time ago, most likely during upgrade dsm is creating 2nd system partition as a backup, thats why you have 2 similar partitions. One is with old version and one is with new version. Thats why if you brick system during upgrade you have to delete both system partitions (about 2 GB each).
OFFTOPIC
Maybe its time to change topic name, cause its about DSM 6.0.2 - DSM 6.1.1
-
What about here? https://download.synology.com/download/DSM/release/
I give up. How many download centers they have? And why i am redirected from global dl to usdl? 
-
viewtopic.php?f=2&t=20216#p72622
....
Original post by jun
I've uploaded a 6.1 alpha build to mega, for brave guys only
. (Note: AMD needs extra work. Not fully supported)....
-
I made a mistake, i migrate from DSM 6.0.2-8451 Update 11 to 6.1.1 with 15101.
Now, my DSM not starting.
I cant downgrade to 15047, any idea? I have HP gen8
DSM dont work any more with DSM 6.0.2-8451 Update 11, im scary..
Change loader to jun's 1.02a2. Its low chance it can help, but most users report that upgrade bricks xpenology, even synology users got problems with dsm 6.1.1, thats why its has been revoked. Or you have to wait till synology will release new version dsm 6.1.x.
-
There is no such update on the official synology download site, its unsafe to install it.
Not sure what you mean by that but DSM 6.0.3-8754 is official and live. I will test the update on a test VM soon but I have the feeling this will not work.
Maybe it is available from DSM update but its not here:
https://usdl.synology.com/download/DSM/release/
or here:
-
Check kitcatalogue settings. In local_config.php is option to set:
// The Full URL that the catalogue will be served from (i.e. the browsable location of /index.php) // e.g. http://www.example.com/catalogue // DO NOT include a trailing slash '/' // For SSL, use a URL like: https://www.example.com/catalogue $config['app.www'] = https://:port
-
Hi there. New update 6.0.3-8754 is here, I installed it on my "test VM" and I after reboot it enters in recovery because "you move your disks to a new DS3615x".... Any ideas? Thanks
There is no such update on the official synology download site, its unsafe to install it.
-
-
Do you have installed proper certificate from synology? Try to ping global.download.synology.com to see if you can access it.
That address pings fine from the xpenology box.
i only have the default cert that DSM has installed and comes with.
Yeah, thats the one cert. I have no idea why you dont see synology packages, but you can do 2 things and both are not satisfied.
1. download from synology site and install manually packages you want,
2. try to do hard reset from settings
-
If you upgraded DSM to 6.1 and having issues then try to uncomment AMD option in jun's loader. Some people confirmed it is working. But if you want to upgrade to DSM 6.1 it is highly not recomended.
-
Do you have installed proper certificate from synology? Try to ping global.download.synology.com to see if you can access it.
-
Has there been a fix for the APC UPC not being detected in DSM 6.0.1 UPDATE 1 or 11 pugged in either front or back.
It was working fine in 5.2 with a HP N54L, plugged in the back usb ports.
UPDATE - Back-UPS ES 500 and Back-UPS ES 350 are on the Syno compatibility list, however Back-UPS ES 700 is not
Yes there is a fix. The issue is down to the current build not having USB 1.1 Compatibility (APC USB for mine is 1.1 probably the same for all early ones, mines a Smart UPS 750).
The fix is to install a USB 3.0 card in the N54L, that acts as a hub and lets DSM see it correctly. Got mine from Amazon.co.uk here: https://www.amazon.co.uk/gp/product/B01C86K4IG/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
DSM 6 now sees it correctly.
Hi, I've the same issue !
Why the onboard USB doesn't work and an extra USB card work ? Isn't a parameters in BIOS ?
So, this will fix in future release like DSM 6.1 loader ? or I must buy this type of USB card ?
Thanks
DSM 6.x does not have USB 1.1 drivers and loaders does not have it yet. You can use cheap USB 2.0 hub, it should fix that issue.
-
I think it is possible, but my advice is to have one more NIC for maintenance purpose for Xpenology/DSM only.
-
About push, can you confirm it doesn't work on 6.1
To me push notification works with DSM 6.x and android device without using QC.
-
It was removed for some reason. Synology users got problems with reaching DSM after update, there is some issue.
-
Does anyone run dns server on xpenology? I can run it but cant get response from internet, port 53 is open and reachable.
-
Why not use the 3615sx loader then if that is what you want instead of fiddling wit the grub.cfg file?
It was for testing purpose only, downloaded synology.img, its the only image for version 1.02a2 by jun i could find.
My post is for information only if someone else get error 13, its some point to start to fix it. Next step would be to manually install pat file for different models.
-
don't try to install 6.1.1 if the updater suggests it, 6.1.1 uses a new kernel 15101 instead of 15047 from 6.1 so jun 1.0.2a/a2 will not work
Fresh install on esxi works fine.
-
I dont know if this is only possibility but today i did something unusual and got error 13 during installation. I started fresh VM under esxi with juns loader 1.02a2. Its loader for ds3617xs, since i wanted ds3615xs, during boot up i changed 1 line in grub, i changed
loadlinux 3617 usb
with
loadlinux 3615 usb
.
This caused error 13. But after restart and leaving all untouched installation went fine.
-
Yes, there is problem with MTU set as high. There was few topics about this, just search forum. MTU higher than 2000 or 3000, dont remember now, causes issues with WebGUI, etc.
https://xpenology.com/forum/search/?&q=mtu issue login&sortby=relevancy
-
I'm back again
sorry!Do I need to take into account any of the options listed by the installation?
db.use_mysqli - true
db.host - localhost
db.port - 3308
db.username - kitcatalogue
db.password - ******
db.database - kitcatalogue
Thank you...
Sorry i didnt mention about hat. You need to make some tweaks here:
- standard db.port is 3306,
- db.user is root,
- db.password is blank, no password.
Also to login as root you need to use command: sudo su -. Admin password.
-
SSH commands:
- mysql, (to open mariadb)
- create database ;
Thats it.
Glad to hear you made it.
-
Hi,
Yes about the MTU, it changed automaticully when trying to make the cluster..
It does do something with the other NIC of the other VM..
Going to check if I can find anymore info on the web..
One more suggestion, im not sure where i saw it but one or both "machines" require static address on nic designated to HA cluster.
-
Yes a real cs407, but with the 3615 I haven't had this issue
I meant xpenology DSM. But with real synobox its not a problem.
[SOLVED] Unable to access Synology after upgrade
in DSM 6.x
Posted
Search forum, there is few informations about dsm 6.0.3.
1. dsm 6.0.3 will brick your xpenology, viewtopic.php?f=2&t=32842
2. how to deal with it, few topics