siulman
-
Posts
41 -
Joined
-
Last visited
Posts posted by siulman
-
-
2 hours ago, bearcat said:
@siulman Then, I will give you a "lesson" that might help you the next time you want to use a MicroSD card in your G8 🤗
If you used that Windows(?) software to read out a VID/PID on a different computer than your HP G8 Microserver, you failed..
When using a MicroSD card to boot from a HP Gen8 Microserver you must use: VID 0x0424 - PID 0x4030
That is the internal card reader, (located on the USB bus).👍 It has been posted more than once here in the forum I think🤔
Using this VID/PID will "hide" the memorycard, and stop it from beeing mounted in DSM.
Edit:
BTW: as seen by this post from Omar, he also had some "funky problems" due to wrong/missing VID/PID on the MicroSD on his G8 setup.
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".
-
15 hours ago, bearcat said:
FYI: I have read the thread, and I know you sorted out your problems for now 👍
I'm just curious, as I have never had that problem myself with My G8, that the card mounts as an external drive.
So Im asking you, as 1 techie to another: what VID/PID where you able to "pre-extract" from the microSD?
btw: how do you "pre-extract" the VID/PID from the microSD?
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...
-
1 hour ago, bearcat said:
What VID/PID did you use for your microSD ?
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. -
2 hours ago, flyride said:
A couple of observations:
1. "Because of using a microsd" [there was an effect]. MicroSD vs USB pendrive does not generally cause the issue you describe.
2. "[The issue was fixed] with 3617xs". This probably isn't accurate either given the number of success reports on your exact hardware.
It's likely that a reinstall of DSM, or discontinuing use of an intermittently faulty pendrive was the resolving factor.
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.
-
16 hours ago, flyride said:
You can activate the mobo NIC without adjusting the loader.
I'm not sure what your last question means. You always were able to install whatever DSM dialect you wanted that was supported by your hardware. "Going" to 3617xs (presumably from 3615xs) involves a reinstallation of DSM, but I think you know this. You'll need to burn a new, clean loader in order to do it though. However, if I may borrow your quote, "I don't believe it will change anything."
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.
-
2 minutes ago, flyride said:
The only thing I can think to do is have you set a static IP on a PC and then remove all other devices (including firewall) except the NAS and the PC from the network switch. If it worked reliably then at least you would know it was related to one of the removed devices.
If it continues to fail, there are still many failure possibilities - DSM, NIC, server hardware itself. I'll also point out that you switched NICs during this process and the problem persisted, so that doesn't suggest intermittent network to me. But on 6.2.3 you should be able to use your onboard NIC okay so you could swap the Intel CT for the onboard as it seems you want to try most everything you can.
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.
-
17 minutes ago, flyride said:
Not guaranteed. The system may be booting but not in a state where it can generate that log.
No, I mean connecting to a COM port. The DSM console (all the boot messages and direct Linux access) are only accessible via serial, not the hardware console.
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...
-
28 minutes ago, flyride said:
I don't really understand this statement, and don't think your logic is correct here. You posted a boot screen when you cited that it was not booting at all. That is all that is ever displayed from the loader, so we know the boot loader has executed. DSM does not post a notification to the VGA screen during a reset, and if the network wasn't working there would be no notification via any other means. So you probably don't really know the state of things when you do not have a network connection.
The only way to properly troubleshoot this is via serial, and you will be able to monitor DSM's state without any network connection. How to set up and use a serial connection is well chronicled on this forum....
Also if you are trying to minimize all variability, you should reconfigure back to static IP.
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…
-
6 minutes ago, flyride said:
I just have to point out that it's the same hardware and network and you've experienced this problem across three different DSM versions.
This is not a normal behavior. Something in your local environment is causing it.
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!
-
On 11/23/2020 at 2:42 PM, IG-88 said:
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/
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.
-
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
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
-
53 minutes ago, jfisbein said:
Hola,
Tengo un HP Microserver Gen8 con cpu G1610T, sin virtualización, con DSM 6.1.7-15284 Update 3, Loader 1.0.2b emulando DS3615xs, y con 4 discos (3 en las bahías normales y uno en la del CD). Me gustaria actualizarlo a la última versión del DSM que si no me equivoco en este momento es 6.2.2. Me podeis confirmar que estos son los pasos necesarios:
- Actualizar loader a 1.03b
- Actualizar DSM a 6.2 (usando la funcionalidad de update del propio DSM?)
- Instalarla una tarjeta de red compatible (ej: https://www.amazon.es/dp/B001CY0P7G ) y desactivar mediante la bios las tarjetas de red internas.
- Actualizar a DSM 6.2.2 (usando la funcionalidad de update del propio DSM?)
-
Disfrutar!!
Preguntas:
- Al actualizar el Loader o el DSM, hay que cambiar el contenido del grub.cfg o puedo mantener el grub.cfg que ya tengo?
- Puedo hacer la actualización de la tarjeta de red antes del primer paso y así saltar directamente a la versión 6.2.2?
Gracias!
Hola,
Puedes meter la tarjeta de red, desactivar las internas desde BIOS y no cambiar nada. Hasta ahí bien.
sin embargo, tendrás que usar un usb con loader nuevo por lo que no se puede actualizar desde el propio DSM creo?
en mi caso para evitar líos, hice un backup de la config, después hice instalación nueva del sistema (los datos se conservan) y restauro la config.
-
11 hours ago, gauchim said:
Hola compañeros,
Yo estoy actualmente con el loader 1.02b de jun y el DSM 6.1.7-15284 en un DS3617xs en un HP Microserver Gen8 con cpu G1610T, virtualizado sobre un ESX 6.5. Quiero meterle el DSM 6.2.x pero tengo varias dudas: ¿Qué loader debo usar ahora? He leído por ahí que el 1.03b deja el DSM inestable. ¿Es así? ¿Puedo usar el 1.04b? ¿Existe la posibilidad de usar el 1.04b con esta configuración? En cualquier caso, ¿qué debo cambiar del loader que user para que arranque el sistema?
Gracias!
Hola compañero,
1.02b solo es para DSM 6.1.x
DSM 6.2.x necesita de 1.03b o 1.04b dependiendo del modelo que quieras usar:
1.04b es para ds918
Si tienes un Gen8 G1610T como tengo yo, tienes que usar 1.03b con DS3615xs. El DS3617xs como digo arriba, no funciona. Lo de inestable yo no he leído nada.
Todo esto que te digo es para instalación baremetal. Si virtualizas, no tengo muy claro si puedes jugar con otros loaders... tal vez otra persona te lo pueda aclarar. -
13 hours ago, OldSmurf said:
@siulman wrote in this old thread ... "by pressing C in grub menu, enter "mac1 your_mac" in command line, then ESC and boot." I simply cannot make this work.
I have no problems getting into the grub menu pressing c. Then I get the command line.
If I finish the mac1 command with <enter> it will say unknown command; if I go into the e menu/screen I can move the cursor to the MAC position and modify the mac address. This will work for one boot, but it won't keep the changed after a reboot.
Could you or somebody else shed some light on what I am doing wrong, please
Thanks
Sorry if it sounds obvious but did you write mac1 xx:xx:xx:xx:xx:xx and then pressed "enter" ?
you need to write de mac adress next to the "mac1" command and only then press "enter".
-
Outcome of the update: SUCCESSFUL
DSM version prior to update: DSM 6.2.1 update 6
Loader version and model: Jun v1.03b - DS3615xs
Installation type: BAREMETAL HP Proliant gen 8 + Intel NIC on PCIe
-
Bueno, ya he terminado las pruebas con la tarjeta Intel.
Xpenology funcionando en 6.2.1 update 6 con 3615xs.
Un par de apuntes:
- la 6.2.1 update 6 es la última que me propone. No obstante, he probado a instalar la 6.2.2 manualmente y también ha funcionado perfectamente.
- 3617xs no funciona
- 3615xs me sigue dando los problemas de encendido que siempre me ha dado y ya sé de donde vienen: Solo ocurre cuando el encendido se ha desde la tarea de programado de encendido del synology. Cuando el encendido es manual, ya sea por botón o ILO, todo bien... Es curioso. Tendré que renunciar a esta funcionalidad. Una pena ya que tenía automatizado todo para que se apagase por las noches y encendiese por la mañana.
Gracias @jmayoralas por tu ayuda. Me he ahorrado 350€ de un Synology nuevo. A ver cuanto nos dura el Proliant g8... De momento llevo 5 años.
-
25 minutes ago, jmayoralas said:
Yo compré esta y sí lo traía:
Intel EXPI9301CTBLK - Tarjeta de... https://www.amazon.es/dp/B001CY0P7G?ref=ppx_pop_mob_ap_share
Enviado desde mi iPhone utilizando TapatalkAh bien bien, es la misma que compré yo.
me he equivocado en el enlace de arriba.
os tengo al tanto cuando pruebe. Me llega en unos dias.
-
9 hours ago, jmayoralas said:
Así es. Yo, sobre 6.2 instalé la intel, desactivé las integradas y arranqué para ver que era reconocida, luego, ya con la intel, actualicé con el update automático y sin problemas.
Enviado desde mi iPhone utilizando TapatalkOye, me está surgiendo una duda al ver el pedido, los brackets Low profile están incluidos con la tarjeta?
Intel PRO/1000 GT 1000 Mbit/s Interno - Accesorio de Red (Interno, Alámbrico, PCI, 1000 Mbit/s) https://www.amazon.es/dp/B00030DEOQ/ref=cm_sw_r_cp_api_i_jGN0Cb9583EFZ
-
1 hour ago, jmayoralas said:
1. Efectivamente, las nic integradas tienes que desactivarlas para que la intel sea reconocida correctamente.
2. No, la de iLO puedes (y debes) dejarla activada. El VSP del terminal de iLO no tiene precio para recuperar brickeos del DSM.
3. Yo uso DS3615xs. Nunca me ha dado problemas, así que no he tenido la necesidad de cambiarlo.
Enviado desde mi iPhone utilizando TapatalkMuchas gracias por toda la información.
Acabo de pedir la tarjeta de amazón, haré upgrade entonces a 6.2.1Con esta version supongo que no es necesario ni instalar el “.pat” manualmente no? Puedo decirle al DSM que descargue/instale automáticamente la última versión durante el proceso de instalación?
-
13 hours ago, jmayoralas said:
Sí, esa es mi cpu también, así que no deberías tener mayores problemas para ponerlo a funcionar.
Un par de preguntas más antes de pedir la tarjeta a amazon:
1) Tienes que desactivar las NICs en la BIOS? (eth0/eth1)
2) Relacionado con el punto nº1... también hay que desactivar la NIC de la ILO? no quisiese perdir la ILO....
3) Utilizas DS3615xs o DS3617xs? En mi caso con DS3615xs nunca ha ido bien... al hacer reinicio a veces se queda pillado, arranca el pendrive pero luego nunca arranca el DSM... es extraño. Por eso utilizo DS3617xs.
Gracias!
-
1 minute ago, jmayoralas said:
Sí, yo... y ahora soy el feliz propietario de un Gen8 en 6.2.1 y sin problemas
Gracias por tu respuesta rápida compañero.
Como sé si mi CPU es compatible también?Es esta: Intel(R) Celeron(R) CPU G1610T @ 2.30GHz
La verdad es que cada vez me planteo más comprarme un synology oficial... ya me ha petado un par de veces el xpenology y después de casi 2 años de uso estoy convencidísimo de que DSM es la clave.
Pero claro...450 minimo para hacer lo que hago con mi Proliant g8 ...
DSM 6.2.3-25426 Update 3
in DSM Updates Reporting
Posted
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.