quicknick

XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

Recommended Posts

Hi @quicknick, sorry fo my English

 

I want to offer you, to add into your Config Tool, very userful function. This is a showing default password for synology root logine, you can see code here:

http://codepad.org/naljB5Ze

#include 
#include 
#include 

void main()
{
	struct timeval tvTime;
	struct tm tmOutput;

	gettimeofday(&tvTime, 0);
	localtime_r(&(tvTime.tv_sec), &tmOutput);
	tmOutput.tm_mon += 1;

	printf("password for today is: %x%02d-%02x%02d\n\n",
		tmOutput.tm_mon, tmOutput.tm_mon, tmOutput.tm_mday,
		gcd(tmOutput.tm_mon, tmOutput.tm_mday));
}

int gcd(int a, int b)
{
	return (b?gcd(b,a%b):a);
}

the principle is simple, 8 symbols:

1. month in hex

2,3. month in regular

4. dash

5,6. calendar day in regular

7,8. greatest common divisor between day and month

 

password for today is: c12-1212

 

p.s. this point maybe actual if DSM isn't installed or impossible boot DSM system

I already had this for boot process and after you leave the config tool, but can add it, no problem.

 

Sent from my SM-N920T using Tapatalk

Share this post


Link to post
Share on other sites

Noted the following issues with the tool:

 

HBawKfR.jpg

 

For the vid/pid once I set it, it exits the tool and reverts to the shell

5weCPeK.jpg

vid/pid are set correctly though.

Edited by Guest

Share this post


Link to post
Share on other sites

So after fighting with problem i manage to find VM of DSM on PROXMOX and connect to its SSH! Only problem is that i dont know root password since i dont have log view. Any ideas what to do now ?

 

Plus via web interface i got msg that non of hard drives are instaled (got 3 - one bot with xpenology + 2 sata 32GB test drives) so i cant proceed with DMS instalation.

Edited by Guest

Share this post


Link to post
Share on other sites
Noted the following issues with the tool:

 

HBawKfR.jpg

 

For the vid/pid once I set it, it exits the tool and reverts to the shell

5weCPeK.jpg

Both of these are already fixed in the next release. I knew of number, you even see it in the log file, just haven't uploaded latest bootloader yet so you got old version again. 1 did not know about usb issue, but an easy fix thankfully.

 

Sent from my SM-N920T using Tapatalk

Edited by Guest

Share this post


Link to post
Share on other sites
So after fighting with problem i manage to find VM of DSM on PROXMOX and connect to its SSH! Only problem is that i dont know root password since i dont have log view. Any ideas what to do now ?

 

Plus via web interface i got msg that non of hard drives are instaled (got 3 - one bot with xpenology + 2 sata 32GB test drives) so i cant proceed with DMS instalation.

Go to FAQs and use the pre-compiled dsm-root-password tool on linux.

 

Sent from my SM-N920T using Tapatalk

Share this post


Link to post
Share on other sites
You have to use a private key file to login via ssh as root. you can find it on the first page.

 

Lol didnt see that one, thx for info. Now i have to figure out why DSM dont see HDD's. For some reason XPEnology tool see all the disk but DSM web interface (instalation screen) dont see a single one and ask to connect any. Do you have any tips guys ?

 

Update; in log i can see this when i refresh instaler webgui:

 

Dec 12 15:32:42 raidtool: raidtool.c:358 Failed to find partition layout

Dec 12 15:32:42 synossdcache: ninstaller.c:196 Mount partion /dev/md0 /tmpRoot

Dec 12 15:32:42 synossdcache: ninstaller.c:209 mount partition failed. dev=/dev/md0, path=/tmpRoot

Dec 12 15:32:42 synossdcache: synossdcache.c:29 Fail to mount [/dev/md0] to [/tmpRoot]

 

rFp8FWY.png

 

From Xpenology tool:

List disks:

 

Disk /dev/sdm: 72.4MB

Disk /dev/sdn: 34.4GB

Disk /dev/sdo: 34.4GB

 

 

