Polanskiman

what i would try you still have ports free in you setup so you could put in an additinal 17th drive, change syno config file to support all ports including the onboard (8+8+6=22?), aktivate onboard contoller in bios, start with additional empty drive, initialize it and create a basic volume, the init will put your acctual installation on the additional drive, shutdown, cut power to all raid6 drives, place the single drive that it will be used first (internal sata?), boot new 1.02a2 loader and install/update to 6.1 on that single disk, after 6.1 running change the config file so that it will support all ports (22?), after checking that all ports are present in diskmanager shutdown, reconnect the raid6 drives, start and if things are running good the single disk will be used to start the system and will be "master" to init the other partitions on the raid 6 drives (and the raid6 array will be found) if that works and the raid6 drives habe all the mirrored config from the 17th drive it can be deleted and removed, afterward the config can be re-done so that only the 8+8 is used i have a dsm 5.0 and it has ext4, i also plan to dpdate and with 6.1 it makes sense to use btrfs instead of ext4 so offloading (backup) and new clean istall with new raid6/btrfs seems the better solution This could be a solution. Just keep in mind to properly number your drives. Each drive needs to go back to the exact same location, that is the same SATA port on the controllers else the volume will be degraded. If you initially created a Disk Group the order may not be an issue, else it WILL be.

Strange though that you were able to boot without selecting the AMD boot line in Grub menu. Anyhow, use your NIC real MAC address. Not that this was the problem but this is what I recommend to everyone. No need to generate anything. If your problem is solved please add [sOLVED] to the title.

Yes that was for v1.02a2. The model (3615 or 3617) is irrelevant.

Jun released v1.02a 3 weeks prior the release of the source code of DSM 6.1. He said that he did not need the source code to make the loader work since his patching method was still functional with DSM 6.1. That's one thing. Now for the modules, I am guessing that he either reverse engineered the modules and fiddled with them or recompiled the modules with the kernel source code of linux 3.10.102 which has been available for close to a year already. I am just guessing here, so do not quote me on this one. That's a question that Jun would need to answer himself. But in general one needs at least the source code of the kernel to be able to compile a module that will work with that kernel version.

At least one person did it and he had to hard reset the machine and then it seemed to work.

Jun, would you mind commenting on this? I have seen several people saying that v1.02a is working with AMD based CPU hardware. How is this possible? Thanks.

Normalement ce dongle marche avec le module btusb.ko qui lui normalement fait parti des modules par default. Avez vous essayé un autre port usb? Aussi, laissez branché le dongle, redémarrez et ensuite tapez cette commande via ssh: dmesg | grep Blue Envoyez le resultat ici.

Yes it works.

I presume you are using the real MAC address of the NIC. In principal there is no need to do anything for the LACP. Just make sure that your MAC address is reflected in the grub.cfg file for Synology Assistant to be able to find the box during install (read the tutorial). That is correct. If some drives come up missing the raid will be degraded. I am not entirely sure how to proceed in your case specially because you have pushed the limits of what 3615xs is supposed to accept in terms of max drives. Normally the IBM M1015 uses the mpt2sas module which is included in Jun's loader v1.01 so from a compatibility stand point both cards should be fully functioning. For the rest, there are several ways to go but none will be a smooth ride in my opinion considering what I said above. I think you should find a way to remove 4 drives prior installation making sure the raid is not degraded before the upgrade. I'll let others chime in on this.

where does the *.ko come from? did you compile it from the synology kernel sources? https://sourceforge.net/projects/dsgpl/ ... z/download if you alrady have installed dsm (and the *.ko is correct) you can copy it to \usr\lib\modules\ (where all kernel modules are located) other way might be to add it to extra.lzma (synoboot.img\image.img\extra.lzma\extra\usr\lib\modules\) using osfmount or modify the extra.lzma that is already on the usb-stick (2nd partition) Let me get this straight guys. You are taking a module from Quicknick's loader v2.2 which is made for DSM 6.0.2 (kernel 3.10.77) and you are trying to added it to Jun's loader v1.02a (or v1.02a2) which is made for DSM 6.1 (kernel 3.10.102). That will simply NOT work. The module needs to be compiled against DSM 6.1 source code to work with DSM 6.1 and then it needs to be added to Jun's latest loader (v1.02a2). DSM 6.1 had an updated kernel thus the reason why modules need to be recompiled. What could possibly work is to add the module to Jun's v1.01 loader ramdisk and update the rc.modules file (DO NOT add the extension .ko of the module in the rc.modules). That should normally work if the module was compiled properly. Keep in mind though that many modules in Quicknick's loader were faulty. This is one of the reasons why he took the loader down.

Yes. People have reported that it works fine.

sorry i'm just guessing, its what i would try so .... looking further into the extra.lzma, there is /etc/rc.modules ... EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" ... so looks like the firmware file has to be mentioned in that file to work? Tossed a kernel ID? Not sure what that is supposed to mean but if modules were not compiled against the proper source code they would simply not work. Do not confuse modules and firmware. All modules within the v1.02a (or v1.02a2) loaders are compiled against DSM 6.1 source code and made to work with linux kernel 3.10.102. There is no other way around. In your case, the firmware seems to be missing. I checked the extra ramdisk and it is not there. The rc.modules also needs to be updated with the added firmware or whatever module you add in the ramdisk else it wont be loaded during kernel boot. I have made the necessary changes in the ramdisk. Let me know if it works (or not). I can't test it myself since I do not have that NIC. https://mega.nz/#!OQplzISJ!L6HzXJq2ZwX- ... k99jYVwKBc note to myself: This ramdisk only contains the additional firmware bnx2-mips-09-6.2.1b.fw on top of the default ones added by Jun. Nothing else.

