Jump to content
RESET Forums (homeservershow.com)

All Activity

This stream auto-updates     

  1. Today
  2. Don't know, but probably everything on the market atm works :)
  3. JackoUK

    Unable to connect to NAS from a specific computer

    "I was thinking that this being a newer Windows machine might be the issue as well. Even though my other machines are on W10, they started with an "older" version of W10 compared to this one. " I guess it is the other way round: devices having been upgraded 'in place' rather than via 'clean install' do not interoperate properly with 1809's interface. "It could very well be something to do with SMB1, …" Most unlikely: I disabled SMB1 everywhere once the advisory came out. MSFT had long since abandoned SMB1, were removing Homegroup and upgrading to SMB 3: the new stuff, or the upgrade process thereto, is probably the cause. "Definitely not giving up on this." Wish you well … and have booked your appointment for head-trauma surgery … I'll probably be joining you after 1903 😉
  4. mazo22

    >16gb success on G2020T.

    One more question not in direct connection to this - what is the difference in original HP ram modules - as ilo reports the original as HP smart module the 8 gb non HP does not say hp smart module - apart of the “label hp smart module” is there any additional feature?
  5. JackoUK

    Home Media Server Help

    Good questions … here are my experiences … which I hope are still relevant. In general don't worry about the difference between a server, workstation and a PC as regards Windows. The DELL refurbished Outlet regularly throws up bargains, if you missed the President's offer. It is unlikely you can reparent your Windows 10 license to a new machine unless you bought/built a bare machine and purchased a retail W10 license later (you will have a separate 25-digit code). One advantage of buying a complete machine from an OEM is that the Windows license, though locked to that machine, is comparatively cheap. Upgrading later is expensive, so if you want W10 Pro then get it with the box, don't accept Home and then pay 120 to upgrade to Pro. A new machine will have a UEFI BIOS so disks larger than 2TB are bootable. You can use any SATA disk therein regardless of size or RPM … though best use all the same type for RAID arrays. It used to be the case that an OEM RAID controller would object to 3rd party disks but many machines now use the motherboard SATA connector and INTEL software, so no worries. Bespoke power connectors … and your plans for future upgrades are issues. Make sure you are getting all the connectors you need, even disk caddies could be missing if the purchase spec. says only 1 disk. One point you might miss: a low-end server may not have a x16 PCI slot for graphics. The T30 is OK there. (x8 would probably be OK for a server anyways … but you might want something more later). An nVidia 1050 or thereabouts should be fine and is one card which does not require an additional power connection. Maybe lower according to PLEX requirements. A fanless design would be even better (quieter).
  6. JROrtiz

    Unable to connect to NAS from a specific computer

    I was thinking that this being a newer Windows machine might be the issue as well. Even though my other machines are on W10, they started with an "older" version of W10 compared to this one. SMB1 has been deprecated but I went in and enabled the SMB1 service manually and even then it doesn't work. At one point, it did pop up in the network neighborhood briefly but disappeared after a few minutes. It could very well be something to do with SMB1, but it works fine on all my other machines so I feel like there must be something else at play here. I've also tried disabling SMB1 on the Drobo to force a more up to date protocol and it didn't make a difference. For now I'll just have to have one of the shares mounted by the Drobo Dashboard. That seems to have gotten me around the issue until I find a proper solution. Definitely not giving up on this.
  7. JackoUK

    Unable to connect to NAS from a specific computer

    Welcome to the asylum! There is another thread on this forum which offers some options, typically tinkering with Windows services. From memory one has to get about 4 ducks in a row … but no-one gave an explanation of the problem cause. I had the same issue network-wide across W10 Pro machines running 1803. None of the 'fixes' worked for me and I tried headbanging too 😞 1803 was the version where MSFT removed Homegroup. I noticed (by accident) that the last devices to be upgraded from 1709 could all see others on the network. So my best guess is MSFT screwed something up. When I moved to 1809 I decided to go nuclear: I did a clean install of W10 1809 on ALL my machines. No problems anywhere now. SMB 1 … I thought that was unsafe and deprecated and a recommended removal? Everyone should be using SMB 3 now - the best part of Windows 8. https://blogs.technet.microsoft.com/josebda/2012/06/28/the-basics-of-smb-multichannel-a-feature-of-windows-server-2012-and-smb-3-0/ Does DROBO insist on SMB 1?
  8. JROrtiz

    Unable to connect to NAS from a specific computer

    Another update: Looks like everything reset once I reboot. I have to remount a share through Drobo Dashboard again in order to be able to see it through explorer. I really wish I could figure out what is actually preventing it from showing up on this specific machine while the Synology works just fine.
  9. JROrtiz

    Unable to connect to NAS from a specific computer

    After digging through tons of forums and sites and even trying to reach out to Drobo support, I was able to find a roundabout way of getting it to connect. I used the Drobo Dashboard software to mount one of the shares. As soon as I did that, I was able to see the Drobo on the network and access everything else, even after unmounting the share from the Dashboard. I still have no clue what was preventing this machine from seeing it on the network, but looks like once the Dashboard exposed it to the machine, it was able to pick it up. So strange but at least it's up and running now.
  10. ieatrocks

    >16gb success on G2020T.

    Sure enough, it sees it but cannot use it. It appears that the memory is "Hardware reserved" and does not hit at all. Definitely not actually in use even if the bios, os, and everything can see the additional 16gb. edit: Windows PE and windows 10. The built in diagnostics and ilo also reported it being there though. Ah well.
  11. schoondoggy

    >16gb success on G2020T.

    Intel CPU's of this era could only use 8GB per slot.
  12. schoondoggy

    >16gb success on G2020T.

    What OS are you running?
  13. JROrtiz

    Unable to connect to NAS from a specific computer

    Thanks for the advice. I just gave it a shot and unfortunately that didn't work either. Still digging around to see what else I can try.
  14. BSR

    Unable to connect to NAS from a specific computer

    I have occasionally run into similar issues on my network. There have been a few cases where I couldn't figure out why PC-A wouldn't find NAS-B despite having what you've outlined set up. Rather than spend more time on it, I've just made the NAS IP address static and mapped it in the hosts file in Windows (C:\Windows\system32\drivers\etc\hosts). Then the PC always finds the NAS. I've never actually spent the time to figure out WHY this happens -- this is just a workaround that has always worked for me. Once it's working, I lose my motivation for figuring out the issue's root cause and just use it.
  15. ieatrocks

    >16gb success on G2020T.

    OS sees 20. Onboard diags tests all ok, but the tests take less than 5 mins so obviously it's not thorough. You're absolutely right when plugging in 2 sticks of rdimm though, I get a boot loop. With 1+1 udimm and rdimm, I pass BIOS. edit: > Registered memory is not supported on the MS Gen8. Even swapping out the pentium for a xeon? Looking for clarification from someone who's tried hopefully. I know the specs say no, but it also appears that's a limit of the chip not the board from what I gather.
  16. Yesterday
  17. I've been banging my head for a few days now trying to figure this out and I've run out of ideas. Hoping the very intelligent crew here can help me out. I have a Drobo 5N and a Synology RS816 on my network, both of which have been working without issue for quite some time now. I've always connected to both via Windows Explorer by simply going to the network address i.e., \\N5 and \\SYN (sample names). I recently got a new desktop which is where the issues are coming up. When I try to go to \\N5, it results in a message saying it cannot find that location. However, \\SYN works just fine. What's strange is that I can see and manage the Drobo through the Drobo Dashboard software. What could be preventing Windows from seeing the Drobo on the network? I've already enabled the SMB 1.x protocol, ensured the workgroup names are the same, rebooted both the machine and the Drobo, made sure network sharing is enabled, and even did a fresh install to ensure that some program I installed didn't cause the issue. Every other machine I have can access the Drobo without issue. It's just this new desktop, and everything is running Windows 10. Another strange phenomenon that I discovered is that if I go to "\\DROBO" (verbatim, not a sample name) it leads me to the Synology. Where is Windows getting the mapping from that it is directing that address to the Synology? This is driving me nuts so any advice would be greatly appreciated.
  18. schoondoggy

    >16gb success on G2020T.

    Do you have an OS running on the server? How much memory is available in the OS? Registered memory is not supported on the MS Gen8. The server will sometimes boot with registered memory installed, iLo can see it, but it is not available for the OS. I assume your OS will see the 4GB and the 16GB will not be available.
  19. Thanks Skandal, Do you know if there is a maximum HDD size on the P420? Or should any disk theoretically work?
  20. Yes. I bought mine at eBay, and saw other do the same without a problem. I bought a 9207-8i, works pretty well. But If you want HW RAID you might want to look to other options. Probably a P420 is a better choice. Don't go RAID5 for that amount of space. If a disk fails, the stress added to the other disks when rebuilding the array might kill another.
  21. ieatrocks

    >16gb success on G2020T.

    I've got 16gb ddr3 Rdimms that the server won't accept and 4gb Udimms that I have to use. But, if slot 0 is a Udimm, slot 1 won't even check for registration. Currently a 4gb Udimm in slot 0 and a 16gb Rdimm in slot 1 boots normally and shows 20gb available. Can I get some confirmation with anyone else able to test this? Is there a real technical reason why we might want to avoid this? Rdimms that don't register should act just like Udimms as far as my reading leads me. Will a xeon upgrade let me use 2 of my Rdimms for 32gb? Apparently the inability to accept dimm registration is tied to the pentium chip, but without a swap handy to test, I don't know if the BIOS blocks Rdimm as well.
  22. It's the 1060 you always wanted! @ Newegg Image is the link. Enjoy!
  23. schoondoggy

    ProLiant MicroServer Gen8 Links

    Those should work as they are UDIMM and ECC. The speed is faster than required, but that should not be a problem. It is always good to check return policy before buying.
  24. parshivets

    ProLiant MicroServer Gen8 Links

    How do you think - will this RAM work? HMT41GU7BFR8C-RD https://www.skhynix.com/products.view.do?vseq=999&cseq=75
  25. Hi All, I've seen that there have been many views to this post, any advice from anyone though? Thanks in advance
  26. mcgrog

    HP Microserver Gen10 HD Limit?

    I've just used the startech pcie m2 nvme adapter with a 1tb samsung 970 pro nvme as a boot drive for win 10, got it right before i read the news about the evo pluses coming out, i had it in the 8x bay and got full speed - very nice, that was crazy fast, but now ive shifted it off to the 1x and put a radeon pro wx4100 in the 8x slot, the 1x slot still gives me 4x better speed than sata2 which ive been used to up til now using the odd bay on a my gen 8's for ssds, also have a 12tb seagate helium drive in there and will probably fill the rest of the bays out with them, and also plan to put another ssd in this machines odd bay for some kind of cache.. heres the benchmark of my current setups nvme boot drive in the 1x slot
  1. Load more activity
×