pocopico

Same here, it’s seems that there is a last step that should do something to identify the disks. UDEV maybe ? I have compiled vmxnet3.ko and e1000.ko modules and I get an ip from DHCP. GUI is accessible but no disks are found

Hi, can someone please share a working vmware image ? I have created missing kernel modules and figured what to do in order to have them loaded succesfully (i can provide additional kernal modules if anyone is interested), but i still fail to get the disks identified. I anyone has a VM to test i would be thankfull.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 1 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HPE Proliant MicroServer Gen7 N54L) - Additional comments: Requires reboot

Thanks for the tutorial !!! It was exactly what i was looking for.

Well, it was mainly because of the BTRFS phantom crashes that i had to got to 6.1 ... now my system is unfortunately not bootable anymore so i will have to either wait for new loader of just create the modules and update loader to make it work.

Hi, after some BTRFS volume crashes in 6.02, i have decided to go with the update to DSM 6.1. Unfortunately i did that before searching in depth for the issue, and i recently found that issues exist in 6.1 as well. Anyway, i have already tried to perform the update to 6.1 before updating the 6.02 loader and failed. I have then tried to boot with Jun 6.1 Alpha loader and i found out that the driver is probably missing for the onboard NIC NC107 (broadcom) 1GB card as the server never comes online. I have tried to recreate both ramdisk and extra.lzma with the additional modules taken from the 6.02 image but they fail to load due to kernel incompatibility (3.10.77 in 6.02 vs 3.10.102 in 6.1) and looks like i have to recompile them with the new sources. I will try to follow the viewtopic.php?f=2&t=31211 topic to recreate the missing modules and update the loader with them. Anyway before going through all this painful process, i thought it might worth asking here if someone else did that before and has already compiled the modules i need. Mainly missing the NIC drivers and firmware from the image. I will keep you posted for the progress.

Yes you can try, just write the USB image to a USB key and boot it. Wait a few minutes and start the assistant. You'll be able then to install. I can't get my Gen8 to boot using the .img file. The usb doesn't seem to be seen as a boot device and then it just gets into a network bootloop. Please bear in mind that you will need to change the boot mode to UEFI and not legacy in order to boot this image

Hey codedmind, If you have a Gen8 Microserver then you'll need to wait until a Legacy/BIOS boot image is created. The barebones image is only for UEFI and the Gen8 Microserver doesn't support UEFI. Hi, gen8 supports UEFI. Its gen7 that does not ..

Yes you can try, just write the USB image to a USB key and boot it. Wait a few minutes and start the assistant. You'll be able then to install.

Quick nick, I'm trying to build an ISO image for nonEFI bare metal users (like me) I get to the point that it has boot but when I upload the install pat image I get an error that claims the image is corrupted although I used the same one to install successfully on a VM. I guess I'm missing some parameters in the append entry in isolinux. Could you please pass some info about the append commands with a PM ? Sent from my iPhone using Tapatalk

Oh, i guess you are talking about a bare metal install on a physical system.You will not see anything on the VGA past these messages with this unmodified kernel. All messages are going to be forwarded to the serial console. You can either use the serial port of your board or just check with Synology assistant after a couple of minutes, if it can be discovered. You are kind of "blind" but if you have a network card that is recognized by the built in kernel drivers then you'll be good to start.

There is no video output, you have to use serial pipe connection, check the first post on this thread.