asgaroth

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About asgaroth

  • Rank
    Junior Member
  1. asgaroth

    [SOLVED] Only 2 cores are recognised!

    I'd be interested in this too, does DSM actually use all the cpu's and not just the hard coded 2 limit imposed. I'm currently running Jun's mod v1.01 with DSM 6.0.2 and 2 cpu's passed through via ESXi 6.5. So far its running nicely, but I'd like to bump up the cpu count (only if it will use it). On a side note, is there a restriction on the amount of memory DSM can use? Cheers Asgaroth
  2. asgaroth

    DSM 6.1.x Loader

    Cheers, that worked a treat
  3. asgaroth

    DSM 6.1.x Loader

    Thanks, I'll give it a go.
  4. asgaroth

    DSM 6.1.x Loader

    Hi All, Quick question, is there a vmware tools package for this edition of xpenology? I tried to search this thread for a couple keywords and I didn't see any hits, so I thought I'd ask. Any suggestions appreciated. Cheers Asgaroth
  5. asgaroth

    XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

    This is a re-post from the DSM loader thread, thought I'd put it here too. Hi All, Thank you to all the contributors for the new boot loader. I've just tried the vmware edition and so far so good. The only issue I have thus far in my testing is the ability to detect my HighPoint RocketRAID 2720SGL controller which has all my disks attached. @Trantor was kind enought to build the driver for me for the XPEnology 5.5 bootloader. The link to the post for this one is here. I tried to manually load that module in this version, but it complains of an invalid file format, so I'm guessing it will need to be recompiled for this newer version of DSM. Would it be possible for someone to compile the RocketRAID 2720SGL driver for this version please. The direct link for the source code of the driver can be located here, if you would like to view the download page for different linux versions, then see here. I'd appreciate the any assistance. Thanks
  6. asgaroth

    DSM Loader - Support Requests

    This is a re-post from the DSM loader thread, thought I'd put it here too. Hi All, Thank you to all the contributors for the new boot loader. I've just tried the vmware edition and so far so good. The only issue I have thus far in my testing is the ability to detect my HighPoint RocketRAID 2720SGL controller which has all my disks attached. @Trantor was kind enought to build the driver for me for the XPEnology 5.5 bootloader. The link to the post for this one is here. I tried to manually load that module in this version, but it complains of an invalid file format, so I'm guessing it will need to be recompiled for this newer version of DSM. Would it be possible for someone to compile the RocketRAID 2720SGL driver for this version please. The direct link for the source code of the driver can be located here, if you would like to view the download page for different linux versions, then see here. I'd appreciate the any assistance. Thanks
  7. asgaroth

    DSM 6.1.x Loader

    Hi All, Thank you to all the contributors for the new boot loader. I've just tried the vmware edition and so far so good. The only issue I have thus far in my testing is the ability to detect my HighPoint RocketRAID 2720SGL controller which has all my disks attached. @Trantor was kind enought to build the driver for me for the XPEnology 5.5 bootloader. The link to the post for this one is here. I tried to manually load that module in this version, but it complains of an invalid file format, so I'm guessing it will need to be recompiled for this newer version of DSM. Would it be possible for someone to compile the RocketRAID 2720SGL driver for this version please. The direct link for the source code of the driver can be located here, if you would like to view the download page for different linux versions, then see here. I'd appreciate the any assistance. Thanks
  8. asgaroth

    Drivers requests for DSM 5.2

    I think it must be enabled in the kernel as I can see my ethernet adapters using MSI: 74: 3 65667835 PCI-MSI-edge eth0-rxtx-0 75: 91704218 1 PCI-MSI-edge eth0-rxtx-1 76: 5 3 PCI-MSI-edge eth0-event-2 I wonder, does the driver have a compile time option for MSI/MSI-X?
  9. asgaroth

    Drivers requests for DSM 5.2

    @Trantor Doing big file transfers to the rocketraid device results in high cpu usage (roughly 60%) of which 50 - 55% is spent in system time, it looks like it is high interrupt usage, but I cannot confirm it (i usually confirm using mpstat or some such monitoring tool), I checked /proc/interrupts and i see very high interrupt usage for this card. I'm pretty sure this card is msi/msi-x capable but i cannot do a modinfo on the kernel module to see if there is a module parameter to toggle to enable it. It looks like it is using "legacy" interrupt mode :/
  10. asgaroth

    Drivers requests for DSM 5.2

    I totally agree with your way to load the driver. Much proper than mine In the bootloader. Inside zImage there are the kernel (bzImage) and the ramdrive (rd.gz). Unfortunately the ramdrive is packed inside the kernel, so it's very difficult to edit it. This prevent us to edit/update the ramdrive but also "protect" it from the outside world. It would be nice if dev team can update the release with the last change on this thread like usb lan adapter, rocketraid, missing dependency for ixgbe... The real question is : does your rocketraid adapter works with this driver ? OK thanks for the info on where the drivers are stored, I guess it does make sense that it would be in the bootloader's kernel image So far the card works, I've just created a disk group on those 3 drivers, and I'll create some iscsi lun's and share them out, from there I'll do some testing on my local workstation using the issci luns as a filesystem to create and test some virtual machines, that should give the card a bit of a workout.
  11. asgaroth

    Drivers requests for DSM 5.2

    Hi, thanks for the tip, I added the following snippet: if [ -f /lib/modules/rr272x_1x.ko ]; then KERNEL_MODULES="${KERNEL_MODULES} rr272x_1x" fi Just after the following snippet: if [ -f /lib/modules/btrfs.ko ]; then KERNEL_MODULES="${KERNEL_MODULES} btrfs" fi in the following 2 files: /etc/rc /etc.defaults/rc And I can see the system now loading up the driver. I dont see it on the boot screen where XPEnoboot mentions ":: Loading module ", would be nice to get it to loadup nicely like the rest of them, I cant seem to find the list of modules where it is loading these modules, it does seem to call SYNOLoadModules, but where is it getting the list of scsi hba modules to load from?
  12. asgaroth

    Drivers requests for DSM 5.2

    Hi, thanks for the update, I tried to add the rmmod/insmod parameters to isolinux.cfg, I can see that the mvsas modules is not loaded, but for the rocketraid driver it does not seem to load on bootup. I have tried the following 2 parameters in isolinux.cfg: DiskStation> cat /proc/cmdline BOOT_IMAGE=/zImage root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=mvsas insmod=/lib/modules/rr272x_1x.ko DiskStation> cat /proc/cmdline BOOT_IMAGE=/zImage root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=mvsas insmod=rr272x_1x The above two isolinux commands do not load the rocketraid driver on bootup, but they do remove the mvsas module from loading. However, if I try to load the module from the commandline after dsm has booted, this one fails: DiskStation> insmod rr272x_1x insmod: can't insert 'rr272x_1x': No such file or directory And this one works: insmod /lib/modules/rr272x_1x.ko It presents me with the following dmesg output: [ 230.999537] rr272x_1x:RocketRAID 272x_1x controller driver v1.5.18 [ 231.179881] rr272x_1x:adapter at PCI 27:0:0, IRQ 17 [ 234.749464] rr272x_1x:Attached device index 40 (Path 04 | Target 00 | E0/Sff) 00000000 [ 234.815045] rr272x_1x:Attached device index 41 (Path 05 | Target 00 | E0/Sff) 00000000 [ 234.904635] rr272x_1x:Attached device index 42 (Path 06 | Target 00 | E0/Sff) 00000000 [ 234.976063] scsi4 : rr272x_1x [ 234.979838] scsi 4:0:0:0: Direct-Access WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5 [ 234.980034] sd 4:0:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 234.980035] sd 4:0:0:0: Attached scsi generic sg7 type 0 [ 234.980044] sd 4:0:0:0: [sdi] Write Protect is off [ 234.980046] sd 4:0:0:0: [sdi] Mode Sense: 2f 00 00 00 [ 234.980057] sd 4:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 234.983680] scsi 4:0:1:0: Direct-Access WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5 [ 234.983766] sd 4:0:1:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 234.983773] sd 4:0:1:0: [sdj] Write Protect is off [ 234.983775] sd 4:0:1:0: [sdj] Mode Sense: 2f 00 00 00 [ 234.983779] sd 4:0:1:0: [sdj] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 234.984057] sd 4:0:1:0: Attached scsi generic sg8 type 0 [ 234.984703] scsi 4:0:2:0: Direct-Access WDC WD20EZRX-00D 80.0 PQ: 0 ANSI: 5 [ 234.984923] sd 4:0:2:0: Attached scsi generic sg9 type 0 [ 234.986096] sd 4:0:2:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 234.986104] sd 4:0:2:0: [sdk] Write Protect is off [ 234.986105] sd 4:0:2:0: [sdk] Mode Sense: 2f 00 00 00 [ 234.986110] sd 4:0:2:0: [sdk] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 234.990428] sdi: sdi1 sdi2 sdi3 < sdi5 > [ 234.990616] sd 4:0:0:0: [sdi] Attached SCSI disk [ 234.995309] sdj: sdj1 sdj2 sdj3 < sdj5 > [ 234.995480] sd 4:0:1:0: [sdj] Attached SCSI disk [ 235.013347] sdk: sdk1 sdk2 sdk3 < sdk5 > [ 235.013638] sd 4:0:2:0: [sdk] Attached SCSI disk Which looks alot better than the mvsas output. If you could suggest another way for me to load it up, or am i missing something with the insmod kernel parameter in isolinux. Do you not need to run depmod under DSM to build the module dependancies and symbols? Any tips would be appreciated.
  13. asgaroth

    Drivers requests for DSM 5.2

    Hi Trantor, Thank you for building those drivers, I will definately give them a go. I logged into my nas box and I cannot find a syslinux.cfg file anywhere on the system. I currently use the 5.2-5592.2 boot iso image to boot up my system, I mounted that iso up on a linux box and that doesnt have a syslinux.cfg file in it either. Where does the syslinux.cfg file reside within the DSM environment?
  14. asgaroth

    Drivers requests for DSM 5.2

    Just an update, I upgraded to XPEnoboot 5.2.5592.2 and it appears there is a highpoint driver for the 3xxx/4xxx range of cards, also, it looks like the mvsas driver is a newer version to XPEnoboot 5.2.5565.2. After updating to the newer version, mvsas detected my disks again and the disk groups/volumes are currently being checked. This one looks a little more promising but it is early days yet, I'll keep an eye on it and provide feedback if anything dodgy comes around. PS: I still see errors in the dmesg output for the mvsas driver and the RR 2720SGL, I'm not sure what it is trying to do, I know the card is working properly. DiskStation> dmesg | grep sas [ 1.490896] mpt2sas version 14.100.00.00 loaded [ 1.809304] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013 [ 1.828248] mvsas 0000:1b:00.0: mvsas: driver version 0.8.16 [ 1.828611] mvsas 0000:1b:00.0: mvsas: PCI-E x32, Bandwidth Usage: 5.0 Gbps [ 8.358801] scsi2 : mvsas [ 8.364299] sas: phy-2:4 added to port-2:0, phy_mask:0x1 ( 400000000000000) [ 8.364710] sas: phy-2:5 added to port-2:1, phy_mask:0x2 ( 500000000000000) [ 8.365030] sas: phy-2:6 added to port-2:2, phy_mask:0x4 ( 600000000000000) [ 8.365038] sas: DOING DISCOVERY on port 0, pid:19 [ 8.365040] sas: DONE DISCOVERY on port 0, pid:19, result:0 [ 8.365044] sas: DOING DISCOVERY on port 1, pid:19 [ 8.365045] sas: DONE DISCOVERY on port 1, pid:19, result:0 [ 8.365049] sas: DOING DISCOVERY on port 2, pid:19 [ 8.365050] sas: DONE DISCOVERY on port 2, pid:19, result:0 [ 8.365054] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 8.365057] sas: ata3: end_device-2:0: dev error handler [ 8.523443] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 8.547698] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 8.547713] sas: ata3: end_device-2:0: dev error handler [ 8.547720] sas: ata4: end_device-2:1: dev error handler [ 8.707088] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 8.756611] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 8.756649] sas: ata3: end_device-2:0: dev error handler [ 8.756656] sas: ata4: end_device-2:1: dev error handler [ 8.756659] sas: ata5: end_device-2:2: dev error handler [ 8.908351] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 23.318640] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 23.318656] sas: ata3: end_device-2:0: dev error handler [ 23.318660] sas: ata4: end_device-2:1: dev error handler [ 23.318665] sas: ata5: end_device-2:2: dev error handler [ 23.327565] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 23.340243] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 23.340253] sas: ata3: end_device-2:0: dev error handler [ 23.340259] sas: ata4: end_device-2:1: dev error handler [ 23.340264] sas: ata5: end_device-2:2: dev error handler [ 23.348851] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 23.348983] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 23.348992] sas: ata3: end_device-2:0: dev error handler [ 23.348995] sas: ata4: end_device-2:1: dev error handler [ 23.348997] sas: ata5: end_device-2:2: dev error handler [ 23.350839] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 25.459590] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 25.459602] sas: ata3: end_device-2:0: dev error handler [ 25.460405] sas: ata4: end_device-2:1: dev error handler [ 25.460410] sas: ata5: end_device-2:2: dev error handler [ 25.467232] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 25.595346] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 25.595354] sas: ata3: end_device-2:0: dev error handler [ 25.595359] sas: ata4: end_device-2:1: dev error handler [ 25.595365] sas: ata5: end_device-2:2: dev error handler [ 25.604049] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 25.685466] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 25.685474] sas: ata3: end_device-2:0: dev error handler [ 25.685480] sas: ata4: end_device-2:1: dev error handler [ 25.685482] sas: ata5: end_device-2:2: dev error handler [ 25.686848] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
  15. asgaroth

    Drivers requests for DSM 5.2

    I just want to say that there is a driver in the current XPEnoboot called mvsas which does seem to work ok with this card. Normally we want a rr27x0_XX.ko driver as the mvsas has had trouble with losing communication with drives in the past. I am uncertain if this problem still exists. I have the RocketRAID 2720SGL card attached and the problem does still exist, I have rebooted several times today and my data volume that are on the disks attached to 2720 just will not come back. It's currently hit & miss with the mvsas driver and the RR 2720SGL. I'd be a very happy man if the drivers for this adapter would be included in the next (or a future) release of XPEnoboot. If I knew the procedure of how to compile the driver for XPEnoboot, I would give it a go myself, but I cannot seem to find any examples of how to compile drivers for XPENoboot. Just as an FYI, on my last boot, this is the error messages I get from mvsas driver: [ 74.663814] sas: Enter sas_scsi_recover_host busy: 14 failed: 14 [ 74.663818] sas: sas_scsi_find_task: aborting task 0xffff880135c06e40 [ 74.663820] sas: sas_scsi_find_task: task 0xffff880135c06e40 is aborted [ 74.663822] sas: sas_scsi_find_task: aborting task 0xffff8801360ae080 [ 74.663823] sas: sas_scsi_find_task: task 0xffff8801360ae080 is aborted [ 74.663825] sas: sas_scsi_find_task: aborting task 0xffff880135e92200 [ 74.663826] sas: sas_scsi_find_task: task 0xffff880135e92200 is aborted [ 74.663828] sas: sas_scsi_find_task: aborting task 0xffff8801360a1bc0 [ 74.663829] sas: sas_scsi_find_task: task 0xffff8801360a1bc0 is aborted [ 74.663830] sas: sas_scsi_find_task: aborting task 0xffff880135c06440 [ 74.663831] sas: sas_scsi_find_task: task 0xffff880135c06440 is aborted [ 74.663833] sas: sas_scsi_find_task: aborting task 0xffff880135e92e80 [ 74.663834] sas: sas_scsi_find_task: task 0xffff880135e92e80 is aborted [ 74.663836] sas: sas_scsi_find_task: aborting task 0xffff880135c06bc0 [ 74.663837] sas: sas_scsi_find_task: task 0xffff880135c06bc0 is aborted [ 74.663838] sas: sas_scsi_find_task: aborting task 0xffff8801360a1080 [ 74.663839] sas: sas_scsi_find_task: task 0xffff8801360a1080 is aborted [ 74.663841] sas: sas_scsi_find_task: aborting task 0xffff8801360ae1c0 [ 74.663842] sas: sas_scsi_find_task: task 0xffff8801360ae1c0 is aborted [ 74.663844] sas: sas_scsi_find_task: aborting task 0xffff880135e92ac0 [ 74.663844] sas: sas_scsi_find_task: task 0xffff880135e92ac0 is aborted [ 74.663846] sas: sas_scsi_find_task: aborting task 0xffff880135f57e40 [ 74.663847] sas: sas_scsi_find_task: task 0xffff880135f57e40 is aborted [ 74.663848] sas: sas_scsi_find_task: aborting task 0xffff880136552840 [ 74.663849] sas: sas_scsi_find_task: task 0xffff880136552840 is aborted [ 74.663851] sas: sas_scsi_find_task: aborting task 0xffff880136552e80 [ 74.663852] sas: sas_scsi_find_task: task 0xffff880136552e80 is aborted [ 74.663853] sas: sas_scsi_find_task: aborting task 0xffff880135e92700 [ 74.663854] sas: sas_scsi_find_task: task 0xffff880135e92700 is aborted [ 76.873927] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 76.873929] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 76.883901] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 76.883902] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[3]:rc= 0 [ 76.893886] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 76.893892] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 76.903882] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 84.230665] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 84.230673] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 84.240650] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 84.240653] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[3]:rc= 0 [ 84.250638] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 84.250644] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 84.260631] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 96.583179] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 96.584177] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 96.593158] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[3]:rc= 0 [ 96.594152] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 96.603152] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 96.604152] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 96.613142] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 128.918700] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 128.919727] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 128.928682] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[3]:rc= 0 [ 128.929690] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 128.938680] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[0]:rc= 0 [ 128.939681] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[1]:rc= 0 [ 128.948665] drivers/scsi/mvsas/mv_sas.c 1524:mvs_I_T_nexus_reset for device[2]:rc= 0 [ 129.099576] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1