mmaster23
Transition Member-
Posts
9 -
Joined
-
Last visited
Everything posted by mmaster23
-
Thanks for those infos, i didn't even know SHR wasn't supported natively. Is it over with DSM 6.0 or just a "bug" in this loader ? It's because Synology removed it's support for SHR for this specific model (we're emulating). Previous releases would include this out of the box but this is a more barebone release. So you'll have to do it manually.
-
OK I tried building hyper-v network modules for multiple users asking for a Hyper-V image. Copying the .ko modules from different won't work, obviously. I've setup the toolchain for DSM6.0 and used the sources from github (https://github.com/quiknick/7274-kernel). A quick chroot to the toolchain dev env for x86_64 and make oldconfig. Followed by the module itself: [root@ubuntu16desktop 7274-kernel]# make M=./drivers/net/hyperv/ WARNING: Symbol version dump /7274-kernel/Module.symvers is missing; modules will have no dependencies and modversions. Building modules, stage 2. MODPOST 0 modules Edit: should clarify: The module isn't found so it won't build. The 4.4 linux kernel source doesn't suffer from this.. anyone have any leads?
-
http://imgur.com/a/C6ujx Done, it's just staying on this screen. From a few posts back I've read that adding an serial port can fix this in ESXi, but no luck in Hyper-V. Anyone suggestions? Edit: Generation 2 version of the VM in Hyper-V will leave me with the error "error: terminal 'serial' isn't found." Adding an SERIAL port in Generation 2 is not possible by default. Not true.. You have to use Powershell.. Look up the Get-VM and Get-VMComPort / Set-VMComPort for more options. I have tried both VM v1 and VM v2 with a COM port capture. It boots but the nic is missing. We need the hyper-v kernel components.
-
Dsm doesn't use btrfs raid.. It uses Linux mdadm raid. Btrfs can be used as a filesystem.. It can also be a integrated raid system combined with filesystem. You can migrate your data to the dsm 6 platform but keep in mind this stuff is very much beta and isn't production ready (if it'll ever be that). Make backups..
-
I too am having issues with the Intel 219 NIC. Works for step one (finding the box and uploading the PAT) but doesn't seem to work after the reboot. Unfort. i don't have a serial connection so I can't debug stage 2.
-
Thanks for all your hard work. Now I can finally see my box. I modified Grub.conf for the pid, vid, sn and mac and that works. It boots fine on my Q170 board and I can access the install wizard. Loaded it with the pat file (or let it download it itself) and let it run down the installer. The computer reboots as expected to the USB stick once again. However, after loading the image, I can't get a response. I think the intel nic is down after the reboot. Any thoughts? Again, thank you. Edit: p.s. I've tried both the UEFI image and the UEFI/BIOS image. My board is in true UEFI mode. Testing with a SSD attached to the intel controller. Disks attached to my 9211-i8 don't show up (at this stage?)