Rand__ Posted November 2, 2013 Share #76 Posted November 2, 2013 So, 2008 based card causes crash (see image; still occurs after changing to PVSCSI); 1068e seems to boot at second try. The drives are there but i still dont see them in HDD Management so no adding them to a volume cat /proc/partitions major minor #blocks name 8 0 16777216 sda 8 1 2490240 sda1 8 2 2097152 sda2 8 3 1 sda3 8 5 12048720 sda5 65 32 117220824 sds 65 33 117211136 sds1 65 16 976762584 sdr 65 17 976754247 sdr1 65 25 8192 sdr9 65 0 976762584 sdq 65 1 976754247 sdq1 65 9 8192 sdq9 9 0 2490176 md0 9 1 2097088 md1 9 2 12047616 md2 253 0 12046336 dm-0 Link to comment Share on other sites More sharing options...
wenlez Posted November 2, 2013 Share #77 Posted November 2, 2013 This latest Beta ESXi build can fully install Xpenology, but it fails to detect any of my ASM1602 SATA controllers. Link to comment Share on other sites More sharing options...
Trantor Posted November 3, 2013 Author Share #78 Posted November 3, 2013 So, 2008 based card causes crash (see image; still occurs after changing to PVSCSI); 1068e seems to boot at second try.The drives are there but i still dont see them in HDD Management so no adding them to a volume This first ESXi test build is based on jukolaut kernel sources, not my "updated" one. When you say 2008 card, can you give more informations about it ? I assume you boot from the IDE vmdk and install DSM on standard PVSCSI disk and then add you controller ? Maybe you can explain how you "prepare" your VM before installing ? This latest Beta ESXi build can fully install Xpenology, but it fails to detect any of my ASM1602 SATA controllers. Unfortunately as jukolaut did in his build I removed SATA support from kernel so the PVSCSI work.... Can you please test on bare metal machine to see if your ASM1602 controllers are detected ? Link to comment Share on other sites More sharing options...
Rand__ Posted November 3, 2013 Share #79 Posted November 3, 2013 So, 2008 based card causes crash (see image; still occurs after changing to PVSCSI); 1068e seems to boot at second try.The drives are there but i still dont see them in HDD Management so no adding them to a volume This first ESXi test build is based on jukolaut kernel sources, not my "updated" one. When you say 2008 card, can you give more informations about it ? I assume you boot from the IDE vmdk and install DSM on standard PVSCSI disk and then add you controller ? Maybe you can explain how you "prepare" your VM before installing ? This particular card is an Dell H310 (rebranded LSI SAS-9211-8i flashed to IT mode since my m1015 died). And yes Add your vmdk, add a PVSCSI disk, add controller in passthrough mode. No additional preparation;) Works more or less with the 1068e with ur fusion kernel modules (drives are in partitions) Link to comment Share on other sites More sharing options...
costib Posted November 3, 2013 Share #80 Posted November 3, 2013 Successfully build ESXi version with PVSCSI support in my ESXi 5.5 environment. Nice Cookin' Doc! After install is done, there is an error, see the image link. After one reboot this error is gone. I've tested it also with a physically mapped drive using a RDM file, works perfect! This first ESXi test build is based on jukolaut kernel sources, not my "updated" one. Should we expect a next "stable"/"updated" version or can we use this already in production? Thanks. Link to comment Share on other sites More sharing options...
Trantor Posted November 3, 2013 Author Share #81 Posted November 3, 2013 This first ESXi test build is based on jukolaut kernel sources, not my "updated" one. Should we expect a next "stable"/"updated" version or can we use this already in production? I'm again very busy at work so maybe in few days/weeks... XPEnology is not for real production environment, like they says : If you like it buy it Seriously this build is my first one for ESXi and have lot of issues/bugs, so it's up to you. Are your drives on the 4i seen by the system as in you can add a volume on top of them? I just test beta2a on my bare metal system with my LSI controller (one disk on motherboard sata and one on the lsi card): system boot, and shutdown.... Test with clean v1.2 setup, (only the disk connected to the motherboard during install), connect the lsi card and the second disk and voila DSM detect the disk attached to the LSI controller and I can expand the volume to it Beta2a ESXi : built-in original mpt2sas driver (probably v11 or 12) Beta2a : built-in mtp2sas v16 driver v1.2 : mpt2sas v16 build as module, loaded in ramdrive As you can see the only difference is the way the mpt2sas is built, and maybe the additional modifications to sd.c and libata-scsi.c EDIT: I rebuild ESXi kernel and rd with mpt2sas as module : http://xpenology.trantor.be/esxi/zImage ... as_esxi.7z rename files to zImage and rd.gz and copy them to your usb stick / vmdk Link to comment Share on other sites More sharing options...
nols Posted November 3, 2013 Share #82 Posted November 3, 2013 Does the Promise Raid Controller work? I have a Promise SuperTrack EX12350. Link to comment Share on other sites More sharing options...
Rand__ Posted November 3, 2013 Share #83 Posted November 3, 2013 EDIT: I rebuild ESXi kernel and rd with mpt2sas as module : http://xpenology.trantor.be/esxi/zImage ... as_esxi.7z rename files to zImage and rd.gz and copy them to your usb stick / vmdk That did really good - both cards (1068e + 2008) work now (no boot error with 2008), i think the drives get found as well DiskStation> cat /proc/partitions major minor #blocks name 8 0 16777216 sda 8 1 2490240 sda1 8 2 2097152 sda2 8 3 1 sda3 8 5 12048720 sda5 65 32 117220824 sds 65 33 117211136 sds1 65 16 976762584 sdr 65 0 976762584 sdq 65 1 976754247 sdq1 65 9 8192 sdq9 9 0 2490176 md0 9 1 2097088 md1 66 0 1953514584 sdag 66 1 2490240 sdag1 66 2 2097152 sdag2 66 16 1953514584 sdah 66 17 2490240 sdah1 66 18 2097152 sdah2 66 32 1953514584 sdai 66 33 2490240 sdai1 66 34 2097152 sdai2 66 48 1953514584 sdaj 66 49 2490240 sdaj1 66 50 2097152 sdaj2 66 64 976762584 sdak 66 65 2490240 sdak1 66 66 2097152 sdak2 66 80 976762584 sdal 66 81 2490240 sdal1 66 82 2097152 sdal2 66 96 976762584 sdam 66 97 2490240 sdam1 66 98 2097152 sdam2 66 112 976762584 sdan 66 113 2490240 sdan1 66 114 2097152 sdan2 9 2 12047616 md2 253 0 12046336 dm-0 but unfortunatly none of the drives is being shown in the gui to add to a volume I will try to remove the existing partitions for the sata drives and enable sas in syno.cfg (which killed storage manager last time i tried it but who knows:p) Thanks for the hard work and your help edit: no chance, neither worked. Next and kinda last hope will be to try on physical installation edit2: Physical installation failed with a kernel error which i cant see; thats probably due to some unsupported devices on my board. Its weird though; its late in the boot (secmd already started, then error after that and then some USB messages; i thought it might have worked but it didnt show up on synoassistent and didnt spit out any new status lines). Just ran a knoppix (linux based) live cd - worked ok except graphics, detected lan and drives; so i have no clue what the issue is There are few Linux drivers available (lan & raid only) for the board though ... Link to comment Share on other sites More sharing options...
Trantor Posted November 4, 2013 Author Share #84 Posted November 4, 2013 edit2: Physical installation failed with a kernel error which i cant see; thats probably due to some unsupported devices on my board. Its weird though; its late in the boot (secmd already started, then error after that and then some USB messages; i thought it might have worked but it didnt show up on synoassistent and didnt spit out any new status lines) With which version did you try ? If you did with beta try v1.2 instead. Can you give more informations about your system (mainboard, brand...) Link to comment Share on other sites More sharing options...
Rand__ Posted November 4, 2013 Share #85 Posted November 4, 2013 Yes i used Beta2, will try 1.2 And its an Intel S1200RPS, C222 based. Link to comment Share on other sites More sharing options...
Rand__ Posted November 5, 2013 Share #86 Posted November 5, 2013 Same issue with 1.2. Seems to be usb related as there is some USB-xhci process being RIP'ed... Link to comment Share on other sites More sharing options...
Djey Posted November 5, 2013 Share #87 Posted November 5, 2013 Hi, I'd need to plug a e-sata drive, mapped to ESXi virtual machine in raw mode (RDM), as e-sata, not internal sata. My guess is I have to attach it to another virtual SCSI controller. => If mapped drive is attached to SCSI controller 0 (vmware ParaVirtual), it is seen as internal sata only, like other virtual disks. Changing etc/synoinfo.conf for esata port mapping didn't do what I want. => If mapped drive is attached to a secondary, SCSI controller 1 (either vmware ParaVirtual or LSI), it isn't seen at all. Here is my question : => can xpenology support secondary SCSI controllers, and how ? Would it be solved with a driver ? Thanks. Link to comment Share on other sites More sharing options...
dsmatom Posted November 9, 2013 Share #88 Posted November 9, 2013 Hi Trantor, Firstly thank you for all the work you are putting into this. Really awesome!! I have setup my nas using your latest repack. Unfortunately am not able to see any of my drives connected to my RocketRaid 2340. I assume the card is not supported. Could you please add support for Highpoint RocketRaid 2340. Based on Marvel 88SX6081. The drivers are at http://www.highpoint-tech.com/BIOS_Driv ... rr2340.htm Alternatively can i simply download the drivers myself and telnet or ssh to the running nas and install the drivers? Thanks Link to comment Share on other sites More sharing options...
stifou Posted November 12, 2013 Share #89 Posted November 12, 2013 For people blocked at usb boot 'attached scsi removable disk' try to : 1) unplug ethernet and re-plug it. 'eth0 down, eth0 up' will be displayed 2) Your server should appear in the network by using your computer with synology assistant. 3) follow instructions. Look like 'Booting Kernel' message is not mandatory to detect and install xopenology. This is the first beta for build v1.2a - Add USB to serial FTDI and Prolific chips - Update igb driver for intel I340/I350 support - Update e1000e, r8168 network driver - Add ASIX AX88179 USB 3.0 Gigabit Ethernet driver - Add patched r8169 driver (removed r8168 support from it to prevent conflict) - Add firmware for r8169 (realtek) and tigon3 (broadcom) drivers - Built-in mp2sas and megaraid_sas drivers (instead of modules) - Add lot of virtualization options (hyper-v, vmware, virtio, xen, paravirtualization guest... vbox modules in the next beta) Link : http://xpenology.trantor.be/xpenology-trantor-v1.2a_beta1.7z As usual write img file to your usb stick andcopy modules files (*.ko) in /lib/modules/ Sorry I don't have enought time to repack a full build (pat + synoboot) neither to test it properly... I'm counting on you guys I hope adding firmware will finally fix the support of "strange" r8169 chip and broadcom BCM57788 chip Thank you very much. i try right now Edit : block at setup : attached scsi removable disk Link to comment Share on other sites More sharing options...
dsmatom Posted November 12, 2013 Share #90 Posted November 12, 2013 Hi Guys, just a follow up from my last post. Apologies for my noobness!!! i compiled the rocketraid 2340 open source driver. Created a rr2340.ko module file. When i do inmod /lib/modules/rr2340.ko i get error cannot insert module. Am i correct to assume this error is because i compiled the module using a 2.6.xx kernel, and am trying to add the module to xpenology which is running 3.2.xx kernel??? The driver on the highpoint website as linked in my previous post would not compile using a 3.2.xx kernel. Is there anything that i can do? Can you convert a module compiled with kernel 2.6 to one that is compatible with kernel 3.2? Or does the driver code need to be updated so that it can be compiled using a 3.2 environment?? Or should I just buy a newer card as the 1.2 repack supports the 3xxx and 4xxx series of rocketraid cards? Thank and any help appreciated. Link to comment Share on other sites More sharing options...
Trantor Posted November 13, 2013 Author Share #91 Posted November 13, 2013 The driver on the highpoint website as linked in my previous post would not compile using a 3.2.xx kernel. Is there anything that i can do? /quote] Indeed the sources provided on highpoint website are not compatible with 3.x kernel. But I found some guys who created a patch to get sources to compil on 3.2 kernel : http://ubuntuforums.org/showthread.php?t=1967800 Sorry no time to test it. Link to comment Share on other sites More sharing options...
xrecar Posted November 14, 2013 Share #92 Posted November 14, 2013 DSM 4.2-3202. Any way to fix the reported RAM reported under info via drivers? - 3072 megs vs 16 gigs installed. I'm nervous to upgrade to the new build as I have quite a bit on my volume 6x3 TB - do you think a migration would work? The last 3211 I tried only saw 5 drives. Thanks for your hard work. *sorry , meant to include I'm running on Asus c60m1-i. Link to comment Share on other sites More sharing options...
dsmatom Posted November 15, 2013 Share #93 Posted November 15, 2013 Indeed the sources provided on highpoint website are not compatible with 3.x kernel. But I found some guys who created a patch to get sources to compil on 3.2 kernel : http://ubuntuforums.org/showthread.php?t=1967800 Sorry no time to test it. Hi Trantor, thanks for the info. Unfortunately i'm at the end of my linux knowledge. I compiled kernel 3.2.30 and used this to patch the rocketraid 2340 drivers so that they would compile in 3.2.30. I did compile the drivers with one warning, but it still created the rr2340.ko file. I put the rr2340.ko in /lib/modules on the xpenology. i tried insmod /lib/modules/rr2340.ko and still geting "can't insert ...invalid module format" I also added rr2340 in /etc/rc and then did dmesg. dmesg gives rr2340: version magic '3.2.30 SMP mod_unload modversions 'should be '3.2.30 SMP mod_unload' any help appreciated Do i need to set something when i'm compiling the 3.2.30 kernel to change the version magic so that it matches what xpenology expects? Obviously i'm missing something here!!! Link to comment Share on other sites More sharing options...
postdeals Posted November 16, 2013 Share #94 Posted November 16, 2013 This latest Beta ESXi build can fully install Xpenology, but it fails to detect any of my ASM1602 SATA controllers. Where can i get Use .pat from beta 2a ? Link to comment Share on other sites More sharing options...
wenlez Posted November 18, 2013 Share #95 Posted November 18, 2013 This latest Beta ESXi build can fully install Xpenology, but it fails to detect any of my ASM1602 SATA controllers. Where can i get Use .pat from beta 2a ? It was in this thread, page 7. here is the link: http://xpenology.trantor.be/beta/ Please report your finding. Link to comment Share on other sites More sharing options...
T-REX-XP Posted November 18, 2013 Share #96 Posted November 18, 2013 Hi All! Please add cdc-acm driver support for new build. or compile this module. Hardware http://www.coderforlife.com/projects/lcd/ dmesg [487730.857043] usb 4-5: new full-speed USB device number 6 using ohci_hcd [487731.020391] Got empty serial number. Generate serial number from product. thanks. Link to comment Share on other sites More sharing options...
htpcdude Posted November 19, 2013 Share #97 Posted November 19, 2013 Hi, Can someone add the driver for a Sil3132 SATALink Controller? http://www.sonnettech.com/support/kb/kb ... tion=a3#a3 I am trying to get this working on a laptop via an expresscard 34 adapter to an external exclosure requiring an FIS-based port multiplier. I have tried both XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2) and XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0). Only one of the SATA drives in the enclosure is recognized. This same hardware setup works if the OS is Windows (7, Server 2008 & 2012) or Ubuntu 12.04 Or, can someone recommend an expresscard 34 eSATA adapter that is FIS-based port multiplier compatible that works with xpenology? Thanks, Link to comment Share on other sites More sharing options...
tangal98 Posted November 19, 2013 Share #98 Posted November 19, 2013 Excellent project! If possible, please add driver for ITE 8212F raid controller. Driver can be found here http://www.ite.com.tw/EN/products_more. ... =3&ID=5,91 Thanks! Link to comment Share on other sites More sharing options...
benuk Posted November 19, 2013 Share #99 Posted November 19, 2013 Hi Trantor, can you add driver for TV Card Terratec Cinergy S2 PCI HD? It's the mantis driver from v4l. Is this possible? thx, benuk Link to comment Share on other sites More sharing options...
pumbaster Posted November 19, 2013 Share #100 Posted November 19, 2013 Hi Trantor! Thanks for the 4.3 release I've been waiting for so long! Could you please add Wireless Realtek driver (Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter) to the next release? I need it to enable wifi on my nettop. Just in case, it has worked fine with DSM 4.2 release. The driver is available at the Realtek page. Link to comment Share on other sites More sharing options...
Recommended Posts