Niels_J Posted February 1 Share #1951 Posted February 1 On 10/28/2021 at 4:01 PM, Holger1965 said: i‘d like to build on a Gen8 Hp Server My server is upgraded to XEON E3-1320v2 Hi Holger, Did you succeed? What did you upgrade from? Quote Link to comment Share on other sites More sharing options...
Dfds Posted February 1 Share #1952 Posted February 1 @Niels_Jthe gen8 will happily run DSM 6.2.3 with jun’s 1.03b loader or if you want to try DSM 7 you can build a loader using redpill tinycore, see the thread in the developer discussion section. Quote Link to comment Share on other sites More sharing options...
Niels_J Posted February 1 Share #1953 Posted February 1 29 minutes ago, Dfds said: @Niels_Jthe gen8 will happily run DSM 6.2.3 with jun’s 1.03b loader or if you want to try DSM 7 you can build a loader using redpill tinycore, see the thread in the developer discussion section. Thank you for the info! The 6.2.3 is the one in the first post in this thread, correct? And now for the absolute 100% noob question: Do I just place the img-file on the USB stick, or do I need to edit something in the file and compile it with ... etc ? If so, where might I find the programs for it? Quote Link to comment Share on other sites More sharing options...
gadreel Posted February 2 Share #1954 Posted February 2 4 hours ago, Niels_J said: Thank you for the info! The 6.2.3 is the one in the first post in this thread, correct? And now for the absolute 100% noob question: Do I just place the img-file on the USB stick, or do I need to edit something in the file and compile it with ... etc ? If so, where might I find the programs for it? For Jun's Loader yes, you need to open one of the partitions and edit the grub file with the appropriate S/N and Mac Address. Quote Link to comment Share on other sites More sharing options...
F.K. Posted February 20 Share #1955 Posted February 20 Hi folks, I had to reboot my machine, wondering that the GUI doesn't show up. Connected a monitor to the server and found a GRUB warning, saying: error incompatible license entering rescue mode.... Has anyone an idea what this means and how to get my server booting again? Thanks for any helpful advice My Server: HP ProLiant ML10 Gen9 Modellname DS3617xs Prozessor: INTEL Xeon D-1527 Prozessor-Taktrate 3.3 GHz RAM 8192 MB NIC: Intel-Ethernet I219-LM DSM-Version: DSM 6.1.7-15284 Update 3 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted February 20 Share #1956 Posted February 20 1 hour ago, F.K. said: Hi folks, I had to reboot my machine, wondering that the GUI doesn't show up. Connected a monitor to the server and found a GRUB warning, saying: error incompatible license entering rescue mode.... Has anyone an idea what this means and how to get my server booting again? Thanks for any helpful advice My Server: HP ProLiant ML10 Gen9 Modellname DS3617xs Prozessor: INTEL Xeon D-1527 Prozessor-Taktrate 3.3 GHz RAM 8192 MB NIC: Intel-Ethernet I219-LM DSM-Version: DSM 6.1.7-15284 Update 3 you coud try to rebuild the loader on a new usb flash drive that the vanilla loader edit grub.cfg to mach the usb vid/pid of the new usb flash drive copy zImage, rd.gz and extra.lzma from old usb to the new one (all files on 2nd partiton) the try if the system boot again (if that work you can transfer SN and nic's mac from the olf grub.cfg to the new one) that way you dont change anything to what it is now, ols usb and system would still be the same if this attempt is a no good 1 Quote Link to comment Share on other sites More sharing options...
F.K. Posted February 20 Share #1957 Posted February 20 Hi thanks for your answer. I have simply recorded the USB bootstick with a new image. I did this about 4 years ago the last time - and I had a lot of jitters. But in fact it was much easier and faster under macOS than I feared. Now everything works again and my Synology version is finally on DSM 6.2.3-25426 Update 3 Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 14 Share #1958 Posted April 14 Hi all. I want to create a duplicate copy of my usb flash that has the jun”s loader on it.. in the past my usb drive died and I had to create a new one but I guess perhaps due to the vid/pid being different, It started my xpenology box as being new and I had do sort of a recover and restore data type of thing etc… if I create a copy of my current usb drive, should I use its vid/pid of the original drive in the cfg file on the new drive to prevent the loader from initializing the xpenology box if I ever have to swap out the usb loader flash drive? Quote Link to comment Share on other sites More sharing options...
signigelchan Posted June 4 Share #1959 Posted June 4 you're the best jun! Quote Link to comment Share on other sites More sharing options...
nickybg87 Posted June 11 Share #1960 Posted June 11 Is there a way to change the SN in the grub.cfg remotely (by ssh maybe) given the fact that pid & vid are set and the drive is not visible? Quote Link to comment Share on other sites More sharing options...
tomkoval Posted Thursday at 03:16 PM Share #1961 Posted Thursday at 03:16 PM (edited) To have correct MAC address for NIC you need to change it in /grub/grub.cfg file before booting NAS but if you forgot, there is still a chance to do it (and change serial number as well). To do so we need to change grub.cfg file on internal flash (see above). /dev/synoboot do not show in mount nor fdisk -l but still if you run fdisk -l /dev/synoboot you should see: Disk /dev/synoboot: 119.5 MiB, 125304832 bytes, 244736 sectors <- (size depends of usb drive used, here it is internal flash of Netgear ReadyNas Pro2) Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AFB38D11-BCEA-4409-B348-F4FEEE602114 Device Start End Sectors Size Type /dev/synoboot1 2048 32767 30720 15M EFI System /dev/synoboot2 32768 94207 61440 30M Linux filesystem /dev/synoboot3 94208 102366 8159 4M BIOS boot Create folder somewhere (/) and mount first partition from above mount -o loop,offset=1048576 /dev/synoboot /temp where offset is sector size(512) multiplied by start sector of 1st partition(2048). Now you should have access to grub.cfg in grub folder. Change mac1 and mac2 to correct hardware addresses. After writing to file you can unmount /dev/synoboot and reboot to check if changes applied correctly. Edited Thursday at 03:20 PM by tomkoval corrections Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.