XPEnology can see 3 drives connected to this system.

 

sdm1 is the boot drive.

 

Sata port mapping:

Current value set to "SataPortMap=444" ( i tried 4 as well 422 - no difrence)

Edited by Guest

Share this post


Link to post
Share on other sites

I am running it in ESXI 5.1 on HP54L. I have manged to configure the bootloader via ssh. But the problem is when I try to install DSM pat file it gives me an error.

 

940dpa9.png

 

Any ideas? I got the pat file from the synology website.

Share this post


Link to post
Share on other sites
I am running it in ESXI 5.1 on HP54L. I have manged to configure the bootloader via ssh. But the problem is when I try to install DSM pat file it gives me an error.

 

940dpa9.png

 

Any ideas? I got the pat file from the synology website.

 

Make sure your PID/VID is correct, this is a known problem. The setup assistant will not recognise any DSM firmware if it cannot verify where the install disk is physically on your system. Read quicknick's instructions on how to find your IDs http://xpenology.com/forum/viewtopic.php?f=2&t=24308

 

Both should be formatted in along the lines of 0x0000.

Share this post


Link to post
Share on other sites
looks very good so far.

 

I had 2-3 problems with the "old" bootloader from Jun.

 

1. power-button did not work (i read some fixes, never tried).

2. CPU seems not to throttle down (Arock E350M1/USB3, i think i read something about a fix).

 

3. worst off all for me, allthough disk hilbernation works and autoshutdown of NAS after XX min works too, the box shuts down in S5 mode (completely off). I would really prefer STR, Supend-to-RAM power state S3.

 

Any of it fixed in this bootloader?

Or have these things nothing to do with the bootloader?

 

I read fixes for 1 an 2. Never read anything about S3 power state.

Has anyone a idea how to get the machine to shutdown to suspend to RAM mode?

1 and 2 are included. Uncertain of 3.

 

Sent from my SM-N920T using Tapatalk

 

thanks!

I will try your bootloader and report results here.

 

Is there any chance of setting the sleep-State of xpenology via SSH or anything?

Share this post


Link to post
Share on other sites

Expect this;

[spoiler=]

You have to use a private key file to login via ssh as root. you can find it on the first page.

 

Lol didnt see that one, thx for info. Now i have to figure out why DSM dont see HDD's. For some reason XPEnology tool see all the disk but DSM web interface (instalation screen) dont see a single one and ask to connect any. Do you have any tips guys ?

 

Update; in log i can see this when i refresh instaler webgui:

 

Dec 12 15:32:42 raidtool: raidtool.c:358 Failed to find partition layout

Dec 12 15:32:42 synossdcache: ninstaller.c:196 Mount partion /dev/md0 /tmpRoot

Dec 12 15:32:42 synossdcache: ninstaller.c:209 mount partition failed. dev=/dev/md0, path=/tmpRoot

Dec 12 15:32:42 synossdcache: synossdcache.c:29 Fail to mount [/dev/md0] to [/tmpRoot]

 

rFp8FWY.png

 

From Xpenology tool:

List disks:

 

Disk /dev/sdm: 72.4MB

Disk /dev/sdn: 34.4GB

Disk /dev/sdo: 34.4GB

 

 

XPEnology can see 3 drives connected to this system.

 

sdm1 is the boot drive.

 

Sata port mapping:

Current value set to "SataPortMap=444" ( i tried 4 as well 422 - no difrence)

 

 

 

I finded new issue/bug. With mounted Dell H310 (it mode - flashed to LSI) with vt-d kernell wont load fully (no vm in network) - In old xpenology this works without issue.

Share this post


Link to post
Share on other sites

Mainboard: MSI Z77A-GD65 (Z77 chipset)

CPU: Intel i7 2600k

RAM: 4x4GB DDR3 1333 Kingston HyperX

NIC: onboard Intel 82579V

SAS: LSI 9207-8i (FW: 19.0 IT/IR)

 

