![](https://xpenology.com/forum/uploads/set_resources_8/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
mmaster23
-
Posts
9 -
Joined
-
Last visited
Posts posted by mmaster23
-
-
So far I have migrated 4 of this from v5 to v6 you need to change de vid/pid and then edit synoinfo.conf to enable SHR, so far I have been able to expand with no problems, to edit synoinfo.conf you must ssh and then follow this to enable SHR with sudo:
edit /etc.defaults/synoinfo.conf
comment out/delete
CODE: SELECT ALL
supportraidgroup="yes"
then add
CODE: SELECT ALL
support_syno_hybrid_raid="yes"
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.
-
Still no NEWS on HYPER-V support
Like I said a few pages ago, we need to recompile some hyper-v kernel modules but the build process is being a pain.
-
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?
-
Just convert synoboot.img to vhd with Starwind Convert. work very well. Boot but if you fail, it maybe ethernet problem..
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.
-
I am currently on 5.2 and willing to upgrade to the latest v1 bootloader and upgrade my DSM to version 6.
Is it possible to upgrade and remount my harddrives without data loss? 4x 2tb they are ext4 drives. It is no problem that they are not partitioned as btrfs drives. I've worked with btrfs before and since raid 5/6 are still not declared stable i'm not willing to take the risk. https://btrfs.wiki.kernel.org/index.php/Status
My hardware: Asrock J3160-ITX, 8GB DDR3 1600.
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.
-
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?)
Most LSI cards will NOT work without a patched kernel. Until a patched kernel is produced, you'll have to wait.
mpt2sas: LSI SAS 6Gb/s Host Adapters SAS2004, SAS2008, SAS2108, SAS2116, SAS2208, SAS2308 and SSS6200* Note: It's already included in existing ramdisk but not loaded. By dmesg it's started correctly.
SAS2008 (Falcon) is the LSI 9211/IBM M1015.
-
Hi guys,
Here is my updated ramdisk.lzma: https://mega.nz/#!KBFRxZiY!m_w2uCnUvTyH2leI6hKn1GMDbGRV6MeOLmUFrzHc4R0
Backup your existing ramdisk.lzma (for sure) from image/DS3615xs/ on your usb boot drive and replace it with the ramdisk.lzma from archive.
Or download complete img file:
-
https://mega.nz/#!2dliEDia!FlkILSHCJqRUDTyjzjVUOawke5GEl0ESTiqEAajpaS0 (UEFI)
- https://mega.nz/#!KV8BjaLb!Bt28SEBMlvmcu3DdhMtpG-t-WmycNA4UKASfFwcyrjo (Hybrid UEFI/BIOS)
Compiling any disk adapter modules is not possible at the moment due to unexported syno_libata_get_index function (declared in libata-core). So only way to fix it is recompile kernel (we don't have latest kernel sources to do that) or somehow modify drive adapter sources to not depends on syno_libata_get_index function.
Edit:
Files moved to mega.nz from my webhosting.
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?)
-
https://mega.nz/#!2dliEDia!FlkILSHCJqRUDTyjzjVUOawke5GEl0ESTiqEAajpaS0 (UEFI)
DSM 6.1.x Loader
in Loaders
Posted
Should work fine without a reinstall. Edit the grub config file to include the proper boot arguments.
http://quickconnector.orgfree.com/index.php