pigr8

Members
  • Content Count

    104
  • Joined

  • Last visited

  • Days Won

    2

pigr8 last won the day on February 9 2018

pigr8 had the most liked content!

Community Reputation

20 Excellent

About pigr8

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. yeah exactly what happens to everyone trying passthrough me included, it *should* work since the flag support sas can be enabled but dsm refuses to use them. shouldn't be a dsm problem, for sure something redpill related. btw in esxi how do you use the loader? mounted in sata0 controller? i tried multiple times but using the sata mode in grub loads everything but no /dev/synoboot* is created :S wierd.
  2. it's a common LSI 9211-8i (actually a Dell Perc H200 crossflashed to LSI and in IT mode), enabling the supportsas flag loads mpt2sas at boot correctly and drivers attached show up but not in the guy, so DSM wont use them as data disk (shows no disks attached). i'm not the only one facing this problem, as i wrote with jun's loader the drivers show up as /dev/sdX but with redpill they show up as /dev/sasN, DSM should work with them natively without anyway?
  3. i dont think it's a kernel issue related to the jump to 7.0, i think it's something related to the loader that does not do some kind of conversion like jun's did.. i tried to compile and boot redpill 6.2.4 (i'm now with jun's 6.2.3) and the /dev/sas* problem is there. won't work i'm afraid, sas devices have a different names for driver numbers, sata use /dev/sdA /dev/sdB /dev/sdX and so on while sas use /dev/sas1 /dev/sas2, even if the prefix is changed kernel side i don't think it would work.
  4. yeah pretty much same setup, 7 disk on the HBA detected as sas, i can confirm this.
  5. with the copy string does not compile because no mpt2sas.ko is in redpill custom folder, but it's unnecessary since the supportsas yes brings the HBA card up even on first boot, that's good. fdisk -l shows the disks but the gui still refuses to use them, meh.
  6. is it possible somehow to load mpt2sas during the first boot install? the module is there and with insmod it loads the LSI controller DiskStation> cd /usr/lib/modules/ DiskStation> insmod mpt2sas.ko [ 30.427812] mpt2sas version 20.00.00.00 loaded [ 30.429216] scsi0 : Fusion MPT SAS Host [ 30.431514] I/O scheduler elevator not found [ 30.434368] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4022016 kB) [ 30.509820] mpt2sas0: MSI-X vectors supported: 1, no of cores: 4, max_msix_vectors: -1 [ 30.512751] mpt2sas 0000:13:00.0: irq 73 for MSI/MSI-X [ 30
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615XS - Using custom extra.lzma: NO - Installation type: VM - HP Microserver Gen8 - ESXI 7.0U1b 17168206 - LSI 9211-8i passthrough with 5x hdd shr1 and 1x ssd (SMART and TRIM working) - Additional comment: Updated directly from the WebUI in DSM, reboot required.
  8. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615XS - Using custom extra.lzma: NO - Installation type: VM - HP Microserver Gen8 - ESXI 7.0 Build 15843807 - LSI 9211-8i passthrough with 5x hdd shr1 and 1x ssd (SMART and TRIM working) - Additional comment: Updated directly from the WebUI in DSM, reboot required.
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-update 6 - Loader version and model: JUN'S LOADER v1.03b - DS3615XS - Using custom extra.lzma: NO - Installation type: VM - ESXI 7.0 Build 15843807 - LSI 9211-8i passthrough with 5x hdd shr1 and 1x ssd (SMART and TRIM working) - Additional comment: Used FixSynoboot from flyride. Updated directly from the WebUI in DSM, reboot required.
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 6 - Loader version and model: Jun's loader v1.03b, DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 U2 13473784 on Microserver Gen8 - Additional comments: Dell H200 @LSI Controller in passthrough, NIC set to e1000e.
  11. qbittorrent or eventually transmission
  12. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 4 - Loader version and model: Jun's Loader v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5U2 on Microserver Gen8 - Additional comments: Cougar Point 6 port SATA AHCI Controller in passthrough, NIC set to e1000e. No Reboot Required
  13. Perfect, which bootload are you using? 3615 or 3617?
  14. ok don't know why, i tried 2 vm, my production vm, 2 baremetal and they all worked fine, all based on ds3615xs. maybe it's that, nevermind then! i used docker in the past, i just prefer a standalone spk