bulisor007

I've managed to read the DSM boot disk with the use of 4 breadboard jumper wires. The strange thing is that even though the disk seems to be with no errors and the first partition is marked as bootable, I was not able to boot my computer with that disk. I don't know if this is normal or not, I was still expecting to see some boot messages on the screen then to stop the process with an error message that the hardware is not Synology.

That's true but the pitch of the pins is smaller than the standard USB layout so you can't plug it on a standard socket without an adapter.

I've tried the resistor workaround, without any luck. Currently I'm looking for an USB adapter to be able to read the DOM module and see if that's corrupted or not - this will help me understand if the issue is with the boot disk or with the CPU itself.

I'm having a failed DS1815+ unit (CPU died most likely) and I was wondering if it can be transformed into an expansion unit like DX517. The PSU is still working and I don't believe that the electronic part in an expansion unit is that complex so I may repurpose the failed unit to an expansion unit. Any thoughts?

See on viewtopic.php?f=2&t=2147 what you need to do to run Xpenology on ESXi with Microserver Gen8 and having the fan running at 6% (dead silent). The instructions were for older versions of DSM but are still applicable for the newest versions, with minimal changes.

I would recommend to do the upgrade first bare metal and only once you have everything working as expected to move to VM, just to know what caused the issue in case you face any.

Sometime even if the system was configured to run on VM, you may want to move to bare-metal to get the SMART information available for the HDDs but then you want to move back to VM to get the fan speed running at minimum level. Here are the details on how to perform this steps: 1. VM to bare-metal This works directly, without any action needed, all data is recognized and available immediately. 2. Bare-metal to VM When switching from bare-metal to VM the system won’t recognize the information on the HDDs and will wee the system as not installed. As the data is still on the HDDs (can be e

It's not a driver issue as you would not see the rest of the 10 drives. Please pay attention to what XPEH said as that's most probably the reason why you miss the other 2 drives.

Nothing extra, just 2GB more RAM and 4 x 3TB WD Reds + 1 x 60GB 2.5'' Seagate.

You are right: write speed is significantly higher than read speed (100MB/s vs 50 MB/s) but I don't know exactly why. Still, it seems that this comes from DSM itself and it's not a result of virtualization - the same behavior happens on bare metal installation of DSM (the "noisy" approach).

no

This setup was meant mainly to have XPEnology on a quiet HP ProLiant MicroServer Gen8 and only secondary to have compatibility with other systems. You can install XPEnology directly on the MicroServer Gen8 but you won't have drivers for iLO meaning that the fan will be noisy (at least 39%) - you need to do the workaround with ESXi in order to get the temperatures from the HDD into iLO and have the fan spinning at low rate (I have the fans at 6%). If you setup your HDD as a single RAID0 volume you'll get max of the space but will loose the redundancy - in case of any drive failure you'll lo

HP ProLiant MicroServer Gen8 is a great piece of hardware which would be perfect as XPEnology host but it has a problem: when iLO drivers are not installed the HDD temperature can't be read so the fan will be set at a safe value (at least 39%) to prevent overheating. Of course, the noise coming out of this fan level is rather high so the MicroServer can't be used in environments where noise is a problem. The solution is simple but challenging in the same time: have the right drivers for iLO. As the drivers are closed source from HP, the chance of getting this from HP is rather low. Still,