MastaG

But will it also take into account, the custom serial numbers I've set? and the custom kernel modules for getting ethernet running on the Microserver Gen8?

So I'm currently running DSM 7.0.1-42218 for DS3615xs on my HP MicroServer Gen 8. I remember creating the USB loader using a modified repository and I had to insert the drivers for the internal ethernet controller as well. What would be the easiest way to upgrade to 7.1 without losing data?

I'm running DS3615xs DSM 7.0.1-42218 on my MicroServer Gen8 G1610T. I've compiled it from source a while ago and I remember it took me some trouble to figure out how to add a repository for the ethernet drivers. Anyways it has been running rock solid up until now, surveillance station, docker + portainer and even a Windows 10 VM and I'm very happy with it. Now I believe update DSM 7.0.1-42218 Update 1 and 2 are out now. What's the best way to build a new image (which includes the ethernet driver)?

I even modded my Gen8 to have a fifth drive sticked to the side with velkro lol. Using the sata cable that's meant for the disc drive. I must say that 7.0-41222 works really well so far. I setup a RAID5 pool with btrfs volume and even Surveillance station is working with my camera (one of the main features for choosing Synology over Unraid/TrueNAS imo). So It's just like my geniune Synology.. now I have two running DSM7.

yeah it doesn't seem to be required for basic nas operation. other then that I noticed that 7.0-41222 is actually a beta firmware for the ds3615xs and it's pretty outdated. I see there were newer builds, even a RC, but they didnt release it for this specific model?

oh right.. I didn't know that.. I just put my own macs there and a serial number by some keygen.

Alright I got it to work. I solved the console problem by switching the virtual console port to COM1 inside the bios setup. Then I found out, I was modifying rd.gz from the EFI partition... which was wrong, so I modified the one from the fat partition and found out my drivers were there. Only my libphy.ko would segfault for some reason, I've the vanilla 3.10.108 kernel sources with the browlow config, but I think I did something wrong here. Using the ones from the tg3.7z archive posted here seems to work though. I've just loaded the PAT file for 7.0-41222 and it's working so far. I think a few points that would make life easier for beginners would be: - Make sure the first partition inside the image is set "active"/"bootable" so it actually boots right after flashing it - Add some templates/startup-scripts for loading your own kernel modules instead of having the manually hack the ramdisk - Add some documentation on how to build your own kernel modules, e.g. which kernel sources, config and toolchain you should use for a certain version.

That didn't work for me. I believe it's something like this: mkdir rd cd rd xz -dc < ../rd.gz | cpio -idmv (add drivers) find . 2>/dev/null | cpio -o -c -R root:root | xz -9 --format=lzma > ../rd.new.gz cd ../ rm -Rf rd mv rd.gz rd.old.gz mv rd.new.gz rd.gz Still I can't seem to get any network interfaces. Also the tg3.ko and libphy.ko where not inside the rd.gz archive.. while I did add it to the config.json file... The iLO VSP console only print up to the point where it says: [ 2.167768] <redpill/uart_swapper.c:428> ### LAST MESSAGE BEFORE SWAP ON "OLD" PORT ttyS1<=>ttyS0 From that point on I'm blind...

Thanks my friend, It seems rd.gz is packed using lzma compression. 7z x rd.gz 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=nl_NL.UTF-8,Utf16=on,HugeFiles=on,64 bits,48 CPUs AMD Ryzen Threadripper 3960X 24-Core Processor (830F10),ASM,AES-NI) Scanning the drive for archives: 1 file, 5454480 bytes (5327 KiB) Extracting archive: rd.gz WARNING: rd.gz Can not open the file as [gzip] archive The file is open as [lzma] archive -- Path = rd.gz Open WARNING: Can not open the file as [gzip] archive Type = lzma ERROR: There are some data after the end of the payload data : rd Sub items Errors: 1 Archives with Errors: 1 Sub items Errors: 1 [mastag@AMD3960X t]$ ls rd rd.gz [mastag@AMD3960X t]$ file rd rd: ASCII cpio archive (SVR4 with no CRC) When using 7z to extract it, I'll give me a cpio archive called "rd". Any tips on how to proceed here?

So I've built my modules. Now I've edited the config.json to look like: "extra": { "compress_rd": false, "ramdisk_copy": { "@@@EXT@@@/rp-lkm/libphy-v3.10.108.ko": "usr/lib/modules/libphy.ko", "@@@EXT@@@/rp-lkm/tg3-v3.10.108.ko": "usr/lib/modules/tg3.ko", ... I can verify the files are there. But where do I put the line that says something like: insmod /usr/lib/modules/libphy.ko insmod /usr/lib/modules/tg3.ko

Yeah that's what I meant as well. I can compile the generic kernel release just fine as long as I use their toolchain. However they should release their patched version of the kernel at some point right? Because the license says so.

any idea where I can get the patched kernel sources for linux-3.10.108 used in 7.0.1-42214 ? the toolchain only contains the pre-compiled kernel headers, not the full source...

Thanks bro, That would be great 👍 If you can confirmed the internal NIC isn't supported any longer, then perhaps you can share your card with us. I guess it's a small price to pay to have the latest DSM working

Thank you for the docker files and your own image. Unfortunately even when trying your image, the internal network interfaces still don't come up (at least no DHCP request is being made). So I guess the MicroServer Gen8 internal network interfaces aren't supported anymore in 6.2.4 and 7.x.

Would it be possible to share your image, so I can give it a shot? And can you also point me to the dockerfiles so I can see if he puts anything special in the user_config?