bearcat

Ohh, I now found my "missing" post, and was able to delete it's evil twin

The very same thing happened to me a few days ago, running the same HP N54L and DSM4.2-3211 Repack v1.2, I'm running 5x4TB (WD-RED) in SHR mode, so it took "a while" until the system completed the raid/parity checks. Using the external monitor program, from Synology Assistent, I saw 100% CPU usage during the diskcheck, so I thought that was the reason. When Volume1 was declared "healthy", I did a controlled reboot, hoping the problem would go away, but no such luck.... Googled and read some posts, referring to the SNMP service, which was disabled. Tried to enable and reboot, no change, tried to disable again and a new reboot, no change. Using putty, I connected and ran "TOP", and was only seeing some 2-3% CPU being used by fileindexd (if I remember correct). But still the external monitor shows me 100% CPU being used. (I have tried to look for the Virus/backdoor files that is currently "running around", but have found no trace of it). Question: Has anyone else experienced this, and found a way to solve the problem ? disclaimer: Yes, I know I should have used an UPS, it's on top of my what to buy next list Edit: Topic was "Failing resource monitor widget, CPU usage ?", changed to

when trying to post ?

Followed your instructions, and now my N54L is using the real MAC address, no problem for now. Thanks.

My idea for doing that, is to use the original drive that shipped with the server in the ODD bay, as I have all the needed HW to place it there. I will then re-install xpenology, and do some tests, while waiting for my 4 new storage drives to arrive. That way, it will be easy to pop them in, not needing to open the box once more. Keep in mind, I will be preparing 2 "identical" systems, one for my self and one for a friend of mine, so I should use the KISS approach to make it easy for him later on, as it will be a set and forget system.

@ fonix232: Ahh, that explains it better Will give it a try today, and flash my bios, and mount my primary disk in the ODD bay.

@ fonix232: Yesterday you wrote (in the now closed thread I started): Then how come, that you in July wrote: So, is there or is there not a BIOS reset problem with the N54L and the hacked BIOS

@ fonix232 : So, you where actually able to install and run 2012 R2, using the original NIC, (HP NC107i Integrated PCI Express Gigabit Server Adapter) ? I was trying, using the drivers and firmware for 2112 Essentials, posted here (My R2 is coming from my Technet account, did not know DreamSpark was offering it yet) But I ended up like everyone else in this thread with a no-go. Why would I use Windows ? Because I have used it for so many years, and would like to play around with the new R2, and to see if I could migrate my old server into new and smaller HW. Is *nix a better choice for servers ? Yes, I believe so, but the transition is a pain in the b*tt since I have many services running today, that I would like to transfer with as little effort as possible. There is a time for computers, and a time for family life..... Besides, at work we are *"forced" to use Windows, and if this hobby project was turning out OK, I might be able to buy and install some Micro's at work. So, with Trantors build, there should be no BIOS reset problems with our N54L's ? That sounds good. I have been looking into TheBay_Microserver_Bios_041 that seems to be a good candidate, is this the one you are using ?

I see a possible problem here: http://xpenology.com/forum/viewtopic.php?f=2&t=6&p=6073&hilit=HP+N54L+BIOS#p6081 Is this a well known problem with the hacked BIOS's ?

@ hansel: Since the "only" difference between the 40 and the 54 supposedly is the CPU, I guess the same advantages applies, thanks. Seriously ... as I was saying, there is problem with the NIC, when using the soon to be public released R2 version of the Server 2012 family Even if I installed 2102 (or 2008), that is working very well, and trying to update the firmware for the NIC, I was told by the setup that I already had the most up-to-date version. When updating from 2012 to R2, same problem with the NIC not working. More info of this known problem can be found over there ---> http://homeservershow.com/forums/index.php?/forum/67-hp-microserver/ Have you tried R2 on your 54 yet ? The good thing with that problem, was that I was heading over here to try out what I really wanted to play with But thanks for the feedback, I will try to read some more in regards to the BIOS, to see what I might be missing out with stock. It's fun to be part of the Microserver "family", and I might be getting some more of them if I get a good offer again. I made a friend buy one at the same time that I was getting mine, so I will have to supply him with all the needed support...

Re: XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2) As a new member of this forum, and as a XPEnology "virgin", I would like to say many thanks to Trantor, and the community, for providing this excellent piece of work I just recently got myself a HP Proliant Microserver N54L, and after realizing that MS Server 2012 R2 will not work with the original NIC, I tried this nice build, which "just worked" right out of the box, on a "stock" server, with original BIOS, at least all the things I have tried yet. But as a newbie, I have 1 question that I have not been able to answer myself by reading the forum. - What can I gain, by flashing my BIOS to one of the modifed "floating" around ? (and if I can gain something, what is it, and what BIOS should I use ?)

As a new member of this forum, and as a XPEnology "virgin", I would like to say many thanks to Trantor, for providing this excellent piece of work I just recently got myself a HP Proliant Microserver N54L, and after realizing that MS Server 2012 R2 will not work with the original NIC, I tried this nice build, which "just worked" right out of the box, at least all the things I have tried yet.