Jump to content
RESET Forums (homeservershow.com)

Leaderboard

  1. schoondoggy

    schoondoggy

    Moderators


    • Points

      6

    • Content Count

      8,976


  2. Trig0r

    Trig0r

    Moderators


    • Points

      4

    • Content Count

      1,420


  3. Bilzo

    Bilzo

    Members


    • Points

      3

    • Content Count

      2


  4. typod

    typod

    Members


    • Points

      3

    • Content Count

      32



Popular Content

Showing content with the highest reputation since 07/03/2020 in Posts

  1. 3 points
    Thanks for the reply. It turns out I’d bent a few pins on the CPU socket. God only knows how!! I managed to carefully bend the pins back and I’ve managed to boot up with RAM slots 1 and 2 populated. All seems to be running ok for now. Spot the bent pins in the pic 😬
  2. 2 points
    Ah. Had this same issue with WS202 R2. It is caused by updating the .NET version from the default 4.5 version that installs with the OS. I was able to simply rollback the server to the original version and not update it to latest future versions like 4.8, etc and everything is fine. Unfortunately the Dashboard simply isn’t compatible with the newer versions of .NET. The result is crashing Dashboard and hung up statuses as you’ve seen.
  3. 2 points
    Where else can you compliment someone on their "nice rack" these days
  4. 2 points
    schoondoggy

    RAM

    No it is not. That is registered memory. This server does not support registered memory.
  5. 2 points
    Yes, for me the RAM was the limiting factor as well. I moved onto a DL360 Gen8. Issue with the MS is even if you can fit a mini-ITX board into the case with another low-profile CPU fan, you'll have to do some heavy modding to the I/O area as it's not removable. I tried to do something similar with the HP Z820 workstation because the case is really quite nice. Unfortunately the amount of modding required was beyond my skill and the effort didn't seem to be worth it.
  6. 1 point
    I've been following the Homeservershow podcasts, now RESET podcasts, since 2011. A lot of stuff has changed. Homeserver is long gone and replaced by NAS devices. Cloud is everywhere, streaming is everything and home media-stuff as we knew it is almost gone. So, what's your setup in 2020 @DavidMcCabe? Is your server closet empty? Looking forward to your reply. Have a really wonderful day. Kind regards, Bjorn
  7. 1 point
    Windows Server 2019 Essentials on HPE Microserver Gen10 Plus
  8. 1 point
    Thank you for your answers! They helped so much. Ive updated and switched the P222 to HBA, to find out that it xpenology doesnt support it anymore. Ordered a IBM M1015 for cheap and flashed it to IT mode, passed it on to xpenology. This also gave me extra internal ports(there are 13 sata now of wich I use 6 now). So I can connect extra 2,5 drives in the future. For now there is one SSD where ESXI 7.0 runs on. Ive installed 6.5 preGEN9 and updated it to 7.0 with generic build. The onboard controller is in AHCI indeed. This all works wonderfull now. Next steps, create more sata power and some more cooling I think.
  9. 1 point
    @schoondoggy is your man, not sure they will though as think he uploaded the plan for them a while back so people could do their own as the number required to make it worth while made it not worth while...
  10. 1 point
    On WSE2012R2 I setup Microsoft DirectAccess for this. I think MS has since deprecated the functionality altogether but it did exactly what you wanted. It enabled me to add remote family PCs to the domain over their remote internet connections. They would turn each see the server via the server essentials connector and make nightly backups. They could also access the file shares.
  11. 1 point
    Im successfully running 6.5U1, anything later than that refuses to install due to unsupported CPU warnings
  12. 1 point
    The server won't double in price, this may well do.
  13. 1 point
    That's for sure. The two items I can't block from the internet, I'd like to isolate more. I for one don't want an open mic in my house, but for those wishing to control stuff by voice I think some of the things you show in your layout can help tighten things up. thanks for sharing it!
  14. 1 point
    No. Access-lists on the L-3 switch prevents that. They only have access to the internet.
  15. 1 point
    All APs boradcast multiple SSIDs while each SSID is assigned to a specific VLAN. Each family is assigned an SSID and consequently, a VLAN. It was primarily used to separate our IoT devices from seeing each other (which they will if they were all on the same broadcast domain).
  16. 1 point
    Looks like my enablement kit shipped today for delivery tomorrow.
  17. 1 point
    It would be useful if you could describe the steps which worked in some detail up to the point of failure ... ... and NOT follow MSFT's lead by saying 'something went wrong somewhere' 😉 Using the USB method I presume you loaded the RAID driver (S100i or whatever - I don't have a 10+). I have found that, even with the oldest devices, if the network driver is located and installed ... then the W10 installation program is pretty good at finding any other missing drivers. One somewhat abstruse idea occurs. If you are attempting to install the latest 2004 version of W10, then MSFT may not yet have released the HP 10+ because of a driver incompatibility (as indeed they have not even for some MSFT devices!!). Whether you can grab an older version of W10 I leave in your hands. I suspect though that someone else on the forum must have managed to install W10 2004 on this machine.
  18. 1 point
    The latest update I had from hardware.com was they were due in on the 17th, even though the website says the 14th.
  19. 1 point
    Cheers, I have ordered one from them in preparation for getting the server later in the year. I was looking at Lambda Tek who now have them in-stock but have massively ramped the price up now they are in-stock. 🙄
  20. 1 point
    Worked around the issue with this command. Stops it tripping, makes sense, there is only 1 fan after all. esxcfg-advcfg -s 49 /UserVars/HardwareHealthIgnoredSensors Reff: https://kb.vmware.com/s/article/78989
  21. 1 point
    Hi E3000, No, I've had it 10 months now and it has had no affect on the internal case fans at all. Pete
  22. 1 point
    Recommendations are always useful. I was quite impressed with their site when looking for the Gen10+. It was good to see accessories for a device listed under the main listing so you can easily add them to a single basket rather than running around all over the place. For example: Microserver and Accessories They have also emailed me to keep me informed about the expected deliver date. When I originally placed the order they were due in on the 26/06.
  23. 1 point
    I have not played with Xpenology and ESXi together for a long time, but: 1.Unless something has changed Xpenology does not like RAID cards. HBA's work well and allow Xpenology to configure and manage the drives. 2. In the past the P222 did not behave well as a HBA. I think the latest firmware from HPE is better at supporting HBA mode, but I have not tested it. Xpenology users seem to have good luck using LSI based HBA's in passthrough with ESXi. 3. For the onboard controller, you could add a breakout cable to the system board and use those ports for SSD's. ESXi tends to like RAID controllers, but there have been performance issues with the B120i drives and ESXi in the past. Some have had good luck with AHCI. Sorry I do not have more definitive answers, but these are the areas I would research. Perhaps someone else will have more detail.
  24. 1 point
    Thanks again for replying. Indeed, in the end I bought it. I'm waiting for it to be dispatched from Germany and I paid much more than that. It was about 200 euros on the HPE website. I found this supplier who sold it a 150. God, I hope it was worth it. I was unconfortable with having only 2 screws, the fact that it did not fit precisely made me wonder wether the round surface of the cooler was touching the processor in the right way, as you suggested, but it's difficoult to see from a side view. The compound seemed to adhere but nontheless, let's see if the official HP part even without fan can yield better results. Thank you very very much for your help and suggestions.
  25. 1 point
    I'm going to start putting money aside to do a build for my new home server in December. I'll be going for the base model putting in an E-2246G, 64GB RAM and transferring my drives over from my Gen8 before probably offloading my two Gen8s but I'll keep my ML110 G7 as my backup as its got my LTO drive.
  26. 1 point
    Can you remove the tray from the Gen8 and power it up outside of the chassis? Looks like you have a lot of compound on there, I'd clean everything up and reapply with a smaller amount of compound. Also, as you have 2 screws, make sure its not bent or resting on other components around the socket and that you are getting decent contact. The joys of the HP 65w cooler are it fits, its not cheap though, I paid ~£90 for mine IIRC. and it was a PITA to get hold of..
  27. 1 point
    Can I ask a simple question? Did you remove and replace the thermal paste? It needs to be fresh paste and spread thinly over the whole flat metal area. The screws should squash it down and spread it out but a quick visual check will let you know if the paste is making good contact to both the CPU and heatsink. The ILO temp sensor is slow to respond and seems a bit innacurate from my use. Core Temp seems more accurate with the chipset in this Gen8 HWMonitor is ok and should read the same as Core Temp
  28. 1 point
    You able to power the board up on the tray out of the chassis, are you sure the fans spinning, also, is it spinning in the right direction. Personally I'd take the akasa off of the CPU and see what state the thermal compound is in, you'll be able to see straight off if you have a decent contact between CPU and heatsink.
  29. 1 point
    Thats pretty hot that is.. Are you sure the cooler is actually seated properly on the CPU? There is a better HP heatsink thats rated at 65w which is near on the 69w that ARK says your CPU is, but if you've already swapped to the Akasa unit something's gone wrong somewhere to hit those temps, IMHO...
  30. 1 point
    I would try this one: https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_6b906530d6624549bff23e4eab
  31. 1 point
    From your testing it looks the issue is with slot 2. The memory controller is part of the CPU. It is possible that some debris got on the pins of the CPU and is causing slot 2 not to work. Check the pins and the pads to be sure they are clean.
  32. 1 point
    Ok, it's time to solve all problems with overheating. Stuff: 1x Noctua NF-A8-5V fan with USB power adaptor cable 1x Akasa 3D Fan Guard AK-FG08-SL https://imgur.com/a/7npqgdc Now LSI 9271-4i temperature approximately no more than 57 degrees.
  33. 1 point
    that might be considered verboten in a law-abiding forum
  34. 1 point
  35. 1 point
    Got the answer on other forum. " You can't access a drive from two different OS'ses simultaniously. If you change on one side, the other side does not recognize the update because it is not aware of the possibility, that someone else uses the same disk. This is why we have cluster aware Filesystems in environments, where multiple systems need to access shared data - or, they use NFS... You would need to unmount the drive on one side, then mount it again on the other side. Then the change should show up. They way you are doing it now - wont work. I would suggest you rethink your approach by using NFS exports, which would allow what you try to achieve. E.g. use the disk in system A, export the path via NFS and mount the NFS-export from system B. This can be Read-Write or Read-Only, depending on your need. "
  36. 1 point
    FYI, I have just installed Windows Server 2019 Standard (Desktop Experience) using the latest (WS2016) HP AMD chipset & VGA driver. Everything is recognised in Device Manager and stable.
  37. 0 points
    No, I wish I had. I used the advisory information with circa 10 PCI Slots though it has only 1: no success. It would really interesting to know if it's possible to find a solution to replicate the ESXI way to pass-through in Linux.
  38. 0 points
    On 8/27/2013 at 9:52 PM, TheBiggerMan said: OK – I’ve put together some instructions for the board. Note that (1) these have not been tested, although I did use this approach on my MicroServer successfully, and (2) by using these instructions you agree that I take no responsibility (nor liability in perpetuity) for the effect your usage of these instructions may have on your data – you’re on your own and if it all goes horribly wrong, please do not be surprised! I would strongly recommend you do not have any data on the server at this stage… Before you start, you need the following: A copy of Windows installed (Windows Server 2008 R2 or later will do, any edition – this may work on Windows Server 2008 too, but earlier editions have a different method that these instructions do not cover) on the MicroServer and booting successfully. Note that if you've installed Windows onto a drive in the ODD, you will need to physically remove all the hard drives from the trays (just pulling them out 1/2" will do to be able to boot the server from the ODD), otherwise the MicroServer will try and boot from one of the non-ODD hard drives first. There is no way to specifically prioritize the ODD drive above the others. Insert the MicroSD (or USB key) into the internal slot before you boot. If you are unable to boot, go into the Setup Utility (BIOS) and ensure that the boot order has USB set to lowest priority. Boot the MicroServer into your copy of Windows. Mount the Windows setup ISO. Windows Server 2012 and later has an ISO mounter built in - but if you're running another version, you can use something like Virtual CloneDrive, available at http://www.slysoft.com/en/virtual-clonedrive.html Make a note of the drive letter. Go to "My Computer" or similar in Explorer and make a note of the drive letter and size of your MicroSD card or USB key. If you cannot see it here, then there are a couple of reasons - if the drive is not formatted properly you may be able to get it working by consulting the Disk Management MMC snap-in and formatting it there. Also, if you didn't use Intelligent Provisioning, and you're using the MicroSD card, you may not have the right drivers installed - in which case go and grab them from the HP site and install. Now for the fun stuff: Start an elevated command prompt. Start | type cmd | Right-click cmd (top of menu) | Run as Administrator. Note that you can just run a command prompt if you have UAC turned off (standard for Windows Server installs). Next, run Diskpart to prepare the disk. Enter each of the commands in order. Be very careful as a mistake here can have serious consequences! Note that the question mark “?” below should be replaced with the disk number of the drive you are using: diskpart list disk select disk ? clean create partition primary select partition 1 active format fs=ntfs quick label=”<YOUR LABEL GOES HERE>” exit Now copy the boot sector to the MicroSD card or USB key. You should still be in the command prompt window. Replace $ below with the drive letter of your mounted ISO image, and ? with the drive letter of your newly formatted MicroSD card or USB key. C:\Windows\system32>$: $:\>cd boot $:\boot>bootsect /nt60 ?: Target volumes will be updated with BOOTMGR compatible bootcode. Bootcode was successfully updated on all targeted volumes. $:\boot>exit Note that if you get an error message here, normally you can fix this by closing any open windows with that drive and try again. You could also use the /force switch for bootsect if you prefer. Now we need to copy critical boot files to the MicroSD card/USB key. Using Windows Explorer, copy the following directories and files to the MicroSD card/USB key: bootmgr (file) bootmgr.efi (file) boot (directory) efi (directory) Nothing else is required. Delete the file "bcd" from the directory "boot" on the MicroSD card/USB Key - we'll be recreating it shortly. Start another elevated command prompt. Start | type cmd | Right-click cmd (top of menu) | Run as Administrator. Note that you can just run a command prompt if you have UAC turned off (standard for Windows Server installs). Replace ? in the following BCDEDIT commands with the current drive letter of your MicroSD card or USB key: bcdedit /createstore ?:\boot\bcd bcdedit /store ?:\boot\bcd /create {bootmgr} bcdedit /store ?:\boot\bcd /set {bootmgr} device boot bcdedit /store ?:\boot\bcd /timeout 30 bcdedit /store ?:\boot\bcd /create /d "<Your OS Name Here>" /application osloader That returns a new GUID that you should plug into this next command: bcdedit /store ?:\boot\bcd /default {<GUID>} For the next commands where I've denoted *:, replace it with the drive letter of your current Windows boot drive. So if I'm booted on my MicroServer into the OS I am looking to boot from my MicroSD/USB Key and it's C:, that's what you need to enter here. It doesn't matter what the drive will be when you boot - it matters what the OS you're currently executing the bcdedit command sees! bcdedit /store ?:\boot\bcd /set {default} device partition=*: bcdedit /store ?:\boot\bcd /set {default} path \windows\system32\boot\winload.exe bcdedit /store ?:\boot\bcd /set {default} osdevice partition=*: bcdedit /store ?:\boot\bcd /set {default} systemroot \Windows bcdedit /store ?:\boot\bcd /set {default} detecthal yes bcdedit /store ?:\boot\bcd /set {default} nx optin bcdedit /store ?:\boot\bcd /displayorder {default} /addlast Finally... If you want to run Hyper-V (and have a capable edition of Windows Server, and have installed the role), you must enter the following command (otherwise the Hypervisor won't start and Hyper-V Manager will throw up all sorts of errors): bcdedit /store ?:\boot\bcd /set hypervisorlaunchtype auto Boot into the Setup Utility (BIOS) on your MicroServer and prioritize USB boot as the first item (MicroSD comes under the USB boot order too). I have not been able to find a way to prioritize within the USB boot devices. Therefore, you will need to remove all other storage devices from the USB2 ports (the two USB3 ports on the back of the server are fine as they aren't seen by the BIOS and aren't active until you get into a compatible OS). OK - your MicroSD card or USB key should be all setup. At this point you can install drives into the drive trays and you should be good. I welcome comments from my fellow board members. I hope this is helpful! I created a booting MicroSD using the above guide and it has worked for years and now i'm thinking up updating the OS does anyone know if i can upgrade the OS from Server 2012R2 to 2019 and this will just work, or will it break booting?
  39. 0 points
    I followed the original instructions and got Server 2016 installed but I've not had to upgrade it yet, so presently have no idea... but I've just shut down an older Gen8 that needs reinstalling, so I'm happy to stick W2012R2 on and upgrade to test this... just need time to do it - I have MSDN so no problem with licensing doing this... and I will let you know 🤞
This leaderboard is set to Indiana - Indianapolis/GMT-04:00
×
×
  • Create New...