Polanskiman
-
Posts
2,735 -
Joined
-
Last visited
-
Days Won
120
Everything posted by Polanskiman
-
I've been trying to use v1.01 and v1.02a on a laptop Toshiba Tecra I had laying around for the sake of testing. So far it has been a failure. I'm using a serial consol to see what's happening and this is what I see. There is nothing else in the output other than this: [ 2.857140] ata3: send port disabled event [ 2.857152] ata4: send port disabled event Looking at the bios ata4 is the esata port. There is no mention of any ata3 so not really sure what that port is. I would need to open up the case to see. Anyhow, ideas on the above? Most laptops come with 4 SATA ports. SATA0 is usually the CD drive, SATA1 is the main HDD, SATA2 is most probably an unsoldered header on the main board, and as you discovered, SATA3 is the eSATA. Any way, those messages are not errors, it simply means the kernel picked up there's no device on them, and disabled them, simple as that. sata0 is the HDD, sata1 is the ODD, sata2 and sata3 do not show up and most probably are empty headers as you said. sata4 is the esata port. Yes I am aware those messages are events and not errors, yet kernel loading seems to stop and no further output is seen on the consol. My question actually lies on why this is happening.
-
Then I think the reason you are seing the error message is because of the explanation I gave above. Synology is checking that you are on a real Synology hardware. Since not, that check fails and you receive the above message.
-
Are we talking about buying the license or hacking Surveillance Station. If the latter, please be advised that piracy is not tolerated here. If the former you might not be able as I believe that Surveillance Station uses at least an officially valid paired S/N and MAC address to make sure you are on a real Synology.
-
I've been trying to use v1.01 and v1.02a on a laptop Toshiba Tecra I had laying around for the sake of testing. So far it has been a failure. I'm using a serial consol to see what's happening and this is what I see. There is nothing else in the output other than this: [ 2.857140] ata3: send port disabled event [ 2.857152] ata4: send port disabled event Looking at the bios ata4 is the esata port. There is no mention of any ata3 so not really sure what that port is. I would need to open up the case to see. Anyhow, ideas on the above?
-
Oui. -
You are redirecting to a French topic which basically is talking about the same than the one here. Instead please post directly here, in English.
-
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
Polanskiman replied to Polanskiman's topic in Tutorials and Guides
You could start with loader v1.01. You need to select the 3rd line in the Grub menu which says AMD. Not sure what NIC you have but several people have been able to use the loader with N54L. Make sure you are using the real MAC address of your NIC in the grub.cfg file, that your router has DHCP enabled and that the router is giving out an IP address to your machine after you have selected the 3rd line in the Grub menu. You need to log in your router to make sure. Post back with the outcome so others can benefit from your experience. -
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
Polanskiman replied to Polanskiman's topic in Tutorials and Guides
No sorry. I have stated that this tutorial will remain at DMS 6.0.2, loader v1.01 until Jun's latest loader v1.02a come out of alpha. I do not want to promote Jun's latest loader until it has been tested extensively. You can check the main thread in the announcement section with all the links to loaders in the OP. -
[Off topic. Post Deleted. Please post in the appropriate thread.]
-
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
Polanskiman replied to Polanskiman's topic in Tutorials and Guides
Although I have not tried this I am fairly certain it will not work from a CDROM. The media needs to be writable. -
Modules from 6.0.2 will not work for 6.1. Kernel has been updated as you have seen and all modules needs to be recompiled accordingly. Why don't you stay with DSM 6.02 and v1.01? The latest loader v1.02a is at alpha stage and is mainly for testing purposes although some people are not worried about using it in their 'production' boxes.
-
FYI.. I have just checked and the 'phantom' volume crash errors are reported on the Official Synology forums - on Synology hardware - for the original 6.1 release. So it looks to be an issue with the release - and not Jun's loader.. Which has now been fixed.. #H I see. I should have done my homework! 'Good' to hear it was an 'official' bug! For the sake of completeness I am adding here the link to the report about the issue which I suppose is the one you are referring to: https://forum.synology.com/enu/viewtopic.php?t=128834 What is strange though is that I can't find any other official reports on this on the net, other than the topic above. Below is what the release note of update 2 for DS3615x says. The 'volume crash' message we are seing might be the one I have highlighted in bold below, although it is not very clear what 'display' message they have fixed:
-
[Tuto] Installer/Migrer DSM 5.2 à 6.0.2 (Loader Jun)
Polanskiman replied to Polanskiman's topic in Archives
Oui, rien pour l'instant. AMD n'est toujours pas supporter dans le dernier loader v1.02a. Ne surtout pas faire de mise à jour à DSM 6.1 avec v1.01 - Restez donc avec v1.01 sous DSM 6.0.2. -
Since Update 2, my NAS does not produce the 12h volume error, or the inaccessible DSM dashboard. I'm currently at 1d 6h uptime, mainly because I installed a 5.25" -> 4x 2.5" bracket last evening. But apart from that, my NAS has been running non-stop since last Friday, with Update 2. I understand but I'm in no rush. Those volume errors being gone with an official update from Synology is kind of weird and doesn't sound quite right. Is Synology fixing Jun's patch now? . Joke aside, I'd rather wait Jun to come up with a more stable release.
-
[Deleted a whole set of out of topic posts.] This is the English section. Please comply with that basic requirement. If you are not an English speaker, please make an effort as google translate is not always accurate. You also have the possibility to posts in the Russian Section.
-
I am holding off. I do not have the need to go to 6.1 yet. Also, I am not liking those "volume crashed" or whatever messages that appear on screen even if they seem to have disappeared with update 2. Finally there are still some module loading issues with his release and also still no AMD support. Only Jun himself can answer that question but I suppose that if he has the time he is probably also looking into the recently published source code of DSM 6.1
-
You say that you "moved all your data". Does that mean you did a fresh install or does it imply an upgrade from DS3615xs?
-
Whats the actual knowledge on this. Do i need to worry that my data will be lost if i upgrade? Or i just get the new loader and should update without a problem and not loosing data? (running now DSM 6.0.2-8451 Update 9 baremetal on Hp MicroServer Gen8 G1610 4 gb ram with Juns 1.01 loader) As the topic title says, it's an alpha loader. Jun has made it clear it's for testing purposes only. Now, nothing stops you from trying it on your actual box with data in it but you need to be aware of the possible outcome. Some people have tried it without major issues. If I was you I would wait to use the loader on your 'production' box. The choice is yours.
-
This drivers list is for DSM 5.2 not for 6.1.
-
All of this is being addressed at the moment. SPAM, moderation enforcement and whatnots. Hopefully with the new engine it will all get better SPAM wise and we moderators can focus more into actually moderating the discussions instead of deleting spam day and night. Hang in there.
-
Thanks for providing the new serial format, and the permanent characters for the DS3617xs! I've made an updated generator, you can find it here. Also found an issue in your method. When you generate the serial, you do not care about the padding of the numbers after the "N". It MUST be 6 characters in total. So it cannot be simply "11", it has to be something like "001001" or "000011" or "100001". Thank you very much for your work, But how do i enter mac address? Because the serial number is registered at https://account.synology.com But as you want to run quicconetc gets bogged down There is no need to use QuickConnect. Simply setup a custom DDNS instead.
-
Piracy and violation of Synology propriety apps will not be tolerated in the forum. Topic closed.
-
Piracy is not tolerated in the forum. Topic closed.
-
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
Polanskiman replied to Polanskiman's topic in Tutorials and Guides
No need to change the S/N. The serial number doesn't do anything much by itself. For QuickConnect to work the S/N needs to be paired with a Synology MAC address. I do no support the use of QuickConnect on Xpenology as it's a violation of Synology's service. For the MAC address just use the real MAC address of your NIC. Where do you see such "not authorised" message? When using QuickConnect? If so then it's normal because Synology uses a paired S/N - MAC as commented above. -
It's not that hard to understand that DS3615xs "v1" format serials DO NOT WORK ANYMORE. I hope this makes things clear. I'll update the serial generator as soon as I have some free time to think about the logic needed to do it. So if any of you has some experience with JavaScript, you're welcome to help. On the other hand, it would be nice to have a few "v2" format serials (the ones that are similar to "1480MIN######", as per another online generator), with the respective models and MAC addresses of that unit, so that we can get things rolling again. Please keep the tone down. Also please read your PMs.