Jump to content
XPEnology Community

DarkBlade

Transition Member
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

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

DarkBlade's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Thanks for this - I can vaguely recall doing this for my old DSM 6 install! I should have remembered really. All the drives are seen on the raid card now. However, it's still not seeing the drive on the virtual controller for some reason - but I've given up with that (too much time spent already). Alongside the new drives, it even sees the DSM 6 volume on the older drives from my old DSM server. With the dual 10Gbe NIC, this thing is FAST at moving large files!!! Especially onto another raid array on a backup server.
  2. Before building the loader I changed maxdisks from 16 to 32 (assuming 8 Intel + 24 Adaptec as reported by ./rploader.sh satamap) using the TinyCore GUI text editor. internalportcfg was left at the default "0xffff" Yet the resulting build appears to be limited to 16 disks? (so any disks over the 16 slots are ignored in DSM)
  3. I'm trying to get an Adaptec 72405 (24 port card) working on DS3622xs+ under Proxmox, with DSM installed on the (mirrored) Proxmox VM storage drive, but there is something odd happening. I've spent days trying to get this to work and really need some help! I can get a basic build working following the tutorial here https://www.wundertech.net/how-to-install-xpenology-on-proxmox-dsm-7/ This gets DSM running on the Proxmox storage drive. The next step (and where I am stuck) has been trying to create a build passing an Adaptec 72405 (24 port card set to HBA mode) through - with the DSM will still installing on the VM drive and the disks on the Adaptec card are then seen as additional storage (to create storage pools etc). Essentially the same process as above, but adding the Adaptec driver extension. (./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/aacraid/rpext-index.json ) When booting into DSM and running the Synology installer: The DSM installer format fails - but DSM does is install and is available on rebooting the VM. DSM fails to see the 20G VM disk The drives on the Adaptec card start from slot 3 Only 14 of the 15 drives I currently have installed are picked up (if I add extra drives they are not listed)* *I don't understand this as maxdisks was set to 32 in the user_config.json, so I was expecting to at least to see all the drives (just not necessarily in the right order). I suspect I need to provide some manual values for SataPortMap and DiskIdxMap (assuming these will work using the Adaptec card), but I'm guessing this needs to see all the drives to start with? I'm not sure why the Intel SATA controller is showing 8 Drives - my understanding is that this should only show the single 20gb Proxmox drive. Based on the satamap output below I've set Maxdisks to 32 (8 Intel + 24 Adaptec) At the point the DSM installer errors during formatting, fdisk (via ssh) shows the following: I think the 2048 GB lines here are the DSM created partitions. On reboot with DSM running, fdisk from ssh shows 15 drives (but not the 20gb virtual drive):
  4. Got the Intel NIC x540-t2 working by initially using a virtualised Intel e1000 NIC (no PCI passthrough of the x540 card at this point), running TinyCore and executing the following to get the base loader ready: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS3622xs+ ./rploader.sh build broadwellnk-7.1.0-42661 sudo poweroff Added Serial port (optional for debugging etc) Then ran the full DSM installation - then once completed... Shutdown DSM and the virtual machine. Removed the virtual Intel NIC (in Proxmox). Added the Intel X540 NIC via PCI passthrough. Started the VM. Both 10Gbe ports available in DSM (and visible in Synology Assistant).
  5. Got this working by initially using a virtualised Intel e1000 NIC, running TinyCore and executing the following to get the base loader ready: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS3622xs+ ./rploader.sh build broadwellnk-7.1.0-42661 sudo poweroff Then Ran the full DSM installation - then once completed... Shutdown the virtual machine. Removed the virtual Intel NIC (in Proxmox). Added the Mellanox NIC via PCI passthrough. Started the VM. Both 10Gbe ports available in DSM.
  6. I've tried a build adding a virtual NIC (Intel E1000) alongside the Mellanox card. This allowed installing of DSM, but on reboot, the DSM shuts down the VM. (I believe this might be caused by the DS3622xs+ build only allowing two NICs) I did manage to grab this from the serial output before it vanished off the screen.... So I tried removing the virtual NIC. This allowed the Redpill to boot to the SynologyNAS stage, but still no IP or eth0/eth1 assignment.
  7. I can get a basic build working following the tutorial here wundertech.net  how-to-install-xpenology-on-proxmox-dsm-7 This gets DSM running on the Proxmox storage drive. I'm now trying to rebuild (from scratch), passing an Adaptec 72405 (24 port card set to HBA mode) through - hoping that DSM will still install on the VM drive and the disks on the Adaptec card are then seen as additional storage (to create storage pools etc). I only need/want to use (the first) 20 ports on the card (the remaining 4 ports are not connected to any drives or backplane). When booting into Redpill and DSM: DSM fails to spot the 20G VM disk The drives on the Adaptec card start from slot 3 Only 14 of the 15 drives I currently have installed are picked up. My initial attempts at changing the SataPortMap, DiskIdxMap and MaxDisks values has resulted in no disks showing, or crashing the Adaptec card. (requiring a complete power down to recover on one occasion). I've had a few other issues which I think I have now resolved. My ask is: How can I get the build working using the VM sata1 drive? What values should I try for SataPortMap, DiskIdxMap and MaxDisks? This is the hardware setup in Proxmox This is the satamap output (I manually set maxdisks to 24 in user_config before running satamap)
  8. I've installed a Mellanox ConnectX-3 Pro MCX312B-XCCS Dual Port card in my Proxmox machine, but I'm having no luck with the card when running redpill with DS3622xs+ (which I need to use as I will be passing through a RAID card once I've got the Mellanox card working). I can see the 10Gbe card passed through into TinyCore, where I get two IP addresses for each NIC port. (No virtual NICs are setup in the Virtual Machine) I then execute the following commands: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS3622xs+ ./rploader.sh satamap now ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/jumkey/redpill-load/raw/develop/redpill-virtio/rpext-index.json ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json ./rploader.sh build broadwellnk-7.1.0-42661 But when running Redpill, it fails to allocate either eth0 or eth1 addresses. Is there a way to pause the serial output (there is no obvious error in the tail end of the output), or read the complete logs somewhere? Do I need to add an additional driver? (I assumed these cards were supported without needing drivers) (I've managed to get a build working using a Proxmox virtualised e1000 NIC)
  9. Nevermind - it uses the same Intel X540 10Gb Ethernet solution, so that's a no then
  10. Would you know if one of these would work? HP Ethernet 10Gb 2-port 561T Adapter
  11. I've managed to successfully create a basic DS3622xs+ test VM build in Proxmox and get DSM 7.1 up and running. I'm now trying to pass through an Intel x540-t2 (10gb) ethernet card. The NIC is visible in Tiny Core, but when running Redpill the build doesn't work and the VM is not picked up by finds.synology. I've tried adding to the existing test VM (removing the virtual NIC) and I've also tried building a new VM from scratch. Looking at the serial console, the following lines suggest an issue: The last displayed line on the console is: [ 6.227170] Fixing recursive fault but reboot is needed! Please help!
×
×
  • Create New...