Jump to content
XPEnology Community

amfibia

Member
 View Profile  See their activity

  • Posts

    14

  • Joined

  • Last visited

 Content Type 

Posts posted by amfibia

    HP N54L Microserver - Getting Everything Working

    in AMD

    Posted

    @ fonix232:

     

    Yesterday you wrote (in the now closed thread I started):

    The reset issue does not affect us. This motherboard does not let Synology touch the BIOS settings, and such, it won't be any problem.

    At least for me, it was never, and it was always my settings.

     

    Then how come, that you in July wrote:

     

    I have the same problem, the issue is that DSM, as it is a strictly closed-line product of Synology, expects the BIOS to be in a specific format it can edit (and not the AMI BIOS HP uses in my case, both on my fresh N54L and my hackology server that consists of the stuff in my signature). Now, this invalidates the CMOS, wipes all the changes (I for one need them, as I boot from USB, and primary boot device on this board is a Floppy device set even though there isn't on connected, and fails to go through all the devices to find the USB drive), and you're left with an unusable CMOS config that gets reset every time you restart.

    Unfortunately this service runs real-time, so no matter what you do, power-off via pulling the plug, shutdown via terminal or GUI, the CMOS gets written and thus invalidated.

     

    Now, so far I found only two solutions to counter this:

    1. If you have a CMOS read-only pin, put a jumper on that madafaka. This should protect it from Synology's stupid CMOS-overriding daemon.

    2. If you are good with it, try to modify your BIOS, hack around some default values, and set it up for your taste. I only recommend this to those who know EXACTLY what they are doing!

     

    Another solution would be that someone finds the service that modifies the BIOS, and eliminates it. But I fear that this service might be embedded into many others and would possibly be bad to disable all of them.

     

    So, is there or is there not a BIOS reset problem with the N54L and the hacked BIOS :?:

     

    Back in July I was using a different server :wink: It was a HP MediaServer M8000n, using an Asus-made motherboard with AMI BIOS. Our motherboard with the N54L is a Gigabyte motherboard with dual BIOS, meaning if the primary CMOS is corrupted, the backup is loaded. But any time you save a setting, and it is correct, it gets saved into the secondary CMOS, and is loaded when the primary is corrupted by DSM.

     

    Sorry, I had to change my signature when I switched servers, and thus that post kind of lost its meaning. I will correct it in a moment.

     

    So for further note: I got my Synology server in the beginning of September, any post before this is irrelevant to the ProLiant Microserver line.

     

    Seems I have the reset BIOS issue with a N54L, modded bios.

    it keeps resetting after a restart / shutdown from Exp 5.0

     

    might be due to 5.0 but reading the above from fonix222, it should not be possible to reset the bios by Xpenology as the N54L hasa dual BIOS.

    Anyone else can confirm the bios resets when using power scheduling / WOL with 5.0? OR maybe has a solution?

     

    thanks in advance

    Cannot boot with a hard locked USB pendrive

    in Archives

    Posted

    running 5.0 on a N54L with modded bios. 2x 3TB in SHR

    Running like a charm.

     

    Replaced my pendrive today with one that I can hard lock. But when rebooting the SAN with a locked USB ( like recommended a lot on the forums ) it will stuck while booting at command GRUB. ( even before the actual boot of DSM5.0)

    Once i turn off the lock, it boots perfectly fine with the same USB mounted.

     

    Anyone got a clue what could be the reason? probably I am missing something somewhere.

    XPEnology DS3612xs DSM 5.0-4418 (BETA)

    in DSM 5.2 and earlier (Legacy)

    Posted

    I am sure I didn't even get the warning that it would delete my drives.

     

    So either the setup doesn't recognize that you have an SHR already running or maybe you can uncheck the box and sees how it goes.

    I didn't even have to uncheck it when I upgraded to 5.0 from 4.3

     

    you didn't change your server name by any chance?

     

    for a check you can also read this topic

     

    http://xpenology.com/forum/viewtopic.php?f=2&t=2242#p11196

    XPEnology DS3612xs DSM 5.0-4418 (BETA)

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hey Guys, first thank you for this great work. I've installed version 4.3 since a couple of time, and now i would like to do this upgreade to 5.0 beta.

     

    Is it possible without losing my data which is saved on my hdds?

     

    sorry for my english, i'm austrian. :grin:

     

    yes my data and configs were still ok after upgrading. BUT........ you can never be 100% certain it will survive the upgrade process so ALWAYS make sure you have a backup of your config and your data!!!

×
×
  • Create New...