Uninstall and re-install phpMyAdmin see if that helps.

Turns out the vboxmanage convertdd command did convert it ok, it was the PC i was using it on didn't have VT-x. Now to work out why I am not getting an IP address in bridged mode, which Network card did you select? You can use the Intel Pro/1000 T Server.

Hello and welcome to the forum, First you need to tell us what version of the loader and DSM you are using. Without that basic info it's difficult to help, but here are some preliminary answers: 1) Which guides are you referring to? It seems to me that you are referring to old and outdated guides. The USB key should NEVER be removed. It is necessary for DSM to boot properly. If for some reason you need to reboot or there is a power failure and the USB key is not plugged then DSM will not boot. 2) You can plug the USB key in whichever port pleases you although it seems in some machines DSM does not detect all usb ports for some reason. Anyhow, any port will do but I do recommend you use a USB 2 port instead of a USB 3 port if there is any in your machine. Also to answer your question more precisely, I would recommend you plug your USB key in to one of the outside ports, not because it will effect air flow honestly, but because it will be easier to access when you need to update the loader. 3) It is difficult to comment on that. Personally I have 16GB of RAM and all are seen by DSM (see my signature for more info). It could be a faulty RAM, incompatible RAM, damaged slot, Bios issue/config, mismatched RAM capacities etc etc. I would recommend using 2 RAM sticks of the same capacity to start, making sure both RAM are exactly the same specs. Try only plugging the new 4GB RAM see if it is detected to start with. 4) As for the CCTV cameras, please be informed that if you use Surveillance Station only 2 licenses are free, meaning only 2 cameras. To add more cameras you would need to buy licenses accordingly for each camera but here is the problem; I am not sure it will work and if it does there is no guarantee that it will last forever since you are already infringing the license of DSM by using a software that can only the used on Synology genuine hardware. By the way, we do not condone piracy here so you might need to find another solution for your CCTV cameras. There might be other packages out there for handling camera feeds but I am not knowledgeable in that area.

How did you convert the synoboot.img to vdi or similar? I tried converting through vboxmanage convertdd but now my PC is rebooting on me every time I try to start the virtual? I converted the .img to .iso. There is a plethora of software on the internet that can do that. If you are on a MAC you can simply use the Disk Utility to convert the .img file to .cdr and then simply rename the extension to .iso. Just make sure the image format is DVD/CD Master when you convert it.

Time out.

Ce n'est pas un bug. Le modèle du processeur est codé en dur raison pour laquelle on voit i3 à l'écran car c'est le processeur utilisé par Synology dans les machines DS3615xs. Mais comme indiqué, l'OS utilise toutes les capacités du processeur i5 installé. Pour ce qui est du Xeon je ne peux pas confirmer mais il est possible de vérifier l'activité en temps réel des coeurs si vous avez Debian chroot installé sur votre DSM. Il suffit après de démarrer Debian via ssh et lancer la commande suivante: watch -n 1 cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq

This needed confirmation and it's been confirmed. Reason I was not "very specific" was to prove isssue Next time be specific in your topic title and do not advise people to block domain/IPs or whatnot without any explanation. Failure to do so will be perceived as an attempt to spam. Hope this is clear. I am locking this topic as there is really nothing to talk about here.

You need to describe your problem a bit better. I do not see any problems with SHR volumes, at least it works for me. Hey! My Mainboard is an Asrock J3455M (same problem on VMware/Virtualbox) and DSM boots fine. But after i edited the synoinfo.conf file, so i'd be able to create a SHR Volume, DSM always gives me the error on restart that "Dark Zydor" posted. Error shows all drives connected. Apply update 2.

Not sure where you read that. As far as I know Jun stated what CPU type is required for DS916+ to work properly. For the rest, he states he enabled mcu emulation to take care of the "time bomb" issue. Both matters can be read here: viewtopic.php?f=2&t=20216&start=2530#p98458 here: viewtopic.php?f=2&t=20216&p=98490#p98539 and, here: viewtopic.php?f=2&t=20216&p=98490#p98490

What does network detection issues mean? Did you see the kernel logs to be able to state that? For DS916p to work you need the adequate hardware, and by adequate hardware I mean the CPU should be a braswell processors, 4th Gen Core processor or later. See here >>> viewtopic.php?f=2&t=20216&start=2530#p98458 I have an Asrok N3150B-ITX with realtek RTL811GR chip. burned the DS916 image to a formated USB, known work well, modified VPI and PID, kept the mac and SN. It appeared have booted, but undetectable on network, Router and Synology assist. It is a braswell CPU. It appears to be the network card not being detected. I can tell it is booted by trying to press the power button. If is booted, you have to hold the power button for a few seconds to shut down. It is not booted, touching the button briefly is enough to shut it off. That doesn't mean anything. It's not a way of knowing if the problem is a network issue or something else. You need the logs to be sure as stated above.

I'm running a Xeon E3 1231v3 on an Asus H97i Plus baremetal and it's unable to get an statically defined IP. What paramater should I pass to grub to enable verbose boot? You have to see the logs through a consol and with a serial cable. No other way as far as I know.

This has nothing to do with the network so your problem lies elsewhere. You can either add a # in front of it (that means to comment out) or simply delete the whole line. I always prefer commenting out. Both have the same effect, that is to deactivate the functionality.

What does network detection issues mean? Did you see the kernel logs to be able to state that? For DS916p to work you need the adequate hardware, and by adequate hardware I mean the CPU should be a braswell processors, 4th Gen Core processor or later. See here >>> viewtopic.php?f=2&t=20216&start=2530#p98458