imaleecher
-
Posts
31 -
Joined
-
Last visited
-
Days Won
1
Posts posted by imaleecher
-
-
If you've been using xpenology since the older bootloader, there's a high chance that you have the xpenology folder hidden that's causing the issue.
I had very similar issues and was able to resolve it by removing the folder. I was unable to see it at first because the folder is normally hidden. See link below for command
-
I was finally able to get v1.03b to work successfully after a lot of runarounds with ESXI 6.7.
No Diskstation found within LAN:
I've created a new VM and set my modified synoboot (updated VID/PID/SN/MAC) as an SATA HDD. Booted the 3rd option (Vmware/ESXI) and it detected on the network. Once it was detected, I could then migrate to 6.2.
After migration was completed, all of my packages would close within minutes of the system booting up. To resolve this, I had to delete the hidden .xpenoboot that was located at root. Open SSH and use Putty to remove the .xpenoboot folder.
Quoterm -rf .xpenoboot
Rebooted the system and all the packages would now stay up and running.
Hope this helps other users!
- 2
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.1.4 15217 Update 2
- Loader version and model: Jun's Loader v1.02b - DS3615xs
- Installation type: ESXi 6.5.0
- Additional comments: Requires reboot. Synology Drive (beta) and Synology Moments (beta) icons went missing.
Edit: Update: Synology Drive and Synology Moments icons reappeared on their own.
-
Updated via web browser successfully.
Jun 1.02b
ESXi 6.5
DS3615xs 6.1.4-15217 Update 1 -> Update 2
No reboot required
-
I've updated from 6.1.3-U8 to 6.1.4-15217 (md5 23acaefffb0d01aa9f57870fcfcfb887) and noticed it actually installed 6.1.4-15217 Update 1. This might explain the differences Balrog pointed out above. New release with Update 1 preapplied.
ESXi 6.5
Jun Loader v1.02b
-
On 7/29/2017 at 9:28 AM, DragsterPS said:
Yes, i can do it, but the problem is that my case is very dificult to close and it is already placed in a small location.
Opening the "difficult" case and physically disabling the LED is easier/quicker than finding an even more difficult software solution.
-
Your motherboard doesn't support USB boot; it's too old.
Are you sure? This is what I read from Intel Desktop Board DP965LT Technical Product Specification, page 74:
3.8 Boot Options
In the BIOS Setup program, the user can choose to boot from a diskette drive, hard drives, a USB drive, CD-ROM, or the network. The default setting is for the diskette drive to be the first boot device, the hard drive second, and the ATAPI CD-ROM third. If enabled, the last default boot device is the network.
My mistake. Have you tried checking if Legacy USB is enabled?
-
Your motherboard doesn't support USB boot; it's too old.
-
Thanks! Will try this out later this evening.
*Update - works on my baremetal 6.0.1-11. Thanks wer!
-
No not that I'm aware of. My first install was a migration from 5.2 to with shr and the shr was recognised in DSM 6 no problem. After that I did a fresh install on the same box and by default shr isn't an option under DSM 6. You can edit the config file to re-enable shr which works perfectly. I have drives using shr with btrfs on the new DSM 6 build. I can't say for sure about shr 2 as I have no first hand knowledge, but my guess would be that it should be fine. I'm not sure if a migrated system would allow a new disk group/volume to use shr by default, but editing the config file should soon fix that problem.
That sounds good to hear. Thank you for the information. I'll need to do some testing myself as YMMV of course. How would one edit the config file for SHR? You said soon so I'm guessing it's not possible as of now?
-
Are there any issues with migrating from DSM 5.2 SHR/SHR-2 RAID to DSM 6.0?
-
Just updated to 5.0.22-108108-2 and phpVirtualBox seems to be back up and running
-
press tab to edit options
automatic boot in 0 seconds...
Loading ../zimage... ok
Loading../rd.gz... ok
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Bootng the kernel.
_
this is what I get
look like crash in 0 seconds
Proceed forward to http://find.synology.com on another system and it should find a new NAS on your network.
Had to mess around with the boot and select "Install" vs "Run" a few times to get it to finally accept DSM 6.0.1 install. I was able to get it to boot but could not create a volume. Will try again when I have more time. Thanks okitsme for your contribute.
-
How about Foscam FI9803EP @ $89.99
-
Just uninstall and re-install it, i found opt/ folder was deleted after the upgrade
Thank you a.ahmed, that worked. Time to import back my VMs.
-
Another thing to note, can anyone select Control Panel > Hardware & Power > Enable UPS support
-
Is anyone else having issues logging into phpVirtualBox after the update? I can get to web browser login page but cannot log in. I'm getting the following issue:
Exception Object ( [message:protected] => Could not connect to host (http://127.0.0.1:18083) [string:Exception:private] => [code:protected] => 64 [file:protected] => /volume1/web/phpvirtualbox/endpoints/api.php [line:protected] => 134 [trace:Exception:private] => Array ( ) [previous:Exception:private] => )
I'm currently running:
DSM 5.2-5967
XPEnoboot 5.2-5644.5
phpVirtualBox 5.0.16-105871-3
-
Just updated to 5.2-5967 successfully via web console. Rebooted and haven't seen any issues.
-
-
You have the right XPEnoboot. Just upgrade one at a time until you reach the latest version.
DSM_5.2-5644 <-- you are here
DSM_5.2-5644 Update-1
DSM_5.2-5644 Update-2
DSM_5.2-5644 Update-3
DSM_5.2-5644 Update-5
DSM_5.2.5644 Update-8 (unofficially blessed at the moment but many reported it working)
-
Link was working fine yesterday. Perhaps the link had expired now that April Fool's Day is over.
-
6.0-7307.1 (01/04/2016)
Fix BIOS reset bug
Fix NFS bug
Fix VPN issues
Add Synology 6.0 compatible
New x86 and ARM XPEnoboot
-
Try 20Gb. If you are short of real disk space and you keep the option not to allocate the disk space "now" then it will only allocate enough for the install.
I tend to create the disk as a single file - but I have no idea whether that makes any difference.
Even if you changed the disk type to dynamic (vs fixed), during the initial setup/installation, it'll format the drives and expand to the max size allotted so you won't save any hdd storage.
-
"DS3615xs delivers up to 2,214.77 MB/s throughput in reading and 231,295 read IOPS."
Per Synology's footnote:
"Tested with dual 10GbE connection with Link Aggregation. The performance figures vary on different environments."
Might need some $$$ hardware to test that out.
Photo station and Moments (DSM 6.2)
in Synology Packages
Posted
Yes! Thank you @Kollcn and @mcdull. Subjects are now popping up after updating Cores per Socket in ESXi VM settings.