Search the Community

Showing results for 'SataPortMap'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • GERMAN
    • KOREAN

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

  1. Moin, Ende letzten Jahres habe ich mir einen neuen NAS zusammengestellt. Die Hardware sieht wie folgt aus: Mainboard: Asus P9D-I REV 1.02 (SATA => 2x 6Gb/s blau, 2x 3Gb/s schwarz) CPU: Intel Xeon E3-1220v3 HBA: LSI IBM SAS9220-8i (geflasht zu 9211-8i, IT-Mode, FW ) RAM: 2 x 8GB Kingston PC3-12800 KVR16E11/8, UDIMM, EEC SSD: 1 x 500GB Kingston SA400S37480G HDD: 4 x 4TB Western Digital WD40EFRX-68N32N0
  2. Hello everyone, I need help, I'm already starting to go a little crazy ... I have the following configuration: Gigabyte GA-965P-DQ6 Marvell Yukon 88E8053 PCI-E Gigabit Ethernet (on motherboard) Dual Controller of the Realtek PCIe GbE family (8168F) Although I bought it supposedly to be 8111G or 8111H Intel Core 2 Duo E6400 - 2.13 GHz 4 GB RAM 6 SATA II ports 2 SATA II Gygabyte ports Only modifying USB VID and PID can I install DS3617xs without problems with jun's loader 1.03b When I try to install DS918 + with jun's loader 1.04b a
  3. Intro/Motivation This seems like hard-to-find information, so I thought I'd write up a quick tutorial. I'm running XPEnology as a VM under ESXi, now with a 24-bay Supermicro chassis. The Supermicro world has a lot of similar-but-different options. In particular, I'm running an E5-1225v3 Haswell CPU, with 32GB memory, on a X10SLM+-F motherboard in a 4U chassis using a BPN-SAS2-846EL1 backplane. This means all 24 drives are connected to a single LSI 9211-8i based HBA, flashed to IT mode. That should be enough Google-juice to find everything you need for a similar setup!
  4. my grub.cfg looks like this but i keep getting corrupted file when trying to update or reinstall. any help will be appreciated. #set extra_args_3617='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' set extra_args_3617='' set common_args_3617='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0'
  5. I have a NUC with mini PCIe ASM1061, but this card not reconized with all tested extra drivers version: I have only the 2 sata ports on motherboard, and set sata_args='SataPortMap=22' dosen't seem to work an idea ?
  6. This is an updated tutorial version from the one I made last year. It will enable you to migrate from DSM 5.2 to DSM 6.1.7 directly without the need to upgrade to DSM 6.0.2 first. If for some reason you want to upgrade to DSM 6.0.2 first or simply you do not want to upgrade to DSM 6.1.7 but only to DSM 6.0.2 then use the link above. To upgrade from DSM 6.0.2 to DSM 6.1.7 read here. As most of you know by now Jun was able to find a way to install DSM 6 on non Synology boxes. Here is the thread that I recommend reading. At least make an effort and read the OP: https://xpenology.
  7. Here is your issue. You have your boot loader set to slot 2 when the tutorials indicate that it must be SATA (0:0). Because your SataPortMap=1 that means the first controller (SATA 0) is only mapped for one drive, so this device is not assigned a /dev/sd slot. Therefore, the loader and script cannot find the device to remap for the synoboot devices. Change this to SATA (0:0) and you should find your upgrade works properly.
  8. set extra_initrd="extra.lzma" set info="info.txt" set vid=0x058f set pid=0x6387 set sn=_________ set mac1=001B2177AE6D set rootdev=/dev/md0 set netif_num=1 set extra_args_3615='' #set extra_args_3615='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' set default='0' set timeout='1' set fallback='1'
  9. Hallo Lexizilla Stehe vor einem ähnlichen Problem. Habe mich auch entschieden die HDD Anbindung nur mit SATA Controller zu machen. Aktuell sieht das Setting so aus 8 SATA Anschlüsse auf dem Mainboard und 8 auf einem externen SATA Kontroller. (PCIe) Jetzt ist es so das die ersten 4 HDD richtig erkannt werden nachdem ich die Reihenfolge der SATA Anschlüsse auf dem Mainboard herausgefunden habe. Verwende ich jedoch z.B. den Anschluss Nr. 1 oder 2 auf dem Mainboard dann wird mir keine Platte angezeigt. Das wäre auch nicht weiter schlimm da auf dem zusätzliche
  10. I think I found the error looking through the dmesg log. These appear to be the default commands that were probably loaded with the grub file embedded with the synoboot.img loader. It seems to make sense that it is passing through all these sata devices I'm not using because all my drives are on the LSI controller. How do I modify that startup config to run a SataPortMap=111 or SataPortMap=222 so that I can make the space available for that one remaining drive without modifying the same code to increase the max drives as that is unnecessary IMO. I have only done baremetal x
  11. I know it doesn't make sense, but it is how it is. Installation: baremetal on Intel Celeron G1820 on an Asrock H81M-DG4 motherboard with 4 GB DDR3 RAM. Two Seagate HDDs, 160GB and one IronWolf Pro 4TB. I flashed Jun's v1.03b Loader for DS3615xs on a 4 GB Kingston DataTraveler USB stick using Balena Etcher, but I could not find the DiskStation at all in the network. Jun's 1.04b Loader for DS918+ worked and the DiskStation was found, but I got an error which was solved by changing SataPortMap to 2 in the grub config. I proceeded to install DSM 6.2.3-25426 for DS918+
  12. I’ve searched around looking for an answer I’m not 100% sure if I fully understand but here we go. My mobo being a gigabyte b365 has 6 onboard sata. I’ve ordered 2x JMB585 cards, each have 5 sata ports. Would the proper value be =655 ? thanks
  13. But my mainboard is special,so the 2nd and 3rd SATA controller has only 4ports and 3ports(the 4th was bad) to DSM DISK 1-7.And the loader SSD is the minisata on mainboard at (0:1). I have 8 disks NAS,so I have to use the (0:0) SATA port to DSM DISK 8. I have did this: Keep my loader disk to position 0:1(it's the miniSATA port on my mainboard,so I can't move it.) SataPortMap=243 DiskIdxMap=070003(I'm using DS3617xs) now,the script is useful.and the loader is on DISK 9. In this situation,can I suppress the loader SSD? Or I have to use
  14. As I continue to parse your issue report, I think you are confusing disk "suppression" with disks actually being present. You said you set your loader to position 0:1 but if it is ESXi, it enumerates starting with position 0:0. SataPortMap=1 says there is only one device attached to the first controller, but your drive is in the second position so it is never mapped to a /dev/sdx device. SataPortMap=2 says there are two devices attached to the first controller, so the disk gets mapped to a device and then FixSynoBoot can work. You think you are suppress
  15. I have used a SSD as loader,and it's on the controller port(0:1). My NAS has 3 controllers,so I set DiskIdxMap=070003 SataPortMap=143. The SSD loader is suppressed. and I can seethe disk 1-8 in my DSM correct. but when I update the DSM,it's failed by file is broken. And I use,it doesn't work yet. I reboot it,and use ls /dev/syno*.there isn't synoboot yet.I have check the file mod,it's OK. Then I set DiskIdxMap=070003 SataPortMap=243. the loader is disk 9,the script is useful.So I think if loader is suppressed,the script is not applied.
  16. Just installed xpenology with dsm 6.1 (ds3615) with juns loader 1.02b on the PX6-300d (6 drive NAS). Pretty straight forward using this guide to boot from usb. GUIDE: Customer OS on PX6-300D 1) Had to plug the USB in the back usb port. 2) Entered the PID/VID/SN and mac1 and mac2 3) also required to enter: SataPortMap=6 After that it booted right up and installed DSM with the synology assistant. Working good so far with no issues and all 6 bays can be utilized.
  17. Before you begin to change something in your working system, it is strongly recommended to make backups of your most valuable data, so you do not regret about their irretrievable loss. Everything you do is your fear and risk, no one encourages you to do it. The easiest and most reliable way to safely try to do it, turn off all the disks and the boot flash drive from the current system, take a clean disk and another USB flash drive and try to install a new version of the bootloader and the system, if it rolled, then do already on the current system. 1. How to install (described for a
  18. that you have set in SATAPORTMAP, it tells me that there is no HDD
  19. Ce tuto est une mise à jour du tuto que j'ai déjà fait l'année dernière. Le tuto ci-dessous permet d'installer/migrer DSM 5.2 à DSM 6.1.7 directement sans devoir à passer par DSM 6.0.2. Si pour une raison ou une autre vous voulez migrer à DSM 6.0.2 d'abord ou alors tout simplement vous ne voulait pas migrer à DSM 6.1.7 mais souhaiter migrer à DSM 6.0.2 uniquement alors utilisez le lien ci dessus. Pour mettre à jour DSM 6.0.2 à DSM 6.1.7 voir ici. Comme la plupart de vous doivent déjà le savoir Jun a réussi un exploit en créant un loader permettant l'installation de DSM 6 sur d
  20. ***For experienced individuals comfortable with synology and linux command line, I take no responsibility for any issues encountered*** ***Read fully before considering*** Please read all necessary documentation for setting up Xpenology before reading this guide. Try the start-here guides below: This guide docuements the process of using Linux to modify the synoboot.img for your environment and writing to a usb hard drive. Additonally, this guide shows the upgrade process from 6.1.7 to 6.2.2 with extra drivers (extra.
  21. Here's my config from ESXi And if I do `lsscsi -C` it shows two controllers (0 = sata controller, 1=mpt3sas) Additionally the drives in the list are out of order:- Syno Drive # SAS Slot 1 3 3 0 4 1 5 7 7 4 17 11 19 8 21 15 22 14 23 12 This is the sata args from my grub.cfg
  22. Every controller that DSM can see will reserve slots. It enumerates the controllers based on PCIe slot number, lowest to highest. If the total number of reservations exceeds the number of slots then the ports are truncated. If you have extra/idle virtual controllers in your VM definition, it will create what you see here. A secondary issue is that DSM doesn't know how many ports are on a controller, so you may need to do some tweaking in grub.cfg to help it know how to arrange the controllers and ports. For baremetal this tends not to be an issue, but under ESXi
  23. XDOM

    DSM 6.2 Loader

    i check the content of the extra file and the file is there but no at /usr/lib/modules/update Its possible that your extra/extra2 is not loading at boot? maybe a error in my grub.cfg? ======================== if serial --port=0x3F8 --speed=115200;then set has_serial=true terminal_input --append serial terminal_output --append serial else clear fi terminal_input --append console terminal_output --append console if [ x"${grub_platform}" = xefi ]; then insmod efi_gop insmod efi_uga el
  24. Hi also i bought asmedia 1066 but system wont boot juns 103 with ds3617xs on hp ml310e gen8 server. so 1 test disk on asm1066 and 2 raid 1 on b120 internal software raid my sata_args are: sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=44 SasIdxMap=0' could you suggest a config? esxi use b120 software raid for the datastore where is located synoboot.img and vmdk if add pci sata with passtrough system won't boot up. logs report this: it seems that on booting it recognize the first an
  25. config SYNO_SATA_PORT_MAP bool "Modify SATA Hosts Port Number" depends on SYNO_FIXED_DISK_NAME default y help <DSM> #18789 Reads Sata-Port-Mapping information and forces the sata hosts to initialize specified number of ports. This makes the disk name not skip some characters. Notice - Do NOT set the port number out of the range that [0-9]. It supports as most 9 ports now. For example, SataPortMap=4233 means the 1st host use 4 ports, the 2nd host use 2 ports, the 3rd and 4th host use 3 ports. config SYNO_DISK_INDEX_MA