siulman

Alguien ha probado a comprar la tarjeta de red Intel? Yo tengo un proliant g8 y que desastre cuando actualicé a 6.2.1...perdí acceso... jeje

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5 update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3617xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Microserver Gen8 - Additional comments: REBOOT REQUIRED

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3617xs - Installation type: Baremetal (HPE Proliant MicroServer Gen8) - Additional comments: No reboot required

Hello guys. Solved. Upgraded to DS3617XS using a new pendrive.

@sbv3000, Same behavior with a reservation on the DHCP server. I had some hope as the first 4 or 5 reboots where ok but then it failed.... Sticks in “booting kernel”...but nothing happens.... I am really not sure about the network issue... any other idea? @Dfds, I already tryed this, same issue...

Hello @sbv3000, Thank you for your response. It’s funny, I am a network egineer so I have never questionned the network in this issue.... Specially because I had the same set up before with “openmediavault” and it was working perfectly. I am using a static @IP adress in the server out of the DHCP scope of the DHCP server. I’m going to try to put a reservation. That’s easy and we will see.... I am using the native NIC MAC adress. I changed that in creation process of the pendrive. The DHCP server is a fortinet firewall, I should be able to debug and sniff the DORA process for the DHCP...I can try this also... Are you sure there is no possible “loader” error or something?

Hello guys, I am getting crazy with this one. I have an HP Proliant gen8 G1610T with Jun 1.02b ds3615xs on it. Everything is running fine except sometimes when I reboot my server or I power it off/power on DMS is no starting! Le USB drive is loading because I see the “Booting Kernel” or “uncompressing kernel” message on the CLI console but DMS does not start. I don’t see it in synoassistant and it’s not responding to a ping through the network. How do I solve it? I just manually reset the server. Either reset from the ILO either power off / power on. This issue is completely RANDOM. Sometimes it happens, sometimes not, and this is what is killing me. I have been days without the issue doing reboots and sometimes I have it everyday... Should I test with ds3617xs? I searched on the forum but didn’t see this issue to others.... Help please.

Hello everyone, just wanted to inform I have tested to plug into my server a pendrive with an old bootloader version. Using the "syno assistant" just clicked on "repair" and everything just booted with the old version. So I guess if and update fails, I just have to flash a pendrive with and old working bootloader and "repair" to boot.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 - Update 3 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HPE Microserver Gen8 G1610T & Intel NUC ESXi 6) - Additional comments: Requires reboot

Hello @Polanskiman, Thank you for your response. Message received and understood. Before any update I always check the forum and make sure people succeded with the same hardware as me + I test the update on my VM. However, how to proceed if the update fails? Is there a roll-back method? I understand when you proceed with an upgrade you are flashing the bootloader usb key but also performing some modifications in the primary disk where the system is installed. So, even if you reflash the usb key with the previews bootloader, is the primary disk blocking for the roll-back? or can you do a "repair" thing ? Thanks

Among all what you said, I decided to do a “win32imager” of my current microsd. I flashed it in a pendrive changing vid/pid and worked perfectly. I think it’s the easyest way. I am just entering into the xpenology world. This is great, however, I still have a doubt. What happens if someday for some reason I do an upgrade and it fails. How to roll back?

Hello @IG-88, Thank you for your response. This is a pretty good explanation. In understand now why "version" "6.1.0" was displayed in my "syno in assistant soft" when I tried to boot with the new USB Flash using 1.02b indeed. I though upgrades did not write anything in the USB stick/microsd. I realize now that it does! Concerning the first point... I was not able to open the partition where the "grub.cfg" is in a my microsd card. Windows10 just propose to format de partition but apparently can't open it. Concerning the second point, allow me to ask: What happens is my microsd fails tomorrow? How can I restore my system? Giving the fact I am running 6.1.4-15217 update 3 in a DS3615xs in a proliant gen8 and there is no bootloader for this kernel.... What is the procedure in this worst scenario? Is there a tutorial or somehing? would the "repair" work?

Responding to myself and maybe in order to help if someone is in the same situation as @mikhan stated below, chaning the mac adress from the grub menu worked perfectly. --> by pressing C in grub menu, enter "mac1 your_mac" in command line, then ESC and boot. I still don't know why creating another usb stick didn't work, if someone can provide some clarity on this it would be great... Thanks!

Hello @Polanskiman, I understand what you say and totally agree, Personally, I won't be using quickconnect, however I don't see a reploy to the question of the original title... can we change the mac adress after? I did a fresh install of DSM 6 on a proliant gen8 in a microsd and everything went smoth. As I used microsd card I didn't have to change PID, VID and therefore also forgot to change mac-adress as it just loaded straight forward. Is that serious and can provoke potential issues? I realized it was not clean when I tried to install xpenlogy on a nother VM in the same LAN...obviously same mac with different @IP cause conflicts... I tested then to set up a new flash usb stick setting VID PID and mac (with OSF mount) but when starting the server the "syno assistant", it provides a DHCP @IP as it was a "new install"? and just propose a "repair". I guess it's logical because of the new mac adress... What should I do? Should I proceed with the repair? I don't want to lose all my config! Changing the mac adress from the grub menu itself pressing "c" would be better? won't it break anything? Please help!!!! I would like to avoid a fresh install

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Proliant Gen8 G1610T) - Additional comments: Requires reboot

Hi guys, need your help here. I'm trying to install xpenology (DSM 5.2) on virtualbox. I've downloaded the .iso file. Followed the steps here:http://www.wijngaard.org/synology-virtual-diskstation-5-1-with-virtualbox/ Everything boots fine, but when I'm in the installation menu, I get: "unable to format the disk (35) " (see attached) Could you help? Thanks a lot. https://photos-1.dropbox.com/t/2/AAA2Oz ... apture%20d’écran%202016-02-04%20à%2020.41.21.png/EIXrvAcYqnogBygH/iNm-6b65r7cXFqv13--TbmNDtRVc0l4Bfl2E-MFbZpI?size_mode=5