Jump to content
XPEnology Community

jrac86

Member
  • Posts

    40
  • Joined

  • Last visited

Everything posted by jrac86

  1. Thanks everyone who helped me realize my mistake. I put the SataPortMap and DiskIdxMap in the correct place. I still get 2 dummy blank ports in the first 2 slots, but better than 12 of them lol. So there is no way to get rid of those dummy other than using i440fx instead of q35? Is there a performance hit using i440fx? I know I have to set my HBA card to not use pcie when using i440fx. I just have no idea what difference it makes.
  2. Now that I understand the sataport map and diskidxmap, I will give TRCP another shot.
  3. Here is my config. Anything look incorrect?
  4. Same result... Here is the output again with the VM using Virtio
  5. Think it was from when I was troubleshooting a few weeks ago. I will change it back to Virtio and see if that changes anything.
  6. Post a screenshot of your VM hardware settings
  7. Thank you for the explanation - I did look through many posts and never got as easy of an explanation like you provided. However, when I set the SataPortMap to 11H and DiskIdxMap to 181900, my disk shelf is still showing the first drives starting at 13... Being there are 6 ports on my motherboard and 6 dummy ports, I thought maybe changing the SataPortMap to 66H and DiskIdxMap to 181E00 would work, but same outcome. Any idea what I'm doing wrong here? I am using the DS3622xs build 42661.
  8. I realized, I just didn't understand why you chose the values you did for DiskIdxMap. Should I be setting mine to 060600 - skip the first 6 disks for the first two controllers and starts at 0 for my disk shelf?
  9. I also tried messing with sata_remap, but that didnt work either. Not sure if that is even supported here or I just did it incorrectly.
  10. I tried SataPortMap as 00H and 11H without specifying the DiskIdxMap... Both ways gave the same result.
  11. @pocopico Awesome, I used the SataPortMap as 11H and it seems to find all my disks. As @Orphée mentioned though, it see the dummy 6 port controller and my onboard 6 port controller, then the 24 disks from the disk shelf - this makes DSM start at disk 13 (since the first 12 are detected but not being used). If there any way to have DSM just skip over those first 2 controllers entirely as I will not be using them at all? Ideally would want the first disk in my disk shelf to be registered as Disk 1 in DSM.
  12. Can you explain this more? So in my case, I have the dummy 6 port controller, then the 6 port controller with the sata0 img disk, then my 24 disk HBA card... What would my SatPortMap and DiskIdxMap be for this situation?
  13. Awesome info! Ill be moving off the usb to a virtual disk then. I had to passthrough the HBA card bc proxmox has a limit of 6 passed through sata drives for a vm.
  14. I built mine on proxmox... I don't have a guide, but can try to assist. Doing most of this from memory since my DSM array is being built. I created a usb boot drive using balena etcher and the arpl .img file. For the VM, leave the machine as 1440fx (if you pick q35, it will create dummy controllers which for me was making the setup more complicated). I used the VirtIO for network and removed both the vm disk and cd drive. Also attach a serial socket - this will allow you to see the output during the DSM boot process and can report issues here with the output. Then I added the usb to the vm and set that as the boot drive. If you have a disk shelf then you will need to passthrough the HBA card (LSI 9200-8e is what I used). If you just have drives attached to our motherboard, you can passthrough the individual sata drives (proxmox only allows 6 sata drives to be passed through). If you are passing through a hba card, you need to follow the following guide: https://pve.proxmox.com/wiki/PCI(e)_Passthrough. The other thing to know, is that passing through hardware is done in groups (called iommu). For example, if your pcie slot is in the same iommu group as a usb controller, you will passthrough both to the vm. This may be a deal breaker depending on what hardware is in your iommu groups. The guide above explains this as well as this (it is for a gpu passthrough, but similar principles) https://www.reddit.com/r/Proxmox/comments/mib3u6/a_guide_to_how_i_got_nvidia_gpu_passthrough_to_a/ Once you do that, you can start the VM. You will need to go to the web gui with the ip and port 7681 (http://xx.xx.xx.xx:7681) and then follow the steps. I used the DS3622xs and the older build version, but you may need to try several (the DS2422 one did not work for me). Generate the serial, install the modules that are detected, and set the max disks to whatever value you need. Once you build and then boot the bootloader, you can then go to find.synology.com and it should detect the instance. Again, I'm doing this off memory, but without knowing your exact hardware or setup, can't really give any more useful devices. If you run into any issues, post here and we can try to assist further. Good luck!
  15. All working now. Thanks again for all the assistance!
  16. Donation sent! Will try a new usb port and report back
  17. @fbelavenuto Got the new HBA card and finally in DSM and detecting all disks! Seriously, is there any way to donate for this project? The only question I have left, is that I see this message over and over in the serial output once booted in DSM. I am guessing that it is detecting the USB that it's booting off of? Is this normal and can be ignored? And this keeps popping up in DSM:
  18. I am not sure if this was actually a problem with arpl.. My hba card died today and I am ordering a new one. Will test again once I get the new one in.
  19. Synology loads, but says no disks were found. When going to the add ons, the usual two that were loaded are no longer there (mpt3sas and the virtual ethernet) Here is the boot log:
  20. I am also having issues. DSM never loads. Boot log attached. Looks like add on issue. insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
  21. Ah okay. The card is an LSI9200 I believe. I am pretty sure they only are in IT mode as there is no built in RAID (I also erased the bootloader). Anything I can run to confirm this? Otherwise I'll just see how it goes once the new release is created. @fbelavenuto - thanks for your work again and your responsiveness... doing an awesome job!
  22. Same issue as @pigr8, disks not detected. Also, is there no longer a way to manually add addons through that menu? I used to add mptsas and megaraid_sas just ini case those were needed (no idea if they actually are though).
  23. I think you are correct, looks like it's setting it to the following. Adjust maxdisks and internalportcfg automatically maxdisks=2 internalportcfg=0x3 If I manually update the user_config.json to more disks and rebuild, DSM finds more disks (prompts to erase up to 16 drives) but then fails to install. Is this a bug or is something wrong with what I am doing and it's causing the script to only identify 2 of my disks when it initially runs? Here are the disks it can see: SynologyNAS> ls –la /sys/block ls: –la: No such file or directory /sys/block: md0 ram13 ram6 sdd sdk sdr synoboot md1 ram14 ram7 sde sdl sds ram0 ram15 ram8 sdf sdm sdt ram1 ram2 ram9 sdg sdn sdu ram10 ram3 sda sdh sdo sdv ram11 ram4 sdb sdi sdp sdw ram12 ram5 sdc sdj sdq sdx SynologyNAS> cat /proc/cmdline console=ttyS0,115200n8 earlycon=uart8250,io,0x3f8,115200n8 root=/dev/md0 syno_hw_version=DS3622xs+ netif_num=0 sn=2030SQRG8SKVQ HddHotplug=0 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 Here is the output when installing DSM:
×
×
  • Create New...