DSM not starting SOMETIMES in proliant gen8 G1610T


Recommended Posts

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.

Link to post
Share on other sites

check your network cables and switch connections

also check your router/dhcp server if you have set a static IP on the NAS or an address reservation on the router - only set one (I would recommend a router reservation)

if you run a network sniffer you should be able see if the DHCP request/response traffic

Are you using the native nic MAC address or a different one? - use the native MAC.

It sounds to me that there is some sort of problem with IP address being allocated and the above might help you trace it

Link to post
Share on other sites

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?

Link to post
Share on other sites

@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...

Link to post
Share on other sites

Not sure if your model has the feature, but can you access the ilo ssh/serial port and watch the 'full boot' process? You might see a kernel panic/driver issue or other error.

Another test could be to use a spare hdd and create a clean install of DSM (disconnect your raid drives of course :) ) and see if you can replicate.

Link to post
Share on other sites
  • 1 month later...
  • 1 month later...

Same here with Jun 1.02b ds3615xs, i dont have a screen plugged in so cannot see the status.  However I have switched to DHCP (not static or allocated on router) and so far seems to be OK. 

 

Any thoughts on why would changing to DS3617XS fix this, and where you got the idea?

 

 

Link to post
Share on other sites
  • 2 years later...

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?

Link to post
Share on other sites

i'd suggest to update to 6.2.3 and check for crashed drivers in dmesg

with 6.2.1 and the original extra.lzma i'd expect some drivers crash on boot (that's the reason your onboard broadcom failed)  and that can results in restart and shutdown not working

when using 6.2.3 the old original extra.lzma will work again properly (synology reverted the changes from 6.2.1/6.2.2) and you onboard nic should be working again

 

if disk hibernation does not work with 6.2.3 then its because of log activity, fix it with this

https://xpenology.com/forum/topic/32861-hdd-fail-to-hibernate-after-upgrade-from-622-to-623/?do=findComment&comment=179577

 

 

Link to post
Share on other sites
1 hour ago, IG-88 said:

i'd suggest to update to 6.2.3 and check for crashed drivers in dmesg

with 6.2.1 and the original extra.lzma i'd expect some drivers crash on boot (that's the reason your onboard broadcom failed)  and that can results in restart and shutdown not working

when using 6.2.3 the old original extra.lzma will work again properly (synology reverted the changes from 6.2.1/6.2.2) and you onboard nic should be working again

 

if disk hibernation does not work with 6.2.3 then its because of log activity, fix it with this

https://xpenology.com/forum/topic/32861-hdd-fail-to-hibernate-after-upgrade-from-622-to-623/?do=findComment&comment=179577

 

 

 

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? 

Edited by siulman
Link to post
Share on other sites
10 minutes ago, siulman said:

But when I am forced to reset because the system is not booting, after DSM is running again,

no, if its not booting and then boots pressing the reset button then i have no idea beside bios update

if its a microserver gen8 then a lot of people have this hardware and dont have such problems, so you might search the forum about the bios version they using

 

i do remember that there was a problem with a older microserver that lost bios settings after shutdown

look here

https://xpenology.com/forum/topic/1909-annoying-bios-reset-issue-is-really-bugging-me/

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.