alirz1

I had read that the 6.x loader uses synology model that didn't support SHR raid. Is that still true? If I do a new install using xpe 6.0.2 update 7. Would I be able to use SHR . Thanks

Hello Everyone, i currently have a xpenology DSM 5.2 setup. I would like to upgrade the motherboard/cpu/ram in the system. Given that all drivers are included in xpenology, could i simply swap out those components in my system and plug the hdds in the same sata port sequence, without the system messing up or anything? By the way for now i would be keeping the same versoin of xpenology/dsm etc... not touching that for the moment. I just want to upgrade the hardware for now.

I'm looking to get the ASROCK q1900 board to setup a second xpenology. As per my searches here the board looks to be supported. My plan is to use for DSM 5.2 for now. In the xpenology compatibility matrix it shows as below. Does it mean that the SATA controller is NOT supported in DSM 5.2? but only in higher version of DSM like 6.x? Asmedia ASM-106x SATA/SAS 2 YES , NO (dsm5.2)

Hi, Im currently using the xpenolog 5.2 loader from mid last year on my barebone setup. Its an intel system(motherboard:DQ45EK) with an onboard NIC (Intel 82567LM Gigabit chipset i believe). MB specs: https://downloadmirror.intel.com/16959/ ... nglish.pdf I wanted to give dsm 6 a show. So i burnt the Jun 1.01 loader to the USB. Now i have tested that usb stick on my desktop pc and it is bootable for sure. However the barebone system doesnt seem to be getting a network link. As my router uses static ip assignment and im not able to ping the IP. From what i've found here, the NIC is supported. UPDATE: figured it out. Had to set to BIOS to use UEFI boot instead of legacy...

Hello Everyone, I'm currently running DSM 5.2 latest update with xpenology 5.2-5967.1 loader. I need to add more drives to my setup and im looking for a PCI 1x SATA expansion card. Not really looking for one with a RAID controller, just need more sata ports. Should any sata expansion card work as im not looking to support raid controller drivers? Im looking at something like this: http://www.ebay.com/itm/4-port-SATA-III ... SwCypWoOXY its a Marvel 88SE91XX chipset Thanks

Please add support for the following SATA controllers. I'm unable to find any info as to if these are already support in 2.3 or not. Intel C2550 Marvell SE9172 Marvell SE9230

Hello, SATA Controller: Marvell SE9172 I looked on the first page in the supported drivers list but i could not find it. I've been eyeing the "ASRock AD2550R" board and looks thats the sata controller on it. LAN is in the supported list though. possibility to add it in a future release. Thanks

I hope all these new requests are being taken for subsequent releases..otherwise 2.3 is going to keep getting delayed

I'm interested in the answer to this also. I ran into a similar issue. Perhaps this is something to do with sataportmap"?

So i spun up a baremetal box with the current xpenology bootloader adn DS 6.0.2. Everything seems to work fine except that i cannot create a BTRFS volume. It crashes upon creation. EXT4 seems to be working fine, Is this a known issue?

I just spun up the VM. The ssh login via the private key is being refused. Can someone please provide the root password? I dont know what was the need to complicate console access so much for this! PS: I cant get the serial connection to work...Im currently running the VM in virtual box because Vmware workstation gives kernel panic

