phguk

Transition Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

1 Neutral

About phguk

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Apologies for the delay, thanks for sharing this info R0bb0. I'll download & try the same. Rgds Paul
  2. - 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 3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP Microserver Gen7 N54L - Additional comments: MY config uses a separate Intel NIC. I'm curious that this update wasn't automatically offered (as earlier updates) but seeing someone successfully updating manually with identical hardware, I elected to do the same. I would say the reboot took rather longer than earlier updates (or maybe that was me simply being ner
  3. Slightly OT but can I ask how did you arrive at running VMware ESXi-6.7.0-20191204001-standard-customized (VMware, Inc.) [ fresh install/upgrade etc] ? I'm aware there are HP Microserver specific builds for Gen9 & later which appear to work on Gen 8 too. Thanks Paul
  4. I appreciate all the input and am vaguely encouraged that I'm not the only one with a N54L that sees occasional "blips". Because my power schedule involves shutdown overnight, it's difficult to determine whether the lack of responsiveness occurs after the unit has been successfully restarted in the morning, or (as Billat29 speculates) may be because of shutdown problems the night before.
  5. Yes, you're probably right. I appreciate the suggestions. I'll dig out the vacuum cleaner and get to work. As I said before, this is a mild irritant which I can live with.
  6. Every now and again (maybe once a month) my HP Microserver N54L running 3615s 6.2.2-24922 Update 2 becomes unreachable (I can't login and pings fail). The expedient action is to simply remove power from the server then reboot. I don't think this behavior is related to newer levels of DSM and previously I've simply ignored this irritant. I have power schedule enabled (05:00-23:59) which seems to work as designed. When I look in the DSM logs, they show a reboot but nothing else relating to the hang or preceding events. Sadly I can't reproduce because it happens very infrequently and up to now,
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: New Installation - Loader version and model: JUN'S LOADER v1.03b - DS3615xs (previously with internal NIC only I was running DS3617xs 6.17-15284 U3 using v1.02b) - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 7 N54L + HP NC360T (NIC) - Additional comments: Disabled internal NIC & added NC360T NIC then new install using v1.03b and single "sacrificial" disk + shutdown OK; then added back 4 disks with data on - DSM complained system partitions failed & reb
  8. Many thanks. I'll add the card next week and report back.
  9. I've an HP G7 N54L running 1.02b bootloader and DSM 6.1.7-15284 Update 2 (DS3615xs) using the onboard NIC. I've since purchased an Intel 82575-T2 PCIe 1Gb dual port adapter which I'd like to add (and disable the onboard NIC). I am planning to 1. Insert new NIC card and using the BIOS (a) disable the onboard NIC and (b) confirm the MAC(s) of the new NIC ports 2. Must I now edit grub.cfg to reflect I've now got two ports with updated MACs *before* I reboot [should I use force mode] ? Have I missed anything else ? Thanks in advance Paul PS. I
  10. I would like to revisit this topic: I've an HP G7 N54L running 1.02b bootloader and DSM 6.1.7-15284 Update 2 (DS3615xs) using the onboard NIC. I've since purchased an Intel 82575-T2 PCIe 1Gb dual port adapter which I'd like to add (and disable the onboard NIC). Based on MitchBook's experience, I was planning to 1. Insert new NIC card and using the BIOS (a) disable the onboard NIC and (b) confirm the MAC(s) of the new NIC ports 2. Must I now edit grub.cfg to reflect I've now got two ports with updated MACs *before* I reboot [force mode] ? Have I missed anything el
  11. Fab - these steps worked for me too and I'm now successfully running DSM 5.2-5592 Update 2. One more question: can you elaborate on your earlier comment "Even managed to get the power-off on press of power button". What did you change/update to accomplish this ? When I press the power button, my N54L server simply powers off abruptly Many thanks Paul
  12. Andywhit, would you mind describing the steps you followed ? I'm currently sitting at DSM 5.1-5022 Update 5 but am a bit confused whether I can simply jump to (install) the latest 5.2 5592.2 or does this upgrade have to be accomplished in a series of steps. Thanks in advance Paul