Wizengamot

Trying to get an IBM x3650 M4 to work with this as baremetal. Here are the steps I followed so far. I am looking for anyone who knows what bootloader I should use (and the most recent compatible .PAT file). The current ones I am using obviously do not work with this hardware. I will list the hardware as I know it. 1. Intel Xeon E5 2620 (2 CPUs total) 2. The BIOS shows the drivers for Intel Pro 1000 Network adapter. 3. I have an LSI 9211-8i card installed with a single 8tb drive attached. 4. The system as 120 GB of RAM installed. 5. All onboard SATA ports are empty. 6. The Network Cards MAC addresses were listed in the BIOS, I have copied all four addresses from there for use in grub.cfg. Here are the steps I followed. 1. Using OSFMount I mounted the synoboot.img found in the file synoboot-ds918.zip, ensuring it was not read-only. Based on what I was reading this bootloader is 1.04b. 2. Edited grub.cfg a) created four entries for nic's, using all four MAC address copied from the BIOS b) Removed the ESXi boot option by commenting it out at the bottom of grub.cfg. c) Generated a serial for a DS916 and placed it within the correct location in grub.cfg. d) Found the PID, VID for the USB device to which I planned to write the IMG file and placed them in the correct locations within grub.cfg. This was double checked to ensure that VID and PID were put in the proper locations. e) Saved grub.cfg. 3. Wrote the resulting image file to the USB stick that I found the VID and PID values for. 4. Installed the USB stick into the hypervisor boot slot and booted the server. 5. It booted to the point where it said I should locate the synology using find.synology.com 6. I have the synology assistant on my computer so I used that to search for the device after waiting for awhile. I repeated the search after waiting again for about 3 minutes. No synology was ever found. I ran through the above procedure once before with the modifications required for ESXi and was successful in eventually getting synology going. The big issue with ESXi was that I could not get that system to recognize my 9211-8i adapter properly and see the drives attached to it (even though it was loaded, adapter showed in devices) it never showed drives.. but I digress. This is my attempt at using DSM bare metal on the same hardware and I'll just use DSM to power any VMs I may want rather than ESXi. I have several theories but the one that stands out is this: Is the NIC being detected by the bootloader and if not, is there a way I can get the NIC to be detected and working? Other question that may or may not be relevant are. 1. Does the updated 1.04b boot loader support the hardware I have listed above? 2. If the bootloader does NOT support it, what is the latest bootloader I should try and the corresponding version of DSM that would work? 3. If I should try a different bootloader and DSM are there any modifications I should make to my steps above (aka things known not to work). What I mean by this is that during my reading I have seen that some bootloaders had problems with multiple NICs but I saw that was back at 1.02 so I assumed such problems had been resolved by 1.04b, hence my use of 4 nics. I am not looking for someone to essentially do this for me, but rather someone who might know where I am going wrong and point me in the right direction and I most certainly want to thank anyone who takes the time to read this and respond. Thanks, Wizengamot

This is now working. There was a problem with the network that was fixed. Many thanks to Luchuma for their comment because it prompted me to look further into the networking and I found the issue as a result. Did not find a way to mark their post as answer.

Yes. I checked using Linux to determine what the MAC was on each NIC. Not sure how to do this using ESXi but I was playing around with ProxMox earlier and I had the MAC addresses from when I tried this same procedure using PROXMOX. I did not even get this far on ProxMox and I found that ESXi had more information so I switched.

Here is the guide I have been using. I am using the files referred to in the Tutorial. 1. It refers to the VMDK file from the DS3615xs 6.02 Jun's Mod V1.01 2. It refers to two options for the IMG file, I am using the DS3615_6.2 image file. 3. I have modified the IMG file using Notepad++ and OSFMount as per the instructions. In my case I have 4 NICs, so I put those into the GRUB.CFG file. Using a serial for a DS3615. 4. Configured the VM exactly as the instructions said to do so. 5. The adding of the second disk was a bit unclear so I created a second disk of 500GB, Thick Provisioned, lazy zeroed. I believe the writer of the Tutorial meant for many disks to be added, but I only added 1. The idea being that more can be added later on as needed. I got right up the point where I see the Command Line screen as per the instructions. The black screen that says to visit find.synology.com. This website cannot find anything at all. So I promptly downloaded Synology Assistant. This is where things get weird. The assistant DOES find a synology on the network. Everything matches, the MAC I assigned, The Model I am installing, Serial Number given, but the IP address of the unit is 192.168.1.156. This is very very odd, because while the IBM x3650 M4 has 4 nics in it, only one is connected to a wire right now and it is only (theoretically) able to use 192.168.88.1 - 192.168.88.254 (this is according to the VLAN 0 configuration in ESXi. So.... I try to install DSM onto the found Disk Station. It asks for the PAT file and I give it the PAT that I grabbed which in this case is DSM_DS3615xs_23739 which I got from synology under the 6.2 folder. I got 6.2 because I was using the 6.2 bootloader. The "odd" file out is the VMDK from the zip file and it could well be a VMDK from 6.02. (see point #1). During the installation it recommends that I use Manual Network settings and suggests an address in the 192.168.88 subnet. When I attempt to use ANY address in this subnet it tells me that the address is in use. (It is not). I moved on to letting it use DHCP for networking and tried to run the install again. It failed right after applying the network with the message: The big question is this. How on earth can this VM get an address of 192.168.1.156 when the VLAN 0 says the only discoverable addresses are the range of 192.168.88.1 - 254? I think this is the root of the problem and I so far have not found a way around it. Thanks for your help in advance. B