Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About XPyno

  • Rank

Recent Profile Visitors

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

  1. Interesting thing, I will check also this. At the moment what is strange is that when I have booted the microserver for the very first time, the hard drive was recognized on port1 (the only time) with the added message: "ATA security state of this disk is invalid"...and there isn't this added message when it works (connected to port3/4 in AHCI mode or to port1/2/3/4 in RAID mode). I have passed the last days on the net trying to find similar cases with maybe the hope to find a solution and there are also lots of cases from people having issues with other hard drive models/brands not being detected on port1 e port2 of microserver gen8, when the controller is set in AHCI mode. So at the moment I'm not sure if it is the drive that is "picky" or the microserver... So I have asked what models of disks other have used on their microserver, because obviously I really need the AHCI mode for install xpenology, and there is a lot of people here that also use the gen8. Many thanks to all for your help
  2. Where to look for these? I have checked in BIOS and I didn't found these options nor in Server Security menu nor in Advanced Options. Thanks for suggestion, I will try hdparm with drive in slot3 and AHCI enabled for now. I would like to know why it isn't detected on slot1&2 when AHCI mode is enabled. If I change to RAID mode the controller reset itself and I can see the disk on slot1&2. When I'm in AHCI mode I can see the drive on slot3 so probably the hdparm result will be the same. Or I'm wrong?
  3. thanks for reply I have the latest microserver gen8 (HPE branded front door) production date 2017. My BIOS is the latest J06 (11/02/2015). At the boot screen it says HP AHCI SATA Controller (v0.90) (this one don't recognize the hard disks) and then HP AHCI SATA Controller (v0.84). I have tried to set again the controller in HP Smart Array RAID MODE for test and with F5 I have entered the smart array manager setup. Here I can see that the drive IS recognized again. Changed again the controller in SATA AHCI mode and it ISN'T recognized anymore, same as before. The diagnostic of the microserver is ok, no errors, and the hard disk too, I have checked it before I have installed it in the microserver and checked again after this problem, cables and backplane seems ok. The drives (4x WD GOLD WD4002FYYZ 4TB) were perfectly new, sealed and never used. When I have booted the microserver for the very first time, the hard drive was recognized (the only time) with a strange message: "ATA security state of this disk is invalid" (from what I know is a security feature used most on laptop but for sure it was not enable on my WD GOLD). It seems like the microserver have "blacklisted" the drive from using it in AHCI mode on port1 and port2, the ones sata3 because port3 and 4 are sata2 and when connected to these ports it works. If I listen the sound it emits when it is installed on the microserver, at the start I can hear the usual spin-up of the motor, then when the boot sequence arrives at "HP AHCI SATA controller....initializing /" I can hear the the motor spin-down and it isn't recognized (no message). Reset the server don't restart the the hard drive motor, the only thing is a shutdown of the microserver.Very strange... I know that HP in the past have indicated that the maximum configuration supported on the microserver is 4x3TB, however later they have stated to have added support for maximum 4x4TB. And at the moment this is what is indicated on the manual of the microserver (4x4TB). At the moment I don't have a spare drive for test lower hard disk size, however your gentle reply have confirmed me that the size of hard disk is not important. Maybe it is something else so I have started to ask what model of disks have other people used...or HP have crippled something...
  4. Hi, Is there someone who have used, with the hp microserver gen8, hard disks of 4TB or higher installed in slot1 and/or slot2? If yes could you kindly tell me what models have you used? For me it seems impossible to have the hard disks recognized and so I can't install xpenology (baremetal). With SATA controller set in AHCI mode, slot1 and slot2 don't recognize the hard disks, that are recognized if I set the controller in RAID mode (however useless for an xpenology baremetal install). The hard disks are recognized in slot3 and slot4 but so I remain with only two drives... Many thanks to all
  5. From what I have read the microserver gen8 needs the1.02a image for DS3615XS or there will be later some error during the installation procedure.
  6. Hi to all, I have tried to “first” install Xpenoboot 5.2-5967.1 on: Microserver Gen8 / G1610T / 4GB / BIOS J06 Only changes done to the BIOS are: 1) disable network boot 2) change RAID controller to AHCI-mode I have double checked to have put correct PID and VID on the USB pendrive (inserted on mobo internal connector) that I have used for install. Also I have changed the serial number and corrected/inserted the two mac addresses of lan with the original ones of the microserver. I have put the ethernet cable on the lan2 port and the hard disk on slot1. My bootlog says: eth0 not RUNNING eth1 not RUNNING So my machine didn't get an IP address. A bit strange because the NIC of the Microserver Gen8 (BCM5720) is apparently supported. Also many users have the Gen8... I can’t try to test the workaround of manually assign an IP address, the subnet mask and the gateway at the "diskstation login" prompt, because the usb keyboard doesn’t work at the login prompt. It works before that when I’m in the grub menu of selections Install/Upgrade but after that it doesn’t work anymore from what I have understanded probably due to the lack of OHCI driver that is needed for low speed devices (usb 1.1). Using PS/2 keyboard is out of question because the Microserver Gen8 doesn’t have the PS/2 connector on mobo. I have checked if it's possible to force the static IP changing something in the USB config files on pendrive or by insert some command at the grub start menu (after that it is impossible) but I haven't found nothing. Do you know if this is possible to change something? Do you know how to check if the correct driver for the lan card are installed or not? I mean, I know that the IP addresses aren’t assigned but how to know if at least the card is correctly recognized? What to check on the bootlog or maybe in the "debug" bootlog? so I can concentrate my tests on why the IP’s aren’t assigned. Many thanks for your suggestions
  7. In terms of performance if you can pass-through the hard disk controller using the vt-d (or amd equivalent) you have no visible differences. I have to admit that from my tests, using only one lan, I can't see any difference even if I don't use vt-d and use a .vmdk disk (one on every single physical hard disk) or direct disk access, but it all depends on the type of workload you apply. However If you can't use vt-d because your cpu doesn't have it nor the direct disk access, and you can only use .vmdk, I don't recommend using the .vmdk, too much troubles on recovering files if something goes wrong, so try to go with baremetal in this case.
  8. Hi, I'm in a pretty similar situation as you. I have a Microserver Gen8 and I have the two eth0 eth1 with the "not RUNNING" message so I can't install nothing. The usb keyboard (no PS2 is possible on my system) works only until the grub menu selection then doesn't work anymore so I can't even try to set the static IP as suggested. This for what I have understanded is due to the lack of OHCI driver that is needed for low speed devices (usb 1.1). The kernel loads only the correct EHCI driver but not OHCI and so the system can't comunicate with usb (low speed) keyboard. In the past there was some something done for add the correct driver to the bootloader but it was done only for a specific version of it (I think 4.2..) and so it's not possible to use that addon anymore. I have checked too if it's possible to force the static IP changing something in the USB config files but I haven't found nothing. Let me know if you find something more about this problem...
  9. Hi to all, probably a silly question...but the last bootloader for the DSM 5.2 isn't the 5967.1 or there is also a 5967.2?