FiberInternetUser

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.

To Hostilian: What I did to disable the tty service was to rename the tty.conf file in /etc/init .. the command I used was "mv /etc/init/tty.conf /etc/init/tty.conf.not .. then do a restart and check again with dmesg | grep tty. Thanks for info about .NormalShutdown file. YMMV

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 After testing the dual UEFI/Legacy build (bare metal) on motherboards with/without a physical serial port, I don't see the errors with motherboards that have a physical serial port. No errors are displayed or logged after a reboot or a shutdown/restart. I do see the errors with motherboards that don't have a physical serial port. After doing some research on some of the Synology NAS models, it appears some models do have a physical serial port. This is not exposed to the user. I have read articles where some owners have opened their Synology NAS's to physically connect up the serial comm port. The main reason for doing this was to recover from a "Bricked Unit". On reboot or shutdown/restart the following is logged in the "messages" logs for motherboards without a physical serial port. 2016-10-02T19:34:23-04:00 Test-NAS60 synoscgi_SYNO.Core.System_1_shutdown[12971]: system_sys_init.c:90 synopoweroff: System is going to poweroff 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.740657] init: synonetd main process (4969) killed by TERM signal 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.741148] init: synostoraged main process (9548) terminated with status 15 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.742680] init: hotplugd main process (11016) killed by TERM signal 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.743111] init: smbd main process (11382) killed by TERM signal 2016-10-02T19:34:23-04:00 Test-NAS60 [ 320.835177] init: syno_poweroff_task main process (13011) terminated with status 1 Logs from motherboard with physical serial port 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.178048] init: synonetd main process (5536) killed by TERM signal 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.178468] init: synostoraged main process (10964) terminated with status 15 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.179553] init: hotplugd main process (12425) killed by TERM signal 2016-09-27T20:18:29-05:00 Test-NAS48 [ 1373.184887] init: smbd main process (12631) killed by TERM signal 2016-09-27T20:18:29-05:00 Test-NAS48 syno_poweroff_task: System is acting poweroff. Also, as stated in the post from jun on Page 1, if your motherboard does not have a physical serial port the logs will fill up with the following, if you don't stop/disable the tty service: 2016-10-02T19:33:46-04:00 Test-NAS60 [ 283.376096] init: tty main process ended, respawning 2016-10-02T19:33:56-04:00 Test-NAS60 [ 293.377424] init: tty main process (12828) terminated with status 1 2016-10-02T19:33:56-04:00 Test-NAS60 [ 293.377449] init: tty main process ended, respawning 2016-10-02T19:34:06-04:00 Test-NAS60 [ 303.378699] init: tty main process (12846) terminated with status 1 To see if you are getting the tty errors, you can check your logs. SSH in, use the following command "dmesg | grep tty" Hope this information is helpful.

Sorry about that, working with too many images .. it should be grub.cfg in the grub directory .. on the dual boot image (EFI/Legacy) by setsunakawa. I am working on a Legacy image too and that one has the isolinux.cfg file. Thanks for catching my error, I went back and corrected my post.

I made a couple bootable thumb drives and on one of them I do believe I did add the rmmod=ata_piix command. The generated MAC does not need to match the actual MAC address. Once you get your XPEnology Box running, using a separate Windows Machine, go to a command prompt and enter the following. arp -a and hit return .. this command will show you the MAC address you setup in the grub.cfg file. Good Luck

Yes, I changed the VID, PID, Serial #, and Mac Address. In testing, I did setup one drive as BRFTS and later when I did a reboot the volume did not unmount. I installed Video Station and Photo Station. There were no errors when installing and after a reboot. Quick Connect does pop up the dialog box to let you login. I don't have an account so I didn't try to login. More testing to do. So far, so good. Also, I installed -8451 update 1 without errors. Thanks to setsunakawa for the Legacy Boot Loader.

To get past the drive errors using the EFI/Legacy image posted a few pages back when using a motherboard with a Legacy BIOS ... I added SataPortMap= the number of drives in my system to the correction grub.cfg not isolinux.cfg file as I first wrote. I have 4 drives installed so the line I added to APPEND was SataPortMap=4. When booting using a Legacy BIOS, it recognizes my 4 drives without any errors. Hope this helps. Also, after recognizing my 4 drives and trying to install DSM 6, I was in a continual install loop. To correct this, I replaced the image/DS3615xs/ramdisk.lzma in the boot partiton as show in Post 1 by jun. Hope this info helps. DSM6 working on a Gigabyte GA-H67N-USB3-B3 motherboard, RAID 5 (with data protection) ext4.