siulman

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: Proliant Gen 8 G1610 - Additional comments: REBOOT REQUIRED -- Intel NIC removed as not required anymore.

Ahahah, thanks for that! I will remember it if I go to a microsd again someday. We always miss things when reading guides... Good to read it now. However, my issue of "random boot issue" was not related to microsd as I had it with multiple pendrives way before now... since my first post actually...it's just I decided to keep always up my server as a "workaround".

No worries @bearcat, I always enjoy exchanging information, discussing and learning from others! So, for the VID/PID, I always use a tool that I've found in the past and works for me. It's "ChipEasy_EN_V1.5.6.6.exe" in my case. I obtain the vid/pid with it and then with "osfmount_x64.exe" I just mount the pendrive and edit the grub.cfg with this values. Just following the tutorial in this site...

Hello, I used its own vid/pid pre-extracted from the microSD. If you haven’t read the thread, fyi, I am still running a stable DS3617xs version with no random issues on booting.

Hello, I thank you very much for your help but I am just sticking to facts. I spent my whole day on that. After your last statement I took again a new pen drive and flashed again the 3615xs. Same random boot issue. So I took again a different pen drive this time (not the microsd) and went back to 3617xs. Boots perfect everytime... BTW, this time I don't have the shared folder appearing nor the external usb detected on the DSM. I don't know if it's related with the pen drive vs microsd. Also, I am running the latest 6.2.3 update 2 with no update issues. Finally done. Hopefully it remains stable. Thanks again for your support.

Hello, I have some updates. Here is what I've tested: 1) Removed the Intel NIC via PCI and enabled motherboard NIC. You were right. Not required anymore. The system boots but still same random issue of not booting randomly. 2) Decided to test a microsd instead of pendrive and went for DS3617xs (because I knew this solved my issue in the past but I wrongly thought for some reason that it was not compliant with my server anymore). Fyi, it does not involve a DSM resinstallation as you can just chose the option of "Migrate". This works when you go 3615xs <--> 3617xs no matter in what direction, it is very quick and smooth. This did the work. After multiple reboots and power off / power on I can tell you this does not happen on 3617xs. Don’t know why but it has solved it again. That being said, and because of using a microsd, I have now it displayed as an “external drive” in my system… I’ve never seen that before with a pendrive. It has also created two shared folders that can’t be deleted as they are said to be used by the system. I can even explore the sd-card…(grub, etc...) Is that normal? But I have a big issue: When migrating the DSM I chose the option of “downloading the latest version” which used to work. I already did this migration in the past. It installed 6.2.3-25426. When trying to update to 6.2.3-25426 update 2, it says “ Failed to install file. The file is probably corrupted” I will try to investigate this issue…but at least happy that 3617xs boots always reliably. see snapshots below.

I know what you mean and I'll do that with a laptop directly connected in the same subnet but I don't believe it will change anything. Concerning the motherboard NIC, I can go for it without changing anything on the pendrive itself? Am I able to move to 3617xs now too? It was the only setup that "fixed" this issue for me. Thanks.

I am affraid I won't be able to get a console cable right now... I would need a usb/console adapter + the console cable. Any other idea in the meantime? I've teste to put the static IP back but it's the same...

All right, let me explain again. When your DSM is up and running and you force a hard reset from the physical button (or the logical one from the ILO interface), the server reboots. Once DSM is up and running again you get a message saying that your system was unexpectedly stopped right? Ok, so I was reacting to a previous statement that said that it might be the NIC driver failing. If that was the case, and my DSM does not respond (not being able to ping it or to connect to it on web), then the system would be up and running right? Only I wouldn’t have network connectivity… But when forcing a reset through the button, next time it starts I should get the message saying the it was not properly stopped. Please, correct me if I am wrong. That being said, when you say troubleshooting via serial you mean with a VGA screen connected to it? I have ILO access. Am I not supposed to see the same through it? I will try to look for this procedure in this forum…

Well...when it comes to local environnement (LAN & Network) I am pretty confortable as it's my day to day so if you have any idea please share.... because I don't think it's on the network. I have a DHCP reservation to make sure DHCP provides same IP to my mac adress (before I used static but changed just to see if anything different could improve...). And also how it is possible that the issue is random? When it does not boot, it's not related with the NIC as the system is not booting at all. If it was, it wouldn't respond to ping of course but I would be receiving a notification from the DSM saying it was shut down unexpectedly due to my "reset" to make it work because it would have gone live! So, let's brainstorm together... what can make that sometimes the system boots and sometimes not...? Before 6.1 I found a workaround which was changing to 3617xs. I didn't have this issue on this one. But when upgrating to 6.2.1 onwards, I realized 3617xs was not working anymore and went back to 3615xs. Unfortunatelly, 3615 has this issue for me.... I've tested of course different pendrives but same.... Any information I can provide so you can provide guidance let me know.... like BIOS config or other.... Thanks in advance!

I've tried to update firmware which I think updates BIOS? I don't know what to do anymore...it is very frustrating. It can boot of for three times and the fourth is getting stuck. It is random.

Thanks for your response. I might haven’t been clear enough on my last post. I have been performing the updates since 6.1 and now I am running the lastest version of 6.2.3. I have been suffering this issue since I can remember. The thing is... I am not sure about the drivers. If it was related only with the NIC driver, the system will boot up anyway right? But when I am forced to reset because the system is not booting, after DSM is running again, I am not having any message saying the it has been shut down unexpectedly. What are your thoughts on this?

Hey guys, I am bringing back my own 2018 topic again. I know I told you I fixed this issue by updating to DS3617xs, but the fact is that once I had to move to DSM 6.2.1, I purchased an intel network card because of the compatibility issues, disabled the integrated NICs and had to go with DS3615xs as the DS3617xs was not working in that setup. I decided to keep the server up and running 24/7 to avoid any "not booting" issue. But know I want to start having the server off for some time and just power on-demand. I am facing again this issue where sometimes the server is not booting and I am forced to reset. It's painful.... Just wondering if someones have faced this before and found some workaround?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 6 - Loader version and model: Jun's v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP ProLiant Microserver Gen8 G1610T - - Additional comment: Onboard NIC disabled on BIOS.Additional Intel NIC. I was concerned on this udates because of the different feedbacks but all was transparent for me.

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922- update 4 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen8 - Additional comment: manual reboot required: Intel NIC PCIe