sarieri

The drive that crashed was an HGST 8T entreprise drive, and the four that were okay was the seagate ironwolf 4T. I guess there might be a difference between hibernation mechanism between these drives.

That is what I think the problem is. The hibernation option was turned on everytime the drive crashed. Also, I have been use BTRFS, and I heard that ext4 might be more stable.

I'm running XPE NAS in ESXI. I can't run XPE as the O/S since I have a nvidia graphic card to run in another VM(ubuntu) to transcode for emby in ESXI and Xpenology does not have a driver for that. I will definitely try to put my ESXI on a USB to boot and disable other sata ports. As for the data store set up, It doesn't seem to matter. I set up a SHR before with all four 4T drives and the 8T drive, and it crashed. I also set up a basic volume with the 8T drive only, and it crashed just this morning. SATA ports and SATA cables were switched so those should not be a problem. The powersupply is a 500w one, seems to have enough power. Also, if it's the problem of the powersupply, drives should crash randomly, but in my case, it was always the 8T one. Right now I can only suspect that if it is the case that Lsi 2308 has some compatibility issue with HGST drives.

If I select the third option when the loader boot up, all five drives show up. However, it randomly crashed in 2 or 3 days, if I put all five drives under SHR raid. It was always the 8t drive that crashed but I the complete S.M.A.R.T status was fine. I checked with WD's Data Lifeguard Diagnostic app as well, and it had no problem at all. My powersupply, sata cable were switched as well, problem still insisted. I also tried to change the port the drive connected to, but still no luck. The drive was a HGST HUS728T8TALE6L4 and it is in the compatibility list of DS918+.

Hi guys, I'm kind of confused about how sata ports are mapped in xpenology. So I installed dsm6.22 24922(918+) with jun's loader v1.04b modded with extra.lzma on my ESXI host. The weird thing is that one of my five(four 4T and one 8T) drives is missing if selecting baremetal option(first option) when the loader boot up. I did some research on how to modify the synoinfo.conf file under /etc.defaults and got no luck. The default parameters in that file was: internalportcfg="0xffff", esataportcfg="0x0", usbportcfg="0x30000", and maxdisks="16". The four drives that are recognized were from slot 17 to slot 20. I have no idea why they were there even though the maxdisks should sixteen. My motherboard is a ASUS p9d mh/sas 10g-dual, which has 6 sata ports and 8 sas port under lsi2308 controller. My esxi host is installed on a ssd drive which is connected to the sata port labeled orange under the photo below, and all fives drives are connected to sas port labeled red. I passthrough the lsi2308 controller to the Xpenology.

BTW, the sas controller has been flashed to IT mode.

Hello everyone, I'm kinda of new to this. My motherboard is the ASUS P9D MH/SAS 10G-DUAL. So I was trying to install DSM6.22 24922(918+) with jun's loader v1.04b on my ESXI host. I didn't change anything except the mac address of two ethernet ports and the SN in grub.cfg. The ESXI host was installed on a ssd drive connected to a sata3 port on the motherboard. I tried to pass through my SAS controller and connected all 5 drives to that sas controller. If I understand things right, I should select first option when the loader boot up and install the DSM. What happened is that although I'm able to install the DSM selecting first option in loader, it only recognize 4 drives. The DSM can only recgonize all five drives when I select the third option when the loader boot up. This is kind of wierd, cuz I can't install the DSM system selecting the thirds option when loader boot up. It always came up with error 13(I did wipe all my drives beforehead and I don't think changing PID and VID in grub.cfg is necessary for installation in ESXI). I can install the DSM with the first option and make it recognize all 5 drives by selecting third option when booting up though.