Leaderboard

Popular Content

Showing content with the highest reputation on 10/16/2020 in all areas

  1. NOTE: This problem is consistently manifested when running as a virtual machine, but many have encountered problems with Synoboot devices on baremetal installs of 6.2.3 and under certain conditions, other 6.2.x versions. The fix can be implemented safely on baremetal installs. You can verify if you have the issue by launching SSH and issuing the following command: $ ls /dev/synoboot* /dev/synoboot /dev/synoboot1 /dev/synoboot2 If these files are not present, your Synoboot devices are not being configured correctly, and you should install the fix script. If synoboot3 exists that is ok
    1 point
  2. Simple and dirty fix based on written above. Modified /etc.defaults/syslog-ng/patterndb.d/scemd.conf: filter f_scemd { program(scemd); }; filter f_scemd_sev { level(err..emerg) }; # destination d_scemd { file("/var/log/scemd.log"); }; destination d_scemd { file("/dev/null"); }; log { source(src); filter(f_scemd); filter(f_scemd_sev); destination(d_scemd); }; Edit file and reboot. Result - HDD hybernation works fine now... My config: DS3617xs, DSM 6.2.3-25426-U2, extra.lzma v0.11.2_test.
    1 point
  3. you will be able to change the board as long as a storage and network driver for the new board is present in the loader, in most cases the storage is sata/ahci and the loader does support a good variety of network drivers already, the disks position are not important as dsm will look for this by itself (disks now days can be identified by uuid) the only things might be 4th gen intel cpu minimum for 918+ 1.04b loader and csm/legacy in bios for 1.03b loader (3615/17) the only one thing you need to look after is the usb boot devices vid/pid, new usb with old image or old usb with defaul
    1 point
  4. DSM usually modifies the boot loader during upgrades. The recent 6.2.3 error 21 issue requiring SynoBootFix is because the loader was not accessible for upgrade due to incorrect initialization of the synoboot devices. But if an old loader encounters a newer DSM version, it will just be upgraded in place with no notification. So you can replace a loader stick with a fresh burn and a working system should just boot.
    1 point
  5. For those Linux newbs who need exact instructions on installing the script, follow this here. Please be VERY careful with syntax especially when working as root. If you have not turned on ssh in Control Panel remote access, do it Download putty or other ssh terminal emulator for ssh access Connect to your nas with putty and use your admin credentials. It will give you a command line "$" which means non-privileged In File Station, upload FixSynoboot.sh to a shared folder. If the folder name is "folder" and it's on Volume 1
    1 point