ozool

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ozool

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Did you manage to get this working?
  2. Hi, I'm trying to switch from a Highpoint SGL2720SGL to an LSI 9207-8i. The system is running correctly on ESXi 6.7 with the Highpoint card but seems to crash when I switch to the 9207-8i. The 9207-8i works perfectly when passed through to a Windows VM, but nothing shows up in Synology Assistant when passed to the Xpenology VM. I'm using loader 1.03a2 with DS918+ and I have synoboot on SATA0:0 with a second virtual disk on SATA1:0. Can anyone help? Pasting my serial port output below. Thanks. patching file etc/rc patching file etc/syn
  3. My ESXi-based Xpenology system (DSM 6.2-23739 1.03a2) is now showing Disk1 as 'Crashed'. Disk1 is actually a vmdk file hosted on ESXi which seems to be healthy. Clicking the 'Health Info' button returns 'Access Error. An Error occurred when accessing this drive...' Is there any way to restore access to the disk in DSM?
  4. My ESXi-based Xpenology system (DSM 6.2-23739 1.03a2) is now showing Disk1 as 'Crashed'. Disk1 is actually a vmdk file hosted on ESXi which seems to be healthy. Clicking the 'Health Info' button returns 'Access Error. An Error occurred when accessing this drive...' Is there any way to restore access to the disk in DSM?
  5. Hello again IG-88, This has been working fine for me with four disks attached to the first mini-SAS port on the controller, however, when I add a disk to the second mini-SAS port it seems to occupy the same HDD slot in DSM as one of the four on the first port. i.e. DSM can't see all 8 ports as individual drives. My card is a Highpoint 2722 SGL with 2x internal mini-SAS ports for a maximum of 8 SATA ports. looking in my logs, I see the following: [ 10.448356] scsi host4: mvsas [ 10.449301] sas: phy-4:4 added to port-4:0, phy_mask:0x1 ( 400000000000000) [ 1
  6. Is a custom ramdisk for 3617xs or 3615x DSM 6.2 planned for the future or is the intention to support only the 918+ loader?
  7. That seems to have fixed it. My drives are now visible on the RocketRAID card.
  8. I Checked the log and I can see the mvsas driver has loaded. I'm not really sure what most of this means, but I'm seeing four instances of this type of error (I assume one for each of my four attached disks): [Fri Jul 27 12:30:46 2018] sas: DOING DISCOVERY on port 0, pid:6 [Fri Jul 27 12:30:46 2018] sas: ATA device seen but CONFIG_SCSI_SAS_ATA=N so cannot attach [Fri Jul 27 12:30:46 2018] sas: unhandled device 5 So it looks like something is preventing the drive from attaching. Thanks again for your help.
  9. Thanks! I now have all four NICs recognised and working. lspci -k | grep 'Kernel driver' reveals that mvsas is in use, but I still can't see my drives. Is this likely to be something to do with the sataportmap setting? Seeing as I'm running on ESXi, I'm not sure how to configure it or how to count the SATA controllers. I have two virtual disks attached (on SATA 0:0 and SATA 0:1). There are currently four drives attached to the RocketRAID card, but none are visible to DSM. Any suggestions?
  10. Hi, after a lot of Googling how to fix this, I ended up here. I couldn't find synoconfig.conf, but I did find synoinfo.conf which contained the same info. Unfortunately, after editing maxlanport="2" to maxlanport="8" I was still left with only two NICs visible from withing DSM. Can you offer any help? Am I editing the correct file? I'm running 1.03a2 on ESXi 6.7. It seems to be working well apart from not seeing my passed-through RocketRAID 2720SGL and the NIC issue above. Thanks.