Jump to content
XPEnology Community

yaroslava

Transition Member
  • Posts

    9
  • Joined

  • Last visited

yaroslava's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Thanks for taking the time to answer. And Xpenology of course.
  2. Any idea how to throttle the CPU if the folder structure for the CPU does not exist? After upgrading to 5664 and the latest 5967 I don't have cpuX/cpufreq/ entries anymore on a GT1610T Celeron CPU: Diskstation> ls -lR /sys/devices/system/cpu/cpu0 /sys/devices/system/cpu/cpu0: drwxr-xr-x 6 root root 0 Jul 25 01:13 cache -r-------- 1 root root 4096 Jul 25 01:15 crash_notes -r-------- 1 root root 4096 Jul 25 01:15 crash_notes_size drwxr-xr-x 2 root root 0 Jul 25 01:15 power lrwxrwxrwx 1 root root 0 Jul 25 01:15 subsystem -> ../../../../bus/cpu drwxr-xr-x 2 root root 0 Jul 25 01:13 topology -rw-r--r-- 1 root root 4096 Jul 25 01:13 uevent Thanks!
  3. Hi, Would it be possible to add driver support for HP Proliant software controllers (like the B120i one)? Basically the hpvsa driver. Thanks!
  4. In my case it was a new install plus I have an Intel CPU. Basically the ...cpu0/cpufreq/scaling_governor files do not exist any more and thus the governor cannot be set. On the same machine I had those entries on xpeno 5.2 5592.2 (boot loader and synology) but now on bootlolader 5644.5 and syno 5664 update 8 the CPU is always running at max speed...
  5. It looks like since 5.2 5644 (Update 8 at least) the cpu governor are available any more. Any idea how to get around it and lower the CPU power consumption? Thanks,
  6. It should work without any issues. There are folks that are using it with synology so as long as you boot of a different disk (not sure whether the bios supports 8TB) you should be just fine. I myself am using 6TB on a G8 - I only have issues in ESXi due to the HP drivers but that's outside Synology.
  7. Replying to myself, it looks like the ESXi drivers for B120i doesn't properly support HDD bigger than 4 TB (in my case 6TB). When bypassing the RAID controller and mounting the drivers as SATA AHCI or Legacy, the RDM works fine. Through the controller, it simply does not recognize the partition...
  8. As a quick update, after 3 days of going back and forth it looks like there's an issue with the HP drivers. If I'm using legacy sata, the drives are picked up without a hiccupt. Through the controller though they aren't (they work fine though on bare-metal). So likely the driver messes something up. I'll probably have to try different versions hoping I can find one that works. Ironically the new versions are known to be quite slow and most people downgrade ...
  9. Hi, I have a xpeno 5.0 running on HP Micro Gen8 bare-metal. After an upgrade to RAM I'm trying to move the system to ESXi without success. On bare metal, using the b120 controller (each hdd is in RAID0) or the AHCI SATA works without any issues, xpeno simply boots up. Like the others indicates on this forum, for ESXi I have used the RAID0 approach with the controller, installed the dedicated ESX 6.0 ISO, downgraded the driver to 5.5.088 for maximum speed, created a VM and mounted the HDD as RDMs. With both 5.0 and 5.2, the hdds content is not properly recognized - when booting, the install interface appears mentioning there's nothing installed. Going back to bare metal indicates the configuration lost however after installing everything is the same. However If I go ahead with the install in ESXi, the data partition is not formatted yet nothing is found. I have tried this with both nanoboot and DSM 5.0 and latest xpeno and 5.2. It basically looks like RDM simply doesn't preserve the proper structure for some reason. To make things worse, in ESXi not using the controller seems unstable; the devices are found yet 5-10' ESXi stops viewing then and gets stuck. Any tips folks on how to migrate things between bare-metal and ESXi on Gen8? I'd like to avoid having a complete reinstall simply because in case something goes wrong, I'd like to be able to reuse the HDD outside ESXi. thanks!
×
×
  • Create New...