billat29
-
Posts
351 -
Joined
-
Last visited
-
Days Won
10
Posts posted by billat29
-
-
"Please be informed that piracy is not tolerated in the forum. The use of Quickconnect IS an abuse of Synology's services." Forum Mod. who doesn't seem to get GNU.
OK I'll bite.
The fact that the Quickconnect code may be covered by the GPL does not give us the right to use any service that it connects to. We could use the code to define how to implement our own QC service and modify our version of the DSM code so that it points to ours not Synology's. But using theirs, indeed, creating false credentials in order to do so, could well fall under the scope of various computer misuse acts around the world.
-
Luckily I still have the logs ....
update.synology.com
checkip.synology.com
autoupdate.synology.com
-
Just to add to the general paranoia :
While I was testing a DNS server on my network (and looking at the logs), I found that my box - which has quickconnect off - contacted account.synology.com and another url (I forget) which retrieved my external IP.
So they probably have a better idea of how many people are running XPEnology than anyone here
-
Have you selected option 3 for AMD in the menu?
Hang on. Are you using the v1.02a alpha loader? I don't think it has AMD support in it
-
I was very pleased to see that Andy was back and doing an update. I had a bet with myself about how long it would be until someone asked when is it ready.
I lost.
It looks like a big change so I'm sure that migrating the existing content, users etc will not be a trivial task - especially as most existing installations have probably taken each upgrade step along the way.
But I'm looking forward to it.
-
Yes, it works for Gen 7's.
Can anyone suggest any help or places where the confirmed latest build of Jun's loader can be downloaed please?
It works on N54L. My signature shows that I have an additional nic (left over from another project) but I can confirm that the onboard nic works just fine.
I followed the procedure in the first post of this thread. If you read it, it will point you to jun's OP. Right at the beginning of jun's post are two links either of which will get you the right loader for 6.0.
Be aware that the first link gets you to a folder which also contains jun's alpha loader for 6.1. You don't want that one. You want v1.01.
-
What hardware are you running?
and what version of the bootloader are you using. I'm a bit worried about "system.img"
-
Maybe it will be better to install ESxi on N40L and after Xpenology
-
Non of the Images worked with my N40L so far. There was no Network-Connection for sure. I checked the port on my switch and also the ARP-Table.
Because the System was stuck with 6.1 on loader 1.01 and 1.02 not working, I had to format the first partition to downgrade from 6.1 to 6.0 because he just offered me to recover the system which did not work. A reinstallation or forced installation was not possible on the N40L as I've described before.
When jun originally posted 1.02a he said "no AMD yet"
-
Hallo
I use the 6.0.2 Jun's Mod V1.01 loader with DSM DSM 6.0.2-8451 Update 9.
Can i Upgrade the Bootloader to DS3615xs 6.1 Jun's Mod V1.02-alpha and DSM Version: 6.1-15047-1 or is dis not Possible? or ist this bootloader not Stapel, and the Machines can Crash?
I have a HPE Microserver G8 i3 4130 and 2 GB ram.
Thanks for Information
It's an alpha version. OK for testing but I wouldn't trust my data with it yet.
-
Hi everyone, and thanks for all your support.
I have a HP Microserver n40l server, and I have followed all the instructions for setting up jun load 1.01. If I plug a VGA cable I see "Booting the kernel". But the problem is I cant find synology nas through find.synology.com or synology assitant. I have tried with a lot of different usb with same result. I think that this HW is supported. I have checked that my mac is fine as VID and PID. Also I have tried running wireshark in a laptop with rj45 directly connected, I cant see any dhcp request.
How I can debug this?
thank you!
are you selecting the amd-boot option?
Nope, should I ? Thanks!
Yes. You should.
-
im wondering how is everyone able to do the incremental updates? I had version 5 till i broke my box. now im finding out that with win32disk imager once the image is written the Alpha version i cannot edit the grub file because its not visable within windows explorer only partition master can see the usb key which i cant assign a drive letter. can someone tell me what the f*** is going on?? the arcao jun file was fine from october???. but the alpha one i cant make the necessary changes...
I would be surprised if you could see the files from WIndows Explorer. I used OSFMount to mount the image as per the tutorial referenced here http://xpenology.com/forum/viewtopic.php?f=2&t=20216
-
Sorry if this is *** obvious and you have checked this - but is the VM trying to boot from the new disk rather than from the Xpenology boot loader?
-
Does anyone read what I wrote above? READ.
Happens every release
I did once think of writing a general guide - read the forum; set auto updates off; don't update until you know it works; always have a backup; and above all - read the forum.
But noone would read it
-
Yes. The next screen should be the one that asks you whether you want to keep all your settings or not.
-
The virtual disks are too small. Try 20Gb each - and you can choose not to allocate all the disk space when you create them
-
Check that they are not both using the same mac address
-
When you setup your DSM, did you go into Control Panel and change the update settings from "newest DSM and all updates"?
If not, then I am going to guess that it downloaded DSM 6.0 and tried to apply it.
So. What to do?
You could read this http://xpenology.com/forum/viewtopic.php?f=2&t=13288 and try the suggestions there.
Note the disclaimer
-
Are there any news about update 9? It isn't really specified what issues it is causing, and I can't see much about related topics either.
It's been running on my N54L (disclaimer: There's a HP NC360T card in it) for at least 10 days. So far without me noticing any problems.
-
Im not 100% sure but as i remember some people got this problem before. Try with different pendrive
Good suggestion
-
Ah wait. Are you trying to install DSM5.2 with jun's loader? That won't work.
-
I'm a bit confused about what you are doing, but then if you have been struggling with this for a while, then you have tried "everything".
So. In your searches, have you found that your LSI card is supported?
What version of the bootloader are you using and where did you source it?
I just found the USB stick I was previously using for 5644.5 and I seem to have been running the unmodified cfg file. So you shouldn't need to modify anything.
-
Hello to all,
sorry if my question is on another topic already answered, i search but i didn't find something...
I am running windows 10 on my main machine and i have xpenology 5.2 installed on vmware player 12 and i want to attach it 2 3tb's and 2 4tb's hdds so i can benefit from SHR. I tried to add physical drive through vmware player but it give's me error, possibly because the drives are above 2tb's.
Is there any way i can add these drives on vmware player or i must install xpenology on esxi or bare metal ?
Thank you.
"Workstation Player supports physical disks up to 2 TB capacity."
https://pubs.vmware.com/player-12-windo ... -guide.pdf
page 142
-
Hello All,
could someone help me to integrate "Usb 1.1 ohci-hcd driver" on my N40L ? (jun's release).
I was waiting for the new quicknick release that should integrate it but I was thinking to try it myself
I'm pretty happy with the Jun's release, only missing my USB UPS due to this driver not integrated.
I was waiting for the much discussed quicknik release hoping for the same driver to get my USB printer working on my N54L, and then I found a USB 2.0 hub in my box of computer bits.
I plugged it in (unpowered) and it all worked.
Say bye to Quickconnect
in Packages & DSM Features
Posted
@fonix232
Interesting. There is a theoretical point about not putting more restrictive terms on GPL code but we're only be arguing about a small part of the system.
What you say makes sense. Synology are not immune to the same market forces that have shaped the computer industry and that means first - you can only make money selling boxes for so long and then you need to unbundle the software and services.
Second, when you do unbundle, if you go do the route of selling upfront software licences, then at some point you find you are not getting new users and you run out of reasons to sell new licences to your existing users.
Hence Cloud and subscription based functionality.
However, this will only work for them if the guys who made their reputation in the company by shifting boxes can change their mindset to the new order. My experience in the industry says that is not certain.