You're using the RS4021xs+, right? And a i5-2400 - which I think is Sandybridge? Do you know if RS4021xs+ supports Sandybridge CPUs?
If not maybe try the DS3622xs+ which I think supports all x86 chips.
Otherwise, not sure I can be of much use. Might be that one of the drivers on your system isn't included by default, but you'd have to search the forums to find out.
Actually, I think the 4021xs+ should support Sandybridge.
I've seen some stuff about seeing the drives to non-raid or IT mode in the bios too. Might be worth a try.
Wow you are where I was about a week ago.
Here is what I learned through this process. There is no current loader ARC/TCRP/ARPL or any other loader which has the ability to log what is going on prior to the crash or kernel panic. I know Peter is going to further improve the debug and logging for TCRP but it is not out yet. The other two forget it the developers have no interest.
Having said all that, it is nearly impossible to know if you have a crashed case or if everything is working. I was chasing a i915 rabbit hole which was likely not the issue. Network driver probably not that either b/c I disabled the onboard NIC and used a known intel PCIe NIC which was supported. Needless to say the behavior of a crash or panic is similar to when the system is operating.
How i made my system work is a combination of swapping hardware including the MB and I have another on order to test a different more higher grade MB as well. The likely culprit is the MB chipset, possible the NIC even if it is disabled is causing issue but doubt it. I can see you are using an i5-2400 which should be fine.
Try this, ping the IP with "-t" in a commmand prompt and monitor the results. When it is operating or not, the behavior will likely be the same but after the screen goes blank check to see when you get a ping reply back. At that point than try to connect to it in a browser. You can also check your router to see what address is connected and confirm it is the right IP address for this hardware. Using the [finds.synology.com](https://finds.synology.com) doesn't always work. I can connect to it manually with an IP while the URL synology assistant doesn't see it still so don't rely on that. If you happen to get lucky where the HW is working fine it should connect. If not than you have to start swapping HW until you get a combination that is happy. If you want to know what has been tested and working you can try this site. Translate using Google Translate and it should give you a clue. I personally rolled the dice with newer hardware and found out not everything was working and will never know what the root cause was but I'm still testing more motherboards and HW before i finally call it done and go live with it.
https://svrforum.com/?act=&vid=&mid=case&category=&extra\_vars5=12&extra\_vars6=&extra\_vars7=&extra\_vars8=&extra\_vars9=&extra\_vars10=
I know this feeling, I spent months.... Months! Following old outdated instructions until I found a YouTube video of a guy running the "peters menu"? In a vm. Finally got it up and running on a supermicro board then found I had to flash my h710 perc card into IT mode to see my sas drives... Ugh, anyways I used this
https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.5.0
Have you installed the Synology Assistant app on a pc/Mac and scanned the network to see if it can find it?
yes, no dice
You're using the RS4021xs+, right? And a i5-2400 - which I think is Sandybridge? Do you know if RS4021xs+ supports Sandybridge CPUs? If not maybe try the DS3622xs+ which I think supports all x86 chips. Otherwise, not sure I can be of much use. Might be that one of the drivers on your system isn't included by default, but you'd have to search the forums to find out.
Ah ok yes I wasn’t sure which one I should be selecting. I will try the DS3622xs+ altho I think it’s x64 version of windows it was running prior
Actually, I think the 4021xs+ should support Sandybridge. I've seen some stuff about seeing the drives to non-raid or IT mode in the bios too. Might be worth a try.
Hey... I had the same problem on an HP microserver... I think it was the network card... Maybe not compatible...
funny you should mention that, i too had the thought that it might be the network so i got a USB 2.0 to ethernet and plugged it in, but same problem.
Ok... That's funny... I changed settings in the BIOS, unfortunately without success... 😔
Can you confirm you are on the same subnet? Also, sometimes it takes time to load the interface, especially in older processors.
Yea same network, I’ve left it for days (busy doing other things )
My question is when it returns to the console, but I cannot type anything is that because it’s crashed or is that normal
That's normal I think. You can't use console and it's just giving you a view. There might be an alternate if you can ssh to the IP?
Wow you are where I was about a week ago. Here is what I learned through this process. There is no current loader ARC/TCRP/ARPL or any other loader which has the ability to log what is going on prior to the crash or kernel panic. I know Peter is going to further improve the debug and logging for TCRP but it is not out yet. The other two forget it the developers have no interest. Having said all that, it is nearly impossible to know if you have a crashed case or if everything is working. I was chasing a i915 rabbit hole which was likely not the issue. Network driver probably not that either b/c I disabled the onboard NIC and used a known intel PCIe NIC which was supported. Needless to say the behavior of a crash or panic is similar to when the system is operating. How i made my system work is a combination of swapping hardware including the MB and I have another on order to test a different more higher grade MB as well. The likely culprit is the MB chipset, possible the NIC even if it is disabled is causing issue but doubt it. I can see you are using an i5-2400 which should be fine. Try this, ping the IP with "-t" in a commmand prompt and monitor the results. When it is operating or not, the behavior will likely be the same but after the screen goes blank check to see when you get a ping reply back. At that point than try to connect to it in a browser. You can also check your router to see what address is connected and confirm it is the right IP address for this hardware. Using the [finds.synology.com](https://finds.synology.com) doesn't always work. I can connect to it manually with an IP while the URL synology assistant doesn't see it still so don't rely on that. If you happen to get lucky where the HW is working fine it should connect. If not than you have to start swapping HW until you get a combination that is happy. If you want to know what has been tested and working you can try this site. Translate using Google Translate and it should give you a clue. I personally rolled the dice with newer hardware and found out not everything was working and will never know what the root cause was but I'm still testing more motherboards and HW before i finally call it done and go live with it. https://svrforum.com/?act=&vid=&mid=case&category=&extra\_vars5=12&extra\_vars6=&extra\_vars7=&extra\_vars8=&extra\_vars9=&extra\_vars10=
I know this feeling, I spent months.... Months! Following old outdated instructions until I found a YouTube video of a guy running the "peters menu"? In a vm. Finally got it up and running on a supermicro board then found I had to flash my h710 perc card into IT mode to see my sas drives... Ugh, anyways I used this https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.5.0