I tried giving the 2.2 bootloader VM a shot on my windows 10 PC running Workstation 12 but im getting kernel panic after boot: i guess ill wait for 2.3 and see if it somehow resolves the issue. [ 5.031010] IP: [< (null)>] (null) [ 5.031320] PGD 139580067 PUD 132b24067 PMD 0 [ 5.031729] Oops: 0010 [#1] SMP [ 5.031746] Modules linked in: el000(O) [ 5.031762] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G O 3.10.77 #8451 [ 5.032725] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B32.1507021939 07/02/2015 [ 5.033724] task: ffff88013a0ff510 ti: ffff88013a100000 task.ti: ffff88013a100000 [ 5.034727] RIP: 0010:[<0000000000000000>] [< (null)>] (null) [ 5.035724] RSP: 0000:ffff88013a103e48 EFLAGS: 00010046 [ 5.036726] RAX: ffffffff81ab0240 RBX: ffff880135d0e800 RCX: 0000000000000000 [ 5.037726] RDX: ffff88013a103e80 RSI: ffff880135d0e800 RDI: ffff88013a103e78 [ 5.038725] RBP: ffff88013a103ee0 R08: ffffffff81853460 R09: 0000000000000000 [ 5.039725] R10: ffff880135d0e800 R11: 3030322038302e30 R12: 0000000000000000 [ 5.040728] R13: ffffffff81853460 R14: 0000000000000000 R15: 0000000000000000 [ 5.041725] FS: 0000000000000000(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000 [ 5.042724] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 5.043724] CR2: 0000000000000000 CR3: 0000000132bc5000 CR4: 00000000000407e0 [ 5.044727] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 5.045723] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 5.046728] Stack: [ 5.046748] ffffffff813c1a5e ffff880139817898 0000000000000000 ffffffff813c26f0 [ 5.047723] 0001880100000000 ffffffff81ab0240 0000000000000400 ffff880132b69458 [ 5.048722] ffff88013a22f800 0000000000000000 0000000000000000 0000000000000000 [ 5.049722] Call Trace: [ 5.049760] [] ? efivar_init+0x8e/0x2f0 [ 5.050731] [] ? efivar_update_sysfs_entries+0x60/0x60 [ 5.051736] [] ? kset_register+0x50/0x60 [ 5.051771] [] ? efivars_sysfs_init+0x73/0x200 [ 5.052739] [] ? heartbeat_trig_init+0x32/0x36 [ 5.053729] [] ? efivar_create+0x150/0x150 [ 5.054739] [] ? do_one_initcall+0xea/0x140 [ 5.054771] [] ? kernel_init_freeable+0x13a/0x1bb [ 5.055741] [] ? rest_init+0x70/0x70 [ 5.056731] [] ? kernel_init+0x5/0x180 [ 5.056761] [] ? ret_from_fork+0x58/0x90 [ 5.057730] [] ? rest_init+0x70/0x70 [ 5.057750] Code: Bad RIP value. [ 5.057769] RIP [< (null)>] (null) [ 5.057788] RSP [ 5.057808] CR2: 0000000000000000 [ 5.057827] ---[ end trace bff46408c820fbeb ]--- [ 5.058732] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 5.058732]

Ok i still do see the following error after very reboot of the xpenology. I havent experienced any problems with the system so i dont know if these errors are "normal" for my box or not Aug 24 22:09:28 nas root: == DSM finished boot up == Aug 24 22:09:29 nas transmission-daemon[21868]: UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84) Aug 24 22:09:29 nas transmission-daemon[21868]: UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95) Aug 24 22:09:31 nas kernel: [ 32.126188] pin 45 is protected by driver. Aug 24 22:09:31 nas kernel: [ 32.126270] BUG: unable to handle kernel paging request at 0000000000002c81 Aug 24 22:09:31 nas kernel: [ 32.126273] IP: [] syno_mv_9235_disk_led_set+0x27/0xd0 Aug 24 22:09:31 nas kernel: [ 32.126280] PGD 1336d1067 PUD 130641067 PMD 0 Aug 24 22:09:31 nas kernel: [ 32.126283] Oops: 0000 [#1] SMP Aug 24 22:09:31 nas kernel: [ 32.126363] CPU: 0 PID: 18698 Comm: scemd Tainted: P C O 3.10.35 #1 Aug 24 22:09:31 nas kernel: [ 32.126365] Hardware name: /DQ45EK, BIOS CBQ4510H.86A.0133.2011.0810.1010 08/10/2011 Aug 24 22:09:31 nas kernel: [ 32.126367] task: ffff88013623d080 ti: ffff880135e44000 task.ti: ffff880135e44000 Aug 24 22:09:31 nas kernel: [ 32.126368] RIP: 0010:[] [] syno_mv_9235_disk_led_set+0x27/0xd0 Aug 24 22:09:31 nas kernel: [ 32.126372] RSP: 0018:ffff880135e47d18 EFLAGS: 00010202 Aug 24 22:09:31 nas kernel: [ 32.126373] RAX: ffff880132b32800 RBX: 0000000000000000 RCX: ffff880132b32b30 Aug 24 22:09:31 nas kernel: [ 32.126375] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff880132b32800 Aug 24 22:09:31 nas kernel: [ 32.126376] RBP: 0000000000000000 R08: 0000000000000009 R09: 0000000000000001 Aug 24 22:09:31 nas kernel: [ 32.126378] R10: 00000000f7784430 R11: 0000000000000000 R12: ffff8801313336c0 Aug 24 22:09:31 nas kernel: [ 32.126379] R13: 0000000000000009 R14: 0000000000000001 R15: 0000000000000000 Aug 24 22:09:31 nas kernel: [ 32.126381] FS: 0000000000000000(0000) GS:ffff88013bc00000(0063) knlGS:00000000f49e0b70 Aug 24 22:09:31 nas kernel: [ 32.126382] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 Aug 24 22:09:31 nas kernel: [ 32.126384] CR2: 0000000000002c81 CR3: 000000013065c000 CR4: 00000000000007f0 Aug 24 22:09:31 nas kernel: [ 32.126385] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 24 22:09:31 nas kernel: [ 32.126387] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Aug 24 22:09:31 nas kernel: [ 32.126388] Stack: Aug 24 22:09:31 nas kernel: [ 32.126389] 0000000000000008 ffffffffa0c85c78 ffffffffffffffff 00000000f49e0038 Aug 24 22:09:31 nas kernel: [ 32.126392] ffff8801313336c0 ffffffffa0c825a4 ffffffff81862788 ffff880135e47de0 Aug 24 22:09:31 nas kernel: [ 32.126394] ffff8801362b9000 0000000000000009 00000000ffffff9c 00000000ffffff9c Aug 24 22:09:31 nas kernel: [ 32.126397] Call Trace: Aug 24 22:09:31 nas kernel: [ 32.126403] [] ? SetSCSIHostLedStatusBy9235GPIOandAHCISGPIO+0x68/0x100 [bromolow_synobios] Aug 24 22:09:31 nas kernel: [ 32.126406] [] ? synobios_ioctl+0xe54/0x1090 [bromolow_synobios] Aug 24 22:09:31 nas kernel: [ 32.126411] [] ? filename_lookup+0x2c/0xb0 Aug 24 22:09:31 nas kernel: [ 32.126413] [] ? getname_flags.part.31+0x84/0x130 Aug 24 22:09:31 nas kernel: [ 32.126416] [] ? user_path_at_empty+0xa0/0x120 Aug 24 22:09:31 nas kernel: [ 32.126420] [] ? sysfs_getattr+0x4b/0x60 Aug 24 22:09:31 nas kernel: [ 32.126422] [] ? dput+0x22/0x1b0 Aug 24 22:09:31 nas kernel: [ 32.126426] [] ? compat_sys_ioctl+0x1e7/0x1500 Aug 24 22:09:31 nas kernel: [ 32.126429] [] ? sys32_stat64+0x10/0x30 Aug 24 22:09:31 nas kernel: [ 32.126433] [] ? sysenter_dispatch+0x7/0x21 Aug 24 22:09:31 nas kernel: [ 32.126434] Code: 1f 44 00 00 53 0f b7 ff 89 f3 e8 25 7a f9 ff 48 85 c0 48 89 c7 0f 84 a0 00 00 00 48 8b 90 f8 04 00 00 48 Aug 24 22:09:31 nas kernel: [ 32.126455] RIP [] syno_mv_9235_disk_led_set+0x27/0xd0 Aug 24 22:09:31 nas kernel: [ 32.126458] RSP Aug 24 22:09:31 nas kernel: [ 32.126459] CR2: 0000000000002c81 Aug 24 22:09:31 nas kernel: [ 32.126462] ---[ end trace 3c9d101388eea937 ]--- Seems like DSM wants to set the LED status for the drive status but obviously i have no leds here. So im thinking this is somewhat normal and can be ignored safely?

issue turned out to be due to incorrect SATA mode set in the BIOS. sata mode was set to IDE. Setting to AHCI got rid of the erros

So i switched the SATA mode to ACHI and have rebuilt the xpenology from scratch. Good news is that the ata_piix error is gone. The boot process doesnt hang at ata_piix BUSY now!!!! awesome. Also, no more of those " WANT IDX INDEX" error in the messages log.. Also Awesome. For now i've only connected two hdds to the system on sata port 1+2. The other two drives are unplugged. Real test would e to use the system like this for a day and see if it freezes. hopefully not as i dont see why it should now. There are no panics in the log anymore. So in a day or two ill connect the other two drives and set them up and report back.

Thank you very much for your very detail and informing post. Yes you were indeed correct on the SATA mode. It was set to IDE. instead of being AHCI.I'm not sure when this got changed because i've been using this setup for several months and only started experiencing problems when i started using a RAID 0 setup that was done in DSM. Here is the hard and other info: Hardware: Intel motherboard DQ45EK, BIOS CBQ4510H.86A.0133.2011.0810.1010 08/10/2011 (its a pretty old board). CPU: Intel core 2 duo (2.4 GHZ i believe) 4GB ram No add in cards. HDD: 4x3TB Sata Western digital RED. The board has 4 SATA ports. The mother board also support RAID but im not using it. Its very likely that two of the four ports are for the sata controller as is usually the case. however that shouldn't be causing an issue unless the current IDE SATA mode is having some problem with that. I will soon, switch to AHCI and start everything from scratch.

Hello, I recently wiped my xpenology NAS clean and wanted to do a brand new setup from scratch. Once i did that three days ago. Its gone into this strange mode where it has become unresponsive, ping works but no other service is working. I can sometimes log into the DSM but cant really do anything, its like a ghost web process is making the DSM run and thats about it. I then looked into /var/log/messages and noticed the following: Aug 24 08:37:45 nas kernel: [39206.420031] ------------[ cut here ]------------ Aug 24 08:37:45 nas kernel: [39206.420039] WARNING: at drivers/ata/libata-core.c:5428 ata_qc_issue+0x2a6/0x3e0() Aug 24 08:37:45 nas kernel: [39206.420145] CPU: 1 PID: 21689 Comm: sshd Tainted: P C O 3.10.35 #1 Aug 24 08:37:45 nas kernel: [39206.420147] Hardware name: /DQ45EK, BIOS CBQ4510H.86A.0133.2011.0810.1010 08/10/2011 Aug 24 08:37:45 nas kernel: [39206.420149] ffffffff8151f517 0000000000000000 ffffffff81039c9a ffff88013164c000 Aug 24 08:37:45 nas kernel: [39206.420152] 0000000000000003 ffff88013164dc50 ffffffff813b7b50 ffff88013164c000 Aug 24 08:37:45 nas kernel: [39206.420155] ffffffff813b0ad6 ffff880131662a80 ffff88013164c218 0000000000000000 Aug 24 08:37:45 nas kernel: [39206.420158] Call Trace: Aug 24 08:37:45 nas kernel: [39206.420163] [] ? dump_stack+0xd/0x17 Aug 24 08:37:45 nas kernel: [39206.420168] [] ? warn_slowpath_common+0x6a/0xa0 Aug 24 08:37:45 nas kernel: [39206.420171] [] ? ata_scsi_set_sense.constprop.33+0x30/0x30 Aug 24 08:37:45 nas kernel: [39206.420174] [] ? ata_qc_issue+0x2a6/0x3e0 Aug 24 08:37:45 nas kernel: [39206.420177] [] ? ata_scsi_rw_xlat+0x168/0x210 Aug 24 08:37:45 nas kernel: [39206.420180] [] ? ata_scsi_set_sense.constprop.33+0x30/0x30 Aug 24 08:37:45 nas kernel: [39206.420183] [] ? ata_scsi_translate+0x9f/0x170 Aug 24 08:37:45 nas kernel: [39206.420186] [] ? ata_scsi_queuecmd+0x1eb/0x460 Aug 24 08:37:45 nas kernel: [39206.420190] [] ? internal_add_timer+0x18/0x50 Aug 24 08:37:45 nas kernel: [39206.420194] [] ? scsi_dispatch_cmd+0xd1/0x340 Aug 24 08:37:45 nas kernel: [39206.420197] [] ? scsi_request_fn+0x2d4/0x4b0 Aug 24 08:37:45 nas kernel: [39206.420201] [] ? __blk_run_queue+0x2a/0x40 Aug 24 08:37:45 nas kernel: [39206.420204] [] ? queue_unplugged.isra.58+0xe/0x30 Aug 24 08:37:45 nas kernel: [39206.420206] [] ? blk_flush_plug_list+0x1b9/0x210 Aug 24 08:37:45 nas kernel: [39206.420209] [] ? blk_finish_plug+0xb/0x30 Aug 24 08:37:45 nas kernel: [39206.420213] [] ? __do_page_cache_readahead+0x1bd/0x250 Aug 24 08:37:45 nas kernel: [39206.420216] [] ? ra_submit+0x1c/0x30 Aug 24 08:37:45 nas kernel: [39206.420219] [] ? filemap_fault+0x229/0x480 Aug 24 08:37:45 nas kernel: [39206.420223] [] ? __do_fault+0x6e/0x4f0 Aug 24 08:37:45 nas kernel: [39206.420226] [] ? handle_pte_fault+0xab/0x9a0 Aug 24 08:37:45 nas kernel: [39206.420229] [] ? kmem_cache_alloc+0xd8/0xe0 Aug 24 08:37:45 nas kernel: [39206.420232] [] ? __do_page_fault+0x1af/0x460 Aug 24 08:37:45 nas kernel: [39206.420236] [] ? alloc_file+0x26/0xe0 Aug 24 08:37:45 nas kernel: [39206.420239] [] ? sock_alloc_file+0x9a/0x130 Aug 24 08:37:45 nas kernel: [39206.420243] [] ? __fd_install+0x23/0x60 Aug 24 08:37:45 nas kernel: [39206.420246] [] ? SyS_socketpair+0x152/0x210 Aug 24 08:37:45 nas kernel: [39206.420249] [] ? page_fault+0x28/0x30 Aug 24 08:37:45 nas kernel: [39206.420252] ---[ end trace 28d794b310603a79 ]--- One thing i want to point out is that (another thread was opened but got no help there) during the xpenology boot process, it hangs at the "ata_piix" process in state BUSY for at least 1 minute. After the boot has completed, the messages log shows a lot of entries like " Aug 24 09:12:41 nas kernel: [ 5.225718] want_idx 0 index 1. delay and reget Aug 24 09:12:41 nas kernel: [ 6.225007] want_idx 0 index 1 Aug 24 09:12:41 nas kernel: [ 6.225011] want_idx 0 index 1. delay and reget Aug 24 09:12:41 nas kernel: [ 7.225004] want_idx 0 index 1 Aug 24 09:12:41 nas kernel: [ 7.225006] want_idx 0 index 1. delay and reget Aug 24 09:12:41 nas kernel: [ 8.225005] want_idx 0 index 1 Aug 24 09:12:41 nas kernel: [ 8.225006] want_idx 0 index 1. delay and reget Aug 24 09:12:41 nas kernel: [ 9.225004] want_idx 0 index 1 Aug 24 09:12:41 nas kernel: [ 9.225006] want_idx 0 index 1. delay and reget Not sure if its relates somehow...I think i only started noticing these error when i added two NEW additional drives to the system. Previously i only had two drives. Now im running two disk groups with 2disks in each group with in RAID 0. Possibly Xpenelogy having issue support the ata controller with 4 drives or something? I have done a smart check on all my drives and they are fine.

Hello, I have been using xpenology's 5.2-5644.5 build for several months without any problem. Three days ago i decided to add two more disks to the system (total of 4 now) and decided to setup two disk groups in DSM with two disks in each group with RAID 0. All 4 disks are WD 3TB each in size. For this i had to drop all the volume, for some reason i had to force install DSM from scratch also... Today i experienced a loss of connection to the box so i had to power cycle it. Power cycle seemed to take a little bit longer before the synology was accessible. I decided to check /var/log/messages log and noticed some messages that dont look normal. Primary concern is the obvious "want_idx 1 index" error and the " invalid raid superblock magic on sda3" error. Would someone please help me in determining what these mean. All my drives are in good shape, no bad sectors or anything. The RAID setup was done in synology DSM. One thing to point out is that, i currently do not see "/volume" when i do a df-h. However i can change directory into /volume1 and browse all my data etc. DSM also reports NO problems with the setup. Finally, would upgrading to XPEnoboot 5.2-5967.1 (17/07/2016) help as i see official support the last 5.2 DSM My xpenology box is an old intel core2 duo with an intel board. These errors are recent and i had not noticed this problem before. g 22 19:13:45 nas kernel: [ 2.429966] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Aug 22 19:13:45 nas kernel: [ 3.067701] Unknown LPC device 3a14 Aug 22 19:13:45 nas kernel: [ 3.067705] ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20130328/utaddress-251) Aug 22 19:13:45 nas kernel: [ 3.067712] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20130328/utaddress-251) Aug 22 19:13:45 nas kernel: [ 3.067717] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20130328/utaddress-251) Aug 22 19:13:45 nas kernel: [ 3.067722] lpc_ich: Resource conflict(s) found affecting gpio_ich Aug 22 19:13:45 nas kernel: [ 3.127389] coretemp coretemp.0: Using relative temperature scale! Aug 22 19:13:45 nas kernel: [ 3.127400] coretemp coretemp.0: Using relative temperature scale! Aug 22 19:13:45 nas kernel: [ 4.337361] P0 P2 P1 P3 ] Aug 22 19:13:45 nas kernel: [ 4.348246] P0 -- P1 -- ] Aug 22 19:13:45 nas kernel: [ 5.140065] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 6.140007] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 6.140011] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 7.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 7.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 8.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 8.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 9.140005] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 9.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 10.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 10.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 11.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 11.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 12.140005] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 12.140007] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 13.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 13.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 14.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 14.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 15.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 15.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 16.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 16.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 17.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 17.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 18.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 18.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 19.140004] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 19.140006] want_idx 0 index 1. delay and reget Aug 22 19:13:45 nas kernel: [ 20.140005] want_idx 0 index 1 Aug 22 19:13:45 nas kernel: [ 20.142735] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 21.142009] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 21.142013] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 22.142005] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 22.142007] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 23.142004] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 23.142006] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 24.142011] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 24.142013] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 25.142006] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 25.142008] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 26.142004] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 26.142006] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 27.142005] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 27.142006] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 28.142010] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 28.142012] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 29.142014] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 29.142016] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 30.142004] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 30.142006] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 31.142004] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 31.142006] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 32.142010] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 32.142012] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 33.142014] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 33.142016] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 34.142004] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 34.142006] want_idx 1 index 2. delay and reget Aug 22 19:13:45 nas kernel: [ 35.142004] want_idx 1 index 2 Aug 22 19:13:45 nas kernel: [ 35.158821] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 36.158007] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 36.158010] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 37.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 37.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 38.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 38.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 39.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 39.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 40.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 40.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 41.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 41.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 42.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 42.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 43.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 43.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 44.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 44.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 45.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 45.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 46.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 46.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 47.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 47.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 48.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 48.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 49.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 49.158006] want_idx 1 index 3. delay and reget Aug 22 19:13:45 nas kernel: [ 50.158004] want_idx 1 index 3 Aug 22 19:13:45 nas kernel: [ 50.361964] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014. Aug 22 19:13:45 nas kernel: [ 50.457378] md: invalid raid superblock magic on sda3 Aug 22 19:13:45 nas kernel: [ 50.457381] md: sda3 does not have a valid v0.90 superblock, not importing! Aug 22 19:13:45 nas kernel: [ 50.505627] md: invalid raid superblock magic on sdb3 Aug 22 19:13:45 nas kernel: [ 50.505630] md: sdb3 does not have a valid v0.90 superblock, not importing! Aug 22 19:13:45 nas kernel: [ 50.561990] md: invalid raid superblock magic on sdc3 Aug 22 19:13:45 nas kernel: [ 50.561993] md: sdc3 does not have a valid v0.90 superblock, not importing! Aug 22 19:13:45 nas kernel: [ 50.614195] md: invalid raid superblock magic on sdd3 Aug 22 19:13:45 nas kernel: [ 50.614197] md: sdd3 does not have a valid v0.90 superblock, not importing! Aug 22 19:13:45 nas kernel: [ 50.614215] md: sda2 has different UUID to sda1 Aug 22 19:13:45 nas kernel: [ 50.614222] md: sdb2 has different UUID to sda1 Aug 22 19:13:45 nas kernel: [ 50.614228] md: sdc2 has different UUID to sda1 Aug 22 19:13:45 nas kernel: [ 50.614235] md: sdd2 has different UUID to sda1 Aug 22 19:13:45 nas kernel: [ 50.837936] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after Aug 22 19:13:45 nas kernel: [ 50.941999] bromolow_synobios: module license 'Synology Inc.' taints kernel. Aug 22 19:13:45 nas kernel: [ 50.942006] Disabling lock debugging due to kernel taint Aug 22 19:13:45 nas kernel: [ 50.942401] 2016-8-22 23:13:38 UTC Aug 22 19:13:45 nas kernel: [ 50.942409] Brand: Synology Aug 22 19:13:45 nas kernel: [ 50.942412] Model: DS-3615xs Aug 22 19:13:45 nas kernel: [ 50.942414] set group disks wakeup number to 4, spinup time deno 7 Aug 22 19:13:45 nas kernel: [ 50.950790] synobios: unload Aug 22 19:13:45 nas kernel: [ 51.687248] EXT4-fs (md0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 Aug 22 19:13:45 nas kernel: [ 56.553732] EXT4-fs (md0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1 Creating /dev/synoboot1... Creating /dev/synoboot2... Aug 22 19:13:47 nas s70_synocheckhw: external/external_fan_adjust_config_full_speed.c:90 Cannot find HIGH fan table. Aug 22 19:13:47 nas umount: can't umount /initrd: Invalid argument Aug 22 19:13:48 nas kernel: [ 61.396733] zram: module is from the staging directory, the quality is unknown, you have been warned. Aug 22 19:13:48 nas [ 61.495180] init: syno-auth-check main process (12880) killed by TERM signal Aug 22 19:13:48 nas synoexternal: write to uart2 error, error=(5)Input/output error insmod: can't insert '/lib/modules/aesni-intel.ko': No such device insmod: can't insert '/lib/modules/crc32c-intel.ko': No such device Aug 22 19:13:49 nas kernel: [ 62.169646] i2c_algo_bit: exports duplicate symbol i2c_bit_add_bus (owned by kernel) insmod: can't insert '/lib/modules/i2c-algo-bit.ko': invalid module format Aug 22 19:13:49 nas kernel: [ 62.324738] 2016-8-22 23:13:49 UTC Aug 22 19:13:49 nas kernel: [ 62.324746] Brand: Synology Aug 22 19:13:49 nas kernel: [ 62.324748] Model: DS-3615xs Aug 22 19:13:49 nas kernel: [ 62.324751] set group disks wakeup number to 4, spinup time deno 7 Aug 22 19:13:49 nas synonetseqadj: synonetseqadj.c:312 Error internal NIC devices 1 does not equal to internal NIC number 4 Aug 22 19:13:49 nas interface-catcher: eth0 (dhcp) is added Aug 22 19:13:49 nas interface-catcher: lo (inet 127.0.0.1 netmask 255.0.0.0 ) is added Aug 22 19:13:50 nas dhcp-client: started on eth0 Aug 22 19:13:51 nas spacetool.shared: raid_allow_rmw_check.c:48 fopen failed: /usr/syno/etc/.rmw.md4 Aug 22 19:13:51 nas spacetool.shared: raid_allow_rmw_check.c:48 fopen failed: /usr/syno/etc/.rmw.md2 Aug 22 19:13:51 nas spacetool.shared: spacetool.c:2835 [info] Old vg path: [/dev/vg2], New vg path: [/dev/vg2], UUID: [HP9HrN-JDWG-KVZH-Ec3O-HVkE-FUdZ-XuxMvT] Aug 22 19:13:51 nas spacetool.shared: spacetool.c:2835 [info] Old vg path: [/dev/vg1], New vg path: [/dev/vg1], UUID: [hviZLe-2Uk7-lfPq-RXgv-7w25-Jx6Y-CqlUIW] Aug 22 19:13:51 nas spacetool.shared: spacetool.c:2842 [info] Activate all VG Aug 22 19:13:51 nas spacetool.shared: spacetool.c:2853 Activate LVM [/dev/vg2] Aug 22 19:13:51 nas spacetool.shared: spacetool.c:2853 Activate LVM [/dev/vg1] Aug 22 19:13:52 nas spacetool.shared: spacetool.c:2896 space: [/dev/vg2] Aug 22 19:13:52 nas spacetool.shared: spacetool.c:2896 space: [/dev/vg1] Aug 22 19:13:52 nas spacetool.shared: spacetool.c:2922 space: [/dev/vg1], ndisk: [2] Aug 22 19:13:52 nas spacetool.shared: spacetool.c:2922 space: [/dev/vg2], ndisk: [2]

I've deployed the VM from the very post in this thread. After waiting for a few minutes when the VM does become available through http://findsysnology.com Its promting me to setup and then install the DSM solftware? Is that normal. I though the VM would have that already.