MarcHT91
-
Posts
34 -
Joined
-
Last visited
Posts posted by MarcHT91
-
-
9 hours ago, Polanskiman said:
Anyways, did you try with a formatted drive?
Did you make sure to modify the MAC address on v1.02b before upgrading to match the one on v1.01?
I tried with the formatted drive. No luck either
-
Tu proliant es amd? Si es el caso, no te queda mas que formatear las particiones del dsm (no de los datos) y reinstalar la version 6.0.2 con el bootloader 1.01 (creo que es el unico que funciona con amd)
-
23 minutes ago, Polanskiman said:
That Dell Vostro 230 does have a serial port. Having a serial adapter like these ones would enable you to see the boot logs.
Anyways, did you try with a formatted drive?
Did you make sure to modify the MAC address on v1.02b before upgrading to match the one on v1.01?
Is the MAC address fixed in the router?
I did again the procedure this time on a baremetal starting at 6.0.2 and it worked fine. So I am not really sure what is going on with your setup specially when it is actually working on DSM 6.0.2 which mean the NIC is already recognized.
yes, i've seen the adapters I might end getting one... With a formatted drive you mean using just 1.02b without doing first 1.01?
I modified mac address through grub using the console (as far as I know capital letters make no difference in MAC addresses), and the computer is connected straight to a laptop, without any router. If I use the laptop as a DHCP server to give xpenology an IP could help?
-
4 hours ago, Polanskiman said:
"It doesn't work" will not help resolve the issue. Please provide more information. What do you see on screen for example? Do you have access to boot logs via serial? Those would give as a clue of what is happening.
I tested the upgrade procedure myself on a VM with VirtualBox starting from a 6.0.2 fresh install with v1.01, then switching to v1.02b and migrating to 6.1.2 and it all went fine. I can access DSM fine which was not the case with v1.02a2 when I did the test some weeks ago. This means Jun has fixed his patch and now modules are properly copied during migration with v1.02b.
Yes, you're right, my bad for not providing any info. I can't access via serial to the computer, is there any way to get a boot log or a dump file? The only thing I've seen behaving different from 1.01 to 1.02b is the network card booting. With 1.01 the computer boots, then the nic goes off (I can see it from the laptop atached to it, it says disconnected) and less than a minute later boots again and the connection to the webgui works. With 1.02b I haven't seen this process going on, it just boots on and stays like this. My guess is than the nic drivers are not loading like they used to do in 1.01.
Thank you
-
7 hours ago, Polanskiman said:
With v1.01 only DSM 6.0.2 will work. For DSM 6.1.1 and 6.1.2 you need v1.02b.
The custom extra.lzma provided in the tutorial is only for v1.01 no for v1.02b.
If there is no information on the screen (totally black screen) then it means the loader is simply not booting. There should be at least something as mentioned in the tutorial.
Try the following on a formatted drive. Install DSM 5.2 or DSM 6.0.2 on your test machine (don't use the custom extra.lzma). Turn off the machine when DSM is installed and you can confirm having access to DSM GUI. Now burn v1.02b and modify the grub.cfg as you did for 5.2 or 6.0.2. When finished plug the usb and re-start the machine. Use Synology Asistant to find the machine and go through the upgrade process.
It doesn't works. All ok with 6.0.2 and 1.01 but it doesn't appears on the network after flashing 1.02b
-
On 6/19/2017 at 6:55 PM, Polanskiman said:
With v1.01 only DSM 6.0.2 will work. For DSM 6.1.1 and 6.1.2 you need v1.02b.
The custom extra.lzma provided in the tutorial is only for v1.01 not for v1.02b.
If there is no information on the screen (totally black screen) then it means the loader is simply not booting. There should be at least something as mentioned in the tutorial.
Try the following on a formatted drive. Install DSM 5.2 or DSM 6.0.2 on your test machine (don't use the custom extra.lzma). Turn off the machine when DSM is installed and you can confirm having access to DSM GUI. Now burn v1.02b and modify the grub.cfg as you did for 5.2 or 6.0.2. When finished plug the usb and re-start the machine. Use Synology Asistant to find the machine and go through the upgrade process.
This is the only walkaround i haven't tried yet. I'll do it tonight and let you know.
Thank you!
-
Hi! I'm having some issues or doing it wrong... When using 1.01 - 6.0.2 baremetal all worked fine. (I'm using an old Dell Vostro 230 with DS3615xs)
I'm not sure on how to update the bootloader and the DSM, what should I do first, but when I flash the new bootloader (either 1.02a or 1.02b) the system doesn't shows on lan, just with the 1.01 loader. I tried to do the update to 6.1.1 or 6.1.2 with the 1.01 bootloader and then switch of and flashing 1.02b, the system doesn't appears on lan anymore.
By now I'm just experimenting with xpenology to use that same machine as my first nas once I know how to work with it, so by now I don't mind formating the drives as I don't have any important data yet.
Thanks in advance!
-
tengo un techo de 7-8 MB/s y picos de 10MB de subida alguien que tenga el microserver que me pueda decir que velocidades tiene de upload /donwload con xpenology por si sirve de algo tengo red gigabit cableado y isp de Adamo 850/300
es distinto MB que Mb, ethernet es Gbit, es decir tendras un maximo teorico dentro de tu red de unas 100MB/s y si es fuera de tu red, la subida maxima sera de unas 25 MB/s (si tu isp ofrece 300Mbits de subida). Para que te hagas una idea, si te dicen que tu fibra es de 100Mbits, velocidad real sera unas 10MBytes.
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
in Tutorials and Guides
Posted
Hi, I.ve just got the serial to usb, but I couldn't fine how to get connected to the console, some help would be appreciated.
Thank you!