[DSM 6.1.x Loader]

C'mon, ppl, this is not the time to be silent! Please, tell me how to fix this. Is there a new image I need to download?

 

P.S. I *knew* not having a terminal console would come to bite me in the ass one day!

[DSM 6.1.x Loader]

Yes, Update 9 totally hosed my machine. It won't reboot, and even after a hard reset won't come back.

[DSM 6.1.x Loader]

Updated to DSM 6.0.2-8451 Update 3 on my N54L > No problem !

 

Thanks for the confirmation! Worked flawlessly, indeed!

[DSM 6.1.x Loader]

DSM 6.0.2-8451 Update 3 is ready. Is it safe to update to this?!

[DSM 6.1.x Loader]

Regarding the unclean shutdown for ESXi users.

 

To get rid of the unclean shutdown warning just add a serial port to the vm with following settings:

- use named pipe

- Pipe name: \\.\pipe\com_1

- Near end: server

- Far end: a virtual machine

 

As a result the unclean shutdown warning will not appear in the logs anymore.

 

 

As others mentioned in this thread, this is much easier:

 

"(...) changed the console output on the following service only ... /usr/share/init/syno_poweroff_task.conf:console output ... from "console output" to "console none". After reboot the error of "improper shutdown" is gone."

 

Unless you were talking about something else.

[DSM 6.1.x Loader]

Thanks for your reply.

 

I get the backup wizard. I log in, and then get to a page (synoauth.synology.com) that says:

 

Redirect your personal information back to http://192.168.14.10:5000, please make sure http://192.168.14.10:5000 is your DS domain.

 

After I confirm and click 'Next', it's just an empty page.

 

 

P.S. If Hyper Backup requires the use of Synology services (does it?) then never mind: like others, I don't mind using Xpenology, but don't feel like defrauding Synology by using fake serials, etc. Otherwise I'd still like to know.

 

Even on the real Synology box, I got the blank page the first time. Close it and try again and everything seems to work.

 

On the Xpenology box, I got the same situation (close the browser and try again and it seems to work).

 

I saw the synoauth.synology.com address also. This is the first time I saw an app bounces traffic around like that.

 

 

Thanks for the reply.

 

Tried that several times, but the page stays blank, unfortunately.

[DSM 6.1.x Loader]

Thanks for your reply.

 

I get the backup wizard. I log in, and then get to a page (synoauth.synology.com) that says:

 

Redirect your personal information back to http://192.168.14.10:5000, please make sure http://192.168.14.10:5000 is your DS domain.

 

After I confirm and click 'Next', it's just an empty page.

 

 

P.S. If Hyper Backup requires the use of Synology services (does it?) then never mind: like others, I don't mind using Xpenology, but don't feel like defrauding Synology by using fake serials, etc. Otherwise I'd still like to know.

[DSM 6.1.x Loader]

Is anyone using the latest DSM Hyper Backup with Amazon Drive?! All I'm getting is a blank screen when I initiate the Hyper Backup and connect to the cloud.

 

Anyone have an answer to this, btw?

 

At which step do you have a blank screen?

 

If I click on Hyper Backup, it launches backup Wizard. I then can select S3 then [Next] and a backup destination settings opened up. I don't have the keys needed to go further.

 

Up until that point, it seems to work fine on my end.

 

 

Thanks for your reply.

 

I get the backup wizard. I log in, and then get to a page (synoauth.synology.com) that says:

 

Redirect your personal information back to http://192.168.14.10:5000, please make sure http://192.168.14.10:5000 is your DS domain.

 

After I confirm and click 'Next', it's just an empty page.

[DSM 6.1.x Loader]

Is anyone using the latest DSM Hyper Backup with Amazon Drive?! All I'm getting is a blank screen when I initiate the Hyper Backup and connect to the cloud.

 

Anyone have an answer to this, btw?

[DSM 6.1.x Loader]

Is anyone using the latest DSM Hyper Backup with Amazon Drive?! All I'm getting is a blank screen when I initiate the Hyper Backup and connect to the cloud.

[DSM 6.1.x Loader]

