vegeta

Dell PERC H330 not recognized by XPenology

Recommended Posts

I have a Dell T330 with PERC H330 in HBA mode, but the XPenology VM doesn't recognize the disks in passthrough mode.

 

FreeNAS, Unraid and Linux VM's see the disks just fine, but XPenology doesn't.

  • Jun v1.0.2a2 bootloader
  • Flat Disk
  • HW Level 10
  • PVSCSI
  • VMXNET3
  • SataPortMap=8888

Any tips while debugging this? I'd really love to use XPenology and I've been using it for a while on a different machine with VMware virtual disks.

 

My configuration in VMware:

WtSWWyUh.png.jpeg

 

boot log  

 

[  628.210489] Restarting system.

                    GNU GRUB  version 2.02~beta2-36ubuntu3.9

 +----------------------------------------------------------------------------+
 | DS3617xs 6.1 Baremetal with Jun's Mod v1.02-alpha                          |
 | DS3617xs 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall                |
 |*DS3617xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha                        |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 |                                                                            |
 +----------------------------------------------------------------------------+

      Use the ^ and v keys to select which entry is highlighted.
      Press enter to boot the selected OS, `e' to edit the commands
      before booting or `c' for a command-line.
   The highlighted entry will be executed automatically in 0s.
[    2.004999] I/O scheduler elevator not found
patching file etc/passwd
patching file etc/rc
Hunk #1 succeeded at 170 (offset 7 lines).
patching file etc/synoinfo.conf
Hunk #1 succeeded at 280 (offset 4 lines).
patching file linuxrc.syno
Hunk #1 succeeded at 39 (offset 2 lines).
Hunk #2 succeeded at 118 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 451 (offset 67 lines).
patching file usr/sbin/init.post
START /linuxrc.syno
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ohci-hcd ... [  OK  ]
:: Loading module uhci-hcd ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading module BusLogic ... [  OK  ]
:: Loading module vmw_pvscsi[    2.103297] sd 1:0:0:0: [sda] Assuming drive cache: write through
[    2.105763] sd 1:0:0:0: [sda] Assuming drive cache: write through
[    2.112039] sd 1:0:0:0: [sda] Assuming drive cache: write through
 ... [  OK  ]
:: Loading module megaraid_mm ... [  OK  ]
:: Loading module megaraid_mbox ... [  OK  ]
:: Loading module megaraid ... [  OK  ]
:: Loading module scsi_transport_spi ... [  OK  ]
:: Loading module mptbase ... [  OK  ]
:: Loading module mptscsih ... [  OK  ]
:: Loading module mptspi ... [  OK  ]
:: Loading module mptsas ... [  OK  ]
:: Loading module mptctl ... [  OK  ]
:: Loading module ata_piix[    2.338844] ata2: Read current link speed fail, retry 1
[    2.344843] ata2: Read current link speed fail, retry 2
[    2.350841] ata2: Read current link speed fail, retry 3
[    2.366838] ata3: Read current link speed fail, retry 1
[    2.372837] ata3: Read current link speed fail, retry 2
[    2.378835] ata3: Read current link speed fail, retry 3
 ... [  OK  ]
:: Loading module megaraid_sas ... [  OK  ]
:: Loading module mpt2sas ... [  OK  ]
:: Loading module mpt3sas ... [  OK  ]
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
[    2.422175] md: invalid raid superblock magic on sda3
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...

       30776 inodes used (19.77%, out of 155648)
          18 non-contiguous files (0.1%)
           8 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 27992/3
      242418 blocks used (38.94%, out of 622544)
           0 bad blocks
           1 large file

       24512 regular files
        3183 directories
           2 character device files
           0 block device files
           0 fifos
        1229 links
        3070 symbolic links (2771 fast symbolic links)
           0 sockets
------------
       31996 files
/sbin/e2fsck returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
No upgrade file exists
End upgrade procedure
============upgrade
Wait 2 seconds for synology manufactory device
^[[BFri Aug 18 14:54:49 UTC 2017
/dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,size=2020704k,nr_inodes=505176,mode=755 0 0
proc /proc proc rw,relatime 0 0
linuxrc.syno executed successfully.
Post init

[    9.584467] BTRFS: has skinny extents

 

Hide  

 

Share this post


Link to post
Share on other sites

check one of the 'other' linux installs and see which sas/sata driver the board is using. should be an lsi sas 3008 (from the manual) might be that this chipset driver is not in the boot loader (I have the same problem with the mvsas driver which I'm researching) but also check out a post from @ig88 who has created a variant extra.lzma file that has some additional drivers added.

Share this post


Link to post
Share on other sites
5 hours ago, sbv3000 said:

check one of the 'other' linux installs and see which sas/sata driver the board is using. should be an lsi sas 3008 (from the manual) might be that this chipset driver is not in the boot loader (I have the same problem with the mvsas driver which I'm researching) but also check out a post from @ig88 who has created a variant extra.lzma file that has some additional drivers added.

I found a post about him writing about a custom extra.lzma, but not one with a custom extra.lzma.

 

Could you help me locate it?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now