Jump to content
XPEnology Community

PhoenixNL72

Rookie
  • Posts

    8
  • Joined

  • Last visited

Everything posted by PhoenixNL72

  1. In the past I used this website to generate valid Synology serial numbers based on the MAC number you enter on the site: https://jsfiddle.net/7Lorpu77
  2. You could try the modified loader from this post: I am currently using it on a Asus M3N78-CM motherboard which features the nForce 8200 chipset (MCP78S) which also uses an nForce network controller (Manual: NVIDIA® nForce built-in Gigabit MAC with external Realtek8211CL PHY) I couldn't get the normal Jun 1.03b version to work with that network controller using DSM 6.2.3 on this motherboard. With the modified version from the post above the system could be found using Synology Assistant (Unfortunately you need to use the ds3617 version of the pat file for 6.2.3 too which is nolonger on the Synology website. But you should be able to get it from the Internet Archive Wayback Machine.)
  3. PhoenixNL72

    DSM 6.2 Loader

    Oh, Ok. Thanks for clearing that up. I thought the lack of the correct iGPU hardware would cause a kernel panic during boot or something.
  4. PhoenixNL72

    DSM 6.2 Loader

    Hm, not sure. Could be a protection issue with the PID/VID/Serial number, or a kernel panic? Are you sure the VM's hardware setup is compatible ? AFAIK 1.04b only works with the 918+ DSM pat files and those require you to have at least an intel Haswell or later processor (I3/i5/i7 4xxx or later) due to the iGPU (915 I think it needs?) requirement. As is listed here: Did you put the correct extra.lzma on the USB stick? Or the extra.lzma modded by user Real3x: I'm assuming you don't have a DSM installed on any HDDs yet. And the system is freezing on the USB Bootloader only. (If you do have DSM setup on a harddrive then it might have problems while booting from that, which would be a different problem.)
  5. PhoenixNL72

    DSM 6.2 Loader

    madhits45: You could rewrite the USB loader with the original img file. That way any data the upgrade wrote to it is removed. But if you did any modifications of the config files/extra.lzma etc you will have to redo those (Though with OSFMount you could make those changes inside the img file itself). Alternatively you can do it on the USB stick afterwards and create a new IMG file from that IUSB stick using the Win32DiskImager read the data from the USB stick to a new IMG file (you can enable the Allocated Partitions Read only option so you don't include unallocated space on the USB stick in the image).
  6. PhoenixNL72

    DSM 6.2 Loader

    Are you sure PID, VID and Serial in grub.cfg are correct? From my experience 6.2.2 is a lot more touchy about those being correct then 6.1.7. It's also more touchy with the USB flash disk used. I could boot 6.1.7 just fine from an SD Card in a flash card reader. But 6.2.2 absolutely refused. I also couldn't get 6.2.2 to boot with a serial number generated with the old webbased serialnumber generator. Seems you need a serial that starts with something like C7L, Like the one in Jun's original 1.03b bootloader. If you are sure you are using the correct PID & VID for your USB stick, and are using a valid synology serial number. Try using a different model and/or brand USB boot stick.
  7. PhoenixNL72

    DSM 6.2 Loader

    the .pat files are the regular DSM OS files from synology. You can download the DS3615xs, DS3617xs and DS918+ build 24922 versions, which are the ones most commonly referred to in polanskiman and IG-88's installation guides, from here: https://archive.synology.com/download/DSM/release/6.2.2/24922/ (For other versions you can go to the parent directory and select the one you want. Do not go to the 6.2.3 version unless you know what you are doing (e.g. you know your hardware is natively supported by the DSM version as there isn't a working extra.lzma available for 6.2.3 yet afaik.) Make sure you download the correct one for the bootloader. So DSM_DS3615xs_24922.pat, DSM_DS2617xs_24922.pat for the two Bootloader 1.03b versions or DS918+_24922.pat for the 1.04b bootloader Also make sure you read this thread for upgrading to/installing DSM 6.2.2 using Bootloader 1.04b/1.03b:
  8. Pretty sure the problem is that the drive number is limited to 12 per default. That combined with the fact that there are skipped sata ports from your motherboard integrated SATA controller (which is the reason the ports for the SAS controller start from disk7) imho makes it so DSM doesn't properly detect drives connected to the remaining SAS ports. I think the solution would be to enlarge the number of drives usable to 14. You can change the "maxdisks" value in /etc.defaults/synoinfo.conf and /etc/synoinfo.conf I think it's It's very likely that will solve your problem. Alternatively if you are using Jun's Bootloader 1.2b you can change the grub.c to properly make DSM aware of the number of ports per controller. Locate the line with "set sata_args". It should look something like this: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' If your onboard SATA port has only 2 ports (and the SAS controller has 8 then change SataPortMap=1 to SataPortMap=28 might do the trick to remove the 4 disk gap between the samsung SSD (DIsco 3) and the WD 2TB (Disco 7) (SataPortMap = 28 means 2 sata ports located on the first sata controller, 8 on the second.) If your motherboard has 4 sata ports, set SataPortMap = 48. If your motherboard has 6 you can still use SataPortMap=48 this should just mean that DSM will skip onboard sata port 5 & 6 (and those should therefore never be used to connect a harddisk !) (Check also for more detailed info on sata_args )
×
×
  • Create New...