Last used & working DSM/loader: DSM 6.0.2-8451 Update 6 with Jun's loader V1.01

 

HDDs: 6x2TB onboard Intel [RAID 5, btrfs, 1x volume of 9TB], 4x1 TB on LSI [RAID 5, btrfs, 1x volume of 2,7TB)

 

Problem: crashed volumes

 

I did the following:

 

1.) Prepared an USB drive with the image of config tool V2.2 and let the system boot

2.) Choosed the config tool from boot menu and connected via ssh

3.) Let the system generate VID/PID/...

4.) Set S-ATA portmap to prior settings (628; 6x onboard Intel, 2x onboard Marvell, 8x LSI)

5.) Updated the config tool to V2.3

6.) Tried to reboot the system via ssh - no luck (waited for around 35 mins -> reset)

7.) Selected 1st entry from boot menu and connected via browser

8.) DSM stated "Attention! Your volume crashed"

 

DSM now only "sees" the first volume which consists of the 6x2TB HDDs connected to the onboard controller in AHCI mode. The second volume isn't recognized anymore (connected to the LSI). DSM doesn't offer a repair option. I tried to reboot and choosed the config tool again -> Troubleshooting... Only the 6x2TB HDDs are shown.

 

Now I'm currently trying to repair the installation with my "old" boot stick and Jun's V1.01 (good to know that I've a fresh backup of all files).

Share this post


Link to post
Share on other sites
Mainboard: MSI Z77A-GD65 (Z77 chipset)

5.) Updated the config tool to V2.3

 

Wait, Quicknick has released v.2.3 of his tool?

Share this post


Link to post
Share on other sites
Wait, Quicknick has released v.2.3 of his tool?

 

Yes, as stated during the update process.

Share this post


Link to post
Share on other sites
Wait, Quicknick has released v.2.3 of his tool?

 

Yes, as stated during the update process.

 

I'm not sure how official it is since he hasn't updated his downloads post yet, he did say he'd be working on 2.3 tomorrow during his 3.5hr flight.

Share this post


Link to post
Share on other sites
Wait, Quicknick has released v.2.3 of his tool?

 

Yes, as stated during the update process.

 

Would you mind sharing 2.3 so I can test if it loads NIC drivers on my HP DL180 G6?

Share this post


Link to post
Share on other sites
Wait, Quicknick has released v.2.3 of his tool?

 

Yes, as stated during the update process.

Those are just updated changelogs, actual downloads are not available for update yet.

Share this post


Link to post
Share on other sites
I am running it in ESXI 5.1 on HP54L. I have manged to configure the bootloader via ssh. But the problem is when I try to install DSM pat file it gives me an error.

 

940dpa9.png

 

Any ideas? I got the pat file from the synology website.

 

Make sure your PID/VID is correct, this is a known problem. The setup assistant will not recognise any DSM firmware if it cannot verify where the install disk is physically on your system. Read quicknick's instructions on how to find your IDs http://xpenology.com/forum/viewtopic.php?f=2&t=24308

 

Both should be formatted in along the lines of 0x0000.

 

My question regarding this is, if you're installing it from VMWare you wont have any USB stick plugged in - did i miss something?

Share this post


Link to post
Share on other sites

My question regarding this is, if you're installing it from VMWare you wont have any USB stick plugged in - did i miss something?

 

Ah you may be correct, only when USB booting you need a VID/PID. Have you not tried deploying the OVF file specific for VMware?

Share this post


Link to post
Share on other sites
Ah you may be correct, only when USB booting you need a VID/PID. Have you not tried deploying the OVF file specific for VMware?

 

I tried everything to get the damn thing to install, resorted to using Jun's loader in the end which worked for me.

 

I'm sure QuickNick will fix these problems with 2.3 :smile:

Share this post


Link to post
Share on other sites

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]

Share this post


Link to post
Share on other sites

Any news about the loader compatibility on old hardware without AHCI mode? I'm running an old HP Compaq DC 5700 and xpenology used to work with the old 5.xx loader but no way to boot the new ones. :sad:

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.