For those of you still using ESXi 6 u2 (so many bare metal users of late), I was able to upgrade flawlessly (from oktisme's image), all the way to DSM 6.0.2-8451 Update 2, without any problem. The install consisted of a (very rapid) migration of my old disks, and editing /usr/share/init/syno_poweroff_task.conf, to avoid the 'improper shutdown' issue.

 

Everything seems to work. Hard disk temperature status can be read properly, and all S.M.A.R.T. info. And it boots up real fast! Perfect version! And many thanks to the OP for making this!

 

How do you get S.M.A.R.T. working in Esxi6 u2

It show not available in my dsm

 

 

Nothing special, reallly. I'm using my old ICH10 controller, in pass-thru; and whereas the S.M.A.R.T info didn't work for in in oktisme's patch, with this one it simply does:

 

https://1drv.ms/i/s!AhSxhQ9g_mrMhzVrZl2lD3LfIXFr

[DSM 6.1.x Loader]

For those of you still using ESXi 6 u2 (so many bare metal users of late), I was able to upgrade flawlessly (from oktisme's image), all the way to DSM 6.0.2-8451 Update 2, without any problem. The install consisted of a (very rapid) migration of my old disks, and editing /usr/share/init/syno_poweroff_task.conf, to avoid the 'improper shutdown' issue.

 

Everything seems to work. Hard disk temperature status can be read properly, and all S.M.A.R.T. info. And it boots up real fast! Perfect version! And many thanks to the OP for making this!

[DSM 6.1.x Loader]

Very good. all working. DSM 6.0.2 8451 Update 1. DO NOT UPDATE TO UPDATE2. after reboot it stuck to grub saying "invalid magic number". you had to reflash the usb key, but after a reboot same thing again.

 

Just to be sure, this has no relevance on ESXi, right?

[DSM 6.1.x Loader]

I currently have oktisme's DSM 6 running (with RAID5, Btrfs). I wonder, will it be possible to create a new VM, using the OP's boot-loader trick, and use my existing disks? (sans losing the data, of course). I suspect the OP'a image won't finish the install (as Synology is effectively already on the disks). But will I be able to just use the Upgrade button then?

 

Thanks.

[DSM 6.1.x Loader]

Thanks for feedback jun. I changed the console output on the following service only ... /usr/share/init/syno_poweroff_task.conf:console output ... from "console output" to "console none". After reboot the error of "improper shutdown" is gone.

 

^^ Brilliant work! Thank you!

[DSM 6.1.x Loader]

Not too worried, maybe, but I presume an unclean shutdown will result in DSM starting a 'parity check' each time, which may take 2 days or so, putting a lot of extra stress on your array for the duration! (Even when it's just 'read', like maybe half the stress of a full rebuild?)

 

So, while I applaud the OP's brilliant (and most hopeful, so far) initiative, if at all possible, I'd like the 'unclean shutdown' thing resolved too, please.

Not that I've seen..

Disks and CPU are zero % after booting up - every time - after seeing this message about the improper shutdown. I don't think it's doing a parity check - or anything, really.

 

My box was powered down using either the power option on the console, the shutdown or poweroff commands (at a SSH terminal), so it was 'going down properly'.. It didn't suddenly switch itself off and reboot..

Personally, I think it's a bug (and there have been previous notifications on 'actual' synology devices about this bug) but it would be nice to resolve it..

 

#H

 

 

Thanks for the feedback. Normally your Storage docklet will say something like 'Volume 1 (normal)'. Or, in this case, 'Volume 1 (parity check)' on an unclean shutdown. If it ain't saying the latter, then I guess it's all good.

[DSM 6.1.x Loader]

I've tried both UEFI and legacy UEFI/BIOS and both are working fine.

 

I have one problem tough... Every time I shutdown my machine, I got an "improper shutdown" notification on the next boot.

 

Anyone else experiencing this?

 

Cheers

 

Me too

 

And me..

Not too worried about it though.. I would say this is a nice to have (unless there really is a problem that puts the data at risk)..

 

 

Not too worried, maybe, but I presume an unclean shutdown will result in DSM starting a 'parity check' each time, which may take 2 days or so, putting a lot of extra stress on your array for the duration! (Even when it's just 'read', like maybe half the stress of a full rebuild?)

 

So, while I applaud the OP's brilliant (and most hopeful, so far) initiative, if at all possible, I'd like the 'unclean shutdown' thing resolved too, please.

[Working DSM 6]

I would love to have something faster but don't like the options Synology has as far as processors go. I gave it 4 cores in the VM but it only sees 2. It doesn't throttle CPU much but it will use as much RAM as you give it, as evidenced in the VMWare statistics. It's a pig...

 

The Info Center data for your CPU is either simply hard-coded (to conform to the model used), or otherwise bogus. For instance, the Info Center tells me I have an INTEL Core i3-4130, with 2 cores, whereas 'more /proc/cpuinfo' correctly shows an i7 980X, with CPU 0 and CPU 1, each with 2 cores (exactly as I specified in the VM).

[XPEnology Developers contact me for 7393 kernel src code]

@oktisme sovled the problem through userland, and I want to try a different approch.

I recently wrote a linux kernel module to dynamically patch the dsm kernel.

With this hack, we only need to repack rd.gz to load this special module at early stage,

zImage & pat is used as is, so changes are kept minimal.

 

Now it works on latest version DSM 6.0.2-8451, sort of.

 

 

^^ If this works, you'll become my new hero!

[Working DSM 6]

I don't recall ever registering my Synology device, though I may have. It has always pulled updates. I used the VMDK provided by the OP and it already had the Serial in it.

 

I never registered anything either. So, what benefits are there to registering a seial number/mac address? Will it get rid of the error 21 whilst trying to upgrade?

[Working DSM 6]

"Everything worked well for several days" is just anecdotal (just as saying it's unstable, based solely on that, btw). My DSM 6.0.1-7393 has been running for over 2 months now, and never had any issue with it...

What??? Really???

Five weeks ago, at page 35, you said you were dying to get a stable version.

Well, is it?! Am dying to get a stable version of this on ESXi 6, with Btrfs. Wish someone would give me a straight ansswer on this.

and at page 42, 3 weeks ago, you said you finally got it installed

Finally got around to installing DSM 6.0.1-7393 on ESXi 6.0 (via the posted DSM6_esxi_hw10.ova here). Works like a charm. It won't let me upgrade to 6.0.2-8451, though. Is there a way around that?

Thanks.

So, where did you pull your "DSM 6.0.1-7393 has been running for over 2 months now" out huh?

Liar!!!

 

 

My, dude, you're stretching. Did I step on some sore toes per chance?! LOL.

 

DSM 6 simply runs stable for me, in that it doesn't crash. Period. Obviously many fixes have been made, later on, to improve Btrfs (less CPU usage), and fixes for the new Hyper Backup (which I haven't used yet) for instance. But, otherwise, it really runs like a charm! Can't tell you exactly how long it's been running now, as I had some (unrelated) Blue Screens in ESXi, requiring an intermediate reset or two, but it's been running DSM 6.0.1-7393 stable thru-out the entire time, which was my point.

[Working DSM 6]

 

What do you like in btrfs ? I'm just using basic functions of backup that why maybe I haven't yet found any advantage to use btrfs for now..

 

Btrfs, unlike any regular raid (like found on DSM up to 5), protects you from bad sectors too. A regular raid setup will just blindly copy bad sectors across the array. Btrfs, otoh, will detect these (thru a form of shadow-copying, but then far more advanced), and will thus keep your data integrity up, even over time. And I really want that, as the alternative is like FreeNAS, with ZFS. And the latter requires me to buy an entirely new machine, with ECC memory (and a lot of it too), new CPU, etc. So, DSM 6 is essentially a dream come thru for me. So, I want to stick with it.

[Working DSM 6]

But so far so good for me. And I, for one, will not downgrade to 5.2, ever, because I'd be missing out on Btrfs again.

 

So, here's to hoping Synology will release the latest source code soon!

 

And you could format the partition in Btrfs on bare metal servers?

 

Reading several times this thread, I've tried both their servers format the partition in the RAID5-Btrfs, but it did not work, only to ext4.

 

Not bare-metal, no, but via ESXi 6.0 u2. Sorry if I gave the impression I was running on bare-metal too.

 

My disk controller is set 'pass-thru', though (cheap, but reliable, ASM 1026 chipset), so DMS 6 accesses it directly. I can't fathom why it shouldn't work for you if you stuck in a similar ASM 1026 controller (ca. $30).

 

But yes, without Btrfs DSM 6 offers nothing spectacularly new to me, either.

[Working DSM 6]

Downgrade to 5.2.

 

Why?

If the installing DSM6 and create a partition occurs normally, and everything worked well for several days.

Easy, because DSM6 currently NOT stable. "everything worked well for several days" doesn't mean it's completely stable.

 

"Everything worked well for several days" is just anecdotal (just as saying it's unstable, based solely on that, btw). My DSM 6.0.1-7393 has been running for over 2 months now, and never had any issue with it. Yes, that is also anecdotal. Point being: it's probably not as unstable as you make it sound. There have been several Updates since, so, obviously, they fixed several things. But so far so good for me. And I, for one, will not downgrade to 5.2, ever, because I'd be missing out on Btrfs again.

 

So, here's to hoping Synology will release the latest source code soon!

[XPEnology Developers contact me for 7393 kernel src code]

I have no problem giving t

It to anyone. It is open source.

 

This is interesting. As you have the DSM 6.0.1-7393 source, apparently, perhaps it could be used to make an official XPenology release (along with boot menu), which can be upgraded too, without error 21.