NeoID
-
Posts
224 -
Joined
-
Last visited
-
Days Won
2
Posts posted by NeoID
-
-
Can anyone explain why the Mac address and Serial Number need to be changed in grub.cfg in Jun's loader, and why they can't be left at the default? If it needs to be changed, does it need to be changed to the Mac address of my NIC, or does it need to be changed to something else? Finally, is the Mac address I set in grub.cfg the one I should be using for setting up WOL?
Thanks for the help!
Strictly speaking, for the loader to work there is no need to modify the MAC address and S/N which come by default in the grub.cfg file. It should actually just work fine as is. The changing of these two values is more a matter of customisation of your box than anything else.
You can change the MAC address in the grub.cfg file to your NIC's real MAC address which will in turn be the MAC address used for WOl.
Not quite true. I use XPenology mainly for Photo Station and that doesn't convert videos if the serial isn't set or invalid. It has been mentioned in another threads as well. Even the logs complain about a invalid license check.
-
Edit: Solved by applying a new serial
I have the same problem, and so far failed to change the serial.
Could you please give me a quick explanation how you managed to do that?
Thanks!
Sure, use this: https://xpenology.github.io/serial_gene ... r_new.html
If you don't know how to modify the boot image read this guide: viewtopic.php?f=2&t=22100
-
Found the following in the logs:
2017-05-03T02:10:02+02:00 moto kernel: [11455.177314] Can't get Core 2 temperature data 2017-05-03T02:15:02+02:00 moto kernel: [11755.309262] Can't get Core 2 temperature data 2017-05-03T02:20:02+02:00 moto kernel: [12055.513710] general protection fault: 0000 [#1] SMP 2017-05-03T02:20:02+02:00 moto kernel: [12055.516855] CPU: 1 PID: 13921 Comm: snmpd Tainted: P C O 3.10.77 #8451 2017-05-03T02:20:02+02:00 moto kernel: [12055.516956] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B64.1605280101 05/28/2016 2017-05-03T02:20:02+02:00 moto kernel: [12055.517114] task: ffff88031f0a80c0 ti: ffff88031eed4000 task.ti: ffff88031eed4000 2017-05-03T02:20:02+02:00 moto kernel: [12055.517218] RIP: 0010:[] [] mutex_lock+0x4/0x20 2017-05-03T02:20:02+02:00 moto kernel: [12055.517332] RSP: 0018:ffff88031eed7d08 EFLAGS: 00010246 2017-05-03T02:20:02+02:00 moto kernel: [12055.517408] RAX: ffff880329fb2400 RBX: a7c0c3c748bd76f8 RCX: 0000000000000000 2017-05-03T02:20:02+02:00 moto kernel: [12055.517507] RDX: 000000000000258b RSI: 0000000000000002 RDI: a7c0c3c748bd76f8 2017-05-03T02:20:02+02:00 moto kernel: [12055.517607] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 2017-05-03T02:20:02+02:00 moto kernel: [12055.517735] R10: 000000000000000b R11: 0000000000000246 R12: ffffffff8184e0f0 2017-05-03T02:20:02+02:00 moto kernel: [12055.517836] R13: ffff88031eed7d80 R14: 000000000000fdc0 R15: a7c0c3c748bd76f8 2017-05-03T02:20:02+02:00 moto kernel: [12055.517936] FS: 00007f51fcfbc780(0000) GS:ffff88033fd00000(0000) knlGS:0000000000000000 2017-05-03T02:20:02+02:00 moto kernel: [12055.518050] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2017-05-03T02:20:02+02:00 moto kernel: [12055.518131] CR2: 00007f51fcfba000 CR3: 000000031ec8b000 CR4: 00000000001407e0 2017-05-03T02:20:02+02:00 moto kernel: [12055.518262] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2017-05-03T02:20:02+02:00 moto kernel: [12055.518376] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 2017-05-03T02:20:02+02:00 moto kernel: [12055.518476] Stack: 2017-05-03T02:20:02+02:00 moto kernel: [12055.518506] a7c0c3c748bd75a0 ffffffff8137a91b 0000000000000000 ffff88031eed7d80 2017-05-03T02:20:02+02:00 moto kernel: [12055.518622] 00007fff560d5c30 ffff88031eed7d80 00007fff560d5c30 0000000000000000 2017-05-03T02:20:02+02:00 moto kernel: [12055.518739] 00000000008407f0 ffffffffa0aecece ffffffffffffffff ffffffffa0ae9cf7 2017-05-03T02:20:02+02:00 moto kernel: [12055.518859] Call Trace: 2017-05-03T02:20:02+02:00 moto kernel: [12055.518908] [] ? syno_cpu_temperature+0xfb/0x1d0 2017-05-03T02:20:02+02:00 moto kernel: [12055.519032] [] ? GetCpuTemperatureDenlowI3Transfer+0xe/0x80 [bromolow_synobios] 2017-05-03T02:20:02+02:00 moto kernel: [12055.519178] [] ? synobios_ioctl+0x507/0x1100 [bromolow_synobios] 2017-05-03T02:20:02+02:00 moto kernel: [12055.519290] [] ? dput+0x1e/0x2a0 2017-05-03T02:20:02+02:00 moto kernel: [12055.519363] [] ? mntput_no_expire+0x13/0x130 2017-05-03T02:20:02+02:00 moto kernel: [12055.519451] [] ? path_openat.isra.43+0x146/0x4f0 2017-05-03T02:20:02+02:00 moto kernel: [12055.519542] [] ? free_pages_and_swap_cache+0x9d/0xc0 2017-05-03T02:20:02+02:00 moto kernel: [12055.519636] [] ? do_filp_open+0x2f/0x70 2017-05-03T02:20:02+02:00 moto kernel: [12055.519720] [] ? dput+0x1e/0x2a0 2017-05-03T02:20:02+02:00 moto kernel: [12055.519798] [] ? do_vfs_ioctl+0x20e/0x880 2017-05-03T02:20:02+02:00 moto kernel: [12055.519883] [] ? SyS_ioctl+0x80/0xa0 2017-05-03T02:20:02+02:00 moto kernel: [12055.519959] [] ? system_call_fastpath+0x16/0x1b 2017-05-03T02:20:02+02:00 moto kernel: [12055.520403] Code: 31 c0 48 8d 74 24 20 4c 89 e7 89 44 24 0c e8 54 d3 ba ff 8b 44 24 0c 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 90 53 48 89 fb ff 0f 79 05 e8 b2 0c 00 00 65 48 8b 04 25 c0 a7 00 00 48 89 2017-05-03T02:20:02+02:00 moto kernel: [12055.520836] RIP [] mutex_lock+0x4/0x20 2017-05-03T02:20:02+02:00 moto kernel: [12055.520917] RSP 2017-05-03T02:20:02+02:00 moto kernel: [12055.521000] ---[ end trace f35f665396d7d824 ]--- 2017-05-03T02:20:02+02:00 moto [12055.522175] init: snmpd main process (13921) killed by SEGV signal 2017-05-03T02:20:02+02:00 moto [12055.522334] init: snmpd main process ended, respawning 2017-05-03T02:20:02+02:00 moto [12055.712944] init: snmpd main process (32005) terminated with status 1 2017-05-03T02:20:02+02:00 moto [12055.713056] init: snmpd main process ended, respawning 2017-05-03T02:20:06+02:00 moto synoupgrade_SYNO.Core.Upgrade.Server_1_check[32009]: rssfile.cpp:222 Fail to open [/var/run/autoupdate_tmp_file_RSS] err=No such file or directory 2017-05-03T02:20:06+02:00 moto synoupgrade_SYNO.Core.Upgrade.Server_1_check[32009]: dsmupdate.cpp:192 Fail to parse RSS file 2017-05-03T02:20:06+02:00 moto [12060.364074] init: synosnmpcd main process (32007) killed by KILL signal
It looks like it's complaining about the Core 2 temperature before the SNMP process gets killed. First I though its the CPU it struggles with, but another test VM on the same host works perfect. Going through the SNMP logs I see this:
Guessing that there's a floating point co-processor hrDeviceCoprocessorThat log entry comes from my SATA controller I've added in pass-through so I assume that it sees part of the device as a processor which doesn't properly report temperature.
Any ideas on how to deal with this issue? May changing the VM hardware version change anything? It's currently set to 13 (Esxi 6.5).
Edit: I see that I'm getting this too: "[May 3 20:55] general protection fault: 0000 [#1] SMP"
-
Hi guys.
Anyone else using SNMP for monitoring? While on 5.2 I was using LibreNMS and Grafana to keep track of my NAS and virtual machines, but that's no longer working. After upgrading to Jun's DSM 6.0.2 Loader SNMP doesn't work anymore. The thing is that you can enable it, but it will stop working after just a few minutes. Once it stops, it will also crash the resource monitor (failed to connect errors when opened) and it won't work until you disable SNMP and reboot the NAS.
I'm really eager to figure out what's going on. I'm currently on ESXi 6.5 (the VM is configured as a 6.5 VM) with two 1000e NICs. The NAS has 2 cores and 12GB of memory assigned. The resource manager and everything else works perfect until SNMP is enabled and has been polled/been active for a short while. I'm very interested in other people who also use ESXi. Especially users that have a PCI device in pass-through. Would appreciate any feedback that could help me resolve the issue.
-
From the "DSM 6.0.2 Loader ( was "A new loader for latest DSM")"-thread:
Re: DSM 6.0.2 Loader ( was "A new loader for latest DSM")Postby ggoette » 02 May 2017 04:22
Hi there. New update 6.0.3-8754 is here, I installed it on my "test VM" and I after reboot it enters in recovery because "you move your disks to a new DS3615x".... Any ideas? Thanks
So... not safe to install.
-
I use a LSI SAS 9201-16i which works perfect. The only thing that doesn't work with the card is SNMP.
-
I would advice against using DSM 6.1 just yet as it has a few critical issues according to other posts here. Even DSM 6.0 isn't as stable as DSM 5.2 in my opinion. I would also not recommend to just use any image/export you find online, but stick to Jun's.
Regarding the logs:
Make sure SSH is enabled. Use Putty to login as admin and use "sudo su" in order to elevate to root. Now you can write "tail /var/log/messages" in order to see the last messages. You can also read them in VI by using "vi /var/log/messages" and quit by using ":q!".
-
1
-
-
Ok. There might be a connection, but after playing around with both the memory and cpu cores count it seems random wether the tab page works or not. I guess you're onto something, but it's hard to debug without any useful info in the logs. :/
-
I'm running 6.0.2 with update 11 on ESXi and after a few hours I notice the following issues (it works immidiately after the install/upgrade):
[*]The General tab in the control panel goes blank
I get this error too in 6.1 if I use more cores than the original NAS have.
How many cores do you have configured? I'm using 2 which should be similar to the original if I'm not mistaken. I'm using 8 GB of RAM instead of the default 4. After some more testing it looks almost random if the page shows up or not. I'm totally confused.
-
I'm running 6.0.2 with update 11 on ESXi and after a few hours I notice the following issues (it works immidiately after the install/upgrade):
[*]The General tab in the control panel goes blank
[*]The Resource Manager doesn't work and says "Connection failed"
[*]SNMP reporting stops working
I have set a valid (new) serial number as that was required in order to get PhotoStation to convert videos. Any idea on how to solve the other two remaining issues?
For now I can't find any helpful information in the logs.
Edit: I wonder if this is a bug in SNMP. Once activated it reports for just a few minutes and then stops. After that Resource Manager and the General info can't be launched. Disabling SNMP doesn't resolve it.
-
upgrade from DSM 6.0.2-8451 Update 10 to DSM 6.0.2-8451 Update 11 on ESX 6.5 went without a hitch!
Can you share your VM settings with us? It crashes for me on every try and the general-page is now blank. Not sure what else is broken, but at least something is.
-
I suppose it's a DSM 6.x issue. I have the same issue on 6.0, but not on 5.2.
I have changed my serial and mac to match, but I see that messages.log for some reason still complains about it:
2017-04-24T13:13:25+02:00 moto synoflvconv: synoflvconv.cpp:584 Failed to convert video [/volume1/photo/foo/HDV_0005.MP4] to h.264 mp4. 2017-04-24T13:13:25+02:00 moto synocodectool: G1Licence.cpp:79 Licence not Success,error msg "SN format is wrong." 2017-04-24T13:13:25+02:00 moto synocodectool: SYNOCodecPatentG1.cpp:182 ValidateG1Licence failed 2017-04-24T13:13:27+02:00 moto synocodectool: G1Licence.cpp:79 Licence not Success,error msg "SN format is wrong." 2017-04-24T13:13:27+02:00 moto synocodectool: SYNOCodecPatentG1.cpp:235 ValidateG1Licence failed
Edit: According to another thread here, the serial generator has been updated to work with the new format. Maybe changing the serial will help. I'm not sure whether a re-install is necessary or not. Will try when I get home. Link: https://xpenology.github.io/serial_gene ... r_new.html
-
Thanks so much for the file
however, when I enabled auto convert video to mobile friendly version in Indexing in control panel...
even i'm using the admin account to upload thru network drive
it failed at video converting ...every time..
in the log it shows..
System failed to convert video [/volume1/photo/00000.MTS] to mpeg4.
do you guys experience the same ?
Yes, I have the same problem on 6.0.
Edit: Solved by applying a new serial
-
I'm using ESXi and had to reset the system after the update. After a reboot it seems fine, but after a few hours it starts with some weird issues.
The "General" tab in the Control Panel is now blank: http://i.imgur.com/6wG8Kx6.png
At some times it complains about "Failed to check network status". I'm using the virtual E1000 network nic.
-
Has anyone been able to get Letsencrypt working on DSM6?
Whenever I try to request a new certificate I get the following error: "The operation failed. Please log in to DSM again and retry".
I intend to use a subdomain, so set the domain name to the sub-domain, the email to my email adress and leave the subject alternative name blank.
2017-04-23T16:13:04+02:00 server synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[30687]: certificate.cpp:957 syno-letsencrypt failed. 1 [syno-letsencrypt output is not a json: { "error": 102, "msg": "Invalid response from http://bar.example.com/.well-known/acme-challenge/fVBLH22_kKaVi1uJy-Jjd76cNbae3KXxyQli2wZdnng: " 404 Not Found Not Found ]Edit: I managed to request a certificate by routing port 80 to my NAS. However... when going to ip:5001 it still says that the connection is not secure...
-
Is anyone using Jun's loader on ESXI "in production" or is DSM 5.2 still the most stable?
-
Hi guys,
I haven't been very active on the forum since 5.2 was the latest and greatest. After visiting the forum every now and then I see that finally the source has been released, but there's still no "official"(?) build of XPenology available. I thought about giving DS3615xs 6.0.2 Jun's Mod V1.01 a try, but I miss the changelog and structured user feedback of what's working and what's not in a virtual environment such as ESXi. I have to admit that I use 5.2 in "personal production environment", so I'm still quite skeptical of jumping to 6.0 even though I'm very tempted.
Bugs or missing features I've experienced with DSM 5.2:
[*] The "home" directory disappears from time to time when using CIFS. It's possible to access it using the direct path such as \\192.168.1.2\home\, but it's a bit frustrating
[*] PhotoStation, which I love and use a lot for storing photos struggles often with generating thumbnails. Especially when uploading a photo using the mobile app on Android. What happens is that the thumbnail gets corrupted and when you take a look at it though the webpage, you'll only see maybe half of it while the other half is gray. The photo itself seems unaffected by this bug, but since there's no button available for mass re-generating thumbnails it quickly gets annoying.
[*] Not a bug, but the lack of Let's encrypt is pretty huge deal, especially if you want to use WebDAV over WAN with HTTPS.
So, now for DSM 6.0:
Have many have it successfully running on ESXi? Anyone who has done any kind of performance measurements? I'm very interested in thoughts about BTRFS and pass-through of SATA controllers.
What current bugs have you noticed? Are there any known bugs for version V1.01?
-
I'm also very interested. Maybe it could be quicker if you can share your modified image.
I'll take a look at it tonight as I'm pretty busy at work these days.
-
Is there a better way of hiding the boot drive on ESXI or should I still add rmmod=ata_piix to the list of parameters?
Edit: Doesn't seem to work. I've tried both ata_piix and rmmod=ata_piix as extra arguments
Did you ever manage to hide the boot drive?
Yes, I just converted the image to IDE and appended rrmod. Can't remember the details though, but I will check that once I get the time.
-
Well, thing is that we can boot image (even orginal) under proxmox (KVM). Issue is that we cant find Syno on the network since driver for proxmox vlans (intel e1000 or virito) is missing from boot image. Solution is simple. We need boot image with proxmox intel e1000 or universal Virito lan driver.
I'm using intel e1000 on ESXi and it works. It doesn't show up on find.synology.com, but using the desktop app works.
-
Add ata_piix support, tested on VMware
Nobody who knows how to enable ata_piix? Still struggling to remove the boot drive from showing up in Storage Manager on ESXi.
-
I tried to import the .ovf from DS3615xs 6.0.2 Jun's Mod V1.01 to my ESXi 6u2 server, but i got a 'Failed to deploy' message (IOError). I have downloaded the .zip again (maybe it was corrupt), but i got the same error.
How can i get it working
?Same issue here. Also can't hide the synoboot image from the list of disks if I create the VM manually.
-
Is there a better way of hiding the boot drive on ESXI or should I still add rmmod=ata_piix to the list of parameters?
Edit: Doesn't seem to work. I've tried both ata_piix and rmmod=ata_piix as extra arguments
-
Has anyone gotten ESXi pass through to work with a LSI 9211-8i ? I have tried firmwares p07 p12 p20 and have no success. It works in FreeNAS so I am now stumped. Is there a specific firmware that i need?
I have a LSI SAS 9201-16i and it works like a charm on the latest firmware. Don't see the reason why yours shouldn't... any error messages?
Drivers requests for DSM 5.2
in DSM 5.2 and earlier (Legacy)
Posted
I think there's something wrong with the current mpt2sas-driver.
My card (SAS9201-16i) is supposed to be supported, but I get the following error right after boot finished:
While I can see the drives in DSM (even the SN and temp), I get a lot of error in the logs like this:
And as mentiond in other threads. Kernel panics if I try to turn on SNMP which only happens with this LSI card.