koroziv

In my case the culprit was an external USB hard drive. My gen 8 was frozen after every 48 hours. Sent from my SM-G930F using Tapatalk

I got it working in a vm on esxi, but you can't create volumes. So no, not usable yet.

The modules errors are the same for me and others when booting xpeno, nothing to worry I think. Sorry for my confusion with the gen 8 drivers, the symptoms were identical and didn't read carefully enough the thread. Hope I didn't caused any troubles while trying to help Sent from my LG-H815 using Tapatalk

Just make sure that you use the corect driver for your device, I'm not sure if there are the same. Sent from my LG-H815 using Tapatalk

Just to be clear, I have a hp gen8; I just realized that in here it's about another model; not sure if the driver is the same for n40 or other hp model, but the issues are identical

I recommend rdm if you use esxi. If you go native or virtual it is up to you, your necessities and hardaware. I choses esxi because I have an Xeon processor and I like to play with vm's. I have xpenology installed on a datastore and 2 hdd's added using rdm. My drives are each configured in raid 0. The downgrade is in adition to rdm. Sent from my LG-H815 using Tapatalk

Downgrade hpvsa drivers to scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib, it will get better. http://homeservershow.com/forums/index. ... sxi-notes/

The topic is about the 5.2-5644 bl and the .pat file, it was changed after they released the bootloader and the new pat brakes the bootloader. The iscsi problem was present even with the original pat file, it is known but most users do not use it so it's of no importance to them; volumes are useless ?!? think again... I'm just trying to inform users that are not depending on lun's that is ok to update if they want, just don't use the pat file.

I'm running the latest updates with no problems; I don't need iscsi lun's, or to create new volumes (I'll try later to create on a test vm and get back if it works) edit: just added a new volume on the latest update, no problems here [attachment=1]1.JPG[/attachment] [attachment=0]2.JPG[/attachment] I use a hp gen8 microserver, vm on esxi 6.0

I think the issue is when installing fresh, do not use the 5.2-5644 pat file; if you upgrade from a previous version it works, but it has problems with iscsi. Most of us do not use iscsi lun's, so we don't care

If you use iscsi lun do not update First change to the new bootloader, then start your xpeno normally. Then you can update from control panel. If you use esxi you can create a test vm and try there first, to be sure. Sent from my Nexus 5 using Tapatalk

If it's a test vm, just try, nothing to lose but some time I recommend to all that use virtual machines to run xpeno to build test machines, it is an easy way to test updates and community packages before using them on the main install.

That is the error with dsm 6 beta, did you installed that one ? because is not supported by xpenology yet. You should give more details, hardware and software versions used (xpenoboot and dsm)

This is a bug that I had also on my ds212+; after updates hibernate stops working. Just change the time to any other value, hit apply, then change back to your preferred value and hit apply again.

Some details ? bare-metal or virtual machine? I'm on vm (esxi6) and I have working usb hdd. I had to re-attach the drive to the vm, but I was expecting that.

On a test vm (Xpenology 5.2-5592) I created one iscsi lun and target; after that I updated to 5644 in control panel I did not lose the LUN, it is still usable after update; but I can't create another one after update, the target is there but with no LUN mounted. Edit: I tried to create iscsi lun on my main xpeno install, also updated to 5644; same result as on the test one, and it ejected my usb drive. Not sure if related, usb drive over esxi is not so stable, but maybe it is. I am able to test new xpeno-boot if help is needed, install from scratch or update; only in virtual machine (esxi 6.0 on hp gen8) and also only basic functionality. Edit2: I did not lose the iscsi in xpeno, but I can't mount it in windows, so it is useless. The update brakes iscsi.

Hy I've made a test vm for Xpenology; ovf format in a zip archive, just deploy the ovf template and you are good to go. You can edit the vm settings to your liking, if I did something wrong in there let me know. http://sri.noip.me:5000/fbsharing/HJsK5dUm http://s.go.ro/sutc1uiz info: Xpenology 5.2-5592 user : admin password : testpass 1Gb ram 1cpu, 2 cores 16Gb hdd No vm tools installed I did this because I see a lot of users with update issues after updates; If you are to lazy to create a test vm, this is an easy and fast way to get you going.

Go and change the hibernation settings, just change the time and hit apply; after that change back to your preferred values, hit apply again; check if its working again. I used to do that for my hdd hibernation on my ds 212+ after some updates; that trick used to work

Just make a test VM identical with the one you use and test first. Right now I am installing 5.2-5592 to a new one to test some more Edit: I do have an issue, I gave the VM two virtual hdd's 5Gb each; when I try to create a volume, it makes it only 400 Mb. That is note related to this update, I have this problem in the new tesm machine with 5.2-5592. Edit 2: nevermind the issue above, I increased the size to 16 Gb, about 4 Gb are reserved Edit 3: The update from 5.2-5592 to 5.2-5644 worked perfect, I just did it on a fresh installed VM; all automated from control panel, just as normal synology. Note that I only use download station on my system, so I have no idea if other apps are having problems, but usually everything is ok, maybe just some re-indexing of the media...

like I said, all looks ok

I just updated a test vm, all woked fine; just click update in control panel. Edit Updated my main xpenology machine, all looks ok

Did you try to re-scan your media ? I don't use it so I can't try.

Mine is louder than the pc; the fan is 6-9% (esxi, bare metal is 18-26%) but it has an annoying coil noise. I returned the first unit for this reason (celeron) and got one with a xeon in replacement (paid the difference) and it was ok for about 2 weeks, then it started. The only solution is to replace the system fan, very expensive from hp or look for another compatible one (50-75% cheaper) This is the second and last product I will ever buy from hp; the only reason I bought the gen 8 was that the price/performance ratio was hard to beat with a custom build from components.

I also used a custom hp image, so you might have the same issue, solved as described in that link If you have a gen8 microserver here is a forum with a lot of useful info : http://homeservershow.com/forums/index. ... -ms-gen-8/

Hi look here: http://vmtoday.com/2012/09/esxi-5-wont-boot-from-usb/ not my blog but I had the same issue, and that did it for me; you have to install esxi 6.0 again on that usb, using that guide